Vim: vim not work

[alanwei43]

Issue Type: Bug

vim not work, just like have not installed. I tried rm -rf ~/.vscode/extensions/vscodevim.vim-1.12.0, reinstall extension, and restart computer, vim still not work.

Extension version: 1.12.0
VS Code version: Code 1.40.2 (f359dd69833dd8800b54d458f6d37ab7c78df520, 2019-11-25T14:54:40.719Z)
OS version: Linux x64 5.0.0-36-generic snap

System Info

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7700T CPU @ 2.90GHz (8 x 3687)|
|GPU Status|2d_canvas: unavailable_software
flash_3d: disabled_software
flash_stage3d: disabled_software
flash_stage3d_baseline: disabled_software
gpu_compositing: disabled_software
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: disabled_off
rasterization: disabled_software
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: disabled_software
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: unavailable_software
webgl2: unavailable_software|
|Load (avg)|2, 2, 1|
|Memory (System)|31.28GB (20.69GB free)|
|Process Argv|--force-user-env --no-sandbox --unity-launch --no-sandbox|
|Screen Reader|no|
|VM|67%|

[huangzeyu]

me too, I rolled back to 1.11.3 and everything worked fine.

VS Code version: 1.40.2 f359dd69833dd8800b54d458f6d37ab7c78df520

[zires]

me too

[ldm0]

me too

[imAliAzhar]

Same here. v1.12.0 doesn't work.

[Sutherlandon]

Ditto! Rolling back to 1.11.3 fixed the issue

Here's a link to show how to roll back:
https://stackoverflow.com/questions/42626065/vs-code-rollback-extension-install-specific-extension-version/53755378

This is what the VSCode console is outputting:

[qychess]

me too

[syllr]

me too

[cetra3]

To rollback to a working version:

• Open extensions & find VIM
• Press the cog icon next to it
• Select Install Another Version
• Choose 1.11.3
• Restart VSCODE

[victorqin]

me too

[branchang]

same, working on 1.11.3

[o-train]

Had to rollback too :(

[Yocss]

me too, vim V1.12.0 can't run in vscode v1.40.2 macos 10.14

[0900304132]

same, working on 1.11.3

[chaoleili]

roll back to 1.11.3 works

[jeongwooklee]

rolled back to 1.11.3 and worked well.
(with VS code Version: 1.40.2 f359dd69833dd8800b54d458f6d37ab7c78df520)

[liaokaien]

same problem, rolling back do works

[astroshot]

I thought I was the only one and I rolled back too.

[Bouts2019]

me too, and used the same solution...

[fourcolors]

same here, not working.

[detailyang]

rollback works.

[longhaiqwe]

me too, vim V1.12.0 can't run in vscode v1.40.2, win10 remote to centos7.

[cookie314]

rollback works.

[DremyGit]

me too, and I can't do my work now~

[OverMighty]

Can confirm. 1.12.0 doesn't work, but rolling back to 1.11.3 works.

[zhangjinglin]

On mac 10.15.1, VSCODE 1.40.2, vim 1.12.0 doesn't work, use vim 1.11.3 works,
On windows 10 1903, same as mac, vim 1.12.0 doesn't work, 1.11.3 works

[MondoGao]

me too

[AlseinX]

Releasing 1.12 without checking was guilty.
Programmers from all over the world stopped their work and tried to locate the problem.

[leehunkyu00]

me too,
rolling back to 1.11.3 is working

Visual Studio Code Info
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.18362

[icearith]

confirmed +1

[wushukai]

me too,
remote extension did not work, rollback to 1.11.3 is working

[eisukeesaki]

VSCodeVim v1.12.0 not working on:

System Version: macOS 10.13.4 (17E199)
Kernel Version: Darwin 17.5.0

VSCode Version: 1.38.1
Commit: b37e54c98e1a74ba89e03073e5a3761284e3ffb0
Date: 2019-09-11T13:31:32.854Z
Electron: 4.2.10
Chrome: 69.0.3497.128
Node.js: 10.11.0
V8: 6.9.427.31-electron.0
OS: Darwin x64 17.5.0

rolled backed to v1.11.3 and it's working.

[magiczjp123]

same issue, rollback worked

[Hoofoo-WHU]

same, 1.12.0 not work

[soyarsauce]

Another report for latest version breaking on MacOS:
Extension (VsCodeVim) version: 1.12.0
VSCode version: 1.40.2
OS version: macOS 10.14.6

Current workaround:
Re-installed at version 1.11.3, disabled auto-updates in vscode so it doesn't get updated again.

[bailiyang]

so do I
i remove all my vscode and reinstall!!!
but NO effect

[shmokmt]

me too

[jkryanchou]

So Do I .

[Sh4pe]

Had the same problem, rollback worked.

[shenhe930]

me too

VsCodeVim version: 1.12.0
VSCode version: 1.40.2
OS version: macOS 10.15.1

[AlseinX]

so do I
i remove all my vscode and reinstall!!!
but NO effect

I did the same rofl

[rdepke]

I have the same issue with Windows10 1903

[willzhqiang]

me too

[MetalBlueberry]

mewtwo

[numbcoder]

Almost fully feature-complete VIM integration by utilizing neovim:
https://github.com/asvetliakov/vscode-neovim

[PymZoR]

Same

[liyuanqiu]

v1.11.3 is working

How to downgrade to v1.11.3:
https://github.com/VSCodeVim/Vim/issues/4342#issuecomment-563083330

[hyUrbanManager]

me too, fuck waste my time

[privorotskii]

Me too

[jay7n]

Me too. have to rollback to get it work

[londbell]

Me too.

[xujpxm]

not work +1
vscodevim version: 1.12.0
VSCode version: 1.40.2
OS version: macOS 10.12.6

Rolling back to 1.11.3 fixed also!

[Anniywell]

+1
Rollback to 1.11.3

[iyuge2]

+1
Rollback to 1.11.3
Thanks!!!

[wurikiji]

+1
Rollback works

[chrisfroeschl]

yeah, seems like a major problem with the new update, good to see that the rollback to 1.11.3 worked without any issue.

[robertovg]

Please update when it's fixed

[AlseinX]

Almost fully feature-complete VIM integration by utilizing neovim:
https://github.com/asvetliakov/vscode-neovim

I tried this, but some shitpoints that makes me never want to use it.

• The default escape key is C-c, even though configurable. It is so rude to override widely accepted default with the author's personal preference.
• C-c copy and C-v paste with the system clipboard not supported or need complex configuration.
• It needs external installation and even does not autodetect the path. eg. The C# extension automatically downloads, configures and run Omnisharp as language server, and an in-box mono as its runtime, and some other extensions at least detects the path. //By the way the XML extension by RedHat is also a shit because it needs java runtime (why do we have to configure an irrelative specific runtime just for generally used XML?) and still is the 1st place shown in the search result as the 2nd popular one for XML

[with-heart]

• The default escape key is C-c, even though configurable. It is so rude to override widely accepted default with the author's personal preference.

The main reason is the Esc key is used in vscode to cancel/abort many things and >i just didn't have a time to test it properly

I'll test and add Esc as second escape keybinding for next release

@AlseinX https://github.com/asvetliakov/vscode-neovim/issues/74

[AlseinX]

• The default escape key is C-c, even though configurable. It is so rude to override widely accepted default with the author's personal preference.

The main reason is the Esc key is used in vscode to cancel/abort many things and >i just didn't have a time to test it properly
I'll test and add Esc as second escape keybinding for next release

@AlseinX asvetliakov/vscode-neovim#74

What I got from this issue is

The main reason is the Esc key is used in vscode to cancel/abort many things and i just didn't have a time to test it properly

Vscodevim has properly made it while vscode-neovim is currently unable to.
Does it mean that vscode-neovim is not mature enough for using?

[asvetliakov]

Does it mean that vscode-neovim is not mature enough for using?

vscodevim is evolved during 3+ years and has 200+ contributors. vscode-neovim lifetime is just one month and has only single me as contributor. If you want a polished and mature vim extension continue to use VSCodeVim

[AlseinX]

It's so amazing for you to create it within just one month, integrating a vim or neovim could make it behave exactly as-is. But if he can't be installed with one click, it would be very nice.

i---Original---
From: "Alexey Svetliakov"<[email protected]>
Date: Mon, Dec 9, 2019 20:44 PM
To: "VSCodeVim/Vim"<[email protected]>;
Cc: "Mention"<[email protected]>;"Alsein"<[email protected]>;
Subject: Re: [VSCodeVim/Vim] vim not work (#4342)

Does it mean that vscode-neovim is not mature enough for using?

vscodevim is evolved during 3+ years and has 200+ contributors. vscode-neovim lifetime is just one month and has only single me as contributor. If you want a polished and mature vim extension continue to use VSCodeVim

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

[alac1984]

It was just a test to see how many people are actually using the extension ;)

[webberpuma]

same problem here

[edsu]

It was just a test to see how many people are actually using the extension ;)

