Re:Why Is It So Hard to Detect Keyup Event on Linux?
by kelnos on Monday May 17, 2021 @02:45PM
(#27186706)
Right. And on top of that, one of the useful benefits of a TUI is that you can use them while ssh'd into a remote server. If your fancy TUI is expecting to get raw access to the keyboard, it's not going to work in a ssh session.
Re:Why Is It So Hard to Detect Keyup Event on Linux?
by _jal on Monday May 17, 2021 @02:51PM
(#27186779)
Who says? Actual question.
> TUIs are meant for compatibility
Nonsense. Our machines don't even get GUIs installed.
Re:Why Is It So Hard to Detect Keyup Event on Linux?
by arghwhat on Monday May 17, 2021 @11:47PM
(#27191073)
That's exactly what the compatibility is for. Tools that work in the absence of anything advanced, with nothing but a few escape codes to "draw".
Otherwise it wouldn't work on the kernel console (the only thing available without a GUI installed), over SSH, over serial links, even still on dedicated terminals and teletypes.
Re:Why Is It So Hard to Detect Keyup Event on Linux?
by _jal on Tuesday May 18, 2021 @11:29AM
(#27195969)
Terminal is still a first-class UI mode, not some fallback.
If some tooling doesn't work for us (which means over a terminal), then we don't consider it. If something doesn't expose functionality over a terminal, that functionality doesn't exist.
Re:Why Is It So Hard to Detect Keyup Event on Linux?
by arghwhat on Wednesday May 19, 2021 @08:13AM
(#27207496)
Sure, it's a first class UI mode from the 70's, which is extremely useful. Any development of it would be in direct conflict with its qualities.
> If some tooling doesn't work for us (which means over a terminal), then we don't consider it.
Who is "we"? Even the most die-hard TUI fan uses them through a GUI terminal emulator, making that argument fall entirely apart.
The interfaces for advanced UIs is Wayland and X. TUIs are meant for compatibility, not fancy ability.