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

Previous command disappears from the terminal output when it fills the current terminal height #17130

New Issue
Closed
opened 2026-01-31 05:32:58 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 05:32:58 +00:00
Owner
Copy Link

Originally created by @danilaml on GitHub (Apr 1, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19043.0

Other Software

No response

Steps to reproduce

I've first discovered this issue in VS Code and described it (with the gifs and steps to reproduce) here: https://github.com/microsoft/vscode/issues/146450
I was able to reproduce it in the latest Windows Terminal.

Expected Behavior

When scrolling back the command output is delimited by the commands themselves.
image

Actual Behavior

The problematic command disappears from the output, "merging" the two commands stdout together (in the images below the output after the empty line was generated by python -c "print('foo\n' * 27)").
image
image

Originally created by @danilaml on GitHub (Apr 1, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19043.0 ### Other Software _No response_ ### Steps to reproduce I've first discovered this issue in VS Code and described it (with the gifs and steps to reproduce) here: https://github.com/microsoft/vscode/issues/146450 I was able to reproduce it in the latest Windows Terminal. ### Expected Behavior When scrolling back the command output is delimited by the commands themselves. ![image](https://user-images.githubusercontent.com/2046350/161256507-bbdb2b6d-b099-405c-ba6d-6491f6447f06.png) ### Actual Behavior The problematic command disappears from the output, "merging" the two commands stdout together (in the images below the output after the empty line was generated by `python -c "print('foo\n' * 27)"`). ![image](https://user-images.githubusercontent.com/2046350/161256642-baacfbf5-8c7a-4fa7-ad34-7538a3d4cd63.png) ![image](https://user-images.githubusercontent.com/2046350/161255838-bbb56806-764c-43e6-a4ba-09bfa1dfb734.png)
claunia commented 2026-01-31 05:33:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 1, 2022):

What do you have in your PowerShell profile?

@zadjii-msft commented on GitHub (Apr 1, 2022): What do you have in your PowerShell profile?
claunia commented 2026-01-31 05:33:02 +00:00
Author
Owner
Copy Link

@danilaml commented on GitHub (Apr 1, 2022):

@zadjii-msft path returned by $profile doesn't seem to exist so I assume nothing. Note, that I wasn't able to reproduce this issue in the standalone powershell (makes sense, if it's conpty issue). I've tested on two different machines too (same Win version).

@danilaml commented on GitHub (Apr 1, 2022): @zadjii-msft path returned by `$profile` doesn't seem to exist so I assume nothing. Note, that I wasn't able to reproduce this issue in the standalone powershell (makes sense, if it's conpty issue). I've tested on two different machines too (same Win version).
claunia commented 2026-01-31 05:33:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 12, 2022):

This is crazy, and I can't seem to repro this at all, despite the repro steps being pretty straightforward. If this were a conpty issue, then maybe we fixed it between 1.11 and 1.15? But nothing immediately comes to mind...

@zadjii-msft commented on GitHub (Aug 12, 2022): This is crazy, and I can't seem to repro this at all, despite the repro steps being pretty straightforward. If this were a conpty issue, then maybe we fixed it between 1.11 and 1.15? But nothing immediately comes to mind...
claunia commented 2026-01-31 05:33:02 +00:00
Author
Owner
Copy Link

@danilaml commented on GitHub (Aug 12, 2022):

I can still reproduce it in Terminal 1.14.1962.0 (and different versions of VS Code) and Windows 10.0.19044.0 on several machines. Make sure that the output of the command is exactly long enough for the executed command to be at the topmost line after it's done.

@danilaml commented on GitHub (Aug 12, 2022): I can still reproduce it in Terminal 1.14.1962.0 (and different versions of VS Code) and Windows 10.0.19044.0 on several machines. Make sure that the output of the command is exactly long enough for the executed command to be at the topmost line after it's done.
claunia commented 2026-01-31 05:33:02 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 15, 2022):

Maybe it's a timing thing then? Cause I couldn't get this to repro even on a 1.10 build of the Terminal. Maybe it really needs all the output to come in a single conpty frame, and my hardware is just too fast for that.

@zadjii-msft commented on GitHub (Aug 15, 2022): Maybe it's a timing thing then? Cause I couldn't get this to repro even on a 1.10 build of the Terminal. Maybe it really needs all the output to come in a single conpty frame, and my hardware is just too fast for that.
claunia commented 2026-01-31 05:33:03 +00:00
Author
Owner
Copy Link

@danilaml commented on GitHub (Aug 15, 2022):

Are you testing on Win10? Is HW acceleration enabled (I haven't verified that it is or not in my case, but I assume it's the same across the board since I haven't changed any defaults)? There is no timing at play, as far as I can tell. I can wait 10-15 seconds between running commands and the result is the same. The reproducibility rate is 100%. I've also run it on 3 reasonably powerful machines (2-core HT ultrabook, 6-core HT laptop and 4-core Desktop). Is there anything else I can provide to help move this issue?

@danilaml commented on GitHub (Aug 15, 2022): Are you testing on Win10? Is HW acceleration enabled (I haven't verified that it is or not in my case, but I assume it's the same across the board since I haven't changed any defaults)? There is no timing at play, as far as I can tell. I can wait 10-15 seconds between running commands and the result is the same. The reproducibility rate is 100%. I've also run it on 3 reasonably powerful machines (2-core HT ultrabook, 6-core HT laptop and 4-core Desktop). Is there anything else I can provide to help move this issue?
claunia commented 2026-01-31 05:33:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 9, 2023):

Hey we think this might be a known issue in older versions of PsReadline: https://github.com/PowerShell/PSReadLine/issues/724

Does this repro if you Remove-Module PsReadline (or update it) (or just run the command from a Command Prompt profile)/?

I can't believe I didn't catch that before!

@zadjii-msft commented on GitHub (Aug 9, 2023): Hey we think this might be a known issue in older versions of PsReadline: https://github.com/PowerShell/PSReadLine/issues/724 Does this repro if you `Remove-Module PsReadline` (or update it) (or just run the command from a Command Prompt profile)/? I can't believe I didn't catch that before!
claunia commented 2026-01-31 05:33:03 +00:00
Author
Owner
Copy Link

@danilaml commented on GitHub (Aug 9, 2023):

@zadjii-msft hi. PSReadline seems to be impossible to remove from my machine (or to cleanly update due to name change for that matter) and I don't know if I can safely delete its folder in C:\Program Files\WindowsPowerShell\Modules but after I've installed 2.2.6 side-by-side it seems to have gone away (unable to reproduce).

@danilaml commented on GitHub (Aug 9, 2023): @zadjii-msft hi. PSReadline seems to be impossible to remove from my machine (or to cleanly update due to name change for that matter) and I don't know if I can safely delete its folder in `C:\Program Files\WindowsPowerShell\Modules` but after I've installed 2.2.6 side-by-side it seems to have gone away (unable to reproduce).
claunia commented 2026-01-31 05:33:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Aug 9, 2023):

Well that sure is wacky! Alas, I'm not the powershell expert so I can't help with that, but hey, glad it went away?

@zadjii-msft commented on GitHub (Aug 9, 2023): Well that sure is wacky! Alas, I'm not the powershell expert so I can't help with that, but hey, glad it went away?
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-Rendering Help Wanted Issue-Bug Needs-Attention Needs-Triage Priority-2 Product-Conpty
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#17130
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?