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

Ctrl+Break behaves in cmd not as expected #7030

New Issue
Closed
opened 2026-01-31 00:53:20 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 00:53:20 +00:00
Owner
Copy Link

Originally created by @schlamar on GitHub (Mar 20, 2020).

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.720]
Windows Terminal version (if applicable): Version: 0.10.761.0

Usually a Ctrl+C behaves different than Ctrl+Break in a cmd console.

But in Windows Terminal Ctrl+Break behaves like Ctrl+C.

For example you can reproduce this with Python by running in cmd

py -c "import time; time.sleep(60)"

Expected behavior

Ctrl+C --> KeyboardInterrupt
Ctrl+Break --> Program quits without KeyobardInterrupt

This is the default behavior in standalone cmd.exe.

Actual behavior

Ctrl+C --> KeyboardInterrupt
Ctrl+Break --> KeyboardInterrupt

Originally created by @schlamar on GitHub (Mar 20, 2020). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18363.720] Windows Terminal version (if applicable): Version: 0.10.761.0 ``` Usually a Ctrl+C behaves different than Ctrl+Break in a cmd console. But in Windows Terminal Ctrl+Break behaves like Ctrl+C. For example you can reproduce this with Python by running in cmd py -c "import time; time.sleep(60)" # Expected behavior Ctrl+C --> KeyboardInterrupt Ctrl+Break --> Program quits **without** KeyobardInterrupt This is the default behavior in standalone cmd.exe. # Actual behavior Ctrl+C --> KeyboardInterrupt Ctrl+Break --> KeyboardInterrupt
claunia added the Resolution-Duplicate label 2026-01-31 00:53:20 +00:00
claunia commented 2026-01-31 00:53:21 +00:00
Author
Owner
Copy Link

@schlamar commented on GitHub (Mar 20, 2020):

It is possible that this is a regression from the 0.10 update because I haven't noticed this before.

@schlamar commented on GitHub (Mar 20, 2020): It is possible that this is a regression from the 0.10 update because I haven't noticed this before.
claunia commented 2026-01-31 00:53:21 +00:00
Author
Owner
Copy Link

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

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #1119 for more discussion.

/dup #1119

@zadjii-msft commented on GitHub (Mar 20, 2020): Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #1119 for more discussion. /dup #1119
claunia commented 2026-01-31 00:53:21 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 20, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Mar 20, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Resolution-Duplicate
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#7030
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?