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

Less Pollutes Scrollback Buffer in WSL/Ubuntu #5193

Closed
lvfrazao opened this issue Mar 31, 2020 · 3 comments
Closed

Less Pollutes Scrollback Buffer in WSL/Ubuntu #5193

lvfrazao opened this issue Mar 31, 2020 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@lvfrazao
Copy link

Environment

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

Any other software?
WSL v1
less 
$ less --version
less 487 (GNU regular expressions)
Copyright (C) 1984-2016  Mark Nudelman

less comes with NO WARRANTY, to the extent permitted by law.
For information about the terms of redistribution,
see the file named README in the less distribution.
Homepage: http://www.greenwoodsoftware.com/less

Steps to reproduce

  1. Generate file with random text (enough lines to fill up the screen): $ head -1000 /dev/urandom | tr -dc A-Za-z0-9 > rand.txt
  2. Fill scrollback with content: $ for i in {1..100}; do echo $i; done;
  3. Open file with random text with less: $ less rand.txt
  4. Use the down arrow or pgdn keys to scroll down a bit
  5. Exit less and scroll up

Expected behavior

Scrolling up shows input and output from previous terminal commands.

Actual behavior

Scrolling up shows the lines that were viewed in less and overwrites the previous output.

wt_issue

This may be a duplicate of: #3492

@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 Mar 31, 2020
@lvfrazao
Copy link
Author

Slightly more info, this happens with less, but not with vim or nano.

Would appreciate any known workarounds as this makes working in the terminal rather difficult as I basically lose the ability to review previous output anytime I use less.

@zadjii-msft
Copy link
Member

Thanks for the report! This is actually already being tracked by another issue on our repo - please refer to #4676 for more discussion.

/dup #4676

(Apparently that one's actually a dupe of the root cause over in #381)

@ghost
Copy link

ghost commented Mar 31, 2020

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Mar 31, 2020
@ghost ghost 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 Needs-Tag-Fix Doesn't match tag requirements labels Mar 31, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants