Why do terminals insist on interfering with copy and paste?

Question

I appreciate that these terminals are often old and have very entrenched norms, but co...+c and co...+v have been standard in windows and mac for a very long time, and they are expected behavioureven if there's a huge history of this, which I'm certain there is, I find it as just as irritating as the apps that don't actually close when you click the close button. why not perform the expected user behaviour, and leave the alternative as a setting? there are 24 other letters to choose from for keyboard interrupts and the restlinux's ctrl-shift-c/v isn't so bad, but I still have to ask why? for such common, non-dangerous operations, why mess with the expected behaviour?I'm guessing mostly the explanation is that they did it in the first place when the rules weren't so concrete, and development tools like this tend to prioritise legacy users over new?

MBCook · Accepted Answer

This is one of the reasons I love my Mac, though it’s total happenstance it works this way.
Since the Mac uses Command-c/v it doesn’t interfere with the standard Unix terminal’s Control functions. But you can easily trigger the Mac’s functions (such as Commamd-f for find) without worry.
It sidesteps the problem Windows users have that used to frustrate me too.
Edit: I looked it up. Early Macs didn’t even have a control key. It was added later for terminal client compatibility.

PaulHoule · Answer

Control-C has been the &lsquo;break&rsquo; key for serial consoles since the 1970s so it is the GUI cut and paste that is new.

janmarsal · Answer

I keep shutting down my processes with ctrl+c all the time. Then for a moment I become extra careful to hit ctrl+shift+c instead, so next when I open the browser and try to copy something I end up opening the developer tools instead. To make matters worse, I had a mouse with a broken mouse wheel when I was a teen. The middle click still worked, so I learned to rely on autoscroll a lot. So I had to disable the middle mouse click paste because I kept pasting my clipboard everywhere. I hate what I have become.

camgunz · Answer

I think the simple answer is:- Ctrl-C was first, existing before GUIs had been invented.- Ctrl-C isn't really a terminal thing. There are things you can press on a keyboard the terminal will interpret, but it passes Ctrl-C through.- Things that run in terminals rely on this. It's an easy way to send SIGINT.- GUIs came onto the scene, and in Windows Ctrl-C/X/V was copy/cut/paste.- People built terminal emulators (xterm) for UNIX GUIs, and didn't have this conflict because they didn't use Ctrl-C/X/V for copy/cut/paste.- Slowly UNIX terminal emulators and Windows GUI standards started to occupy the same space (GNOME, KDE, WSL), which led to this conflict.So your perspective of Ctrl-C/X/V = copy/cut/paste is expected behavior isn't incorrect, but it's also not incorrect that many (more?) people expect Ctrl-C to send SIGINT in a terminal. You're experiencing the conflict that everyone else is, you'd just make concessions in a different way.To that end, this is configurable in many terminals: Konsole [0], Gnome Terminal [1], xterm [2], URxvt [3].[0]: https://old.reddit.com/r/kde/comments/quirya/how_to_use_ctrl...[1]: https://askubuntu.com/questions/53688/making-ctrlc-copy-text...[2]: https://unix.stackexchange.com/questions/339160/enable-ctrlc...[3]: https://stackoverflow.com/questions/39884093/rebinding-copy-...

leejoramo · Answer

As others have noted, the Macintosh has always avoided this by using the Command key.
I really wish we could create additional OS level modifier keys like Shift, Control, Alt, Window/Command. Such functionality would go along way to solving this issue and maintaining the normal key bindings. This would allow me to add macOS style keybindings on Windows and Linux.
I know about Kinto. And have created my own Windows 1000 line AHK macro along with a fully programmable hardware keyboard to mostly get the key bindings I want. However, being able to add my own OS level modifier keys would make this so much easier and better

t-3 · Answer

*nixes have superior copy-paste functionality using mouse selection + scroll wheel click or shift+insert. Ctrl-c Ctrl-v is really bad and clunky in comparison.

NonNefarious · Answer

"I find it as just as irritating as the apps that don't actually close when you click the close button"Yep, that's a pillar of the Mac experience.

Why do terminals insist on interfering with copy and paste?

Control-C has been the ‘break’ key for serial consoles since the 1970s so it is the GUI cut and paste that is new.

*nixes have superior copy-paste functionality using mouse selection + scroll wheel click or shift+insert. Ctrl-c Ctrl-v is really bad and clunky in comparison.

"I find it as just as irritating as the apps that don't actually close when you click the close button"
Yep, that's a pillar of the Mac experience.