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

Make Alt+F4 work and warn the user about terminating more than one tab #2188

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

Originally created by @arnederuwe on GitHub (Jun 25, 2019).

Originally assigned to: @KaiyuWang16 on GitHub.

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.175]
Windows Terminal version (if applicable): 0.2.1715.0

Steps to reproduce

Start The terminal app, try to close it using Alt + F4

Expected behavior

The app should close

Actual behavior

The app doesn't close, which is inconsistent with 99% of windows apps

Originally created by @arnederuwe on GitHub (Jun 25, 2019). Originally assigned to: @KaiyuWang16 on GitHub. <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Microsoft Windows [Version 10.0.18362.175] Windows Terminal version (if applicable): 0.2.1715.0 ``` # Steps to reproduce Start The terminal app, try to close it using Alt + F4 # Expected behavior The app should close # Actual behavior The app doesn't close, which is inconsistent with 99% of windows apps
claunia commented 2026-01-30 22:49:04 +00:00
Author
Owner
Copy Link

@Shorotshishir commented on GitHub (Jun 25, 2019):

On Second Thought.
PowerShell and WSL individually don't close on alt+f4 as they don't have it set for the task. Windows Terminal shows it has alt+f4 set to close but it doesn't work. perhaps they are trying to make it consistent with the rest two.

@Shorotshishir commented on GitHub (Jun 25, 2019): **On Second Thought.** PowerShell and WSL individually don't close on `alt+f4` as they don't have it set for the task. Windows Terminal shows it has `alt+f4` set to close but it doesn't work. perhaps they are trying to make it consistent with the rest two.
claunia commented 2026-01-30 22:49:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Jun 27, 2019):

This is now the tracking issue for getting alt+f4 working and adding a dialog to stop users from harming their running session state.

@DHowett-MSFT commented on GitHub (Jun 27, 2019): This is now the tracking issue for getting alt+f4 working and adding a dialog to stop users from harming their running session state.
claunia commented 2026-01-30 22:49:05 +00:00
Author
Owner
Copy Link

@praneetloke commented on GitHub (Sep 1, 2019):

It would also be nice if there was an option to prompt the user about closing a tab that has a running program. For example, running a development server of some kind in a tab in interactive mode (vs. daemon mode) is often a development workflow for all sorts of apps (Angular CLI, webpack-based apps, Node apps etc.) these days.

@praneetloke commented on GitHub (Sep 1, 2019): It would also be nice if there was an option to prompt the user about closing a tab that has a running program. For example, running a development server of some kind in a tab in interactive mode (vs. daemon mode) is often a development workflow for all sorts of apps (Angular CLI, webpack-based apps, Node apps etc.) these days.
claunia commented 2026-01-30 22:49:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Sep 24, 2019):

This was fixed by #2526.

@DHowett-MSFT commented on GitHub (Sep 24, 2019): This was fixed by #2526.
claunia commented 2026-01-30 22:49:05 +00:00
Author
Owner
Copy Link

@codenotworking commented on GitHub (Aug 18, 2024):

I don't think this was fixed, because #17613 exists.

@codenotworking commented on GitHub (Aug 18, 2024): I don't think this was fixed, because [#17613](https://github.com/microsoft/terminal/issues/17613) exists.
claunia commented 2026-01-30 22:49:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Aug 18, 2024):

@codenotworking thanks, we’ll keep all further discussion over there rather than on this five year old issue.

@DHowett commented on GitHub (Aug 18, 2024): @codenotworking thanks, we’ll keep all further discussion over there rather than on this *five year old* issue.
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-UserInterface Issue-Task Product-Terminal Resolution-Fix-Available
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#2188
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?