On the other hand, in a terminal, I can use Ctrl-C/Ctrl-V/etc for their intended (in-terminal) purposes and Cmd-C/Cmd-V/etc for their intended (macOS-wide) purposes...
Which is much worse - why is it me, the user that have to care about whether I’m in a terminal or a browser window and switch the shortcuts I use for the same functionality? It should be the same, and macs actually got it right. The first time I had a mac (from an employer), I was annoyed by it, but it is the superior way. Especially that not all terminal emulators go with ctrl+shift either, so there is also the “let’s copy it with shift, nope, without shift, nope, again, oh I killed the process”.
> Which is much worse - why is it me, the user that have to care about whether I’m in a terminal or a browser window and switch the shortcuts I use for the same functionality?
How is it worse? Ctrl + C, Ctrl + D, Ctrl + Z all work as expected in the terminal.
Now you want to copy something, which is obviously not going to work with Ctrl + C, so you just add a Shift to it instead of moving to a totally different key (which you absolutely still could, btw).
No, ctrl+c works one way in the terminal, and a completely other way in every other GUI app. There is no good reason for this arbitrary change in meaning, objectively, otherwise from your logic it would follow that taking a screenshot would be logical in, say, gimp only by pressing ctrl+alt+shift+c, which I hope we can agree would make no sense.
Okay, I see your point now but it's a bit weird for me because having the Ctrl key only for a specific app seems unwise and still less efficient. It's not about Gimp, it's just the terminal that's special.
I've never had an issue with Ctrl+Shift+C. I also don't press Ctrl+C accidentally because I know when I'm using the terminal.
Even on macbook, I don't have issues with accidental presses but I don't like that I have to press an entirely different key on the keyboard to use the terminal.
