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

console output/history auto clears after logout from ssh session #19844

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

Originally created by @mfatty on GitHub (May 9, 2023).

Windows Terminal version

1.16.10262.0

Windows build number

10.0.22621

Other Software

Cygwin
Windows Powershell

Steps to reproduce

Start a new local terminal session (either Powershell or Cygwin)
Ssh to remote linux host (ssh user@ip)
On remote host via the ssh session, run some linux commands and get some output on console
Now I like 100 lines of output on console.
Type 'exit' to logout of ssh session
All the 100 lines of console output/history I had generated from the ssh session are gone.

remote-session.txt

when I type 'exit', everything clears on the console and all I get on the terminal is
Connection to <ip-address> closed.
PS C:\Users\username>

Expected Behavior

I expect to the terminal to keep the console output/history as I switch between local to remote sessions on the same terminal tab.

Actual Behavior

Terminal deletes console output/history when I logout from remote ssh session.

Originally created by @mfatty on GitHub (May 9, 2023). ### Windows Terminal version 1.16.10262.0 ### Windows build number 10.0.22621 ### Other Software Cygwin Windows Powershell ### Steps to reproduce Start a new local terminal session (either Powershell or Cygwin) Ssh to remote linux host (ssh user@ip) On remote host via the ssh session, run some linux commands and get some output on console Now I like 100 lines of output on console. Type 'exit' to logout of ssh session All the 100 lines of console output/history I had generated from the ssh session are gone. [remote-session.txt](https://github.com/microsoft/terminal/files/11428474/remote-session.txt) when I type 'exit', everything clears on the console and all I get on the terminal is `Connection to <ip-address> closed.` `PS C:\Users\username>` ### Expected Behavior I expect to the terminal to keep the console output/history as I switch between local to remote sessions on the same terminal tab. ### Actual Behavior Terminal deletes console output/history when I logout from remote ssh session.
claunia added the Needs-TriageIssue-BugNeeds-Attention labels 2026-01-31 06:55:08 +00:00
claunia commented 2026-01-31 06:55:09 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (May 9, 2023):

What are the contents of your ~/.bash_logout in your remote host? Does it contain anything related to "clear(ing)"?

@lhecker commented on GitHub (May 9, 2023): What are the contents of your `~/.bash_logout` in your remote host? Does it contain anything related to "clear(ing)"?
claunia commented 2026-01-31 06:55:09 +00:00
Author
Owner
Copy Link

@KalleOlaviNiemitalo commented on GitHub (May 9, 2023):

remote-session.txt shows $SHELL being /usr/bin/zsh; thus the contents of ~/.bash_logout may be irrelevant. Instead check $ZDOTDIR/.zlogout and /etc/zlogout.

With hardware terminals, I think clearing the screen during logout was common practice in order to prevent the next user of the terminal from reading the output before logging in.

@KalleOlaviNiemitalo commented on GitHub (May 9, 2023): [remote-session.txt](https://github.com/microsoft/terminal/files/11428474/remote-session.txt) shows $SHELL being `/usr/bin/zsh`; thus the contents of `~/.bash_logout` may be irrelevant. Instead check `$ZDOTDIR/.zlogout` and `/etc/zlogout`. With hardware terminals, I think clearing the screen during logout was common practice in order to prevent the next user of the terminal from reading the output before logging in.
claunia commented 2026-01-31 06:55:10 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (May 13, 2023):

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.

@microsoft-github-policy-service[bot] commented on GitHub (May 13, 2023): 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**.
claunia commented 2026-01-31 06:55:10 +00:00
Author
Owner
Copy Link

@microsoft-github-policy-service[bot] commented on GitHub (May 13, 2023):

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.

@microsoft-github-policy-service[bot] commented on GitHub (May 13, 2023): 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**.
claunia commented 2026-01-31 06:55:10 +00:00
Author
Owner
Copy Link

@mfatty commented on GitHub (May 14, 2023):

❯ cat ~/.bash_logout
# ~/.bash_logout
.
.
$ZDOTDIR/ does not have a logout file
.
.
❯ cat /etc/zlogout
# /etc/zlogout and ~/.zlogout are run when an interactive session ends
clear
.
.
So, /etc/zlogout is in fact the problem. I commented clear in /etc/zlogout and that fixed the issue.
Thank you @lhecker @kalle

@mfatty commented on GitHub (May 14, 2023): `❯ cat ~/.bash_logout ` `# ~/.bash_logout` . . ` $ZDOTDIR/` does not have a logout file . . `❯ cat /etc/zlogout` `# /etc/zlogout and ~/.zlogout are run when an interactive session ends` `clear` . . So, /etc/zlogout is in fact the problem. I commented `clear` in `/etc/zlogout` and that fixed the issue. Thank you @lhecker @kalle
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-Attention Needs-Triage
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#19844
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?