BundleInstall update .vimrc?

[ssmithstone]

Not sure if this is a bug but from what I was reading I thought BundleInstall 'tpope/vim-fugitive' would download the repo and update the .vimrc file, but mine is not updating the file is this the correct behaviour?

[lucc]

I think it is the correct behavior. :h BundleInstall says nothing about automatically changing your .vimrc. Where did you read that?

[Shougo]

You should execute :source ~/.vimrc command manually.

[marslo]

Don't you create link from vimrc in repo to ~/.vimrc?

[MarcWeber]

There is also the autoload plugin - then saving a .vim file is enough to make vim reload it using :source command. The idea behind vundle/vam/NeoPlugin is be declarative: Declare what you want to use, thus the state which plugins to load is your .vimrc - and you should edit it yourself. q:yy:qp will paste the last history line into current (.vimrc) buffer - thus its easy and fast.

#364 shows how to install and require at runtime - Bundle does not do it - I think there should be an extra command

[Shougo]

@MarcWeber No, neobundle supports this feature like this:

NeoBundleDirectInstall 'tpope/vim-fugitive'

[MarcWeber]

I agree I mixed things up. Its too complicated anyway, see #388. There should be two commands 1) InstallAndActivate 2) install (for reviewing before activating).

[lucc]

no reaction, close?

[jdevera]

👍 for closing as wontfix, It is not simple, and not Vundle's job to modify anybody's vimrc. It seems to me like a disaster waiting to happen.

[jdevera]

@gmarik @starcraftman ?

[starcraftman]

@jdevera It is definitely not the job of Plugin/PluginInstall to update a users vimrc.

NeoBundle took the correct approach having a separate command that uses a separate file to load direct installed bundles. I don't think I like this though, as people could forget these plugins exists since they are in a separate file. At the end of the day, users should be responsible for what's installed in their vimrc.

So yes, I'm closing it as won't fix.