VSCodeVim
Vim cursor does not move with "Go to Next Problem" - Reopening: #5746
Hi, I want to re-open a bug report: Vim cursor does not move with "Go to Next Problem" #5746
The problem is that after "Go to Next Problem" the vim cursor is not updated accordingly. Thus any hjkl movement will take place at the old cursor position.
This was fixed several years ago but the problem seems to come back consistently.
Would be great to have this resolved!
A possible, even not ideal solution, could be found here: https://github.com/VSCodeVim/Vim/issues/5746#issuecomment-2205307612
Yep, definitely a regression. Pretty high on the frustration scale. This seems to have been broken in the last release (1.91.0), had been resolved for years prior as mentioned above.
Note that the workaround above, as mentioned in the linked comment, has significant drawbacks - every time you go to next problem, you lose registry, undo history, etc. Vim effectively resets.
Not a knock on the workaround, just want to make it clear that this is a significant issue without a tenable workaround.
Also note that this bug doesn't occur after the editor is first opened (or after the extension is restarted). But after a bit the bug surfaces. Not sure what action or series of actions causes it, will update if I notice a pattern.
Current workaround: This pops up every hour or so, so I hit Developer: Restart Extension Host in the command palette when it does to fix. Makes it livable, although still pretty frustrating, until a fix is released.
I switched from Copilot to Supermaven and this stopped happening. Not certain that was what did it, but that's the only big change I'm aware of. Curious if anyone else would try turning off Copilot or using something else for a bit to see if it fixes it for them as well.
Update 07/20: still hasn't happened. I think it's copilot.
Confirming that disabling the Copilot extension fixed it for me. Also fixes a similar symptom where Ctrl-f search would drop the cursor back to where it started after <Esc>ing out of the search.
...I hit
Developer: Restart Extension Hostin the command palette when it does to fix...
Confirmed this resolves the issue for me.
Feels like a memory leak, keeps getting worse until you restart the server.
Current workaround: This pops up every hour or so, so I hit Developer: Restart Extension Host in the command palette when it does to fix. Makes it livable, although still pretty frustrating, until a fix is released.
Personally I just toggle Vim off and on (run Vim: Toggle Vim Mode twice, keybound to ctrl+cmd+V). I find that a little smoother than restarting the whole extension host (which restarts all your extensions)
And yeah I experience this issue at least a few times a day these days
Been using cursor for a few months and haven't had this issue once, so I really believe it's copilot specific.