3 ms·

Forget confirmation, Ctrl-Q shouldn't exist in the first place. An keystroke that can close your whole session and is near-identical to another, very common key

Forget confirmation, Ctrl-Q shouldn't exist in the first place. An keystroke that can close your whole session and is near-identical to another, very common keystroke is a design flaw, period. Same with the backspace key activating the back button. Using these keystrokes for these purposes should be considered harmful. Ctrl-Q is so harmful that I've long fantasized about hacking whatever driver in the kernel that controls the keyboard and having it ignore whatever signal the keyboard sends out whenever you press Ctrl-Q and not even pass it on to userspace.

shabble 9y ago
On OSX I have a tiny applescript running inside Butler[1] that's active when firefox is foregrounded, and just intercepts Ctrl-Q and runs: tell application "Firefox" set buttonStr to "Ooops" set errMsg to "Close with ?-Q disabled. Use the menu." display dialog errMsg buttons {buttonStr} cancel button buttonStr default button buttonStr with icon stop giving up after 5 end tell I'd imagine similar options exist for other OSes. AutoHotkey for windows, maybe? Not sure what linux/x has by way of systemwide handlers that can both intercept and cancel propagation of offending bindings, though. [1] https://manytricks.com/butler/ https://manytricks.com/butler/