Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buffer goes missing when using powershell #2410

Closed
Tyriar opened this issue Aug 12, 2019 · 6 comments
Closed

Buffer goes missing when using powershell #2410

Tyriar opened this issue Aug 12, 2019 · 6 comments
Labels
Needs-Tag-Fix Doesn't match tag requirements Resolution-External For issues that are outside this codebase

Comments

@Tyriar
Copy link
Member

Tyriar commented Aug 12, 2019

Environment

Windows build number: 10.0.18956.1000
Windows Terminal version (if applicable): 0.3.2171.0
Happens in VS Code too

Steps to reproduce

  1. Run or launch a powershell terminal
  2. Press enter a bunch of times (echo also triggers the behavior)

Expected behavior

Scrollback/scroll bar should appear

Actual behavior

No scroll bar

ps

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Aug 12, 2019
@Tyriar
Copy link
Member Author

Tyriar commented Aug 12, 2019

Running ls will make a scroll bar appear.

@Tyriar
Copy link
Member Author

Tyriar commented Aug 12, 2019

This happens if you have scroll back as well, enter just redraws the entire screen or something, rather than actually pushing a row up. So the top viewport lines just go missing.

@DHowett-MSFT
Copy link
Contributor

This is actually PowerShell/PSReadLine#724. Shipping versions of PSReadline are emitting the destructive "scroll" VT sequence.

@DHowett-MSFT DHowett-MSFT added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. labels Aug 12, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 12, 2019
@DHowett-MSFT DHowett-MSFT added Needs-Tag-Fix Doesn't match tag requirements Resolution-External For issues that are outside this codebase labels Aug 12, 2019
@binaryfunt
Copy link

Should I still be experiencing this bug? It only occurs when running Powershell in Terminal, and according to Get-Module -ListAvailable, I have

ModuleType Version    Name
---------- -------    ----
...
Script     2.0.0      PSReadline

Is there a fix/workaround?

@zadjii-msft
Copy link
Member

Honestly I don't think I fully understand PSReadline versioning - I think from this diff it was fixed in PSReadline v2.0.0-beta4, but I'm not sure if that means it's in 2.0.0 or not.

@DHowett-MSFT should be able to clear things up for me.

I'm pretty sure you shouldn't be seeing this anymore.

@Tyriar
Copy link
Member Author

Tyriar commented Apr 13, 2020

I was confused by this as well recently, in PS6 prerelease info doesn't show up but you can get it via:

Get-Module PSReadLine | % { $_.PrivateData.PSData }

Apparently PS7 shows prerelease info when you run Get-Module PSReadLine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs-Tag-Fix Doesn't match tag requirements Resolution-External For issues that are outside this codebase
Projects
None yet
Development

No branches or pull requests

4 participants