3 ms·
Excellent to see, the ESC ambiguity problem is one that has especially bugged me. I hope there's a plan to standardize this with the relevant organizations! I
by Conlectus 5y ago
Excellent to see, the ESC ambiguity problem is one that has especially bugged me.
I hope there's a plan to standardize this with the relevant organizations! I worry that's the only way to see widespread adoption.
- nine_k 5y agoYes, I can imagine a mostly-backwards-compatible, but much improved, standard; let's call it VT-2021.
- drran 5y agoIf you are native English speaker, then start with kind of "caniuse" site, but for terminals and VT, please. It will help a lot if we will be just aware of available features in existing terminals and their compatibility with standards.
- nine_k 5y agoNot a web site, but terninfo and termcap databases, normally present on a Unix system, have this information. I would hazard to say that some basic subset of VT100 commands is "universally" supported, even on Windows if one uses Windows Terminal. Various obscure high-end features from 1980s, like programmable font bitmaps, or sixel support, much less so. Also, modern terminals support Unicode, including emoji (as double-width symbols), which was unimaginable in 1980s or 1990s.
- DHowett 5y ago> if one uses Windows Terminal. This is also true of the Windows Console as of Windows 10. Any VT100 (also VT220, VT4xx, VT5xx, xterm ...) support we add to Terminal eventually flows out to the console host integrated into Windows. :)
- drran 5y agoHow to display terminfo in a consumable way? What about non-standard features, like drawing, sixels, sound, mouse, touches, clipboard, fonts, true color, transparent background, color emoji, double size text, etc.?
- saurik 5y agoAnd yet, I feel like that database doesn't succeed in replacing a website that tells me "the following terminals support OSC 8 and with what awkward limitations", which is knowledge I find both useful and important for web browsers despite being able to do runtime tests to determine the support of most features. "Oh, it turns out 78% of my users wouldn't be able to parse OSC 8 even if I went to the trouble of using it... maybe I'll work on a different feature today".