Proper handling for the case when ~/.vim is under source control

[maljub01]

When the user's ".vim" folder is part of a git repo, using git clone and git add (as the plugin does) creates a "semi-submodule" which doesn't work properly. This commit makes vundle check first if this is the case, and if so properly adds the bundles as git submodules.

[gmarik]

Thanks for the pull request!

Few notes:

1. everyone keeps ~/.vim under control (or should be)
2. not everyone keeps ~/.bundle under source control tho
3. I assume you do keep ~/.bundle scm-ed that's why you had this "semi-submodule" issue

Not merging your commit in yet, but it will be used to add submodule support to Vundle soon!

Let me know what you think!
Thanks again!

[maljub01]

You're right, that's exactly the case. I am keeping ~/.bundle under scm mainly because this way when I clone my dotfiles repo I don't have to clone vundle as well. And I also get the added benefit of having all my other bundles already installed too.

[maljub01]

The last few commits extend submodule support to updating & deleting bundles. It works well on Linux. I'm pretty sure it needs some modifications to work properly on Windows though.

[gmarik]

That's cool maljub01!
I'll take a look!

[silasb]

I think I'm interested in this.

What I'm looking for is some way to install my bundles in a specific location. I think $HOME/.vim/bundles would be good, so I could easily ignore that in my SCM.

[MarcWeber]

#145 (related to)