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

SSH then running a reset caused blank space #9083

New Issue
Closed
opened 2026-01-31 01:45:31 +00:00 by claunia · 8 comments
claunia commented 2026-01-31 01:45:31 +00:00
Owner
Copy Link

Originally created by @NathanR1225 on GitHub (Jun 17, 2020).

Environment

Win 10
Windows Terminal Version: 1.0.1401.0

Any other software?
SSH?

Steps to reproduce

  1. SSH into Linux using power shell or Ubuntu terminal
  2. run some commands (to full console )
  3. run reset to clear console
    Show example in images

Expected behavior

When running reset the console should clear like it does but put the next line at the top of the screen.

Actual behavior

Used SSH to log into a piece of hardware running linux. When I ran the reset command it clears the screen but adds a blank new line above the terminal line. resizing the terminal from full screen to partial screen then back to full screen does remove some new lines. Seen in Power shell and Ubuntu terminal.
image
image

Originally created by @NathanR1225 on GitHub (Jun 17, 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 Win 10 Windows Terminal Version: 1.0.1401.0 Any other software? SSH? # Steps to reproduce 1. SSH into Linux using power shell or Ubuntu terminal 2. run some commands (to full console ) 3. run reset to clear console Show example in images # Expected behavior When running reset the console should clear like it does but put the next line at the top of the screen. # Actual behavior Used SSH to log into a piece of hardware running linux. When I ran the reset command it clears the screen but adds a blank new line above the terminal line. resizing the terminal from full screen to partial screen then back to full screen does remove some new lines. Seen in Power shell and Ubuntu terminal. ![image](https://user-images.githubusercontent.com/63110047/84912193-2a00f200-b087-11ea-963f-41caa5c7a138.png) ![image](https://user-images.githubusercontent.com/63110047/84912224-36854a80-b087-11ea-8fbd-41b1351f7024.png)
claunia commented 2026-01-31 01:45:32 +00:00
Author
Owner
Copy Link

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

Would you mind sharing the output of...

infocmp | grep "rs[123]"

in a session where reset is acting up?

@DHowett commented on GitHub (Jun 17, 2020): Would you mind sharing the output of... ```bash infocmp | grep "rs[123]" ``` in a session where `reset` is acting up?
claunia commented 2026-01-31 01:45:33 +00:00
Author
Owner
Copy Link

@NathanR1225 commented on GitHub (Jun 17, 2020):

Command was run in Ubuntu terminal

rs1=\Ec\E]104\007, rs2=\E[!p\E[?3;4l\E[4l\E>, sc=\E7,
@NathanR1225 commented on GitHub (Jun 17, 2020): Command was run in Ubuntu terminal ``` rs1=\Ec\E]104\007, rs2=\E[!p\E[?3;4l\E[4l\E>, sc=\E7, ```
claunia commented 2026-01-31 01:45:33 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jun 18, 2020):

This is because AdaptDispatch::EraseInDisplay returns false in conpty mode, which prevents the remaining steps of the AdaptDispatch::HardReset method being executed. That include the cursor position not being reset to 1,1 so the conhost cursor ends up out of sync with the conpty client.

I can't help thinking this passthrough approach is wrong - I mean idea of "failing" in conpty mode as a way to trigger a passthrough. I'm also not convinced that we should be aborting command sequences (like HardReset) on the first failure. I'd much rather we just continued executing everything, and accumulated the failure status.

So instead of:

if (success)
{
    success = _EraseScrollback();
}

we could just have:

success = _EraseScrollback() && success;

That at least should fix this particular problem.

@j4james commented on GitHub (Jun 18, 2020): This is because `AdaptDispatch::EraseInDisplay` returns false in conpty mode, which prevents the remaining steps of the `AdaptDispatch::HardReset` method being executed. That include the cursor position not being reset to 1,1 so the conhost cursor ends up out of sync with the conpty client. I can't help thinking this passthrough approach is wrong - I mean idea of "failing" in conpty mode as a way to trigger a passthrough. I'm also not convinced that we should be aborting command sequences (like `HardReset`) on the first failure. I'd much rather we just continued executing everything, and accumulated the failure status. So instead of: ```cpp if (success) { success = _EraseScrollback(); } ``` we could just have: ```cpp success = _EraseScrollback() && success; ``` That at least should fix this particular problem.
claunia commented 2026-01-31 01:45:33 +00:00
Author
Owner
Copy Link

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

I also find the failure=passthrough behavior somewhat suspect. 😄

@DHowett commented on GitHub (Jun 18, 2020): I also find the failure=passthrough behavior somewhat suspect. :smile:
claunia commented 2026-01-31 01:45:33 +00:00
Author
Owner
Copy Link

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

Thanks for digging into this!

@DHowett commented on GitHub (Jun 18, 2020): Thanks for digging into this!
claunia commented 2026-01-31 01:45:33 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 21, 2020):

:tada:This issue was addressed in #6763, which has now been successfully released as Windows Terminal v1.1.2021.0.🎉

Handy links:

@ghost commented on GitHub (Jul 21, 2020): :tada:This issue was addressed in #6763, which has now been successfully released as `Windows Terminal v1.1.2021.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.1.2021.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 01:45:34 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 22, 2020):

:tada:This issue was addressed in #6763, which has now been successfully released as Windows Terminal v1.1.2021.0.🎉

Handy links:

@ghost commented on GitHub (Jul 22, 2020): :tada:This issue was addressed in #6763, which has now been successfully released as `Windows Terminal v1.1.2021.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.1.2021.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
claunia commented 2026-01-31 01:45:34 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Jul 22, 2020):

:tada:This issue was addressed in #6763, which has now been successfully released as Windows Terminal Preview v1.2.2022.0.🎉

Handy links:

@ghost commented on GitHub (Jul 22, 2020): :tada:This issue was addressed in #6763, which has now been successfully released as `Windows Terminal Preview v1.2.2022.0`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.2.2022.0) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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-VT Help Wanted Issue-Bug Product-Conpty Resolution-Fix-Committed
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#9083
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?