Vim extension is not working
See original GitHub issuecode-server
version: code-server v1.1119-vsc1.33.1- OS Version: DigitalOcean Ubuntu 18.04
- Extension: VSCodeVim
Description
After installing the VSCodeVim extension, I’m unable to use vim keymappings. I tried toggling vim mode as well, to find the error command 'toggleVim' not found
.
I’ve tried installing extension versions 1.4.0, 1.8.0, and 1.0.8 as per indicated in previous similar issues but am not able to get it to work at all. Any version of code-server in particular I should try downgrading to?
Steps to Reproduce
- Install code-server v1.1119-vsc1.33.1
- Install VSCodeVim (1.4.0)
- Try Vim Keybindings / Toggle Vim Mode
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:14 (5 by maintainers)
Top Results From Across the Web
Does not start up with VSCode and no vim commands work
Steps to reproduce the behavior: open vs code; try to use vim mode; try to use any vim command in the command palette....
Read more >Vim extension not working : r/vscode - Reddit
I've been using Vim extension for a few weeks and everything has been working great. But first thing today I opened a file...
Read more >vim emulation extension in VScode causing problems
I've been using VS Code in "VIM mode" for years now without a problem. I'm on v1.46 now. I fired it up today...
Read more >Installing Vim Inside Visual Studio Code
A step by step guide on how to install Vim in VSCode using the VSCodeVim extension.
Read more >Getting Started with Vim in Visual Studio Code - YouTube
In this developer productivity video, I go over why you should use Vim commands in VS Code and help you get started with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is being fixed upstream https://github.com/VSCodeVim/Vim/pull/3525#issuecomment-662529074
Any chance this could re-opened? Or should I open a new issue?
Running 2.1692-vsc1.39.2 in a docker container (Ubuntu 18.04) with VSCodeVim 1.12.2