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

Exit code 1 when exiting an Ubuntu multiplexed pane #9182

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

Originally created by @guillaumemeyer on GitHub (Jun 20, 2020).

Environment

OS:
image

Terminal:
image

SubSystem:
image

Steps to reproduce

  1. Open an Ubuntu tab, then open a second multiplexed ubuntu session in a pane
  2. Run some commands in the right pane, such as htop
  3. Go back to the prompt and type exit

Expected behavior

The right pane should close, leaving only the first pane.

Actual behavior

The right pane doesn't close and raises an error code 1:
image

Originally created by @guillaumemeyer on GitHub (Jun 20, 2020). # Environment OS: ![image](https://user-images.githubusercontent.com/1385518/85207307-3061c900-b328-11ea-8ee0-e61c1d213d0b.png) Terminal: ![image](https://user-images.githubusercontent.com/1385518/85207317-3d7eb800-b328-11ea-9255-81fbae484520.png) SubSystem: ![image](https://user-images.githubusercontent.com/1385518/85207342-6f901a00-b328-11ea-9fec-ad3de2551783.png) # Steps to reproduce 1. Open an Ubuntu tab, then open a second multiplexed ubuntu session in a pane 2. Run some commands in the right pane, such as htop 3. Go back to the prompt and type `exit` # Expected behavior The right pane should close, leaving only the first pane. # Actual behavior The right pane doesn't close and raises an error code 1: ![image](https://user-images.githubusercontent.com/1385518/85207282-fdb7d080-b327-11ea-99ac-1aa13bd4b2cd.png)
claunia added the Issue-QuestionNeeds-Tag-FixResolution-Answered labels 2026-01-31 01:48:05 +00:00
claunia commented 2026-01-31 01:48:06 +00:00
Author
Owner
Copy Link

@TrueshotBarrage commented on GitHub (Jun 25, 2020):

I can reproduce the same error using the steps outlined above.

@TrueshotBarrage commented on GitHub (Jun 25, 2020): I can reproduce the same error using the steps outlined above.
claunia commented 2026-01-31 01:48:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 26, 2020):

This is interesting. Before you exit, can you run echo $? to show the error code from the previous process?

@DHowett commented on GitHub (Jun 26, 2020): This is interesting. Before you `exit`, can you run `echo $?` to show the error code from the previous process?
claunia commented 2026-01-31 01:48:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jun 26, 2020):

Oh, and, how do you exit htop?

bash reflects the exit code of the last process as its own exit code. That means that when htop exits with code 1, bash says "I HAVE FAILED" and Terminal picks that up. That's by design - Terminal defaults to preserving the window when the process inside it has exited.

To turn off this behavior, set closeOnExit to always. 😄

@DHowett commented on GitHub (Jun 26, 2020): Oh, and, how do you exit `htop`? bash reflects the exit code of the last process _as its own exit code_. That means that when htop exits with code `1`, bash says "I HAVE FAILED" and Terminal picks that up. That's by design - Terminal defaults to preserving the window when the process inside it has exited. To turn off this behavior, set `closeOnExit` to `always`. :smile:
claunia commented 2026-01-31 01:48:06 +00:00
Author
Owner
Copy Link

@guillaumemeyer commented on GitHub (Jun 26, 2020):

I'm exiting htop with ctrl+c, and you're right about the exit code @DHowett :
image

@guillaumemeyer commented on GitHub (Jun 26, 2020): I'm exiting htop with `ctrl+c`, and you're right about the exit code @DHowett : ![image](https://user-images.githubusercontent.com/1385518/85871546-d69d4b00-b7ce-11ea-8739-ec71695ce2ea.png)
claunia commented 2026-01-31 01:48:06 +00:00
Author
Owner
Copy Link

@guillaumemeyer commented on GitHub (Jun 26, 2020):

And yes using "closeOnExit": "always" in the terminal settings solves the issue.

@guillaumemeyer commented on GitHub (Jun 26, 2020): And yes using `"closeOnExit": "always"` in the terminal settings solves the 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 Issue-Question Needs-Tag-Fix Resolution-Answered
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#9182
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?