Vim: vim not work
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® Core™ 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% |
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 177
- Comments: 84 (5 by maintainers)
To rollback to a working version:
1.11.3me too, I rolled back to 1.11.3 and everything worked fine.
VS Code version: 1.40.2 f359dd69833dd8800b54d458f6d37ab7c78df520
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
throwwhen there is no.vimrcavailable on disk.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:
Hopefully we at least get a refund.
It was just a test to see how many people are actually using the extension 😉
That was pretty scary to work without vim mode. Thanks for the quick fix!
What is being done to stop this happening in the future?
Releasing 1.12 without checking was guilty. Programmers from all over the world stopped their work and tried to locate the problem.
I tried this, but some shitpoints that makes me never want to use it.
Fixed in 1.12.1, sorry for the trouble.
1.12.2 did the trick! Thank you rebornix
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?
Almost fully feature-complete VIM integration by utilizing neovim: https://github.com/asvetliakov/vscode-neovim
There are still issues happening, it seems related to how vsix is being unpacked. Reopen
me too Activating extension
vscodevim.vimfailed: Unable to find .vimrc file1.12.1 still not working on my Mac 10.15.1 and VSCode 1.40.2 Rolling back to 1.11.x resolves issues.
Answer: lots!
so do I i remove all my vscode and reinstall!!! but NO effect
roll back to 1.11.3 works
same, working on 1.11.3
me too, vim V1.12.0 can’t run in vscode v1.40.2 macos 10.14
same, working on 1.11.3