I read a lot of answers online that its a bad idea, but the arguments did not make a lot of sense. “it’s a heavily ingrained part of the eco system”. Well if I can change it, what’s the deal?
It makes more sense to make an interrupt signal be the harder shortcut, and copy to be ctrl+C, matching other programs and platforms.
I’ve done it for about a decade without anything bad ever happening.
I have rebound copy and paste to ctrl+c and ctrl+v in konsole and bound the interrupt to ctrl+x using stty intr ^x
Also I keep it consistent across ssh sessions by using Xpipe.
I honestly wasn’t even aware that anybody thought it might be bad for any reason.
Me too!
Ctrl-k Ctrl-u in nano don’t interfere either :)
@Deckweiss @matcha_addict
Ctrl+shift+k and u? I’m pretty sure it’s Ctrl+k and +u
@psud yes no shift I’ll correct it, but that’s what I meant ctrl-u ctrl-k
Why? It seems like you would want to kill a program more than copying text. Is it just a habit thing?
Not in my workflow. Usually programms terminate after doing their job. And I copy the output all the time to google for stuff or to put it in another terminal or another command.
Ctrl+X is not significantly more difficult to press than Ctrl+C. But Ctrl+Shift+C is.