You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to put this issue up so anyone that might be using vim-plug will know about it. I've been using vim-plug on one of my machines for some time now and just noticed this with a .dump file that has the header at the top so the auto-detect does not work.
The global setting for extensions is not initialized before vim-plug finalizes all plugin initialization. This behaves a bit different from Vim with a manual installation, which does catch the global variable setting set in the vimrc before initializing the plugins. I'm pretty sure it is a code execution order issue.
I want to put this issue up so anyone that might be using vim-plug will know about it. I've been using vim-plug on one of my machines for some time now and just noticed this with a
.dump
file that has the header at the top so the auto-detect does not work.The global setting for extensions is not initialized before vim-plug finalizes all plugin initialization. This behaves a bit different from Vim with a manual installation, which does catch the global variable setting set in the
vimrc
before initializing the plugins. I'm pretty sure it is a code execution order issue.I've asked the vim-plug community about this in junegunn/vim-plug#838
I'll update the documentation or code for moosefw_vim once I know what they say. :)
The text was updated successfully, but these errors were encountered: