<story><title>VSCode-Neovim: Use embedded Neovim in VSCode without emulation</title><url>https://github.com/vscode-neovim/vscode-neovim</url></story><parent_chain><item><author>capableweb</author><text>Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around&amp;#x2F;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.&lt;p&gt;Installing plugins is one good example of this, where even if you use a Vim plugin (or this, it seems), you still need to resolve to using the mouse&amp;#x2F;Tabbing to actually install the plugin itself.&lt;p&gt;While with Neo&amp;#x2F;Vim itself, you never need to reach for the mouse, because the entire thing, not just the editing&amp;#x2F;writing, is meant to facilitate keyboard-only usage.</text></item></parent_chain><comment><author>eric-hu</author><text>I do now have memorized some mix of vim and vscode keybindings, but to me it&amp;#x27;s worth it. I&amp;#x27;m not at 100% keyboard navigation because in some cases I&amp;#x27;ve burned 5-10 minutes looking up a shortcut, repeatedly 1&amp;#x2F;mo for 3 months. After so many (overly) spaced repetitions, I recognize the shortcut isn&amp;#x27;t worth memorizing.&lt;p&gt;&amp;gt; Installing plugins is one good example of this, where even if you use a Vim plugin (or this, it seems), you still need to resolve to using the mouse&amp;#x2F;Tabbing to actually install the plugin itself.&lt;p&gt;I agree with you here, but I rarely need to install new plugins. It&amp;#x27;s certainly not a task I repeat for a given plugin. Plugins are actually the reason I do primary development in VSCode instead of Neovim natively. I can set up linters, language highlighters, etc in VSCode much faster than I can in Neovim. The ecosystem in VSCode also seems to be bigger for what I&amp;#x27;ve done in the last few years.&lt;p&gt;---&lt;p&gt;Anyways, here are some VS Code keybindings I&amp;#x27;ve found essential to go hand-in-hand with vscode-neovim. These few probably get me to 90% keyboard navigation for day-to-day editing.&lt;p&gt;cmd-shift-m: toggle the bottom tray problems (works as a universal way to show&amp;#x2F;hide the bottom)&lt;p&gt;cmd-b: toggle the left sidebar (in whatever context it was last in)&lt;p&gt;cmd-shift-e: show the current file in the left sidebar&lt;p&gt;cmd-0: move context&amp;#x2F;focus to the left sidebar
cmd-1: move context&amp;#x2F;focus to the editor
cmd-2: move context&amp;#x2F;focus to the right editor (or open an editor split, if not yet split)&lt;p&gt;ctrl-1,...9: highlight Nth tab from the left
ctrl-0: highlight rightmost tab&lt;p&gt;cmd-p: fuzzy find file
cmd-shift-p: fuzzy find any installed action by description</text></comment>
<story><title>VSCode-Neovim: Use embedded Neovim in VSCode without emulation</title><url>https://github.com/vscode-neovim/vscode-neovim</url></story><parent_chain><item><author>capableweb</author><text>Personally, my problem with trying to use Vim keybindings in VS Code is not about the motions of moving around&amp;#x2F;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.&lt;p&gt;Installing plugins is one good example of this, where even if you use a Vim plugin (or this, it seems), you still need to resolve to using the mouse&amp;#x2F;Tabbing to actually install the plugin itself.&lt;p&gt;While with Neo&amp;#x2F;Vim itself, you never need to reach for the mouse, because the entire thing, not just the editing&amp;#x2F;writing, is meant to facilitate keyboard-only usage.</text></item></parent_chain><comment><author>Tyr42</author><text>I guess I am the target market.  I don&amp;#x27;t mind using the mouse when I&amp;#x27;m not in the &amp;quot;flow&amp;quot; of editing.  Even browsing code, scroll wheels are pretty expressive, and clicking to jump to definition is fine.  Ok not typing, so I don&amp;#x27;t need to keep my hand on the home row.&lt;p&gt;But the actual editing doesn&amp;#x27;t use the mouse.</text></comment>