:BundleInstall and :Bundles throw errors, don't work

[maxcountryman]

Hi,

I've been banging my head against a wall with this for the last several hours: basically I can't seem to get Vundle to work at all.

I'm running OS X 10.7.3, MacVim Snapshot 64. I've cloned Vundle into ~/.vim/bundle/vundle. Here's my vimrc for reference: http://pastebin.com/raw.php?i=tXhZJ1bH

The most persistent error is related to /var not being writable: "Can't open file: /var/folders/q4/..." (Although the specific path is owned by be user and other apps are using /var just fine.) Also I see "Error fetching scripts!" with :Bundles. There's some other error about undefined variables that pops up now and then.

I finally decided to just rm -rf ~/.vim and start from scratch. But the same issues persist. Any idea what might be causing this?

[maxcountryman]

I managed to capture the error output:

Error detected while processing function vundle#scripts#all..<SNR>27_load_scripts..<SNR>27_fetch_scripts: line 21: E484: Can't open file /var/folders/q4/d0lp3tbs551f6lp59btd3hr40000gn/T/v5jsU64/0 line 24: Error fetching scripts! 0 bundles found

[maxcountryman]

set shell=/bin/bash in my vimrc fixed this. Apparently MacVim was doing something weird with the shell prior to executing the vundle initialization function.

[gmarik]

@maxcountryman, happy to hear that you managed to fix it!

[lloeki]

Wow, that one fixed all bundles refusing to install with a useless processing error. Using zsh here, but it worked at work where I use zsh too.

[confessin]

It fixed for me too.. I was getting a processing error with "E484 can't open file /tmp" I am using fish. Would love to know what went wrong.

[haarts]

I, too, have this problem with fish. zsh and bash worked fine. @maxcountryman can you tell us how you have captured the output?

[maxcountryman]

@haarts I forget how to do it now, but there's a way to copy that buffer where the error propagates in vim. Maybe Google can tell you?

[bs]

I was getting this with Fish as well. @maxcountryman: Is that what you're using?

Vim requires a POSIX-Compliant shell. Fish isn't. The solution is to add this to the top of your vimrc:
" Vim needs a POSIX-Compliant shell. Fish is not.
if $SHELL =~ 'bin/fish'
set shell=/bin/sh
endif

[maxcountryman]

@bs yes, I use fish.

[vikstrous]

I too ran into this and fixed it by adding set shell=/bin/bash to my .vimrc (I'm using fish)

[galli-a]

I just started to see this error on Windows.
This happened after switching from Windows XP to Windows 7.
I installed MsysGit, but with no luck.

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)

[ahti]

@gmarik I just ran into this as well. Wouldn't this be pretty easy to fix by wrapping all shell invocations in a /bin/sh -c 'foo'?

The solution of setting the shell in .vimrc works, but makes :sh run bash as well, where I'd rather use fish.

[jdevera]

@ahti that would unfortunately not fly on windows.

[mascip]

set shell=/bin/bash fixed it for me too, in ArchLinux. Thank you!

[dopatraman]

Many thanks for this.

[jueqingsizhe66]

My Windows10 Solution:
put the git in the path environment

and add "set shell=git" in the vimrc

ok. Everything works fine.

[YaoXuanZhi]

2333, this plug-in relies on git, so make sure that you can find git in system environment variables.

[arwildo]

If you're using Windows, delete the set shell=powershell, it only works at cmd terminal