4 ms·
> A tty doesn't know about the concept of key press or key release events. It only knows about 'data stream in' and 'data stream out'. This is basically the l
by pjc50 6y ago
> A tty doesn't know about the concept of key press or key release events. It only knows about 'data stream in' and 'data stream out'.
This is basically the long and the short of it; it's a very old API, and retrofitting key-up detection reliably is a serious problem.
- CoastalCoder 6y agoPerhaps this is nitpicking, but I don't think the issue here is "data stream" vs. not-"data stream". Perhaps a better distinction is "data stream of characters" vs. "data stream that can express key events (and perhaps other stuff as well)".
- swiley 6y agoThis is correct, plan9 continues using a data stream but puts events in the data stream rather than characters. Even on Linux the low level kernel API for getting keypress events works this way.
- icedchai 6y agoIt's really a lower level protocol issue. The serial terminals upon which the "tty" model is based had no event stream outside of characters being sent or received. There are events provided by the serial port itself and delivered out-of-band though (example: modem DCD line drops, SIGHUP is generated.)
- drran 6y agoTo fix this low level problem, someone will need to modify xterm, or libvte, or any other terminal, to send escape sequences for key release events, when such mode is requested by an application.
- patrec 6y agoAlready done. Kitty and other modern terminals have an extended keyboard interface which allows to detect keypress, keyrelase and arbitrary key combinations (unlike legacy vt100-style terminal emulators, where e.g. Tab and Ctrl-I are indistinguishable). For backwards compatibility you need to switch to this mode by sending an escape sequence. https://sw.kovidgoyal.net/kitty/keyboard-protocol.html https://sw.kovidgoyal.net/kitty/keyboard-protocol.html
- eikenberry 6y ago> and other modern terminals Do you know of any source documenting which terminal emulators support this feature other than kitty?
- patrec 6y agoHave a look here: https://gitlab.freedesktop.org/terminal-wg/specifications/-/issues/1 https://gitlab.freedesktop.org/terminal-wg/specifications/-/... Basically Kovid Goyal, the author of kitty, volunteered to write a spec, based on the work he did for kitty, but got fed up with what he perceived as pointless bikeshedding. The authors of other terminals represented in the terminal-wg (e.g. iterm2, mintty and vte -- which powers terminator, gnome-terminal and others) kept going for a bit, but there is no shared spec yet and I haven't checked if anyone else other than Goyal has implemented something at this point (I thought vte had, but I didn't immediately find it when I looked). It also looks like it might take some time till some de-facto standard emerges.