Skip to content
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

Bundles not updating on Windows #399

Closed
galli-a opened this issue Mar 6, 2014 · 7 comments
Closed

Bundles not updating on Windows #399

galli-a opened this issue Mar 6, 2014 · 7 comments

Comments

@galli-a
Copy link

galli-a commented Mar 6, 2014

I just started to see the same errors as issue #175 on Windows.
This happened after switching from Windows XP to Windows 7.
I installed MsysGit, but with no luck.
The default shell for Vim is C:\windows\system32\cmd.exe, but even after changing that to C:\Program Files (x86)\Git\bin\bash.exe, with different levels of escape, I still get the errors.

The errors I get are:

Processing 'gmarik/vundle'
Error detected while processing function vundle#installer#new..<SNR>129_process..vundle#installer#run..vundle#installer#install..<SNR>129_sync..<SNR>129_system:
line    1:
E484: Can't open file C:\Users\gallia1\AppData\Local\Temp\VIo8E1E.tmp
Error detected while processing function vundle#installer#new..<SNR>129_process:
line   13:
E121: Undefined variable: g:vundle_last_status
E15: Invalid expression: 'error' == g:vundle_last_status
line   17:
E121: Undefined variable: g:vundle_last_status
E15: Invalid expression: 'updated' == g:vundle_last_status && empty(msg)
@Shougo
Copy link
Contributor

Shougo commented Mar 6, 2014

Can you upload .vimrc? It should be minimal(less than 50 lines).
It seems shell settings problem.
And the version is latest?

@galli-a
Copy link
Author

galli-a commented Mar 6, 2014

VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Aug 10 2013 14:38:33)
Big version with GUI

A minimal _vimrc file with just a few Bundles set is

" prevent vi compatibility mode {{{
set nocompatible
" }}}

" set encoding to UTF-8 {{{
set encoding=utf-8
" }}}

" vundle settings {{{
" uses vundle
filetype off
" Setting up Vundle
let iCanHazVundle=1
set shellxquote=""
let vundle_readme=expand('~/.vim/bundle/vundle/README.md')
if !filereadable(vundle_readme)
    echo "Installing Vundle..."
    echo ""
    silent !mkdir -p ~/.vim/bundle
    silent !git clone https://github.com/gmarik/vundle ~/.vim/bundle/vundle
    let iCanHazVundle=0
endif
set rtp+=~/.vim/bundle/vundle/
call vundle#rc()

" let Vundle manage Vundle
Bundle 'gmarik/vundle'

" plugin list
"
" original repos on github
" visualize undo tree
Bundle 'sjl/gundo.vim' 
" solarized color scheme
Bundle 'altercation/vim-colors-solarized' 
" add surround action
Bundle 'tpope/vim-surround' 


" non github repos
if iCanHazVundle == 0
    echo "Installing Bundles, please ignore key map error messages"
    echo ""
    :BundleInstall
endif
" end setting up Vundle

filetype plugin indent on
" }}}

@starcraftman
Copy link
Contributor

@galli-a Can I ask why you are manually setting shellxquote? Please comment out this line and retry on Windows with the cmd.exe shell. This variable is used to escape special characters, for cmd.exe it should not be an empty string if I read the vimdocs for this option correctly.

You may also want to see the wiki page for Windows setup (https://github.com/gmarik/Vundle.vim/wiki/Vundle-for-Windows). It explains why you should probably use _vimrc & vimfiles instead of the linux names.

Edit: If you are new to Vim, before using options in your vimrc read their vimdoc: i.e. :help shellxquote.

@galli-a
Copy link
Author

galli-a commented Mar 6, 2014

I actually don't remember why I included that option. In my git history it shows up in an unrelated commit, so I am not sure why that was there. I'll comment the line and let you know.

In fact, on windows I am using _vimrc, but kept the .vim folder to keep the same vimrc file on all systems (Windows and OS X).

@starcraftman
Copy link
Contributor

@galli-a Having one .vimrc that specifies different folders for Windows/Linux is possible. See an example on mine. This might be something I should add to the wiki, since it only really mentions replacing text. Also, I'm not sure now, Vundle probably should assume vimfiles on windows. I'll check that.

@galli-a
Copy link
Author

galli-a commented Mar 7, 2014

That was it. Removing the shellxquote option solved the issue.
Thanks for your help in figuring this out.
I'll check out yout vimrc to see how the compatibility for different platform is done.

@galli-a galli-a closed this as completed Mar 7, 2014
@suhaotian
Copy link

@galli-a good !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants