Naruhiko Nishino wrote: > I found a case below when using `:packloadall` in .vimrc. > > A/plugin/a.vim -- call B's autoload functions. > B/plugin/b.vim > > I think A can laod B's autoload functions. > Do you think this?
Not as it is now. When A/plugin/a.vim is found, then "A" is added to 'runtimepath'. "B" is unknown at this time. I think this is how it should be. You have the "A" plugin and the "B" plugin, they are separate thus can't directly use each others files. If A depends on B, then you can use packadd to add the B plugin. -- $ echo pizza > /dev/oven /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
