3 ms·

I've tried this before out of curiosity, it's usually because I CBA to deal with a vim config or managing & maintaining the integration. For vim mode I just use

I've tried this before out of curiosity, it's usually because I CBA to deal with a vim config or managing & maintaining the integration. For vim mode I just use the standard "vim" extension and sync my settings to all my machines without thinking about it. The VS marketplace says this approach has about 6.5M installs. https://marketplace.visualstudio.com/items?itemName=vscodevim.vim https://marketplace.visualstudio.com/items?itemName=vscodevi... https://github.com/VSCodeVim/Vim https://github.com/VSCodeVim/Vim

rfoo 2y ago
VSCodeVim/Vim misses some of my favorite text objects and most importantly, it still feels laggy even on a 7950X :(
- BaculumMeumEst 2y ago
  I just see embracing the lag and wishing for death as a normal part of the VS code experience
cxr 2y ago
> The VS marketplace says this approach has about 6.5M installs And it's entirely to do with the fact that the creators were the only ones shameless enough to call their extension "Vim". In the early days of VS Code, there were a few extensions that tried to tackle the problem of bringing Vim-style key bindings to VS Code. The VSCodeVim project, branded as simply "Vim" in the extension store, was easily among the worst of them at the time. With the unearned advantage from squatting on the "Vim" name, however, it managed to get most of the attention and contributions.
- setopt 2y ago
  The only others I’ve heard of are AmVim and VSCode-NeoVim, both of which are still active. Are any of the others still in development? Any of them still worth picking over VSCodeVim?