starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-24 07:54:35 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Close button doesnt send a sigint to running process #18396

New Issue
Closed
opened 2026-01-31 06:12:39 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 06:12:39 +00:00
Owner
Copy Link

Originally created by @Ricardonacif on GitHub (Sep 7, 2022).

Windows Terminal version

1.14.2281.0

Windows build number

10.0.19044.0

Other Software

No response

Steps to reproduce

Open any process on Windows Terminal that listens for a SIGINT and waits 5 seconds before closing
Click on the close (X) button on Windows Terminal

Expected Behavior

This should send the SIGINT signal to the process, and let it handle it.

Actual Behavior

It insta closes the Windows Terminal and the underlying process

Originally created by @Ricardonacif on GitHub (Sep 7, 2022). ### Windows Terminal version 1.14.2281.0 ### Windows build number 10.0.19044.0 ### Other Software _No response_ ### Steps to reproduce Open any process on Windows Terminal that listens for a SIGINT and waits 5 seconds before closing Click on the close (X) button on Windows Terminal ### Expected Behavior This should send the SIGINT signal to the process, and let it handle it. ### Actual Behavior It insta closes the Windows Terminal and the underlying process
claunia commented 2026-01-31 06:12:40 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 7, 2022):

Thanks for the report! This may need to be moved over to the WSL repository, since they own what happens when they get a "Console Closing" event. Whether they translate it into SIGINT or terminate the process is up to the subsystem host.

@DHowett commented on GitHub (Sep 7, 2022): Thanks for the report! This may need to be moved over to the [WSL repository](https://github.com/microsoft/wsl), since they own what happens when they get a "Console Closing" event. Whether they translate it into `SIGINT` or terminate the process is up to the subsystem host.
claunia commented 2026-01-31 06:12:40 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 7, 2022):

Does the process get a SIGINT if you're running the process in the vintage console/?

@zadjii-msft commented on GitHub (Sep 7, 2022): Does the process get a SIGINT if you're running the process in the vintage console/?
claunia commented 2026-01-31 06:12:40 +00:00
Author
Owner
Copy Link

@Ricardonacif commented on GitHub (Sep 7, 2022):

Actually, I thought this was the default behavior on Powershell, but it's not actually. It's the option -Wait on Start-Process command that makes the process receive the SIGINT and the terminal waits for the process. Do you guys think there's a way of achieving the same behavior on WT?

@Ricardonacif commented on GitHub (Sep 7, 2022): Actually, I thought this was the default behavior on Powershell, but it's not actually. It's the option -Wait on Start-Process command that makes the process receive the SIGINT and the terminal waits for the process. Do you guys think there's a way of achieving the same behavior on WT?
claunia commented 2026-01-31 06:12:41 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 19, 2022):

Hi @Ricardonacif. I'm curious, why do you want this?

We implemented it this way to make sure the UI updates as quickly as possible and create a "snappy" feeling.

@carlos-zamora commented on GitHub (Oct 19, 2022): Hi @Ricardonacif. I'm curious, why do you want this? We implemented it this way to make sure the UI updates as quickly as possible and create a "snappy" feeling.
claunia commented 2026-01-31 06:12:41 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Oct 23, 2022):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Oct 23, 2022): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Bug Needs-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#18396
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?