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

Vim leaves text in the terminal #10745

Closed
vivekananthrp opened this issue Jul 21, 2021 · 2 comments
Closed

Vim leaves text in the terminal #10745

vivekananthrp opened this issue Jul 21, 2021 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@vivekananthrp
Copy link

Windows Terminal version (or Windows build number)

Windows Terminal 1.8.1521.0

Other Software

Windows 10 (Version 10.0.19042 Build 19042) with WSL2 Ubuntu 20.04.
Vim (8.1.2269)

Steps to reproduce

When I open text files using Vim (8.1.2269) inside WSL2 Ubuntu 20.04, it leaves behind chunks of text from the text file in the terminal.

Steps to reproduce the issue:

  1. Open windows terminal and open a tab with Ubuntu 20.04
  2. Open a text file with enough lines for scrolling
  3. Use keys pg-up / pg-down / g (to reach top) / G (to reach bottom) / scroll through the file using trackpad
  4. Close Vim (using :q)
  5. Scroll up the terminal
  6. Chunks of text from the file appears in the terminal

The above issue doesn't happen if I just use the up-arrow or the down-arrow for navigating through the file inside Vim.

Attaching a screen recording of the above-described issue.

2021-07-21-190049_Trim.mp4

Expected Behavior

Text from Vim should not be seen in the terminal.

Actual Behavior

Text from Vim appears in the terminal, when you scroll-up after closing Vim.

@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 Jul 21, 2021
@zadjii-msft
Copy link
Member

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

/dup #381

@ghost
Copy link

ghost commented Jul 21, 2021

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 Jul 21, 2021
@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 Jul 21, 2021
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