Smart Ctrl+C

[vlad-shatskyi]

On Linux, Ctrl+C should copy text if there exists selection, otherwise it should send SIGINT to the current command.

[SRGOM]

Some may not like this, I think you should have the standard C-S-c and C-S-v for copy and paste. C-c and C-v should be for interrupt and next-key-verbatim only. Just my two cents.

[vlad-shatskyi]

As usual, please vote. My reasoning is that

• Copying and pasting are more frequently used actions and deserve simpler shortcuts.
• It’s consistent with other applications.

[SRGOM]

I like your reasoning but I'd be against making them smart, is it okay to pop a message first time user presses C-c that interrupt is C-S-c? I don't want the situation where a program was interrupted because my selection was messed.

[vlad-shatskyi]

@SRGOM good point, inconsistent behavior can cause mistakes. What do you think if we always copy on Ctrl+C and interrupt on double Ctrl+C press?

[SRGOM]

That does sound a good middle path. On that note- I'm assuming you're doing this as a default behavior and your code actually reads from a config file a list of keystrokes/chords to map to actions? In which case C-c-c for interrupt sounds like a better default. If someone is "power user" enough to need C-c at it's original place, they'd be enough "power user" to edit config!

[deckar01]

The context menu says Ctrl+C is Copy, but it doesn't work.

---

A context sensitive Ctrl+C binding seems like a nice compromise. Ctrl+Shift+C is working great for me now, but I switch back and forth between a mac and linux so it trips me up often. I actually use a mac keyboard on linux with Super mapped to Ctrl.

I would rather deprecate the Ctrl+C interrupt in favor of a modern UI solution like a red button that says "Stop".