PhotoGIMP VS mpv

I used to use PhotoShop heavily and still have a lot of the UI muscle-memorized. I switched to GIMP + https://github.com/Diolinux/PhotoGIMP and found it mostly fits my needs for basic image editing.

There's also photoGimp:

https://github.com/Diolinux/PhotoGIMP

But it's interesting if we can get FOSS Gui toolkits that allow for different approaches to menu/toolbar/discovery where the user can easily adjust and select how things should work - like readline Emacs/vi selection on steroids for Gui.

There is this project that might help you:

https://github.com/Diolinux/PhotoGIMP

I doubt it, code needs to be maintained , even if you will get stuck on old libraries you could miss out on features and improvement, of course if the changes are small and it's more like a patchset (something like photogimp) , that might be more feasible.

I don't like gimp at all, but you can still try PhotoGimp.

did you try PhotoGIMP?

See https://github.com/Diolinux/PhotoGIMP/graphs/code-frequency

https://mpv.io/ has yt-dlp support, if yt-dlp is installed you just need to throw the URL at it and it plays the video (without download).

See https://github.com/mpv-player/mpv/issues/9053

I apologise for not following procedure. I am in the middle of building mpv 0.37 from source. Irrespective of the outcome I will document what I had to do in addition to the instructions on mpv.io and if the problem perststs, where it happens and where not with kernel version, mpv version taken from the screen, and the terminal output.

Use MPV. Partticularily shinchiro's builds. Extract the folder where you want its installation directory to be, if you decide to install it. Otherwise, just drag and drop files on top of its window or executable.

Author of ripgrep here.

Like automatic encoding detection and transparently searching UTF-16?

Or simple ways for composing character classes, e.g., `[\pL&&\p{Greek}]` for all codepoints in the Greek script that are letters. Another favorite of mine is `\P{ascii}`, which will search for any codepoint that isn't in the ASCII subset.

Or more sophisticated filtering features that let you automatically respect things like gitignore rules.

Those are all things that ripgrep does that grep does not. So I do not favor this explanation personally.

ripgrep has just about all of the functionality that GNU grep does. I would say the two biggest missing pieces at this point are:

* POSIX locale support. (But this might be a feature[1].)

* Support for "basic" regexes or some equivalent that flips the escaping rules around. i.e., You need to write `\+` to match 1 or more things, where as `+` will just match `+ literally.

Otherwise, ripgrep has unfortunately grown just about as many flags as GNU grep.

[1]: https://github.com/mpv-player/mpv/commit/1e70e82baa9193f6f02...

- https://github.com/mpv-player/mpv/issues/8692

https://mpv.io played it without fuss.