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

Can we exit terminal completely when command exit is called? #15142

New Issue
Closed
opened 2026-01-31 04:29:41 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 04:29:41 +00:00
Owner
Copy Link

Originally created by @amithegde on GitHub (Sep 8, 2021).

Description of the new feature/enhancement

I usually enter command exit to exit cmd.exe or conemu which exits the process. But with terminal, it displays:

image

Now, need to grab mouse and click the close button to close it completely. Interestingly, when I have quake mode, there is no x button to close it so I need to take help from trusted friend Process Explorer to kill Terminal.

Note: this happens for the first tab, splits and other tabs seem to exit fine.

Proposed technical implementation details (optional)

  • When user enters the command exit terminal process should exit completely
Originally created by @amithegde on GitHub (Sep 8, 2021). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I usually enter command `exit` to exit cmd.exe or conemu which exits the process. But with terminal, it displays: ![image](https://user-images.githubusercontent.com/816051/132563484-b54d59b4-e8b7-45a3-b8c6-1fef76b4e2ac.png) Now, need to grab mouse and click the close button to close it completely. Interestingly, when I have quake mode, there is no `x` button to close it so I need to take help from trusted friend `Process Explorer` to kill Terminal. Note: this happens for the first tab, splits and other tabs seem to exit fine. # Proposed technical implementation details (optional) - When user enters the command `exit` terminal process should exit completely
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 04:29:41 +00:00
claunia commented 2026-01-31 04:29:42 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Sep 8, 2021):

(You can also close it with Ctrl+Shift+W.)

Over to @zadjii-msft for his cached response 😄

@DHowett commented on GitHub (Sep 8, 2021): (You can also close it with <kbd>Ctrl+Shift+W</kbd>.) Over to @zadjii-msft for his cached response :smile:
claunia commented 2026-01-31 04:29:42 +00:00
Author
Owner
Copy Link

@elsaco commented on GitHub (Sep 9, 2021):

By default "Profile termination behavior" in "Advanced" settings is "Close only when process exits successfully". By selecting first option "Close when process exits, fails, or crashes" will close a cmd.exe session without the [process exited with code 1] message.

Sample config:
wt_cmd_exit_setting

@elsaco commented on GitHub (Sep 9, 2021): By default "Profile termination behavior" in "Advanced" settings is "Close only when process exits successfully". By selecting first option "Close when process exits, fails, or crashes" will close a cmd.exe session without the [process exited with code 1] message. Sample config: ![wt_cmd_exit_setting](https://user-images.githubusercontent.com/3933920/132601625-d6a9fce7-ab5a-41fa-bc92-4d37830854d4.png)
claunia commented 2026-01-31 04:29:43 +00:00
Author
Owner
Copy Link

@LuanVSO commented on GitHub (Sep 9, 2021):

type this isntead:

exit 0
@LuanVSO commented on GitHub (Sep 9, 2021): type this isntead: ```cmd exit 0 ```
claunia commented 2026-01-31 04:29:43 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Sep 9, 2021):

Thanks for the report! Please make sure to search for duplicates when filing new issues. There's already a decent amount of discussion in the above issues explaining why this happens.

https://github.com/microsoft/terminal/issues/4263#issuecomment-670164469

This behavior exists to stop an error message printed out by a program from disappearing instantly when it exits. There is a class of applications for which that is extremely important. We're following this behavior because it is the right brhavior to follow, and because you can turn it off with a config option very easily.

https://github.com/microsoft/terminal/issues/4736#issuecomment-592127830

Alas, this is a behavior that's highly conserved across multiple shells and terminal emulators on most mainstream operating systems; more info in #4223 (comment). If you'd rather it just exit every time, set closeOnExit to true. 😄 /dup #4223.

And of course, as mentioned elsewhere in this thread, the closeOnExit setting can change this behavior if you're really used to using exit to close your terminal windows. You can read more about it in the docs here.

@zadjii-msft commented on GitHub (Sep 9, 2021): Thanks for the report! Please make sure to [search for duplicates](https://github.com/microsoft/terminal/issues?q=is%3Aissue+%22process+exited+with+code+9009%22+is%3Aclosed) when filing new issues. There's already a decent amount of discussion in the above issues explaining why this happens. https://github.com/microsoft/terminal/issues/4263#issuecomment-670164469 > This behavior exists to stop an error message printed out by a program from _disappearing instantly_ when it exits. There is a class of applications for which that is extremely important. We're following this behavior because it is the right brhavior to follow, _and because you can turn it off with a config option very easily._ https://github.com/microsoft/terminal/issues/4736#issuecomment-592127830 > Alas, this is a behavior that's highly conserved across multiple shells and terminal emulators on most mainstream operating systems; more info in [#4223 (comment)](https://github.com/microsoft/terminal/issues/4223#issuecomment-574834181). If you'd rather it just exit every time, set `closeOnExit` to true. 😄 /dup #4223. And of course, as mentioned elsewhere in this thread, the `closeOnExit` setting can change this behavior if you're really used to using `exit` to close your terminal windows. You can read more about it in [the docs here](https://docs.microsoft.com/en-us/windows/terminal/customize-settings/profile-advanced#profile-termination-behavior).
claunia commented 2026-01-31 04:29:43 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 9, 2021):

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 (Sep 9, 2021): 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 Issue-Feature 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#15142
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?