Open mrcjkb opened 3 months ago
If you're open to the proposed solution, I'd be happy to contribute :smile:
hi i maintain a fork of nvim-cmp, magazine.nvim, and this looks like something interesting to implement
Is there a way to detect when something has been added to the runtimepath, rather than using packadd?
I'd like to be able to detect when something has been added to the runtimepath as well.
nvim-cmp
can cache runtimepath and check it when on completion events.
Or you can use OptionSet
autocmd.
FAQ
Announcement
Minimal reproducible full config
opt
plugins in the packpathpackadd
nvim-cmp and cmp-nvim-lsp within an autocommand (e.g.InsertEnter
).Description
Most completion sources rely on
after/plugin
to register themselves, and the impact on startup time can be quite heavy (especially when a lot of sources are installed). For this reason, it can be desirable to install the plugins asopt
plugins and lazy-load them (e.g. on anInsertEnter
event).But nvim-cmp sources rely on
after/plugin
to register themselves (for lack of an API). Because Neovim doesn't sourceafter
scripts once the startup initialisation has completed, the sources won't register themselves and nvim-cmp will error when trying to pass them in via thesetup
function.Steps to reproduce
opt
InsertEnter
with a callback thatpackadd! nvim-cmp
packadd cmp-nvim-lsp
cmp.setup
to add the source.packadd nvim-cmp
Expected behavior
No error. nvim-cmp and the LSP source configured and loaded on
InsertEnter
Actual behavior
nvim-cmp errors when calling
setup
, due to the missing source.Additional context
A potential solution would be to execute a
:h User
autocommand with the patternCmpRegisterSourcePre
at the start of thesetup
call, or in the main module that loads thesetup
function. Sources could create an autocommand with that pattern to ensure they are registered at the appropriate time.