This contains my nvim config files for use with vscdoe-neovim. I started having difficulties with Neovim plugins and dependencies partially applying to both Neovim and VSCode Neovim even when only one config or the other was trying to use them. So now I have 3 repos for this kind of thing. One is all my other dotfiles. The other is for systems that will only use Neovim through VSCode, and the other is for systems that will only use Neovim without VSCode. If this seems unlivable to not be able to configure both VSCode Neovim and regular Neovim on the same system, keep in mind I have made a full switch to only using Neovim through VSCode. For me trying to configure Neovim to do what I wanted on its had turned into a disease. This helps me keep configuring/optimizing my Neovim configuration in its place. Additionally, I have now come to favor using Neovim from VSCode, it has become a very powerful and likable combination for me. I will still keep another repo with my standard Neovim configuration, as an option to use on other systems just in case I ever need it, and for historical reference.
I don't recommend anyone try to install and use this config as is, it is probably more useful as inspiration for your own, or if you just want to see my config.
The contents of this folder end up in my WSL2 files at /home/username/.config/nvim/. I have VSCode Neovim configured to use my Neovim installation from WSL2. When I use VSCode's remote features to edit files on other machines or servers, I continue to use my local Neovim installation and config from my local WSL2. It is not recommended to try to install and run the VSCode Neovim extensions on a remote machine or to try to get it to use a remote instance of Neovim (other than the "remote" instance on your local WSL/WSL2).