> On Nov 25, 2023, at 08:20, Lifepillar <[email protected]> wrote: > > What is the use case for an autoload mechanism when plugins have been > turned off? Are you talking about `import autoload` statements in > a vimrc file?
I have a makefile that tests Vim plugins, each test in a dedicated vim --clean. I don’t need autoload per se here, I can explicitly source the autoload scripts, but a plugin script would fail if its import fails. So a plugin’s import autoload has to work even if the plugin isn’t loaded at Vim startup. >> , when is it a good time to use it? > > It's just a matter of personal preference. In most cases the difference > won't be noticeable. I'd stick with relative paths to avoid potential, > although probably rare, name conflicts. Thank you, that helps. Matan -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/14B2DEF4-FAAD-48D3-B104-4BE14C0058C1%40gmail.com.
