dotfiles VS vscode-neovim

Mostly shell hackery and a bunch of more convenient selection, copy and paste functionality plus extensive documentation like the (supposedly) undocumented line selection operator g_ https://github.com/matu3ba/dotfiles/

I am relative satisfied with mine, although I still dont have a working solution for (vendored) project search and custom sources on keypress for completion is also missing (command completion breaks C-l/Tab for file completion): https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

My config consists mostly of documentation, where you can take a look. I have a plugin as git dir I do include for company stuff, because of network shenanigans packer can not handle. https://github.com/matu3ba/dotfiles

You can see my dotfiles here https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

Otherwise, you can check my setup, but I did not setup snippets yet https://github.com/matu3ba/dotfiles

Thats how it works. You could reduce the amount of plugins or document them for quick lookup. I do this extensively in my dotfiles https://github.com/matu3ba/dotfiles/blob/master/.config/nvim/lua/my_packer.lua

For my config I did write a pile of notes of the default keybindings because I found no good and dense note collection on (all) default keybindings and Vim+Neovim hardcodes them with only an annoying way to search exact the exact keybinding. https://github.com/matu3ba/dotfiles/tree/master/.config/nvim

If you want a more minimal example for explanation, you can check my cmake template: https://github.com/matu3ba/dotfiles/blob/master/templates/CMakeList.txt

I find this cleaner to do in lua without vimscript calls, see here.

Since v1.0+ of this extension I have been constantly having issues with neovim's and VSCode's buffers got out of sync. I cannot reliably reproduce the issues however. There are a few similar reports, e.g. https://github.com/vscode-neovim/vscode-neovim/issues/1624. I've switched to other VIM extension (VSCodeVim) which I found more reliable, albeit less powerful.

You can have it both ways! Use neovim to handle key presses in VSCode, keep all the benefits of a text editor that (mostly) Just Works.

- https://github.com/vscode-neovim/vscode-neovim

In insert mode I'd like to be able to hit escape and return to visual mode, but I have to hit escape twice if a suggestion popup is visible. Similar to this: vscode-neovim/vscode-neovim#677

https://github.com/vscode-neovim/vscode-neovim embeds nvim in vscode. I use it at work full-time.

This post is all over the place. What are you asking? What problem exactly did you have with the https://github.com/vscode-neovim/vscode-neovim (ensure that you did not install https://github.com/VSCodeVim/Vim , which people often confuse with the other).

Why not have both? https://github.com/vscode-neovim/vscode-neovim

I was using the VSCodeVim plugin, but it kept breaking. I now moved to the Neovim plugin and works great!