News for hackers. Stuff that matters.

A comment on Why Is It So Hard to Detect Keyup Event on Linux?. Parent comment

Re:Why Is It So Hard to Detect Keyup Event on Linux? by zokier on Monday May 17, 2021 @03:14PM (#27187126)
Correct architecture for terminal applications is command line; line oriented input, line oriented output. Not handling individual key events.
[ Parent | on HN ]
Re:Why Is It So Hard to Detect Keyup Event on Linux? by PaulDavisThe1st on Monday May 17, 2021 @04:45PM (#27188223)
Even back in the 1980s, when I was asked to reimplement the heirarchical DEC VMS "help" command for SunOS (in a terminal window), it was necessary to handle individual characters rather than use line-oriented input. The VMS "help" command had been written for VT100/VT200 terminals and their cousins, and was designed to take action on a single key press, rather than waiting for a return/enter action to "send" the command.
[ Parent | on HN ]
Re:Why Is It So Hard to Detect Keyup Event on Linux? by karatinversion on Monday May 17, 2021 @03:24PM (#27187262)
Not always, mind; having to press enter after every character press in vim would be a major drag!
[ Parent | on HN ]
Re:Why Is It So Hard to Detect Keyup Event on Linux? by zokier on Monday May 17, 2021 @03:33PM (#27187381)
ed/ex works perfectly fine with only line input and output. Afaik TECO stared out like that too.

Gvim works for visual editing

[ Parent | on HN ]
Re:Why Is It So Hard to Detect Keyup Event on Linux? by icedchai on Monday May 17, 2021 @06:15PM (#27189077)
You can read individual characters just fine from a command line app. That's what tty "raw" mode does.
[ Parent | on HN ]