Vim: Plugin no longer works on 1.40.2

[disposedtrolley]

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:

1. Install version 1.40.2 of VS Code (currently the latest)
2. Install the Vim plugin
3. Observe that Vim bindings aren't active
4. 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

[Sphish]

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

[yujinyuz]

Same thing happened to me. Good thing I went here. I've been trying to figure it out what went wrong on my configuration

[hebbian]

Same here, it suddenly can't work properly

[disposedtrolley]

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

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

[yeuem1vannam]

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

[Sphish]

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?

[disposedtrolley]

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 [email protected]

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

[machsix]

error shown in console for v1.12.0:
`` console.ts:137 [Extension Host] Activating extensionvscodevim.vim` failed: Cannot find module './../actions/commands/actions'
Require stack:

• 
  ···

Downgrade to 1.11.3 works

[MMMMMMoSky]

I reinstall the whole VSCode and it doesn't work still...
macOS.
It seems I have to downgrade.

[ajeeb-kp-keleno]

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.

[dkasuga]

I solved the problem by downgrading the version to 1.11.3 on local machine, but I can't still solve the same problem on remote development ssh. Does anyone else have the same problem?

[micuffaro]

Mac OSX Catalina, Solved the issue by downgrading vscodevim to 1.11.3 for the time being.

[waitingsong]

vscode v1.40.0 also has this issue.

[fsoft72]

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 [email protected]

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

This worked for me, but the first line is:

rm -rf ~/.vscode/extensions/vscodevim.vim-*

[bmight]

I was having issues getting the "Install Another Version" menu to show on Win10. I used the CLI command to install 1.11.3. It would auto update itself to 1.12.0 but as long as I didn't reload VS Code I could access the "Install Another Version" menu.

[DominikGorecki]

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

[aaronbbrown]

Same problem. Downgrading to 1.11.3 worked for me.

[DianeLooney]

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?

[tort-dla-psa]

Same issue on centos and arch. Made it quite hard to work today :C

[ChenguangZhang]

Glad to see many sharing the problem, at least my keyboard is not broken -_-'' (Linux Mint 19.2). Downgrading is the solution for now.

[Reshurum]

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

[rebornix]

Fixed in 1.12.1, sorry for the trouble.

[halfcreative]

It is not working 1.12.1, Windows 10

[optimus-bret]

1.12.1 isn't working for Mac either!

[Vinnl]

@rebornix It doesn't appear to be fixed on Ubuntu 18.04 either, on VSCode 1.40.2.

[rebornix]

There are still some issues ppl are seeing now, let's track it in https://github.com/VSCodeVim/Vim/issues/4342#issuecomment-563338094.

[robinsturmeit]

Looked not fixed for me, too, but actually the error is different now: It
fails to read my .vimrc (which is actually a Neovim init.vim).
Deactivating .vimrc makes it work again.

On Mon, Dec 9, 2019 at 5:08 PM Vincent [e-mail] wrote:

@rebornix https://github.com/rebornix It doesn't appear to be fixed on
Ubuntu 18.04 either, on VSCode 1.40.2.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/VSCodeVim/Vim/issues/4340?email_source=notifications&email_token=AJUGR2WSEB3UOWONRAN7RZ3QXZ3RVA5CNFSM4JYDR7J2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGJ5M7A#issuecomment-563336828,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJUGR2SVK3ICLKHN7IUKFJDQXZ3RVANCNFSM4JYDR7JQ
.

--
http://invisionapp.com/enterprise

Robin Sturmeit
Tools EngineerInVision (InVision: Better Products Faster)
p. [phone]
Visit our Newsroom https://www.invisionapp.com/news for the latest on
InVision!

[rebornix]

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

[robinsturmeit]

@rebornix Sorry for the delay. Can confirm that this is fixed. Thank you for the super-fast turn-around!

[stouf]

The issue got fixed in v1.12.2 for me as well. Thank you for taking quick actions, it's much appreciated 🙂

[colbycheeze]

Issue is not fixed. I've tried multiple versions of VSCode, and multiple versions of the VIM plugin. All fail within 5~ minutes with extension host terminated.

Is there any other way to get this working?

[J-Fields]

@colbycheeze Have you deleted the extension folder?

[colbycheeze]

@J-Fields No, I only have one version in the folder. If I disable the vim plugin I do not get the crashes so I've singled it down to just this plugin.