Vundle is not working on Mac OS X Lion (10.7.4) #182

Closed
wael34218 opened this Issue Jun 15, 2012 · 12 comments

Comments

Projects
None yet

Each time vim starts it prompts the following error :

Error detected while processing /Users/waelfarhan/.vimrc:
line 5:
E117: Unknown function: vundle#rc

I tried installing vundler on mac build in vim (7.3), MacVim and https://code.google.com/p/vim/ (7.3.556). All of them had the same problem.

Keep in mind that my .vimrc is the same as the readme file.

Tried it on Fedora (13) vim 7.2.411 and 7.3.55 worked perfectly.

Contributor

gmarik commented Jun 15, 2012

my guess is that instead of vim you're probably using vi )
Please provide more info, like vim version, your actual .vimrc.
Otherwise i'll just keep guessing ;)

Here is the vim version of the built-in Vim

Waels-MacBook-Pro:~ waelfarhan$ which vim
/usr/bin/vim
Waels-MacBook-Pro:~ waelfarhan$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jul 31 2011 19:27:29)
Compiled by root@apple.com
Normal version without GUI. Features included (+) or not (-):
-arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
-conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs
-dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path
+find_in_path +float +folding -footer +fork() -gettext -hangul_input +iconv
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape
-mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse
+mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype
+path_extra -perl +persistent_undo +postscript +printer -profile -python
-python3 +quickfix +reltime -rightleft -ruby +scrollbind +signs +smartindent
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
-toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
-xterm_clipboard -xterm_save
system vimrc file: "$VIM/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -D_FORTIFY_SOURCE=0 -Iproto -DHAVE_CONFIG_H -arch i386 -arch x86_64 -g -Os -pipe
Linking: gcc -arch i386 -arch x86_64 -o vim -lncurses

My .vimrc is an exact copy of the .vimrc of the readme file.

If you need any more information please let me know.

Thank you so much for your quick response

dteoh commented Jun 23, 2012

I am having the same problem as well.

$ which vim
/usr/bin/vim
$ vim --version
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Feb 21 2012 18:42:47)
Compiled by root@apple.com
Normal version without GUI.  Features included (+) or not (-):
-arabic +autocmd -balloon_eval -browse +builtin_terms +byte_offset +cindent 
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments 
-conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con +diff +digraphs 
-dnd -ebcdic -emacs_tags +eval +ex_extra +extra_search -farsi +file_in_path 
+find_in_path +float +folding -footer +fork() -gettext -hangul_input +iconv 
+insert_expand +jumplist -keymap -langmap +libcall +linebreak +lispindent 
+listcmds +localmap -lua +menu +mksession +modify_fname +mouse -mouseshape 
-mouse_dec -mouse_gpm -mouse_jsbterm -mouse_netterm -mouse_sysmouse 
+mouse_xterm +multi_byte +multi_lang -mzscheme +netbeans_intg -osfiletype 
+path_extra -perl +persistent_undo +postscript +printer -profile -python 
-python3 +quickfix +reltime -rightleft -ruby +scrollbind +signs +smartindent 
-sniff +startuptime +statusline -sun_workshop +syntax +tag_binary 
+tag_old_static -tag_any_white -tcl +terminfo +termresponse +textobjects +title
 -toolbar +user_commands +vertsplit +virtualedit +visual +visualextra +viminfo 
+vreplace +wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
 -xterm_clipboard -xterm_save 
   system vimrc file: "$VIM/vimrc"
     user vimrc file: "$HOME/.vimrc"
      user exrc file: "$HOME/.exrc"
  fall-back for $VIM: "/usr/share/vim"
Compilation: gcc -c -I. -D_FORTIFY_SOURCE=0 -Iproto -DHAVE_CONFIG_H -arch i386 -arch x86_64 -g -Os -pipe
Linking: gcc -arch i386 -arch x86_64 -o vim -lncurses

My .vimrc is at https://github.com/dteoh/dotfiles/blob/master/vim/vimrc

dteoh commented Jun 23, 2012

Here is an error that I copied from the terminal while BundleInstall is executing:

Error detected while processing function vundle#installer#new..<SNR>22_process..vundle#installer#run..vundle#installer#i
nstall..<SNR>22_sync..<SNR>22_system:
line    1:
E484: Can't open file /var/folders/4c/92rmd94s3x352nb00rh1vyl80000gn/T/v8v3qao/3
Error detected while processing function vundle#installer#new..<SNR>22_process:
line   13:
E121: Undefined variable: g:vundle_last_status
E15: Invalid expression: 'error' == g:vundle_last_status

You are probably using some weird shell :)

I use this in my fish shell to fix this problem:

set SHELL (which sh)

dteoh commented Aug 21, 2012

Guilty as charged! :)

That would explain why I eventually managed to install vundle successfully.

I ran into the same problem when I switched to the fish shell on Mac OS X 10.8.1. Thanks go to @pusewicz for providing the solution, which I've expanded upon and added to the wiki FAQ.

vrybas commented Dec 28, 2012

@justinmayer let's close this issue then

weynhamz closed this Dec 29, 2012

For it works on Lion :
vundle was here
set rtp+=~/vundle/

had the same issue here, turns out to be cause by iterm, so after I switched back to the default terminal in mac os mavericks, the problem was fixed. Wonder what the underlying problem is? Is there any way to get around it in iterm?

Contributor

lucc commented May 14, 2014

@LeoShawn try to find out if iterm.app and terminal.app run different shells.

If you have this problem and the fix described here does not solve it for you, just open a new issue and maybe link here to tell us what you tried. This issue is closed and you should only comment on it if there is need to add some information to the original problem/topic.

Not working on El Capitan (10.11.1) #668

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment