Why is Control-C ambiguous? Oh wait, you guys use Control-C for copy, but you have forgotten that both Windows and Linux support Control-Insert for copy. That's what I use.
Why is Control-C ambiguous? Oh wait, you guys use Control-C for copy, but you have forgotten that both Windows and Linux support Control-Insert for copy. That's what I use.
That would not be a good approach on Macs where most users are using reduced/laptop keyboards that have no Insert key.
In this respect, Apple got pretty lucky. Most users were not using reduced keyboards in 1987 when they originally decided to add the Control key separate from Command. Plus, Mac OS didn't even have a native terminal at the time; I assume there were terminal emulators for networking/serial use but I can't imagine that was top-of-mind for Apple either.
Regardless, Cmd-C is definitely a more convenient shortcut than Control-Insert, even if you do have the keys for the latter.
> Mac OS didn't even have a native terminal at the time; I assume there were terminal emulators for networking/serial use but I can't imagine that was top-of-mind for Apple either.
I think it was in their mind. The manual for the keyboard (yes, keyboards had manuals back then) says the keyboard has “special keys that work in applications running in alternative operating systems” (https://www.cvxmelody.net/Apple%20Extended%20Keyboard%20II%2...)
I agree with you about Cmd-C being more convenient but that’s besides the point.
My point was that on all three operating systems Ctrl-C has an unambiguous feature: send SIGINT. It is more important to have SIGINT be consistent than have copy be consistent. Accidentally sending SIGINT to a job that has been running for an hour? That hour of work may now be gone. This is a deliberate action that should not be a mistake. Copying is not that? Win+C on Windows doesn’t do any destructive actions.
Not using the combination for one of its ambiguous purposes does not strip it of ambiguity, you've just trained yourself to avoid those circumstances.
That, of course, is one of the pain points that the article addresses: Training yourself to do so is additional cognitive load that never should have been necessary in the first place.
I flip between macOS and Linux and, occasionally, Windows. On one of my laptops, insert is also a Fn switch away, so I have to either remember that this machine needs Ctrl-Fn-F11 specifically when I'm copying from terminal.
On another keyboard I have the same problem, but insert is mapped to a different key entirely, so it is ctrl-fn-equals, and fn is on the opposite side of the keyboard from ctrl.
Contort my fingers in which way on which keyboard? Mental load and annoyance I don't need.
That’s a hardware problem. I avoid mental load and annoyance by using the same keyboard layout everywhere. Even on Windows the bottom left modifier keys on my keyboard are Ctrl Alt Win, and not Ctrl Win Alt.
The keyboard is the most important input device on a computer. It’s worthwhile to customize your key mappings to fit your muscle memory.