3 ms·
One of my favorite features of Kitty is its support for printing images in the terminal through its graphics protocol, meant to be a replacement for libsixel. T
by j-james 6y ago
One of my favorite features of Kitty is its support for printing images in the terminal through its graphics protocol, meant to be a replacement for libsixel. The spec's worth a read - there's few projects linked there that implement it.
https://sw.kovidgoyal.net/kitty/graphics-protocol.html https://sw.kovidgoyal.net/kitty/graphics-protocol.html
- JdeBP 6y agoOther seemingly more minor (but which will possibly be more widely used eventually) features are different forms of underline, selectable through sub-parameters to SGR 4. I've already put this into my terminal emulator, although that version is not released yet; it exists in LibVTE and several other terminal emulators; and the Windows Terminal people also have a backlog item for it. * https://github.com/microsoft/terminal/issues/7228 https://github.com/microsoft/terminal/issues/7228
- MayeulC 6y agoI quite like that as well, it works very well in ranger. However, I was in awe at libsixel's support of animated pictures. I'm not sure how that's done, probably just re-drawing still images? That got me thinking: as kitty supports displaying images from shared memory, couldn't it just expose a buffer for the app to draw inside? Going further, it would be an interesting experiment to make the terminal a fully working "wayland compositor", maybe with some extensions to control buffer placement with escape codes. What would it bring? It seems that the most stable API for application development has been the command line interface. Going further, I'd be interested in running a terminal emulator such as kitty as the sole application on a TTY, like a fbcon replacement.