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

MSYS2 Vim buffer is stuck in the terminal window when scrolling back #11726

Closed
matteocoder opened this issue Nov 10, 2021 · 2 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@matteocoder
Copy link

Windows Terminal version (or Windows build number)

Windows Terminal Preview 1.12.2931.0

Other Software

vim 8.2.3441 (MSYS2 version, from Git Bash),
GNU bash, version 4.4.23(1)-release (x86_64-pc-msys).

Steps to reproduce

Prerequisite:
Create a new profile with the following command line command:

C:\Program Files\Git\bin\bash.exe --norc --noprofile -i -l

and start a new terminal tab using that profile.

  1. Invoke a program, such as yes, whose output scrolls the terminal window, allowing you to scroll back, then press ctrl-c to stop it;
  2. invoke vim, and then issue the command :version;
  3. quit Vim

Expected Behavior

When scrolling back, only the output from yes should be visible.

Actual Behavior

Vim's interface remains "stuck" on the terminal window and mixes with the output of yes. The screenshot shows the issue.

vim stuck

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

Thanks for the suggestion! 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 Nov 10, 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 Nov 10, 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 Nov 10, 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