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

Bad formatting in Windows after exiting vim over ssh #18638

Open
DanielViberg opened this issue Feb 27, 2025 · 2 comments
Open

Bad formatting in Windows after exiting vim over ssh #18638

DanielViberg opened this issue Feb 27, 2025 · 2 comments
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@DanielViberg
Copy link

DanielViberg commented Feb 27, 2025

Windows Terminal version

1.21.10351.0

Windows build number

10.0.19045.0

Other Software

VIM - Vi IMproved 9.1 (2024 Jan 02, compiled Feb 26 2025 16:35:59)
Included patches: 1-1151
OpenSSH_for_Windows_9.5p1, LibreSSL 3.8.2

Steps to reproduce

  1. From a linux machine, running gnome-terminal or foot
  2. ssh to windows 10 machine
  3. Start vim 9.1
  4. Exit vim 9.1 with :q!
  5. Observer vim graphical artifacts still in the bottom of the window

Image

  1. Resize the window and they go away

Script log:
out.log

Expected Behavior

No vim artifacts after exiting.

Actual Behavior

Vim artifacts left after exiting.

@DanielViberg DanielViberg added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 27, 2025
Copy link

We've found some similar issues:

If any of the above are duplicates, please consider closing this issue out and adding additional context in the original issue.

Note: You can give me feedback by 👍 or 👎 this comment.

@DHowett
Copy link
Member

DHowett commented Feb 27, 2025

Team notes: I directed Daniel here from the vim repo :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants