Comment by brimble
3 years ago
In another HN thread just the other day (paraphrasing, but the tone is accurate): "macOS is shit because cmd+Q kills my programs and it's too easy to hit accidentally while trying to strike cmd+A"
3 years ago
In another HN thread just the other day (paraphrasing, but the tone is accurate): "macOS is shit because cmd+Q kills my programs and it's too easy to hit accidentally while trying to strike cmd+A"
> In another HN thread just the other day (paraphrasing, but the tone is accurate): "macOS is shit because cmd+Q kills my programs and it's too easy to hit accidentally while trying to strike cmd+A"
On the other hand, macOS is wonderful because, if you don't want ⌘Q to do that, then you can re-bind the Quit command, and programs respect that. (I don't remember if programs have to opt-in to respecting it, or if the OS enforces it.) I know that various flavours of Linux can do this easily too, but I think that Windows doesn't have a native such feature.
I don't think programs have to opt in. You can remap it the same as every other menu command. Every AppKit app gets that menu entry by default.
The fact that remapping commands requires an exact, case sensitive match of the localized menu item label you have to type in by hand (and cannot copy to your clipboard) though...
It's hard to please everyone, and data-loss is kind of a trump concern, but actually macOS does because it has this feature. The keyboard shortcut is cmd+option+shift+escape but you can probably remap that.
I force quit apps all the time, sometimes even because I want them to restore their exact state. In a lot of apps, the macOS state restoration works great, possibly better than actually quitting them.