Hi Naruhiko, 2016-4-3(Sun) 19:48:13 UTC+9 Naruhiko Nishino: > > I think A can laod B's autoload functions. > > Sorry for typo. > I think A can load B's autoload functions. > > 2016-04-03 17:55 GMT+09:00 Naruhiko Nishino <[email protected]>: > > Hi Bram, > > > > 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?
When placed a dependency packages under the `start` directory, Vim can not resolve it. Users will need to source the package B previously explicitly. Your setting (I guess): Your package setting ~/.vim/pack/my/start/A/plugin/a.vim ~/.vim/pack/my/start/B/plugin/b.vim Your .vimrc (partly) packloadall Solutions to my suggestion: package setting ~/.vim/pack/my/start/A/plugin/a.vim ~/.vim/pack/my/opt/B/plugin/b.vim Your .vimrc (partly) packadd B Remarks: - Package B is moved to the `opt` directory, and explicitly source by packadd. - You do not need to explicitly describe the `packloadall` to .vimrc. Because, This is normally done automatically during startup, after loading your .vimrc file. Please see document (:help :packloadall) It will be solved your issue. -- Best regards, Hirohito Higashi (a.k.a. h_east) -- -- 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.
