I can see in vim how we can:
But I want to:
- Call function only when the plugin is
required
2 Answers
This is pretty much standard sequence of steps.
- Install plugin under
optsubtree - Execute
packaddwhen required - Initialization works the same way as with regular plugins but right after
packaddexecuted for the first time.
-
Initialization works the same way as with regular plugins- with regular plugins I will have some code in my./pluginfolder (not my./pack/start/*folder(s)... this./plugincode will run unequivocally on startup. However, if I only wanted to run that code when Ipackadd matchitor something like that... then how do I do THAT. What is the mechanism of step 3? A plugin will have it's own ``./pack/opt/bundle/some_plugin/plugin/init.lua` folder to initialize itself. But I want to do additional work in my./plugin/additional_config_for_some_plugin.luafile Commented Jul 26, 2023 at 20:44 -
@AriSweedler Vim plugins normally do not require user calling any setup function for that reason. But with Neovim/Lua they do believe that "opt" is of limited use as they can "require() for everything". So if you encounter a situation where some plugin poorly fits under
/startbut still needs too many setup function call(s) then you have to admit it's a dumb piece of code and you'd better to drop it.– MattCommented Jul 27, 2023 at 8:22 -
@AriSweedler Otherwise, you won't have anything better than wrapping both "packadd" and "plugin setup call" into a single function and/or command and use it like that. A dubious design, imo, but sometimes it gets use. See "loading on demand" section of
k-takata/minpac, for example.– MattCommented Jul 27, 2023 at 8:25 -
Oh interesting. So I should be using
functions that require the plugin codeinstead ofoptto delay loading a plugin. My use case is that I'm usingcopilot.nvimand I don't wanna load it until I manually load it. I'm sure I can trivially figure out what specific config delays loading of the plugin and also write a small command that lets me load it later. It's just stupid that I can't use the perfectly finepackaddcommand to do this. Maybe I'll just make a command that runs setup and THEN callspackadd. Exactly as u said Commented Jul 27, 2023 at 21:45 -
@AriSweedler It is much simpler always to start it but with disabled functionality.– MattCommented Jul 28, 2023 at 1:36
I'm starting to set up my environment now and 10 months after your question I'm having the same problem.
The packadd documentation says that the directory should follow the structure pack/*/opt/{name}/plugin/**/*.{vim,lua}
Well, the runtime sorts the directories by putting last the ones that start with after (in a nutshell, that's it), so what I did was add my scripts in after/pack/*/opt/{name}/plugin/**/*.{vim,lua}. With this, when I run the packadd {name} command, my settings are executed after the original settings of the script I loaded.
Well, it may not be so flexible and maybe difficult to manage, but it was as close as I could get.
packadd) is loaded. But I cannot find the Autocmd to run after apackadd. Maybe there is an autocmd after arequirewas my next thought.requireis Lua semantics. You'd have to change its behavior somehow.