openoffice VS mpv

Try LibreOffice or OpenOffice .

> It looks like most of the recent commits are done by someone as mostly a way of learning and not for the sake of the project itself.

> https://github.com/apache/openoffice/commit/d2a7b3cc90e95392...

From that link:

> Most of the commits here seams to be mainly white space changes to random files.

I'm guessing is not "learning" but more of an attempt to game GitHub (e.g. rack up a lot of commits to an impressive-sounding project).

This is Open Office.

OpenOffice is still around. I've had better luck with OpenOffice than with LibreOffice.

OpenOffice is a bit outdated and it's updates don't really update anything if you check the git commits. There is however FreeOffice and OpenOffice, both really good options that look almost the same as MS Office

A different open would be to get open office (https://www.openoffice.org/) use the application called Impress (this is a free PowerPoint alternative).

OpenOffice is a good program. If you've had experience with MS Word, it's relatively the same. It's pretty easy to use too; just choose Writer and start typing. lol

Open office - open source word processor . https://www.openoffice.org/

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.