bpytop VS mpv

Bpytop is a resource monitoring tool designed for Linux, OSX, and FreeBSD systems. Offers a convenient window on CPU usage, memory consumption, disk and network activity, and running processes. Kindly suggested by PalmPilot_IIIx.

https://github.com/aristocratos/bpytop https://github.com/aristocratos/btop

Bpytop is a powerful and visually appealing resource monitor for the command-line interface. You can find the bpytop project on GitHub. The repository provides detailed information about bpytop, including installation instructions, usage examples, and documentation.

It’s Bpytop

Monitor system resources usage: This can be done by using a tool top, ps, htop or bpytop. These tools let you introspect the processes running on a Linux system and the resources they're consuming.

htop is powerful, but considered old-school, the cool kids use glances, netdata or bpytop now.

Check out btop. It’s a rewrite of bpytop in C++. Both are from the same author. FYI, bpytop is also a rewrite of bashtop in python.

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.