And low bandwidth is useful when doing SSH: I posted this quick example of what I use everyday as a reply "ROSshow: ASCII art visualizations for robot sensor data" (https://news.ycombinator.com/item?id=19519165) by ssh'ing to my remote host (which does not have a GPU) from my laptop (which doesn't have a GPU either).
I wanted to share something that you can use right now, and that works reliably even in non optimal conditions.
Notice how my loadavg is above 10, and how I'm using a mlterm binary downloaded straight from mlterm.sf.net/bin.html
The same will work with a vanilla msys2 installation, or with the in-kernel console of "old powerless machines" as noted on https://saitoha.github.io/libsixel/#sayaka-chan
I ran into this issue while writing a shell. All shells use wcwidth() to determine the width of a unicode character. I think all terminals need that information too, and they would also need the analogous information for unknown escapes.
If the concern is the speed of the scrollback on device rendering the content, wouldn't adding GPU support to say mlterm be enough?
Anyway, if someone has a desperate need of graphical output inside a terminal, this is an actual solution working with little risks and default tools: I only recompiled gnuplot with the proper compile-time flag, exported the GNUTERM variable, and voila!!
Yes, but still a throwback to 3 decades past+
Sixel has lots of overhead compared to ascii/Unicode braille art. Using sixel to transmit decent images over ssh is very data-demanding
I'm working on embedded software for some industrial equipment the runs over a serial port, and I'm running into all kinds of annoying problems.
I use Linux, customer uses Windows.
In Linux (Ubuntu 16), I found that large paste to Xterm does not work (I know for sure that this used to work in the past). It seems to discard data when Xon/Xoff flow control kicks in, or when a buffer is too large. I've tried minicom, PL2303, FTDI, picocom, my own serial program, XTerm and Gnome terminal. I'm pretty sure the problem is X or Unity (a C program that transfers data out the serial port works just fine). On the other hand, Xterm supports Sixel, so the embedded software can display graphs.
[Followup: I just traced this problem to "picocom", but it has been fixed in a newer version].
The idea is that I should be able to select calibration data from a spreadsheet and paste it into the terminal emulator connected to my device.
In Windows, embarrassingly, large paste works just fine, for example from TeraTerm. But Putty and TeraTerm do not support Sixel.
I suppose XTerm in Cygwin might work, but it would better to have a native Windows program.
I've not tried Mac, but nobody in the industrial world uses them.
On linux, just adding sixel to gnome-terminal and libvte would go a long way.
FYI, I picked up sixel because it's the closest thing to a standard, and because technically I saw it as good enough for most cases.
> I use Linux
I use Windows :-)
> Do any free native windows terminal emulators support Sixel?
mintty on msys2 and mlterm do. I prefer mintty, it feels faster. I'm eagerly waiting for conpty and hopefully even better consoles in Windows!
However serialized graphics does not seem a project goal of either kitty or alacritty.
This is why right now I'm working on a terminal emulator that implements escape codes that allows a subset of "byte compiled" OpenGL commands to run directly in the terminal window. You now can render a complex 3D scene just by cat'ing a file without any boiler plate code. I think there are many potential use cases for this. It allows for example remote graphics accelerated applications running on another machine via ssh. Once all the textures are uploaded to the GPU RAM the bandwidth required for the display commands is rather low even for interactive games.