Broken navigation with VSCode VIM

[Krakazybik]

In version 0.17.0, Vim navigation is broken: the cursor moves to the same position every time INSERT mode is activated.

It might be related to: #397.

Screen.Recording.2025-02-11.at.20.31.04.mov

The following setting is configured:

"files.autoSaveDelay": 10000

Steps to reproduce:

1. Start editing text.
2. Switch to any other window (with the setting to save on window change) or wait for auto-save.
3. Enter INSERT mode at any position.

Expected result:

The cursor in INSERT mode remains at the same position as in NORMAL mode.

Actual result:

The cursor always moves to the same saved position.

[SunsetTechuila]

hello, I think I understand the issue, but I'm unable to reproduce it

could you please test this change: https://github.com/editorconfig/editorconfig-vscode/tree/delay-newline?

EditorConfig-0.17.1.txt (extension changed to .txt because github doesn't allow to send vsix files, should be renamed back to EditorConfig-0.17.1.vsix)

alternatively you can build it yourself: git clone & npm i & npx vsce package and you will have a vsix file

[Krakazybik]

Checked EditorConfig-0.17.1, the issue is fixed.

[SunsetTechuila]

Thank you

[YazminMelgoza]

I was having this same issue.

[SunsetTechuila]

proper fix requires microsoft/vscode#241075 to be resolved

see #410 (comment)

[diegodorado]

@SunsetTechuila , I am confused... does version 0.17.1 fix the issue? or is microsoft/vscode#241075 required?

meanwhile i just disabled the extension b/c the editor is unusable in this state.

thanks!

[SunsetTechuila]

I am confused... does version 0.17.1 fix the issue

kinda, I suggest you to install one of the older versions instead

or is microsoft/vscode#241075 required?

for a proper fix - yes. I have already opened a PR to VSCode to resolve this issue

[Spongman]

why not just revert whatever change since 0.17.1 broke the extension, release it, and then release whatever the 'proper' fix is when vscode has released that?

[SunsetTechuila]

v0.16.7 & v0.17.0 introduced different issues while trying to fix #330. I don't think it makes sense to revert those changes to reopen the original issue. PR has been already merged