Handlers are not being invoked on packer.startup after #331
#405
Comments
|
Cool, thanks for the report! I think you might be the first person I've encountered actually using the extensible handlers feature. This is expected with #331, because I did not expect people to use handlers like this - I had in mind that a handler would do something at install/update time, and that anything that needed to be done at startup time would be in a After #402, your use case will work again. Until then, we could hack in a shim to run handlers before fully managing plugins (see 8596be7#diff-bae1764133e447f91f3c4ad4892840c0862259c0a2cdfde9b84dc264e72547edR255-R261), or you could perhaps work around this with a |
Ah, right that makes sense although my use case is somewhat different. I was looking for plugin information specifically URL, full repository name and installed location and most of that was not present in
I don't understand how would we run handlers before managing plugins as the handler requires the information you're storing for each plugin in the I do see that the |
nvim --version:git --version: 2.32.0Steps to reproduce
Here's the gist of what's happening in my config:
In
init.lua:In
core/plugins.lua:Actual behaviour
Before this commit (8596be7), the handler would be called every time I open Neovim and thus can be used by Telescope right away. After that commit, the handler is not being called. Although, if I run any of the
Packer...commands, the handler is being called.Expected behaviour
The handler should be called even on
packer.startuppacker files
Plugin specification file(s)
Post or link your plugin specification files here, if you aren't able to provide a minimal
reproducer
Link: https://github.com/dhruvmanila/dotfiles/blob/master/config/nvim/lua/core/plugins.lua
packer log file
Post the contents of ~/.cache/nvim/packer.nvim.log here
Here are the logs where I tried fixing the plugin at commit df0f740 and then at 8596be7.
packer compiled file
Post the contents of
packer_compiled.vimhereThe text was updated successfully, but these errors were encountered: