redirects calls to itself to neovim via nvr. EXE is names Code.exe to trick unity into generating csproj files

gwen 56961aed29 logo 3 anni fa
Code 0855193ae7 tweaks 3 anni fa
.gitignore d0670defb0 Initial commit 3 anni fa
LICENSE d0670defb0 Initial commit 3 anni fa
README.md 316640dac5 more formatting 3 anni fa
vscode-2-nvim.png 56961aed29 logo 3 anni fa

README.md

vscode-to-nvim

redirects calls to itself to neovim via nvr. EXE is names Code.exe to trick unity into generating csproj files

dependencies

building

First make sure you change the line public static readonly string ADDRESS = "\\\\.\\pipe\\vscode-to-nvim"; to reflect your pip location

Then set public static readonly string nvrFile = "C:\\Python39\\Lib\\site-packages\\nvr\\nvr.py"; to reflect wherever pip installed nvr

You should now be able to just run

dotnet build Code

and get an exe in the bin folder

config

  1. set unity's External Script Editor to the Code.exe that you built
  2. set the editor args to "$(File)" $(Line) $(Column)
  3. turn on generate .csproj for local and embedded projects

code folding

if you use code folding I recomend you add these auto commands to your config (vimrc or init.vim)

augroup remember_folds
  autocmd!
  autocmd BufWinLeave * mkview
  autocmd BufWinEnter * silent! loadview
augroup END