Need to run PluginInstall or :BundleInstall each time.

[raghur]

hi,
lately, there seems to be a problem with Vundle. Basically, some plugins aren't loaded unless I issue :PluginInstall or :BundleInstall each time after starting gvim. My vim config is at: https://github.com/raghur/vimfiles

Gvim 7.4 32bit on Windows7x64 with Huge features and patches 1-250

[Shougo]

I checked your .vimrc, but your .vimrc is too long.
You should upload .vimrc less than 50 lines.

[starcraftman]

Hi @raghur. To better solve this please:

1. Identify exactly what plugins don't load.
2. I'd suggest clearing your vimrc file and using the minimal example in quickstart. Then clean out all the example Plugin lines and just add back the commands you identified in 1 to see if it works.

If the plugins work after step 2 then it is probably the other lines in your vimrc.

[raghur]

Ok - I am able to repro this with a minimal vimrc file - here's a gist with the vimrc file, :scriptnames output after starting gvim with gvim -U $HOME/.vimrc2
Then I ran :PluginInstall and again ran :scriptnames - now the list has 160 odd entries.

https://gist.github.com/raghur/10157032

[starcraftman]

@raghur
There is some strange bug going on. For some reason, on GVim Windows the scripts on the rtp are not being sourced in properly. If you look at the rtp though they are properly there. For example, when I tested vim-airline consistently didn't source on startup. After PluginInstall vim-airline was sourced.

The rtp is so long that writing set rtp? doesn't list it all, use echo &rtp to see it. Not sure what's going on here.

[raghur]

@starcraftman - thanks for confirming that you can reproduce the issue.

[starcraftman]

@raghur I think this only happens on Windows, testing on my Linux PC with same config seems to read all the plugins/most correctly including airline (though I didn't test every one individually). Could there be some artefact about the way Windows vim works that it stops loading scripts after a certain number?

Any thoughts @jdevera?
Edit: Correction, to a lesser extend it may impact linux. I noticed a smaller delta between :scriptnames before and after PluginInstall. I'm not an expert on vim startup sequence so this may be a while investigating.

[starcraftman]

@raghur Do you mind trying something? Put the following line at the bottom of your vimrc. Tell me if all the plugins load.

call vundle#config#require(g:bundles)

It is a bit of a hack, shouldn't have to do that. I'm not sure why some of these aren't being sourced. This function appears to force sourcing of the vim scripts by some runtime! calls.

[raghur]

@starcraftman: Ok - I tried it out. I'm afraid it doesn't fix the issue. The behavior is weird though and maybe will help you spot a pattern:

vim-airline loads properly. I now get a count of 124 (vs the 107 without this line). However, some plugins never load. for ex: vim-sparkup no longer loads. Even running a :PluginInstall does not help (:scriptnames remains fixed at 126)

UPDATE Correction: This does seem to load all the scripts.However, vim-sparkup no longer works (no mapping defined for <c-e> anymore - even if I close and open the HTML file

To summarize: Yes - adding this line seems to force load all scripts (based on scriptnames count). However, vim-sparkup specifically does not work anymore. vim-airline does work. But I have no idea if any other plugin is broken. One point to keep in mind is that vim-sparkup requires a rtp parameter - will that have any bearing?

[starcraftman]

@raghur You left the trailing / on the rtp parameter. Did you have that before? Can you try removing it. I believe that is mentioned in the windows wiki.

Back to the actual issue. The function is printed below, I'm not an expert but main difference seems to be the manual runtime function calls on line 30-31. It is a strange behaviour thing. Based on vimdocs, the plugins get read after the vimrc has finished. By that time the rtp is correct and all scripts in path/plugin/*.vim are read. Seems windows GVim doesn't honor this as strictly.

@gmarik @jdevera and @Shougo Do you guys have thoughts on this?

 25 func! vundle#config#require(bundles) abort
 26   for b in a:bundles
 27     call s:rtp_add(b.rtpath)
 28     call s:rtp_add(g:bundle_dir)
 29     " TODO: it has to be relative rtpath, not bundle.name
 30     exec 'runtime! '.b.name.'/plugin/*.vim'                                         
 31     exec 'runtime! '.b.name.'/after/*.vim'
 32     call s:rtp_rm(g:bundle_dir)
 33   endfor
 34   call s:rtp_add_defaults()
 35 endf

[raghur]

@starcraftman yes - that's seems to have fixed the sparkup issue! My bad for not RTFMing windows section.

[jdevera]

weird weird weird.

@starcraftman when you ran it in linux, is it possible that the small delta you say was the installer.vim file?

Is there something special about the plugins that are not loading?

[starcraftman]

@jdevera It is strange. I retested on Linux with this config and you are correct, the small delta was just scripts read in for functions the installer uses. I guess this is purely a Windows issue for some reason. I'll look into some remedy other than invoking require bundles...

[starcraftman]

Well I haven't really found anything else out. I'm documenting the temporary fix with require for now. Though it doesn't look great. Info is in the FAQ under Windows.