There are a few ways I think that sticky keys could be improved. 1)An optional timeout of say, 50 ms. This would be useful to me, as an imprecise typist. For example, when I type '*' or '~', I sometimes release the shift-key slightly too early and get '8' or '#' instead. Therefore, I have sticky keys enabled (which works brilliantly as a solution). However, I don't want the modifier to stick for very long, as it can have unintended consequences. 2)Another useful option would be to disable the beep. DVD players often fake a shift-key keypress to prevent the screensaver activating - and this causes the system to beep. [(1) should probably imply this by default] 3)I crashed my system accidentally - I wanted Ctrl-Backspace, and got Ctrl-Alt-Backspace! Perhaps sticky keys should not stick the combinations: Ctrl-Alt-[Del|Backspace|Esc] ? (It's too easily done! Although I have now turned on DontZap in xorg.conf) I originally reported this to KDE - please see here: http://bugs.kde.org/show_bug.cgi?id=88859 Thank you very much.
#2 exists, as part of the XKB API. The GNOME keyboard accessibility prefs dialog exposes this as a checkbox, you can turn off the beep notifications.
Another nice enhancement would be the ability to handle e.g. ctrl+mousebutton as an event equivalent to e.g. ctrl+someletter in that it would not make ctrl stick.
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
indeed, configurable timeouts and refusing actions from sticky keys would be nice. (ctrl-alt-del we can do nothing about: x doesn't handle that.)
http://www.requea.com/xwiki/bin/download/XWiki/AmandatZohan/1cz1.html
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/259.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.