-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
E117: Unknown function: vundle#begin #506
Comments
Anyone has an idea what happened? |
what is the output of these commands: cd ~/.vim/bundle/Vundle.vim
git remote -v
git pull
git rev-parse HEAD
grep -nC 3 'vundle#begin' autoload/vundle.vim for me it is
Is this similar for you? |
I have totally the same output as you |
There is something that I noticed only now: |
I remember that I have not installed Vunlde in /usr/share/vim/vimfiles/autoload/vundle.vim |
Problem resolved! Thanks! |
@naijim Since this issue has been resolved, could you consider closing it? Thanks! 👍 |
@lucc thanks, resolved it. |
@naijim Since you solved it! How about sharing some experience with us?! Thanks in advance! |
search your system and delete other vundle. just keep one copy of vundle in your .vim directory |
@naijim Thanks so much, though I have already solved that by reconfiguring the .vimrc. |
when dotfiles are cloned onto another system, the command git remote -v in .vim/bundle/Vundle.vim reveals it tracks the dotfiles repo instead of gmariks repo. Better to have in install script to install Vundle fresh For reference see: https://github.com/VundleVim/Vundle.vim VundleVim/Vundle.vim#506
I encountered the following error:
|
I had old vundle installed. Instead of using git pull to update vundle, I removed old vundle from ~/.vim and installed it folowing Quick Start section in the Github page of vundle.
I am currently using Archlinux.
Maybe I broke something when I installed new vundle. I get this:
I exactally followed the instractions on the Github page.
/etc/vimrc only contains one line:
And the content of archlinux.vim:
The Dir tree:
The output of :scriptnames
The text was updated successfully, but these errors were encountered: