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

Bug: ctrl+break is not ctrl+c #1489

New Issue
Closed
opened 2026-01-30 22:28:32 +00:00 by claunia · 7 comments
claunia commented 2026-01-30 22:28:32 +00:00
Owner
Copy Link

Originally created by @Cologler on GitHub (Jun 3, 2019).

Originally assigned to: @zadjii-msft on GitHub.

Steps to reproduce

  1. open windows terminal for cmd.exe
  2. execute command ping 8.8.8.8 -t
  3. press ctrl+break

Expected behavior

windows terminal show ctrl+break

Actual behavior

windows terminal show ctrl+c

Originally created by @Cologler on GitHub (Jun 3, 2019). Originally assigned to: @zadjii-msft on GitHub. # Steps to reproduce 1. open windows terminal for cmd.exe 1. execute command `ping 8.8.8.8 -t` 1. press `ctrl`+`break` # Expected behavior windows terminal show ctrl+break # Actual behavior windows terminal show ctrl+c
claunia commented 2026-01-30 22:28:33 +00:00
Author
Owner
Copy Link

@Cologler commented on GitHub (Jun 3, 2019):

ctrl+break and ctrl+c have a different meanings in ping command.

Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS]
            [-r count] [-s count] [[-j host-list] | [-k host-list]]
            [-w timeout] [-R] [-S srcaddr] [-c compartment] [-p]
            [-4] [-6] target_name

Options:
    -t             Ping the specified host until stopped.
                   To see statistics and continue - type Control-Break;
                   To stop - type Control-C.
@Cologler commented on GitHub (Jun 3, 2019): ctrl+break and ctrl+c have a different meanings in ping command. ``` txt Usage: ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-v TOS] [-r count] [-s count] [[-j host-list] | [-k host-list]] [-w timeout] [-R] [-S srcaddr] [-c compartment] [-p] [-4] [-6] target_name Options: -t Ping the specified host until stopped. To see statistics and continue - type Control-Break; To stop - type Control-C. ```
claunia commented 2026-01-30 22:28:34 +00:00
Author
Owner
Copy Link

@wi-ry commented on GitHub (Jun 12, 2019):

See attached. Ctrl+Break works in standard command prompt, however Windows Terminal processes Ctrl+Break as pressing Ctrl+C:
Capture

@wi-ry commented on GitHub (Jun 12, 2019): See attached. Ctrl+Break works in standard command prompt, however Windows Terminal processes Ctrl+Break as pressing Ctrl+C: ![Capture](https://user-images.githubusercontent.com/9650258/59328846-4a42e780-8ca2-11e9-9051-d383366ef364.JPG)
claunia commented 2026-01-30 22:28:34 +00:00
Author
Owner
Copy Link

@szalapski commented on GitHub (Feb 21, 2020):

Is there a workaround? How do I send an actual Ctrl+Break?

@szalapski commented on GitHub (Feb 21, 2020): Is there a workaround? How do I send an actual Ctrl+Break?
claunia commented 2026-01-30 22:28:34 +00:00
Author
Owner
Copy Link

@int19h commented on GitHub (Mar 6, 2020):

This is affecting some apps that only respect Ctrl+Break. For example, it appears to be impossible to stop a tox+pytest test run without closing the tab, or killing the process from another one.

@int19h commented on GitHub (Mar 6, 2020): This is affecting some apps that only respect Ctrl+Break. For example, it appears to be impossible to stop a tox+pytest test run without closing the tab, or killing the process from another one.
claunia commented 2026-01-30 22:28:35 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 31, 2020):

Alright, I finally dug out my keyboard that has a break key to investigate this.

In conhost

ctrl+break

Down: 1 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x28
Down: 0 Repeat: 1 KeyCode: 0x3 ScanCode: 0x46 Char: ^C (0x3) KeyState: 0x128
Down: 0 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x20

ctrl+c

Down: 1 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x28
Down: 0 Repeat: 1 KeyCode: 0x43 ScanCode: 0x2e Char: ^C (0x3) KeyState: 0x28
Down: 0 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x20

In gnome-terminal, xterm

This is the part that gets interesting: ctrl+break isn't actually encoded as anything. I can't find any documentation that ctrl+break should send anything in VT - presumably because that's supposed to send a signal of some kind, not a key that the client app can understand.

Conclusions

Since conpty at this point is limited to things that can be encoded in VT, there's no way for us to be able to send a sequence specifically for ctrl+break. #879 is our megathread that's tracking adding support for additional keys that currently aren't encodable in VT - I'm going to parent this bug to that thread.

@zadjii-msft commented on GitHub (Mar 31, 2020): Alright, I finally dug out my keyboard that has a break key to investigate this. #### In `conhost` <kbd>ctrl+break</kbd> ``` Down: 1 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x28 Down: 0 Repeat: 1 KeyCode: 0x3 ScanCode: 0x46 Char: ^C (0x3) KeyState: 0x128 Down: 0 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x20 ``` <kbd>ctrl+c</kbd> ``` Down: 1 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x28 Down: 0 Repeat: 1 KeyCode: 0x43 ScanCode: 0x2e Char: ^C (0x3) KeyState: 0x28 Down: 0 Repeat: 1 KeyCode: 0x11 ScanCode: 0x1d Char: \0 (0x0) KeyState: 0x20 ``` #### In `gnome-terminal`, `xterm` This is the part that gets interesting: <kbd>ctrl+break</kbd> isn't actually encoded as _anything_. I can't find any documentation that <kbd>ctrl+break</kbd> should send anything in VT - presumably because that's supposed to send a signal of some kind, not a key that the client app can understand. #### Conclusions Since conpty at this point is limited to things that can be encoded in VT, there's no way for us to be able to send a sequence specifically for <kbd>ctrl+break</kbd>. #879 is our megathread that's tracking adding support for additional keys that currently aren't encodable in VT - I'm going to parent this bug to that thread.
claunia commented 2026-01-30 22:28:35 +00:00
Author
Owner
Copy Link

@lempax commented on GitHub (Apr 15, 2020):

I also experienced this issue on v0.10.781.0. I do hope this will be fixed as I am already accustomed to command prompt using this feature. Thanks.

@lempax commented on GitHub (Apr 15, 2020): I also experienced this issue on v0.10.781.0. I do hope this will be fixed as I am already accustomed to command prompt using this feature. Thanks.
claunia commented 2026-01-30 22:28:35 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 18, 2020):

:tada:This issue was addressed in #6309, which has now been successfully released as Windows Terminal Preview v1.1.1671.0.🎉

Handy links:

@ghost commented on GitHub (Jun 18, 2020): :tada:This issue was addressed in #6309, which has now been successfully released as `Windows Terminal Preview v1.1.1671.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.1.1671.0) * [Store Download](https://www.microsoft.com/store/apps/9n0dx20hk701?cid=storebadge&ocid=badge)
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-Input Issue-Bug Priority-2 Product-Terminal Resolution-Fix-Committed
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#1489
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?