Broken with new release #2322

delgermurun · 2018-01-23T09:32:10Z

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG

What happened: Suddenly stopped working. So I checked repo. Seems like new version released. Couldn't switch into normal mode.

Environment: Mac OS

Extension (VsCodeVim) version: 0.10.12
VSCode version: 1.19.2
OS version: MacOS 10.13.2

rogerwelin · 2018-01-23T09:37:59Z

experienced the same issue

r6203 · 2018-01-23T09:39:00Z

I'm running into this issue as well.

I tried to downgrade the extension by manually install an older release.

v0.10.11 works but only when reloading vscode the first time (after manually installing it).

After the 2nd reload of the editor (by installing another extension or opening and closing the editor), vim stops working.

edit: After restarting the editor, vim still works fine (v0.10.11) but installing another extension or theme, and clicking "reload" kills it.

pyrox18 · 2018-01-23T09:40:27Z

Having the same problem as well. The mode indicator in the status bar is missing, which might indicate that the extension isn't running at all. I'm using v0.10.12 of the extension, VS Code v1.19.2 and macOS 10.13.2.

masiqi · 2018-01-23T09:42:23Z

same issue on my macOS

ChenXiyu · 2018-01-23T09:42:44Z

getting this issue as well

qianliu013 · 2018-01-23T09:44:41Z

the same issue on my win10

jlelong · 2018-01-23T09:44:49Z

The Developer Tools Console says that the extension is not loaded with the message
Cannot read property 'overrideCopy' of undefined.

17hz · 2018-01-23T09:45:13Z

the same issue on my ubunutu16.04 ,cant toggle vim mode

takano-ex · 2018-01-23T09:45:49Z

Same with me here.
Deleting ~/.vscode/ folder and re-installing VSCode doesn't fix the issue.

OSX 10.13.2
VSCode 1.19.2
VSCodeVim 0.10.12

fernando-faubell · 2018-01-23T09:46:19Z

Same issue on my Ubuntu 17.10

sample-usr · 2018-01-23T09:46:43Z

Already reported on #2321 , @jpoon is airborne right now, will fix it as soon as he lands (in apprx. 2hours)

jlelong · 2018-01-23T09:47:38Z

@r6203 you need to set extensions.autoUpdate to false to stick to a former version of an extension.

baurine · 2018-01-23T09:48:09Z

just happened to me when I restart the mac.

jon301 · 2018-01-23T09:50:58Z

If you're in a hurry and can't wait for the fix : downgrade to vscode-vim 0.10.11

set "extensions.autoUpdate" to false in your user settings
uninstall vscode-vim 0.10.12
download vscode-vim 0.10.11 VSIX file : https://github.com/VSCodeVim/Vim/releases
in vscode, ctrl+shift+p > Install from VSIX > Choose vscode-vim 0.10.11 VSIX file
restart vscode

This worked for me.

soupdiver · 2018-01-23T10:02:10Z

Just installed on a fresh Linux Mint 18 install.
When trying to toggle vim mode I get an error saying command 'toggleVim' not found. It's maybe related

jroboyd · 2018-01-23T10:05:20Z

I think some more testing is required?

Inndy · 2018-01-23T10:24:50Z

Same issue here.

Extension (VsCodeVim) version: 0.10.12
VSCode version: 1.20.0-insider
OS version: macOS 10.13.2

stormpat · 2018-01-23T10:26:06Z

Same here. Thanks to @jon301 for the quick fix. 👍

mpseidel · 2018-01-23T10:43:58Z

@jon301 thanks for the quick fix - I live on that extension - thanks guys for all the work you put into it ❤️

TomLingham · 2018-01-23T10:52:13Z

Yup, it broked......... toggleVim "command not found" when trying to enable manually, and no other errors apart from that. Mac OS.

sus007 · 2018-01-23T10:52:54Z

And here I was...about to do a clean install of the VSCode. 😁

JasonAsmk · 2018-01-23T10:53:14Z

I almost had a panic attack 😄 . Shit happen sometimes. Chill guys they gonna fix it ❤️ . Till then use @jon301 's workaround.

valleybay · 2018-01-23T10:56:48Z

This was such a mindfuck. Even though I realised it was broken, I was constantly pressing h,j,k,l, etc. It really is impossible to live without VIm. Thanks for the fix ❤️

chiuan · 2018-01-23T11:14:55Z

experienced the same issue

marisudris · 2018-01-23T11:17:54Z

Same issue on
VSCodeVim 0.10.12
VSCode 1.19.2
Debian 9.0.3

Woulda saved myself alot of trouble (reinstalling vscode, extensions etc.) if I saw this thread an hour ago lol

StoyanIvanovI · 2018-01-23T11:42:35Z

Wish I found that issue before nuking my VSCode install and wrecking my sync setup.

jpoon · 2018-01-23T12:17:55Z

Dupe issue of #2321. I just got to my hotel room, PR #2324 is incoming and as soon as that passes build/test, I'll push a new release out. Sorry for the inconvenience.

As @jon301 mentioned, if you want to run a different version of the extension, all of the versions are available https://github.com/VSCodeVim/Vim/releases. Download the one you want and drag+drop onto VSCode.

pgoodjohn · 2018-01-23T12:37:30Z

0.10.13 works perfectly on macOS!
Thanks for the super quick fix 🙌

weiaicunzai · 2018-01-23T12:38:06Z

same here , no mode bar, nothing, just like this vim extension was not installed at all, Im using ubuntu 16.04 and vscode Version 1.19.2
PS: update my vscode doesnt help , plz fix this

bigface008 · 2018-01-23T12:48:51Z

v0.10.13works in the right way. Thanks for the fix!:+1:

jpoon · 2018-01-23T12:48:56Z

