Vim: Plugin no longer works on 1.40.2

Describe the bug I reloaded my VSCode workspace today (which presumably caused it to upgrade to 1.40.2) which seems to have broken the Vim extension.

I’ve tried completely reinstalling VS Code to no avail.

To Reproduce Steps to reproduce the behavior:

Install version 1.40.2 of VS Code (currently the latest)
Install the Vim plugin
Observe that Vim bindings aren’t active
Run Toggle Vim Mode in the command palette. Observe that the error message command 'toggleVim' not found appears

Expected behavior Vim bindings should be active.

Environment (please complete the following information):

Extension (VsCodeVim) version: 1.12.0
VSCode version: 1.40.2
OS: macOS 10.14.6

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 214
Comments: 35 (5 by maintainers)

Most upvoted comments

There is a setting icon for each extensions in the extension side bar. Click it and you will find “Install Another Version”

What’s the easiest way to downgrade? Is there a CLI command we can run?

+88

sphish on Dec 9, 2019

There is a command here microsoft/vscode#12764 (comment) but I have to remove the extensions manually from ~/.vscode/extensions

Thanks! Running the below works for me:

rm -rf ~/.vscode/vscodevim.vim-1.12.0
code --install-extension vscodevim.vim@1.11.3

Edit: you should probably do what @Sphish suggested, otherwise VS Code will try to automatically upgrade the plugin again.

+22

disposedtrolley on Dec 9, 2019

I have the same issue in Win10. And I downgrade vim plugin to 1.11.3, then it works.

+22

sphish on Dec 9, 2019

@robinsturmeit you can try latest 1.12.2 which should fix this problem.

+16

rebornix on Dec 9, 2019

Fixed in 1.12.1, sorry for the trouble.

+15

rebornix on Dec 9, 2019

I have the same issue in Win10. And I downgrade vim plugin to 1.11.3, then it works.

I have same issue in Debian GNU/Linux bullseye/sid. And it works, after I downgrade to 1.11.3 (I clicked that settings button near VSCodeVim, then I used Install Another version) and restart VSCode.

+14

ajeeb-kp-keleno on Dec 9, 2019

Same problem. Downgrading to 1.11.3 worked for me.

aaronbbrown on Dec 9, 2019

Same to me here. Just start a new container and VSCode Vim no longer works

What’s the easiest way to downgrade? Is there a CLI command we can run?

There is a command here https://github.com/microsoft/vscode/issues/12764#issuecomment-442370545 but I have to remove the extensions manually from ~/.vscode/extensions

yeuem1vannam on Dec 9, 2019

Same problem, running master locally worked for me. I think it was solved for me by https://github.com/VSCodeVim/Vim/pull/4337 . Could we perhaps get a minor release so we could get these issues resolved?

DianeLooney on Dec 9, 2019

1.12.1 isn’t working for Mac either!

optimus-bret on Dec 9, 2019

It is not working 1.12.1, Windows 10

halfcreative on Dec 9, 2019

I can confirm I have the problem with extension version 1.12.0. Problem is not present in 1.11.3.

Version: 1.40.2 Commit: f359dd69833dd8800b54d458f6d37ab7c78df520 Date: 2019-11-25T14:54:40.719Z Electron: 6.1.5 Chrome: 76.0.3809.146 Node.js: 12.4.0 V8: 7.6.303.31-electron.0 OS: Linux x64 4.15.0-70-generic

Amdrel on Dec 9, 2019

Same issue on 1.12

My version of VSCODE

Version: 1.40.2 (user setup) Commit: f359dd69833dd8800b54d458f6d37ab7c78df520 Date: 2019-11-25T14:54:45.096Z Electron: 6.1.5 Chrome: 76.0.3809.146 Node.js: 12.4.0 V8: 7.6.303.31-electron.0 OS: Windows_NT x64 10.0.17134

DominikGorecki on Dec 9, 2019