CTRL+C cancels the current operation even though the UI states it is ESC

[laeubi]

Describe the bug

It happened to me multiple times that I accidentally canceled the current operation!

When an operation is running it says Esc to cancel but also CTRL+c cancel the operation!

This is really annoying because:

1. CTRL+c is a bad choice anyways because it classes with the very familiar "copy" action 99,99% of applications and os use with this shortcut, so one easily mess it up by accident with the terminal having focus and one wants to copy something.
2. CTRL+c in "non working mode" means clear the prompt/command input (and 2x CTRL+c is actually /exit)

Please fix that or add at least a confirmation that the user really want to cancel the operation...

Affected version

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

Additional context

No response

[janakmshah]

The use of Ctrl+C to "cancel" or interrupt a process (SIGINT) predates its use as a command for "copy" by at least a decade.

[laeubi]

The use of Ctrl+C to "cancel" or interrupt a process (SIGINT) predates its use as a command for "copy" by at least a decade.

Not everyone is still working on a green and black teletype terminal these days... Things are changing especially in the IT.

[janakmshah]

Exactly. Not everyone uses Windows anymore. Things are changing especially in the IT.

[laeubi]

Exactly. Not everyone uses Windows anymore. Things are changing especially in the IT.

I don't understand? I'm running copilot-cli under Debian Linux so what has windows to do with that today's Application/IDEs usually use CTRL-C for copy some text?

Do your IDE really force-close without confirmation just in the middle if you press CTRL-C? Open Office? Vi? Nano?

Also I have no problem with the shortcut itself but

1. The UI (terminal, whatever) says ESC is the key to cancel the operation
2. Even worse CTRL+C only clears the text when copilot is not working (while it would be quite easy to restart the process with --continue) and during the work it does not clear --> inconsistent
3. Even then you have to confirm it by pressing CTRL+C twice

So I really don't get what you try to say here and how it improves the user experience in any way or adds anything new to the discussion.