-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PlugUpdate fails on Windows with powershell #1098
Comments
I am getting exact the same error. With the environment variable Here is my version info, for what it's worth:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Explain the problem here ...
I use neovim and vim on both Windows 10 and Linux, with many plugins. Recently on Windows I switched from cmd.exe to powershell, and have been tweaking my _vimrc configuration to work correctly with various plugins including vim-plug. In neovim everything is working, but in vim the PlugUpdate and PlugInstall commands are not working. The following errors are shown by the messages command.
Below is the _vimrc fragment where powershell is configured, including fixes introduced to support other plugins.
" Use powershell on Windows
if has("win32")
" Extension exe required for vim-plug
set shell=powershell.exe
set shellcmdflag=-NoLogo\ -NoProfile\ -ExecutionPolicy\ RemoteSigned\ -Command
" set shellquote=(
" Required to run shell commands
if has("nvim")
set shellquote=
else
set shellquote="
endif
set shellxquote=
" set shellpipe=|
" Required for ack
if has("nvim")
set shellpipe=|\ Out-File\ -Encoding\ UTF8
else
set shellpipe=>
endif
if has("nvim")
set shellredir=|\ Out-File\ -Encoding\ UTF8
else
" Required for fzf
set shellredir=>
endif
endif
I have been trying combinations of values for these options, but with no luck. I also tried the recommended configuration introduced in commit 8a44109, but it did not help.
I thought it might be a filename escape problem as described in the 'Windows System Error E484' entry on the FAQ page, but haven't found a solution.
The text was updated successfully, but these errors were encountered: