[Bug]: vscodevim extension broken

[f0x52]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Firefox, Chrome (PWA)
• Local OS: Arch Linux
• Remote OS: NixOS Linux
• Remote Architecture: amd64
• code-server --version: 4.0.1

Steps to Reproduce

Install code-server 4.0.1, install vscodevim.vim either through GUI or CLI, reload, extension does not work

Expected

vscodevim.vim extension works

Actual

With code-server 4.0.1, vscodevim gave an error that it was disabled because it was incompatible. However upon reinstalling, no such error comes up, but it does fail to load. This happens when installing through the GUI, and with code-server --install-extension.

Going back to 3.12.0 (my easiest option under NixOS), vscodevim works without issue again.

Logs

No response

Screenshot/Video

No response

Does this issue happen in VS Code?

• I cannot reproduce this in VS Code.

Are you accessing code-server over HTTPS?

• I am using HTTPS.

Notes

No response

[jsjoeio]

This doesn't seem to be an issue in 4.0.2. Please give that a try!

[f0x52]

I'm on 4.0.2 now, the same issue persists. It installs, but doesn't actually work. The status bar does show "Activating Extensions..." after every key combo, but nothing vim-related happens

[f0x52]

there are no errors in the browser devtools. Issue is also reproducible with the extension directory copied over from my local VSCode

[jsjoeio]

@f0x52 hmm...I'm not sure what I can do to help since I can't reproduce it myself. What version of the extension are you usng?

[f0x52]

To make sure it's reproducible I got a clean code-server install, 4.0.2. Installed on NixOS inside a container

Installing the vscodevim.vim through the web manager uses v1.21.10. Installing the extension seems to work without issue, but it doesn't actually do anything. It should change the cursor to a block shape, which doesn't happen, and typing is completely blocked but without any way to switch modes like normal vim/with a working extension. Any key input does trigger an "Activating extension..." in the activity bar, but nothing else happens, maybe there are some logs I could access, that I wasn't able to find?

[jsjoeio]

@f0x52 Hmm...I have two suspicious. Either another extension is conflicting or there is a setting that is conflicting.

Can you share your settings.json here? And can you try with only this extension?