starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Erratic cursor in VIM(WSL) #7425

New Issue
Closed
opened 2026-01-31 01:03:42 +00:00 by claunia · 16 comments
claunia commented 2026-01-31 01:03:42 +00:00
Owner
Copy Link

Originally created by @blayz3r on GitHub (Apr 15, 2020).

Environment

Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable):

image
image

Any other software?

image

Steps to reproduce

Open Vim in WSL and press j a few times

Expected behavior

Cursor goes down without jumping

Actual behavior

2020-04-15_13-11-23

Originally created by @blayz3r on GitHub (Apr 15, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 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: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd] Windows Terminal version (if applicable): ``` ![image](https://user-images.githubusercontent.com/12205650/79367175-685d2200-7f1b-11ea-9f24-83d1b37a4dc0.png) ![image](https://user-images.githubusercontent.com/12205650/79367188-727f2080-7f1b-11ea-9f8d-cd423d491d35.png) ```none Any other software? ``` ![image](https://user-images.githubusercontent.com/12205650/79367052-32b83900-7f1b-11ea-944a-983224531478.png) # Steps to reproduce <!-- A description of how to trigger this bug. --> **Open Vim in WSL and press j a few times** # Expected behavior <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> **Cursor goes down without jumping** # Actual behavior <!-- What's actually happening? --> ![2020-04-15_13-11-23](https://user-images.githubusercontent.com/12205650/79367368-c558d800-7f1b-11ea-9b4e-f94697fc107e.gif)
claunia commented 2026-01-31 01:03:43 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 15, 2020):

So it looks like you’re not using Windows Terminal, but you’re using the traditional console. What is the box that vim is running in? It looks like another piece of terminal-emulating software?

@DHowett-MSFT commented on GitHub (Apr 15, 2020): So it looks like you’re not using Windows Terminal, but you’re using the traditional console. What is the box that vim is running in? It looks like another piece of terminal-emulating software?
claunia commented 2026-01-31 01:03:44 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (Apr 15, 2020):

That is correct I am starting WSL from a GVIM terminal buffer, the issue was not there in the Legacy bash on windows

Is this a vim issue then?

@blayz3r commented on GitHub (Apr 15, 2020): That is correct I am starting WSL from a GVIM terminal buffer, the issue was not there in the Legacy bash on windows Is this a vim issue then?
claunia commented 2026-01-31 01:03:44 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 15, 2020):

I'd say yea, if this bug doesn't repro in the legacy console (conhost.exe, the window you get by simply launching wsl.exe or cmd.exe), and this doesn't repro in the Windows Terminal, then this doesn't really belong on this repository.

Thanks!

@zadjii-msft commented on GitHub (Apr 15, 2020): I'd say yea, if this bug doesn't repro in the legacy console (conhost.exe, the window you get by simply launching `wsl.exe` or `cmd.exe`), and this doesn't repro in the Windows Terminal, then this doesn't really belong on this repository. Thanks!
claunia commented 2026-01-31 01:03:44 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (Apr 15, 2020):

Thanks!

@blayz3r commented on GitHub (Apr 15, 2020): Thanks!
claunia commented 2026-01-31 01:03:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 15, 2020):

It depends on your gvim terminal mode.

Can you run :set termwintype and report the value? If it's conpty, this may yet be our fault.

@DHowett-MSFT commented on GitHub (Apr 15, 2020): It depends on your gvim terminal mode. Can you run `:set termwintype` and report the value? If it's `conpty`, this may yet be our fault.
claunia commented 2026-01-31 01:03:45 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (Apr 15, 2020):

Thanks for the follow up. I can confirm that termwintype = conpty

image

@blayz3r commented on GitHub (Apr 15, 2020): Thanks for the follow up. I can confirm that termwintype = conpty ![image](https://user-images.githubusercontent.com/12205650/79373673-e7a32380-7f24-11ea-875f-826814108a30.png)
claunia commented 2026-01-31 01:03:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 15, 2020):

Excellent.

@DHowett-MSFT commented on GitHub (Apr 15, 2020): Excellent.
claunia commented 2026-01-31 01:03:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 15, 2020):

So just to confirm, can you give a detailed list of repro steps? I need to know what's running inside what, when and where and how.

It looks like vim on the inside, but also vim on the outside? Is that gvim, or vim? I don't know how to make gvim show a floating popup, so perhaps it's not just gvim?

@DHowett-MSFT commented on GitHub (Apr 15, 2020): So just to confirm, can you give a detailed list of repro steps? I need to know what's running inside what, when and where and how. It looks like vim on the _inside_, but also vim on the outside? Is that gvim, or vim? I don't know how to make gvim show a floating popup, so perhaps it's not just gvim?
claunia commented 2026-01-31 01:03:45 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (Apr 15, 2020):

Sure the steps are below:
Step 1: Start gvim.exe
Step 2: open wsl with

:term wsl

This is my wsl version
image

Step 3: Open a file with vi filename (press j a few times to move the cursor)

@blayz3r commented on GitHub (Apr 15, 2020): Sure the steps are below: **Step 1:** Start gvim.exe **Step 2:** open wsl with ``` vim :term wsl ``` This is my wsl version ![image](https://user-images.githubusercontent.com/12205650/79375421-9b58e300-7f26-11ea-8d2f-e573cd371f27.png) **Step 3:** Open a file with vi filename (press j a few times to move the cursor)
claunia commented 2026-01-31 01:03:45 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 15, 2020):

Excellent, thanks for the info. This is a combination of a couple things:

  1. we're reprinting far too much text, when we don't actually need to. there's a number of changes that fixed this after 19041 came out.
  2. we were not properly hiding the cursor while we were moving it, so you got to see all the ugly cursor jumping that we were doing during number one.

I'll close this one out as fix-committed, for now, because the core issue no longer reproduces (with the latest console bits in the next version of windows.)

Thanks for bearing with us!

@DHowett-MSFT commented on GitHub (Apr 15, 2020): Excellent, thanks for the info. This is a combination of a couple things: 1. we're reprinting far too much text, when we don't actually need to. there's a number of changes that fixed this after 19041 came out. 2. we were not properly hiding the cursor while we were moving it, so you got to see _all_ the ugly cursor jumping that we were doing during number one. I'll close this one out as fix-committed, for now, because the core issue no longer reproduces (with the latest console bits in the next version of windows.) Thanks for bearing with us!
claunia commented 2026-01-31 01:03:46 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (Apr 15, 2020):

Thanks for the quick turnaround. The Terminal App and WSL are awesome btw

@blayz3r commented on GitHub (Apr 15, 2020): Thanks for the quick turnaround. The Terminal App and WSL are awesome btw
claunia commented 2026-01-31 01:03:46 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 15, 2020):

Thanks! 😄

@DHowett-MSFT commented on GitHub (Apr 15, 2020): Thanks! :smile:
claunia commented 2026-01-31 01:03:46 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (May 13, 2020):

What Windows10 build will the fix go in

@blayz3r commented on GitHub (May 13, 2020): What Windows10 build will the fix go in
claunia commented 2026-01-31 01:03:46 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 14, 2020):

I cannot commit to the dates for any upcoming Windows releases. Sorry.

@DHowett-MSFT commented on GitHub (May 14, 2020): I cannot commit to the dates for any upcoming Windows releases. Sorry.
claunia commented 2026-01-31 01:03:46 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (May 14, 2020):

No problem. Just curious

@blayz3r commented on GitHub (May 14, 2020): No problem. Just curious
claunia commented 2026-01-31 01:03:47 +00:00
Author
Owner
Copy Link

@blayz3r commented on GitHub (Jul 12, 2020):

I still have this issue

@blayz3r commented on GitHub (Jul 12, 2020): I still have this issue
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Performance Issue-Bug Needs-Attention Product-Conpty Resolution-Fix-Committed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#7425
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?