Scrolling Issues while using WSL 2 with Windows Terminal #15660

Closed
opened 2026-01-31 04:44:48 +00:00 by claunia · 4 comments
Owner

Originally created by @soumesh2002 on GitHub (Oct 23, 2021).

Windows Terminal version (or Windows build number)

1.10.2714.0

Other Software

vim inside WSL 2

Steps to reproduce

Screenshot (103)

After I edit my files and write them in vim and I scroll upwards this happens. Please give me a possible fix.

Expected Behavior

Nothing should happen after I edit my files in vim and scroll them upwards.

Actual Behavior

Everything is messed up(e.g. all the characters along with spacing).

Originally created by @soumesh2002 on GitHub (Oct 23, 2021). ### Windows Terminal version (or Windows build number) 1.10.2714.0 ### Other Software vim inside WSL 2 ### Steps to reproduce ![Screenshot (103)](https://user-images.githubusercontent.com/53593544/138569490-1a38c5fd-59d5-4738-b582-4058ab4b3834.png) After I edit my files and write them in vim and I scroll upwards this happens. Please give me a possible fix. ### Expected Behavior Nothing should happen after I edit my files in vim and scroll them upwards. ### Actual Behavior Everything is messed up(e.g. all the characters along with spacing).
claunia added the Resolution-Duplicate label 2026-01-31 04:44:48 +00:00
Author
Owner

@serd2011 commented on GitHub (Oct 24, 2021):

Can't reproduce this in preview 1.12.2931.0

@serd2011 commented on GitHub (Oct 24, 2021): Can't reproduce this in preview 1.12.2931.0
Author
Owner

@soumesh2002 commented on GitHub (Oct 24, 2021):

Can't reproduce this in preview 1.12.2931.0

Thank you for your response, but this happens when whenever I try to edit something with vim, and afterwards when I scroll upwards, everything is messed up

@soumesh2002 commented on GitHub (Oct 24, 2021): > Can't reproduce this in preview 1.12.2931.0 Thank you for your response, but this happens when whenever I try to edit something with vim, and afterwards when I scroll upwards, everything is messed up
Author
Owner

@zadjii-msft commented on GitHub (Oct 24, 2021):

This is gonna sound crazy, but this is a /duplicate of #381. Once we get that working, this should be fixed too. Thanks!

@zadjii-msft commented on GitHub (Oct 24, 2021): This is gonna sound crazy, but this is a /duplicate of #381. Once we get that working, this should be fixed too. Thanks!
Author
Owner

@ghost commented on GitHub (Oct 24, 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 commented on GitHub (Oct 24, 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!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#15660