What happened Ctrl C?
Turned out the way Ctrl-c works is quite simple — it’s just a shortcut key for sending the interrupt (terminate) signal SIGINT to the current process running in the foreground. Once the process gets that signal, it’s terminating itself and returns the user to the shell prompt.
What is the use of Ctrl-C?
Most Commonly Used Shortcuts
| Command | Shortcut | Explanation |
|---|---|---|
| Copy | Ctrl+C | Copies an item or text; used with Paste |
| Paste | Ctrl+V | Inserts the last cut or copied item or text |
| Select All | Ctrl+A | Selects all text or items |
| Undo | Ctrl+Z | Undoes the last action |
How to add Ctrl + C keybindings by default?
If you upgraded to 0.3, you needed to add them manually: https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-3-release/ For the curious, here is the PR where they added the default keybindings for copy and paste and they discuss the challenges of using Ctrl+C by default.
Why does Ctrl + C and Ctrl-V not work?
Pressing Ctrl+C or Ctrl+V will not have the desired effect (copy/pasting). Ctrl+X and many other hotkeys still behave as expected. If more hotkeys are affected is currently not clear. In the state where the hotkeys do not work, I can still see the event being received fine in the hotkey troubleshooter:
When to use Ctrl + C or shift + C?
If text is selected: Ctrl+c will copy the selected text. If text is NOT selected: Ctrl+c will send a interrupt, the same way Ctrl+c usually behaves. If the user doesn’t like that behavior, it’s pretty trivial to remove the new Ctrl+c binding from their settings.json, and rely on the Ctrl+shift+c binding that’s in defaults.json
Why does Ctrl + C randomly stop copying?
I don’t know why this starts happening, it just randomly happens several times a day for me. Pressing Ctrl+C or Ctrl+V will not have the desired effect (copy/pasting). Ctrl+X and many other hotkeys still behave as expected. If more hotkeys are affected is currently not clear.