On windows 10, when I try to run BundleInstall I get the following error:
Error detected while processing function vundle#installer#new..<SNR>29_process..vundle#installer#run..vundle#installer#install:
line 1:
E739: Cannot create directory: ..\_vimrc
What I can't figure out is why Vundle is trying to install plugins to this directory (.._vimrc). I thought I had set the plugin directory to be the equivalent of ..bundle (relative to my runtime directory). If it matters, I installed vim to C:UsersusernameVim
Here's my basic _vimrc file:
set nocompatible
"source $VIMRUNTIME/vimrc_example.vim
source $VIMRUNTIME/mswin.vim
au! BufWritePost $MYVIMRC nested source $MYVIMRC
filetype off " required
set rtp+=%HOMEPATH%\Vim\vimfiles\bundle\Vundle.vim
call vundle#begin('%HOMEPATH%\Vim\vimfiles\bundle')
Plugin 'VundleVim/Vundle.vim'
Plugin 'tpope/vim-fugitive'
Plugin 'L9'
Plugin 'git://git.wincent.com/command-t.git'
Plugin 'rstacruz/sparkup', {'rtp': 'vim'}
" All of your Plugins must be added before the following line
call vundle#end() " required
filetype plugin indent on " required
I also had this issue.
The issue seems to be with setting the bundle_dir. call vundle#begin('........')
That begin method seems to use the first command line parameter instead of the first parameter passed to the method.
A work around is to manually set the bundle_dir after the call vundle#begin... line:
let g:vundle#bundle_dir='~/.vim/bundle/'
Thanks. That worked (after a bit of messing around with the paths). I think to close this issue, though, either the vundle#begin() behaviour should be fixed or at least this workaround should be added to the documentation for installing under windows.
This seems to be a better work around and works with both vim WIN32 and vim msysgit2 versions:
if has('win32') || has('win64')
" Make windows use ~/.vim too, I don't want to use _vimfiles
set runtimepath^=~/.vim
endif
My previous work around was creating a "~" folder in the $HOME folder.
Also this https://github.com/VundleVim/Vundle.vim/issues/62 issue has some other work arounds that don't move "vimfiles" folder to ".vim"
Vim doesn't know "%PATH%" use "$PATH" instead.
type ":echo %USERPROFILE%" for example and it will show you it doesn't know it.
type ":echo $USERPROFILE" and it will show you your user dir.
The windows section of the installation instructions should be updated. Also, there is no need for curl on windows from what I have experienced until now.
Just started utilizing Vundle today. It's been giving me some trouble but using "$PATH" over "%PATH%" got rid of some issues when I'd ':PluginInstall'. Before it would give me the same sort of error as monotasker. Also, I just tested a bit and it seems NERD Tree would not work before the change but runs just fine after.
I run on Windows 7 for what it's worth. I'm surprised I found a solution here. Thank you pepi55!
Thank you pepi55!
The Vundle-for-Windows doc should be updated as it is clearly incorrect!
The problem is that the path passed to vundle#being is passed to the expand function, which treats filenames starting with '%' specially.
Instead of
set rtp+=%HOME%/vimfiles/bundle/Vundle.vim/
call vundle#begin('%USERPROFILE%/vimfiles/bundle/')
the following works for me:
set rtp+=$USERPROFILE/vimfiles/bundle/Vundle.vim/
call vundle#begin('$USERPROFILE/vimfiles/bundle/')
Same issue in #752 and #754
Most helpful comment
Vim doesn't know "%PATH%" use "$PATH" instead.
type ":echo %USERPROFILE%" for example and it will show you it doesn't know it.
type ":echo $USERPROFILE" and it will show you your user dir.
The windows section of the installation instructions should be updated. Also, there is no need for curl on windows from what I have experienced until now.