lsix
glances
lsix | glances | |
---|---|---|
5 | 101 | |
3,082 | 24,957 | |
- | - | |
4.3 | 9.6 | |
6 months ago | 4 days ago | |
Shell | Python | |
GNU General Public License v3.0 only | GNU Lesser General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lsix
-
Are We Sixel Yet
In XTerm, this (rightly) makes no difference. In Foot and Contour however, you still end up a line resp. a screen below where you started, if now with the correct horizontal position.
So it seems to me like what you want should work by default, except it doesn’t.
It should be possible to instead just treat the whole thing as a graphical overlay (by computing or directly asking for the character cell size, as Kirill Panov rightly admonishes me is possible with XTWINOPS) without touching the cursor; that’s what the “sixel scrolling” setting (DECSDM) is supposed to do. Then you can just manually move the cursor forward however many positions after you’re done drawing.
Except apparently the DEC manual (the VT330/340 one above) and DEC hardware contradict each other as to which setting of DECSDM (set or reset) corresponds to which scrolling state (enabled or disabled), and XTerm has implemented it according to the manual not the VT3xx[1,2,3]—then most other emulators followed suit[4]—then XTerm switched to following the hardware[5,6] (unless you and that’s what I’m seeing on my machine right now. So now you need to check if you’re on XTerm ≥ 369 or not[7]. If I’m reading the Notcurses code right, other terminals have followed suit[8].
Again, ouch.
P.S. It seems DEC had an internal doc for how their terminals should operate (DEC STD 070) [9]. It does not document DECSDM at all.
[1] https://github.com/wez/wezterm/issues/217#issuecomment-86449...
[2] https://github.com/hackerb9/lsix/issues/41
[3] https://github.com/dankamongmen/notcurses/issues/1782
[4] https://github.com/arakiken/mlterm/pull/23
[5] https://invisible-island.net/xterm/xterm.log.html#xterm_369
[6] https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-T...
[7] https://github.com/dankamongmen/notcurses/commit/0918fa251e2... (the correct version cutoff is 369 not 359, the patch contains a now-fixed bug)
[8] https://github.com/dankamongmen/notcurses/blob/master/src/li... (look for mentions of invertsixel)
[9] http://www.bitsavers.org/pdf/dec/standards/EL-SM070-00_DEC_S...
-
Quick roundup of bitmap graphics availability in free/open-source terminal emulators
Sixel - Sixel is a standard from the 1970's/1980's DEC VT series. It has enjoyed a tremendous resurgence in popularity thanks largely to saitoha's libsixel project. Many projects are now using sixel; a few you may have heard of include lsix, chafa, and notcurses.
-
Using ASCII waveforms to test real-time audio code
I would point out that sixels[0] exist. There is a nice library, libsixel[1] for working with it, which includes bindings into many languages. If the author of sixel-tmux[2][3] is to be believed[4], the relative lack of adoption is a result of unwillingness on the part of maintainers of some popular open source terminal libraries to implement sixel support.
I can't comment on that directly, but I will say, it's pretty damn cool to see GnuPlot generating output right into one's terminal. lsix[5] is also pretty handy as well.
But yeah, I agree, I'm not a fan of all the work that has gone into "terminal graphics" that are based on unicode. It's a dead-end, as was clear to DEC even back in '87 (and that's setting aside that the VT220[6] had it's own drawing capabilities, though they were more limited). Maybe sixel isn't the best possible way of handling this, but it does have the benefit of 34 years of backwards-compatibility, and with the right software, you can already use it _now_.
0 - https://en.wikipedia.org/wiki/Sixel
1 - https://saitoha.github.io/libsixel/
2 - https://github.com/csdvrx/sixel-tmux
3 - https://news.ycombinator.com/item?id=28756701
4 - https://github.com/csdvrx/sixel-tmux/blob/main/RANTS.md
5 - https://github.com/hackerb9/lsix
6 - https://en.wikipedia.org/wiki/VT220
- My favorite cli/tui programs:
-
The year of the GNU/Linux gaming rig is nigh!
no, I found it and it's called lsix
glances
-
Homelab Adventures: Crafting a Personal Tech Playground
Glances
-
Easily monitor your Server from anywhere
As is from their github repository.
-
Pyenv – lets you easily switch between multiple versions of Python
If I pin a version of Python, isn't that going to wreck any tooling that depends on it? Unless you're saying have multiple versions of Python installed.
This is practically the only remaining annoyance I have with the Python ecosystem (relative imports aside). I use some tools, like Glances [0] whose formula relies on a much newer version (3.12) than the actual package requires (3.8) [1].
So when there's a Python update, all of those update as well. I thought I'd fixed this with pipx, but in a way that's worse, because the venvs it builds depend on a specific version of Python existing, which doesn't work well with brew always wanting to upgrade it.
I want a stable, system-level Python that I don't touch, don't add packages to, and which only exists as a dependency for anything that needs it. If an update would break a package I have installed (due to Python library deprecation, etc.), it should warn me before updating. Otherwise, I don't care, as long as any symlinks are taken care of.
Separately, I want a stable, user-level Python that I can do whatever I want to. Nothing updates it automatically. I can accomplish this by compiling Python and using `make altinstall`, but if there's a better way, I'd love to hear about it.
[0]: https://github.com/Homebrew/homebrew-core/blob/20e744191e74d...
[1]: https://github.com/nicolargo/glances
- Hard disk LEDs and noisy machines
-
Glances for monitoring OPNsense
Wanting to get Glances installed on OPNsense for its integration into homepage.
- Any metrics dashboard out there for viewing power usage???
-
Are there an alternative to htop that lets me see the total resource usage per app?
I don't try but maybe glance https://github.com/nicolargo/glances
-
Dashboard with all container resource usage?
In the meantime Glances is a pretty good way to keep an eye on CPU and memory usage of all your containers. You can either run it as a lightweight docker image or as a native application on your host.
- [Docker] Surveillance du réseau de conteneurs Docker?
-
[Docker] Docker -Container -Netzwerküberwachung?
Bearbeiten: Dies war, was ich war: [https://github.com/nicolargo/glances weise(https://github.com/nicolargo/glances)
What are some alternatives?
ranger - A VIM-inspired filemanager for the console
bpytop - Linux/OSX/FreeBSD resource monitor
sixel-tmux - sixel-tmux is a fork of tmux, with just one goal: having the most reliable support of graphics
btop - A monitor of resources
kitty - Cross-platform, fast, feature-rich, GPU based terminal
bashtop - Linux/OSX/FreeBSD resource monitor
Weechat - The extensible chat client.
Netdata - The open-source observability platform everyone needs
fzf - :cherry_blossom: A command-line fuzzy finder
bottom - Yet another cross-platform graphical process/system monitor.
Vim - The official Vim repository
homarr - Customizable browser's home page to interact with your homeserver's Docker containers (e.g. Sonarr/Radarr)