Also check out the VSpaceCode extension bundle - it reduces the need to use the mouse, but unfortunately not completely.
VSCode-Neovim: Use embedded Neovim in VSCode without emulation
71–80 of 112 posts
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#72Earlier quoted context omitted.
I do now have memorized some mix of vim and vscode keybindings, but to me it's worth it. I'm not at 100% keyboard navigation because in some cases I've burned 5-10 minutes looking up a shortcut, repeatedly 1/mo for 3 months. After so many (overly) spaced repetitions, I recognize the shortcut isn't worth memorizing. > Installing plugins is one good example of this, where even if you use a Vim plugin (or this, it seems…
Thank you for posting these!
My pleasure! This plugin is hands down my favorite VSCode plugin. I worked mostly in vim before, and this plugin made me comfortable doing project work in VSCode.
I'll keep an eye on this thread for a day or two and try to add more essential hotkeys if I think of them.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#73This has caused me to realize that I need to replace my old model of vi: > command mode has primacy; insert mode is a time-bounded special case with: > insert mode is every other mundane editor; use the Esc key to enter the matrix (i.e. command mode)
> Command mode
I think you mean normal mode.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#74This seems like a lot of work to ultimately have a Frankenstein monster.
Just use NeoVim. Name one reason why you need VSCode.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#75I reverted to Vim after trying NeoVim for a few weeks simply because a lot of Vim defaults had to be chased-down and configured just to get basic Vim features in NeoVim. NeoVim also requires messing with a ton of config files compared with Vim so no thanks.
Your single `.vimrc`-style config file should just work, NeoVIM just looks for it elsewhere. Most other differences are config defaults, the majority of which I suspect you have manually added to your current VIM config anyway.
Here is a detailed list of all the differences on the NeoVIM docs: https://neovim.io/doc/user/vim_diff.html
It's totally fine if you simply prefer VIM, of course.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#76For when you hate Emacs so much, you need to form a Voltron of non-Emacs editors to fight it with.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#77Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around/editing the code itself, but everything else. You end up in plenty of situations where you have to resolve using the mouse because you ended up on some sub-page or whatever, where you either need to resolve using the mouse or keep pressing Tab until you get to where you want to go. Installing plugins is one…
VspaceCode might help you and others: https://vspacecode.github.io/.
It allows you to execute arbitrary VScode commands in fewer keystrokes using Emacs like menu (never used Emacs myself, so might be off a little). Along with default key, I've also mapped ctrl+g as a global binding to trigger VspaceCode. So almost anywhere in the UI, I can always use keyboard to navigate.
EDIT: formatting
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#78While I'm missing global mode my choice would be vscodevim.vim (1), mainly because it supports VScode in-browser mode such as github.dev and gitpod.io
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#79This seems like a lot of work to ultimately have a Frankenstein monster. Just use NeoVim. Name one reason why you need VSCode.
Bonus: Neovim isn’t phoning home to Microsoft nor does it try to bifurcate communities on using proprietary plugins.
Re: VSCode-Neovim: Use embedded Neovim in VSCode without emulation
#80Earlier quoted context omitted.
What are your greener pastures?
helix is pretty nice if you’re willing to challenge your traditional vim editing model. vim is action -> selection. helix is selection -> action. Beyond that helix feels like a modern vim. LSP natively supported. DAP as well. Very little configuration and bootstrapping to wade through.
What does that shift in paradigm give you over Visual Mode in Vim?