@pgoodjohn, thanks for validating. Not sure why the tests didn't catch that as this type of error should hit most of the tested code paths.

Now, time to explore the streets of Barcelona! 🇪🇸 If anybody's around here, I will buy you a ☕️ as an apology.

mirsking · 2019-02-25T06:40:40Z

It occur again after upgrading to v1.1.0 release.
Downgrade to v1.0.8 fix this.

pgoodjohn · 2019-02-25T08:43:59Z

It occur again after upgrading to v1.1.0 release.
Downgrade to v1.0.8 fix this.

I'm running 1.1.0 on VSCode 1.31.1 on MacOS and everything is fine

mirsking · 2019-02-25T09:33:45Z

It occur again after upgrading to v1.1.0 release.
Downgrade to v1.0.8 fix this.

I'm running 1.1.0 on VSCode 1.31.1 on MacOS and everything is fine

I'm running vscode 1.31.1 on ubuntu18.04, and v1.1.0 is auto updated by vscode in background.

tskj · 2019-02-25T10:22:47Z

I'm having this issue on 1.1.0 on MacOS.

Edit: Upgrading from VSCode 1.30.2 to 1.31.1 solved it for me.

max-frai · 2019-04-30T13:05:03Z

Same problem on 1.33.1 and mode is stuck in normal with block cursor visualization.

mariomeissner · 2019-05-01T09:59:39Z

VSCode 1.33.1 and Vim 1.7.0, same problem.
Edit: Downgrading both to VSCode 1.31.1 and Vim 1.1.0 solved the issue, but obviously not ideal.

vv13 · 2019-12-09T05:50:45Z

experienced the same issue

same problem on:
Extension (VsCodeVim) version: 1.12.0
VSCode version: 1.40.2
OS version: macOS 10.15.1

calys · 2019-12-09T08:56:03Z

Same here:

Extension (VsCodeVim) version: 1.12.0
VSCode Version: 1.40.2 (user setup)
OS: Windows_NT x64 10.0.17763

Shahor · 2019-12-09T10:57:23Z

Same here :(
Just updated and the vim lpuging won't toggle on now.
This seems to happen regularly... :(

faergeek · 2019-12-09T11:02:57Z

For now the solution is:

jamesalbert · 2019-12-09T18:29:15Z

~~Experiencing the same as @calys and @vv13. I downgraded to 1.11.3 and that worked for a bit, then it auto-updated to 1.12.0 and it's broken again. Same "Command 'togglevim' not found"~~

edit: I jumped the gun on the comment (was having problems last night). This seems to be fixed in 1.12.2

JinSung-Hwang · 2020-04-03T00:15:38Z

@jon301
You are genius
Thank you

jvbianchi mentioned this issue Jan 23, 2018

The lastest VSCodeVim plugin on windows is not working. #2323

Closed

jpoon mentioned this issue Jan 23, 2018

fix: bad jason. fix bad release. #2324

Merged

jpoon closed this as completed Jan 23, 2018

Broken with new release #2322

Broken with new release #2322

Comments

delgermurun commented Jan 23, 2018

rogerwelin commented Jan 23, 2018

r6203 commented Jan 23, 2018 • edited Loading

pyrox18 commented Jan 23, 2018

masiqi commented Jan 23, 2018

ChenXiyu commented Jan 23, 2018

qianliu013 commented Jan 23, 2018

jlelong commented Jan 23, 2018

17hz commented Jan 23, 2018

takano-ex commented Jan 23, 2018

fernando-faubell commented Jan 23, 2018

sample-usr commented Jan 23, 2018

jlelong commented Jan 23, 2018

baurine commented Jan 23, 2018

jon301 commented Jan 23, 2018 • edited Loading

soupdiver commented Jan 23, 2018

jroboyd commented Jan 23, 2018

Inndy commented Jan 23, 2018

stormpat commented Jan 23, 2018

mpseidel commented Jan 23, 2018

TomLingham commented Jan 23, 2018

sus007 commented Jan 23, 2018

JasonAsmk commented Jan 23, 2018

valleybay commented Jan 23, 2018

chiuan commented Jan 23, 2018

marisudris commented Jan 23, 2018

StoyanIvanovI commented Jan 23, 2018 • edited Loading

jpoon commented Jan 23, 2018 • edited Loading

pgoodjohn commented Jan 23, 2018

weiaicunzai commented Jan 23, 2018

bigface008 commented Jan 23, 2018

jpoon commented Jan 23, 2018 • edited Loading

mirsking commented Feb 25, 2019 • edited Loading

pgoodjohn commented Feb 25, 2019 • edited Loading

mirsking commented Feb 25, 2019

tskj commented Feb 25, 2019 • edited Loading

max-frai commented Apr 30, 2019

mariomeissner commented May 1, 2019 • edited Loading

vv13 commented Dec 9, 2019

calys commented Dec 9, 2019

Shahor commented Dec 9, 2019

faergeek commented Dec 9, 2019

jamesalbert commented Dec 9, 2019 • edited Loading

JinSung-Hwang commented Apr 3, 2020

r6203 commented Jan 23, 2018 •

edited

Loading

jon301 commented Jan 23, 2018 •

edited

Loading

StoyanIvanovI commented Jan 23, 2018 •

edited

Loading

jpoon commented Jan 23, 2018 •

edited

Loading

jpoon commented Jan 23, 2018 •

edited

Loading

mirsking commented Feb 25, 2019 •

edited

Loading

pgoodjohn commented Feb 25, 2019 •

edited

Loading

tskj commented Feb 25, 2019 •

edited

Loading

mariomeissner commented May 1, 2019 •

edited

Loading

jamesalbert commented Dec 9, 2019 •

edited

Loading