3 ms·
Meta: I'll again have to criticize this submission's title. It shouldn't be " Why Is It So Hard to Detect Keyup Event on Linux?" (it's not a problem with the k
by solarkraft 8y ago
Meta:
I'll again have to criticize this submission's title. It shouldn't be " Why Is It So Hard to Detect Keyup Event on Linux?" (it's not a problem with the kernel), it should be something along the lines of "Why can't I detect key up events via SSH?".
And the answer to that is simple: That's not what it's designed for.
Or, even better: Instead of concentrating on the complaints part of the article provide on the part in which you're providing value to your readers: "Detecting keyboard events without a display server" or, if you want to get in on the long headlines trend: "Detecting key up events in a TTY environments is hard. Here are some ways".
- tinus_hn 8y agoNo, the submission title is the title of the linked page. That is correct.
- solarkraft 8y agoIt's not uncommon to correct click-baity titles in a submission. By "submission" I'm also referring to the original article.
- tinus_hn 8y agoYour comment does not claim click bait. Your comment claims you disagree with the blog title. The rule is: Don’t editorialize.
- solarkraft 8y ago"... unless it is misleading or linkbait", which I indeed think to be the case here. I clicked because I thought frameworks like Wayland and X or something else inherent about the architecture of modern Linux systems made it difficult to detect key up events, but it just turns out the author was trying to use something that doesn't have any concept of key events, leading to the feeling I was misled.
- setpatchaddress 8y agoI kinda disagree. At least some of the article is specific to Linux's console implementation. Not the "why", but the specific workaround given for the terminal doesn't necessarily generalize to other POSIXs. I think it's fair to specify that in the title. And the complexity of the article's answer is certainly interesting to people who care about receiving keyUp events.