starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Shift-ctrl-C sends interrupt if no text is selected #14013

New Issue
Open
opened 2026-01-31 03:58:31 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 03:58:31 +00:00
Owner
Copy Link

Originally created by @gpvos on GitHub (May 28, 2021).

Windows Terminal version (or Windows build number)

1.7.1033.0

Other Software

Both Command Prompt (10.0.19042.985) and Ubuntu (20.04.2 LTS). Probably others as well.

Steps to reproduce

  1. Make sure you have not selected any text.
  2. Be unaware of the above.
  3. Press shift-ctrl-C

Expected Behavior

Nothing happens. Alternatively, emptying the clipboard would also be acceptable, although less desirable.

Actual Behavior

Interrupt is sent to running program, as if ctrl-C is pressed. Suddenly and unexpectedly, I have to restart my program, or restart editing my command line. If I had wanted that, I'd have pressed ctrl-C, not the text copying command, which is something entirely different. Why would you conflate these two?

Originally created by @gpvos on GitHub (May 28, 2021). ### Windows Terminal version (or Windows build number) 1.7.1033.0 ### Other Software Both Command Prompt (10.0.19042.985) and Ubuntu (20.04.2 LTS). Probably others as well. ### Steps to reproduce 1. Make sure you have not selected any text. 2. Be unaware of the above. 3. Press shift-ctrl-C ### Expected Behavior Nothing happens. Alternatively, emptying the clipboard would also be acceptable, although less desirable. ### Actual Behavior Interrupt is sent to running program, as if ctrl-C is pressed. Suddenly and unexpectedly, I have to restart my program, or restart editing my command line. If I had wanted that, I'd have pressed ctrl-C, not the text copying command, which is something entirely different. Why would you conflate these two?
claunia added the Area-SettingsIssue-TaskProduct-TerminalArea-TerminalControl labels 2026-01-31 03:58:31 +00:00
claunia commented 2026-01-31 03:58:32 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 28, 2021):

I could have sworn we had another thread tracking this somewhere on the repo...

This is how conhost behaves as well. So this is probably behavior that's existed for 20+ years now in the vintage console. Undoubtably, there's someone out there who's muscle memory now involves using ctrl+shift+c to send interrupts.

Plus, since before 1.0, we've been shipping ctrl+c as copy in the user's settings.json by default. For all the users who still have that set (probably a large population), changing this behavior now would probably a pretty major breaking change. They wouldn't be able to send an interrupt at all anymore.

The only possible thing I could think of as a solution here is

  • add another parameter to copy, neverPassThroughToClientApp, which would prevent the key from falling through to the client even when there's no selection
  • opt the defaults.json copy in to that setting, but not the userDefaults.json one.

Though that sure does seem like a cludge. Any more clever solutions?

@zadjii-msft commented on GitHub (May 28, 2021): I could have sworn we had another thread tracking this somewhere on the repo... This is how conhost behaves as well. So this is probably behavior that's existed for 20+ years now in the vintage console. Undoubtably, there's someone out there who's muscle memory now involves using <kbd>ctrl+shift+c</kbd> to send interrupts. Plus, since before 1.0, we've been shipping <kbd>ctrl+c</kbd> as `copy` in the user's `settings.json` by default. For all the users who still have that set (probably a large population), changing this behavior now would probably a pretty _major_ breaking change. They wouldn't be able to send an interrupt _at all_ anymore. The only possible thing I could think of as a solution here is * add _another_ parameter to copy, `neverPassThroughToClientApp`, which would prevent the key from falling through to the client even when there's no selection * opt the `defaults.json` copy in to that setting, but not the `userDefaults.json` one. Though that sure does seem like a cludge. Any more clever solutions?
claunia commented 2026-01-31 03:58:32 +00:00
Author
Owner
Copy Link

@gpvos commented on GitHub (May 28, 2021):

Sorry, I did search.

I have a default install, but of a more recent version. I certainly did not change this key setting. In conhost, I used , so I was pretty happy with this new simpler key combination that is easier to remember than shift-insert or ctrl-insert where I keep forgetting which is which. In my memory, this used to not fall back to interrupt, and this behaviour changed somewhere in the last half year or so.

In essence, yes, I am asking for a new parameter to the copy command, or a separate command. Changing the default is not necessary for me, but I do want to have this option.

@gpvos commented on GitHub (May 28, 2021): Sorry, I did search. I have a default install, but of a more recent version. I certainly did not change this key setting. In conhost, I used <alt-space E K>, so I was pretty happy with this new simpler key combination that is easier to remember than shift-insert or ctrl-insert where I keep forgetting which is which. In my memory, this used to not fall back to interrupt, and this behaviour changed somewhere in the last half year or so. In essence, yes, I am asking for a new parameter to the copy command, or a separate command. Changing the default is not necessary for me, but I do want to have this option.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Settings Area-TerminalControl Issue-Task Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#14013
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?