Raghu

> For me, the perfect solution would be for the User pluginname command to always be fired when a plugin loads, lazily or not. Same here - but there are...

It looks like it... and at least based on my config, it looks like it wasn't always so (can't tell) I find that triggering the autocmd to set up plugin...

neovim :CheckHealth returns ``` ## Python 2 provider (optional) - INFO: Disabled. g:loaded_python_provider=1 ## Python 3 provider (optional) - INFO: Using: g:python3_host_prog = "d:/sdks/python36/python.exe" - INFO: Executable: d:/sdks/python36/python.exe - INFO:...

So gvim 8.1 - 302s neovim 4.0 unstable 200s Since I first ran gvim, it actually had to pull in updates to plugins. When neovim ran, everything was up to...

> @raghur Do you change your &shell before running PlugInstall? No I didn't. Should I? I did try `set guioptions+=!` - but that didn't seem to help much.

Unfortunately, no. I ran PlugUprade and then restarted and ran PlugUpdate 45 Plugins - updated in 161s Win10 x64, Neovim nightly

Here goes with plug.vim from the PR. Btw, my config's reduced to 39 plugins now. I'm a little puzzled why I'm not seeing an improvement. ``` Updated. Elapsed time: 338.211278...

Yeah - I understand the why. I think my numbers might be something to do outside of Vim - likely antivirus/real time scanning etc. that I cannot disable (work m/c)

Yeah - I know.. but when the slowdown was first noticed, even then the same antivirus/endpoint protection crap was active - so I reasoned that it wasn't a factor. Today...

With profiling turned on ``` Updated. Elapsed time: 260.067702 sec. [=======================================] ``` and the profile: ``` FUNCTION 14_update_finish() Defined: ~\AppData\Local\nvim\autoload\plug.vim:1280 Called 1 time Total time: 132.359899 Self time: 0.243230 count...