Open vlcinsky opened 6 years ago
volt
function for Neovim development (prerelease) builds; tested on Windows 10.Pre-setup
Run Powershell as Administrator, then execute:
Set-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\FileSystem' -Name 'LongPathsEnabled' -Value 1
Set-ExecutionPolicy RemoteSigned -scope CurrentUser
Run Powershell as non-administrator, then execute in order:
Invoke-Expression (New-Object System.Net.WebClient).DownloadString('https://get.scoop.sh')
scoop install 7zip sudo innounp dark aria2 git
scoop bucket add versions
scoop install neovim-nightly
Create volt_for_neovim.bat
and insert the following contents:
mklink /H %USERPROFILE%\scoop\apps\neovim-nightly\current\bin\vim.exe %USERPROFILE%\scoop\apps\neovim-nightly\current\bin\nvim.exe
mkdir %LOCALAPPDATA%\nvim\pack
mklink /D %LOCALAPPDATA%\nvim\pack %USERPROFILE%\vimfiles\pack
pause
Run volt_for_neovim.bat
as Administrator, and you're done.
As I am using nvim as my default editor (and vim is used only in some exceptional cases), I am searching for ways to use
volt
to manage neovim plugins and configuration.Currently it seems as
volt
is focusing only onvim
and I had to use~/.config/nvim/nvim/init.vim
file with following content:This allows reusing the
~/volt/rc/default/vimrc.vim
by neovim, but it seems a bit too many steps.It would be nice to have
~/.config/nvim/init.vim
updated the same way, as is done forvim
, e.g. by copying/symlinkng~/volt/rc/<profile>/init.nvim
file.Another topic is location of plugin directory, which differs at neovim and shall put packages into
~/.config/nvim/pack
.Ideal solution would be, if
volt
would allow managingvimrc
/init.vim
files and plugin directories in their default location.