Closed liskin closed 5 months ago
Is this pr https://github.com/junegunn/vim-plug/pull/1157 solve your problem?
Is this pr #1157 solve your problem?
Unfortunately not: https://github.com/junegunn/vim-plug/pull/1157#issuecomment-1809226110
(Let's continue the discussion there.)
When a plugin is installed and before post-install/update hooks are executed, it's necessary to (re)load the plugin. This is being done in
s:load_plugin
: https://github.com/junegunn/vim-plug/blob/ca0ae0a8b1bd6380caba2d8be43a2a19baf7dbe2/plug.vim#L439-L441 Unfortunately, it only loads*.vim
, but there are neovim plugins out there which only have.lua
inplugin/
, such as https://github.com/nvim-treesitter/nvim-treesitter. This causes issues like https://github.com/nvim-treesitter/nvim-treesitter/issues/5536, https://github.com/junegunn/vim-plug/issues/1207. Some plugins work around it by including a dummyplugin/xxx.vim
that loads the.lua
.It'd be good if vim-plug was made neovim-aware and (re)loaded lua plugins as well. (Note there are a few other places in plug.vim that may need an additional
*.lua
.)