Answer: lots!

[minhluuquang]

same problem

[E011011101001]

Rollback to 1.11.3 works

[rebornix]

Fixed in 1.12.1, sorry for the trouble.

[jkornblum]

1.12.1 still not working on my Mac 10.15.1 and VSCode 1.40.2
Rolling back to 1.11.x resolves issues.

[ZurrTum]

1.12.1 still not working on my Mac 10.15.1 and VSCode 1.40.2
Rolling back to 1.11.x resolves issues.

me too
Activating extension vscodevim.vim failed: Unable to find .vimrc file

[rebornix]

There are still issues happening, it seems related to how vsix is being unpacked. Reopen

[kenchilada]

Same problem. Roll back fixed.

[yujincheng08]

Same here. Reinstalled previous version 1.11.3 works.

[brennongs]

rollback worked for me, before that it was like extension wasn't even installed. Need more hands or would that muck up your process?

[Dustii77]

Same issue with 1.12 not working. Rolling back gets it working again.

[E011011101001]

Ver 1.12.1 is now working fine on Mac 10.14.6 and VSCode 1.40.2.

[rebornix]

1.12.2 was out. I'll close this issue once we confirm it fixes all your problems.

There are two issues we fixed in last two minor versions

• 1.12.1. Fix the broken vsix bundle
• 1.12.2. Fix the throw when there is no .vimrc available on disk.

[dtkelch]

Confirmed that v1.12.2 works for me on MacOS 10.14.6 and VSCode 1.40.2.

[Dustii77]

1.12.2 did the trick! Thank you rebornix

[brooth]

That was pretty scary to work without vim mode. Thanks for the quick fix!

[J-Fields]

This is resolved. Thanks for being on top of it @rebornix!

[nomad-software]

What is being done to stop this happening in the future?

[chevtek]

What is being done to stop this happening in the future?

Hopefully we at least get a refund.

[3nuc]

What is being done to stop this happening in the future?

I was actually thinking would it be possible to run like a headless version of VSCode in a CI pipeline that runs the built Vim extension and fails the build if the extension crashes?

[guppykang]

Somehow, this fixed all my .vimrc keybinds when I was setting up my new laptop. (at least if you're on mac)
defaults write com.microsoft.VSCode ApplePressAndHoldEnabled -bool false