|
|
|
|
|
by noobquestion81
1954 days ago
|
|
I dont think the OP’s original point was primarily that the defaults are terrible, in any case. Its that the management of keybindings is godawful. The configuration fix you linked makes this point precisely. In order to have consistency in a basic systemwide function like “copy” you have to dig through forums or bust out your terminal emulator’s man page. |
|
In any case, I think you're assuming too much about how intuitive the system you've grown accustomed to is to other people. I accidentally kill programs in the terminal when I use macOS, because I can't keep the Cmd and Ctrl shortcuts separate in my head. Is that Apple's fault, or is it just something I'm not used to?
IMO, desktop UI designers would like to have three things. The issue is that they're mutually incompatible.
1. Continuity with the ancient tradition of having Ctrl-c send a cancel/abort (or SIGINT) signal.
2. Having the common operation of copying some text mapped to [modifier]-c.
3. Having the most common modifier key be the key in the bottom left corner of the keyboard, which is Ctrl on most PC keyboards.
You can't have all three at once in the same application. macOS solves this problem by abandoning 3, and using Cmd-c to copy text. Most Linux / Unix distributions solve this by partially abandoning 2, by prefixing the shortcut with an additional modifier in terminal applications so that the normal shortcut can continue to be used elsewhere. In my opinion they're both valid approaches. Personally I detest having to grope to find the Cmd key and remap my modifiers using Karabiner on macOS.