3 ms·
xterm supports sixel, so surely anything that sets TERM=xterm256-color or similar will be compatible… right? ∗cough∗ gnome-terminal ∗cough∗
by kps 2y ago
xterm supports sixel, so surely anything that sets TERM=xterm256-color or similar will be compatible… right? ∗cough∗ gnome-terminal ∗cough∗
- spudlyo 2y agoxterm supports sixel, so surely if your TERM is xterm-kitty, it's supported right?
- kps 2y agoI would say so, yes (not a fan of kitty's general NIH), but it could be argued that `xterm-kitty` is at least not identical to a $TERM used for xterm.
- spudlyo 2y agoIndeed. I was trying to humorously reference the author's staunch refusal to remove `xterm` from the TERM identifier, knowing full well that many programs simply look for `^xterm` when determining if the terminal is compatible. As you eluded to with 'NIH', the same author refused to implement Sixel in Kitty because it is "inferior" to Kitty's image implementation.
- SushiHippie 2y agoWhat does "NIH" mean in this context?
- throwaway290 2y agoKitty developer decided to go with a custom image display protocol instead of going with sixel.
- sn0wf1re 2y agoNot Invented Here
- 20after4 2y agohttps://en.wikipedia.org/wiki/Not_invented_here https://en.wikipedia.org/wiki/Not_invented_here - When someone or some group prefers to re-invent something rather than using an existing, perfectly serviceable solution.
- alexvitkov 2y agoWhy do we now have User-Agent in the terminal ;-;
- boomboomsubban 2y agoIsn't the TERM variable ancient? I know one of the "common" exported variables is the VT100, sold in 1978.
- hollerith 2y agoYes, it is very old.