Keep bundles in separate file and manage with commands

[matschaffer]

This is less of an "issue" and more of an idea. I noticed on autoload/vundle/installer.vim:48 you have a TODO about not reloading vimrc. And my coworker (trotter on github) had an interesting idea about putting the Bundle lines in their own file such that you could then have commands to manage them. For example you could run :BundleInstall tpope/vim-fugitive from within vim which would check out the bundle and append it to your "bundlerc" so it would get loaded next time.

Seems like it might kill two birds with one stone if you moved the actual bundle list into it's own file and loaded it during vundle#rc.

Thoughts?

[gmarik]

Nice! Never though about appending bundles automatically on install...
Definitely an idea worth playing with!
Thanks for sharing!

[ches]

This crossed my mind too when first migrating my existing Pathogen bundles that I used to manage with a list in a Rakefile, because I am actually managing Vundle with a separate file. I just do this at bottom of my .vimrc:

runtime include/bundles.vim

Then ~/.vim/include/bundles.vim contains all the Vundle config, including the runtimepath extension and call vundle#rc(). This works fine and appending to the file would work with minimal effort if you encouraged the separate file as a convention.

[rainux]

I also use a separated ~/.vim/vundle.vim to write all vundle related commands, I think it's worth to use a separated file for Vundle configuration, this also make write an shell style installer easier.

Also we can keep the behavior of BundleInstall but make BundleInstall! append the newly installed bundles to Vundle's configuration file.

[rainux]

I can work on this later, please suggest file name for the standard Vundle configuration file name. Personally I suggest ~/.vim/vundle.vim, not vundles.vim because it isn't a list of vundle, it also contain commands to initialize Vundle it self.

[matschaffer]

~/.vim/vundle.vim sounds great to me. Thanks!

-Mat

On Oct 23, 2011, at 4:09 AM, Rainux Luo
reply@reply.github.com
wrote:

I can work on this later, please suggest file name for the standard Vundle configuration file name. Personally I suggest ~/.vim/vundle.vim, not vundles.vim because it isn't a list of vundle, it also contain commands to initialize Vundle it self.

Reply to this email directly or view it on GitHub:
#56 (comment)

[MarcWeber]

VAM implements dependencies (by allowing users to add addon-info.json files which can reference other repositories). bitbucket.org/vimcommunity/vim-pi is the best place to discuss future about such ideas.