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

Funky behavior when using cat, less, etc. over ssh #8221

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

Originally created by @WSLUser on GitHub (May 18, 2020).

Environment

Windows build number:  Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): Version: 0.11.1333.0

Any other software?

Steps to reproduce

Open a brand new Terminal instance. Ssh to a remote Linux host from Powershell 7. Locate or create a text file that enough lines to scroll through several pages worth. I had results I filtered through from a scan I performed using a script that goes to stdout unless I pass a > somefile.txt. Then do cat sometextfile.txt | more. Observer the top line is removed after being visible for less than a second and you can not scroll to it. Use ^C to exit then use clear. Try using less instead. The first line is once again gone after being visible for less than a second. Also the 3rd line after a newline in my case repeated itself after showing about 7 lines including a newline of other entries before continuing with those entries. Now clear again. Here's where it gets really interesting, do a bunch of resizes (just hold onto the bottom right corner and drag it diagonally to shrink and increase the screen size of Terminal). Do a straighup cat (no more this time) and observe the top line of the text file is now viewable. However you get returned to a somewhat unresponsive prompt at the bottom line of the screen which shows part of a line entry of that text file. You can not press enter or ^C and have it do anything (looks like they are being eaten). You can however use the space bar to clear out the characters that filled the prompt and when they are gone, use backspace until you reach the beginning of the prompt. Then you can use ^C to get a new prompt at the bottom. Do the cat again with more used again. Now it appears to actually work the way it's intended.

One last note: In my settings.json, I have

"rowsToScroll": "100",
"historySize": 12000,

under "defaults". I also have retro terminal effects enabled but I haven't really used it (i.e. nothing in my terminal looks different) and I've set Tango Dark as my default color scheme. Otherwise, it's a default settings.json.

Expected behavior

I expect it to show every line correctly and for them all to be scrollable, dependent on your settings.json even after resizes.

Actual behavior

This does not work as intended. However this used to be just fine. I started noticing this in 1251 but hoped that the latest Terminal might change something. There might be several bugs here I reported and if so, I apologize. This is just what I did to get my screen to show everything I wanted it to.

Originally created by @WSLUser on GitHub (May 18, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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! --> <!-- 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. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Win32NT 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): Version: 0.11.1333.0 Any other software? ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Open a brand new Terminal instance. Ssh to a remote Linux host from Powershell 7. Locate or create a text file that enough lines to scroll through several pages worth. I had results I filtered through from a scan I performed using a script that goes to stdout unless I pass a `> somefile.txt`. Then do `cat sometextfile.txt | more`. Observer the top line is removed after being visible for less than a second and you can not scroll to it. Use ^C to exit then use `clear.` Try using `less` instead. The first line is once again gone after being visible for less than a second. Also the 3rd line after a newline in my case repeated itself after showing about 7 lines including a newline of other entries before continuing with those entries. Now `clear` again. Here's where it gets really interesting, do a bunch of resizes (just hold onto the bottom right corner and drag it diagonally to shrink and increase the screen size of Terminal). Do a straighup `cat` (no `more` this time) and observe the top line of the text file is now viewable. However you get returned to a somewhat unresponsive prompt at the bottom line of the screen which shows part of a line entry of that text file. You can not press enter or ^C and have it do anything (looks like they are being eaten). You can however use the space bar to clear out the characters that filled the prompt and when they are gone, use backspace until you reach the beginning of the prompt. Then you can use ^C to get a new prompt at the bottom. Do the cat again with `more` used again. Now it appears to actually work the way it's intended. One last note: In my `settings.json`, I have ``` "rowsToScroll": "100", "historySize": 12000, ``` under "defaults". I also have retro terminal effects enabled but I haven't really used it (i.e. nothing in my terminal looks different) and I've set Tango Dark as my default color scheme. Otherwise, it's a default `settings.json`. # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> I expect it to show every line correctly and for them all to be scrollable, dependent on your settings.json even after resizes. # Actual behavior <!-- What's actually happening? --> This does not work as intended. However this used to be just fine. I started noticing this in 1251 but hoped that the latest Terminal might change something. There might be several bugs here I reported and if so, I apologize. This is just what I did to get my screen to show everything I wanted it to.
claunia commented 2026-01-31 01:23:53 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (May 18, 2020):

The remote host was a Fedora 30 server if it makes any difference when troubleshooting. And ssh is the 8.1 release on Win32 and 8.0 on the Fedora server.

@WSLUser commented on GitHub (May 18, 2020): The remote host was a Fedora 30 server if it makes any difference when troubleshooting. And ssh is the 8.1 release on Win32 and 8.0 on the Fedora server.
claunia commented 2026-01-31 01:23:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (May 19, 2020):

If you make a selection, does it start redrawing the right things in the right places?

@DHowett commented on GitHub (May 19, 2020): If you make a selection, does it start redrawing the right things in the right places?
claunia commented 2026-01-31 01:23:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (May 23, 2020):

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 (May 23, 2020): 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 01:23:53 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (May 23, 2020):

bot still haven't had chance to reproduce.

@WSLUser commented on GitHub (May 23, 2020): bot still haven't had chance to reproduce.
claunia commented 2026-01-31 01:23:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jun 14, 2020):

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 (Jun 14, 2020): 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 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#8221
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?