vim acts crazy in recent builds #4391

Closed
opened 2026-01-30 23:45:50 +00:00 by claunia · 2 comments
Owner

Originally created by @darthpale on GitHub (Oct 10, 2019).

Environment

Windows build number: Win32NT             10.0.18362.0 Microsoft Windows NT 10.0.18362.0
Windows Terminal version commit: 200e90d1c64cb8ad3f48b808ac695bac5bb6e696 

Any other software?

Visual Studio Community 2019 16.3.3

Steps to reproduce

vim Terminal\src\cascadia\TerminalApp\TerminalPage.cpp
yank and paste second line.

Expected behavior

pasted line appears text, below scrolls down

Actual behavior

pasted line appears text scrolls up.
At this point there is no consistency between cursor and location in the file.
Hitting "u" to undo even when at the "Already at the oldest change" point removes the text under the cursor and scrolls everything up. leading to multiple copies of the vim status line

Confirms this is a problem even when ssh [-ing] to a remote machine and using vim there not the local windows instance as well.

Last known working commit: 2c8b3243dc Wed Sep 25 22:00:06 2019 -0700

image

Screenshot is after simply hitting "u" 6 times.

Originally created by @darthpale on GitHub (Oct 10, 2019). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> <!-- This bug tracker is monitored by Windows Terminal development team and other technical folks. **Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**. Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue. If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link. Please use this form and describe your issue, concisely but precisely, with as much detail as possible. --> # Environment ```none Windows build number: Win32NT 10.0.18362.0 Microsoft Windows NT 10.0.18362.0 Windows Terminal version commit: 200e90d1c64cb8ad3f48b808ac695bac5bb6e696 Any other software? Visual Studio Community 2019 16.3.3 ``` # Steps to reproduce vim Terminal\src\cascadia\TerminalApp\TerminalPage.cpp yank and paste second line. <!-- A description of how to trigger this bug. --> # Expected behavior pasted line appears text, below scrolls down <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior pasted line appears text scrolls up. At this point there is no consistency between cursor and location in the file. Hitting "u" to undo even when at the "Already at the oldest change" point removes the text under the cursor and scrolls everything up. leading to multiple copies of the vim status line Confirms this is a problem even when ssh [-ing] to a remote machine and using vim there not the local windows instance as well. <!-- What's actually happening? --> **Last known working commit: 2c8b3243dca0c48dd05ecd7b420a7a03b3e19c93 Wed Sep 25 22:00:06 2019 -0700** ![image](https://user-images.githubusercontent.com/48268993/66604133-8a947280-eb7b-11e9-92ed-a54d73cd9bb1.png) Screenshot is after simply hitting "u" 6 times.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-30 23:45:50 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Oct 10, 2019):

This might be related to #3052, actually. If you revert the change from 5d906d9f3e, does it resolve?

@DHowett-MSFT commented on GitHub (Oct 10, 2019): This might be related to #3052, actually. If you revert the change from 5d906d9f3e78a467c1914a1b8b6fde92e7d86090, does it resolve?
Author
Owner

@darthpale commented on GitHub (Oct 11, 2019):

Thanks, yes reverting 5d906d9 fixes this issue for me.

@darthpale commented on GitHub (Oct 11, 2019): Thanks, yes reverting 5d906d9 fixes this issue for me.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#4391