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

Why is it "required" to let Vundle manage itself? #710

Closed
n-st opened this issue Mar 31, 2016 · 2 comments
Closed

Why is it "required" to let Vundle manage itself? #710

n-st opened this issue Mar 31, 2016 · 2 comments

Comments

@n-st
Copy link

n-st commented Mar 31, 2016

The main ReadMe states:

" let Vundle manage Vundle, required
Plugin 'VundleVim/Vundle.vim'

Why exactly is this "required"? What are the potential consequences of not having that line in the vimrc?

I'm asking because in my case Vundle.vim is a submodule of my dotfile Git repo, so Vundle throws an error when it tries to update itself (because its local repo isn't a normal checkout of the master branch).
I'd rather just update Vundle manually and only have it update the other bundles automatically.
Looking at #565, it seems like :PluginClean might try to remove the Vundle directory when it isn't explicitly mentioned in the vimrc. I could live with that (I don't normally have a use for :PluginClean anyway), but is there anything else I should be aware of?

@ryanoasis
Copy link
Member

You are right it seems to be at least for the case of the clean command.

See the change here: 6af116c

Comes shortly after this issue: #52

Also see: #565

@ryanoasis
Copy link
Member

Added a FAQ to the wiki because this didn't seem to go with the index wiki page as this is not a problem as much as just a question, page here; https://github.com/VundleVim/Vundle.vim/wiki/FAQ

Closing this for now 😄

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

2 participants