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

How to interrupt program without Ctrl-C? #1143

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

Originally created by @nataliethistime on GitHub (May 16, 2019).

  • Your Windows build number

Microsoft Windows [Version 10.0.17134.765]

  • What you're doing and what's happening:

I often use Ctrl-C to interrupt and restart a program however with the copy/paste functions now using the control key I'm not seeing a way to do this?

Originally created by @nataliethistime on GitHub (May 16, 2019). * Your Windows build number `Microsoft Windows [Version 10.0.17134.765]` * What you're doing and what's happening: I often use Ctrl-C to interrupt and restart a program however with the copy/paste functions now using the control key I'm not seeing a way to do this?
claunia added the Issue-Question label 2026-01-30 22:17:28 +00:00
claunia commented 2026-01-30 22:17:29 +00:00
Author
Owner
Copy Link

@eryksun commented on GitHub (May 16, 2019):

If no text is selected, typing Ctrl+C should generate a CTRL_C_EVENT in all processes that are attached to the console. If text is selected, Ctrl+C copies to the clipboard and clears the selection. Press Ctrl+C a second time to generate the event.

It's up to a program how it should handle this control event. It can ignore it or exit gracefully. By default a program started in a new console process group ignores Ctrl+C (e.g. CMD's start /B creates a new process group). Try Ctrl+Break if Ctrl+C seems to be ignored. Ctrl+Break is rarely ignored, except by shells such as CMD. Usually Ctrl+Break is left to the default handler (i.e. exit immediately with STATUS_CONTROL_C_EXIT) or at least is handled by exiting gracefully.

@eryksun commented on GitHub (May 16, 2019): If no text is selected, typing Ctrl+C should generate a `CTRL_C_EVENT` in all processes that are attached to the console. If text is selected, Ctrl+C copies to the clipboard and clears the selection. Press Ctrl+C a second time to generate the event. It's up to a program how it should handle this control event. It can ignore it or exit gracefully. By default a program started in a new console process group ignores Ctrl+C (e.g. CMD's `start /B` creates a new process group). Try Ctrl+Break if Ctrl+C seems to be ignored. Ctrl+Break is rarely ignored, except by shells such as CMD. Usually Ctrl+Break is left to the default handler (i.e. exit immediately with `STATUS_CONTROL_C_EXIT`) or at least is handled by exiting gracefully.
claunia commented 2026-01-30 22:17:30 +00:00
Author
Owner
Copy Link

@binarycrusader commented on GitHub (May 16, 2019):

As @eryksun says, this is up to the shell you're running, not to the Windows Terminal program.

@binarycrusader commented on GitHub (May 16, 2019): As @eryksun says, this is up to the shell you're running, not to the Windows Terminal program.
claunia commented 2026-01-30 22:17:30 +00:00
Author
Owner
Copy Link

@binarycrusader commented on GitHub (May 16, 2019):

See also #813

@binarycrusader commented on GitHub (May 16, 2019): See also #813
claunia commented 2026-01-30 22:17:30 +00:00
Author
Owner
Copy Link

@nataliethistime commented on GitHub (May 21, 2019):

@eryksun I am using CMD and I can't seem to be able to do Ctrl-Break due to a lack of a Break key on my keyboard. Do you know of any alternatives?

I appreciate the help.

@nataliethistime commented on GitHub (May 21, 2019): @eryksun I am using CMD and I can't seem to be able to do Ctrl-Break due to a lack of a Break key on my keyboard. Do you know of any alternatives? I appreciate the help.
claunia commented 2026-01-30 22:17:30 +00:00
Author
Owner
Copy Link

@eryksun commented on GitHub (May 21, 2019):

You may have an fn key that shifts another key to pause/break. Otherwise use the on-screen keyboard.

@eryksun commented on GitHub (May 21, 2019): You may have an fn key that shifts another key to pause/break. Otherwise use the on-screen keyboard.
claunia commented 2026-01-30 22:17:30 +00:00
Author
Owner
Copy Link

@K4pt4n commented on GitHub (Jul 20, 2022):

using powershell 7.2.5 to run a ping -t command is not interruptible. Ctrl+c does not work. Ctrl+Break from the on-screen keyboard does not work.
Any other ideas? Kinda annoying.

@K4pt4n commented on GitHub (Jul 20, 2022): using powershell 7.2.5 to run a ping -t command is not interruptible. Ctrl+c does not work. Ctrl+Break from the on-screen keyboard does not work. Any other ideas? Kinda annoying.
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 Issue-Question
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#1143
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?