Comment by wpm
5 hours ago
OK sure in general maybe, but that isn't what happened here. What happened is a worse design where Ctrl+C sometimes copies and sometimes kills the current process in your terminal. It's annoying and dumb and clearly inferior to what NeXTSTEP and macOS ended up doing with a separate "Super"/GUI/Command key to handle GUI shortcuts like Cut/Copy/Paste, and leaving Ctrl to handle UNIX shortcuts in the terminal. This allowed the readline/emacs text cursor navigation to also carry over into the GUI, so you can treat text anywhere the same regardless if its a GUI text editor or your terminal.
> What happened is a worse design
But the reason it happened like this is precisely your principle I argued against where some shortcut got claimed first and blocked evolution! The way easy out is to rebind Ctrl+C as kill
> allowed the readline/emacs text cursor navigation to also carry over into the GUI
That's another set of dumb defaults that should've evolved years ago but got stuck (just like Ctrl+C)
> treat text anywhere the same
Great aspiration, but I don't see how it follows that you can't change the first-claimed shortcut?