Christian wrote: > can you please include the following change in the next runtime update? > > I have had now already twice the case¹ that a user of vim-airline has > been using the plugin directory for cloning packages. That made the > plugin break miserably. So put a note into the standard documentation > that this is a bad idea. > > ¹ see: > https://github.com/vim-airline/vim-airline/issues/1712 > https://github.com/vim-airline/vim-airline/issues/1440
Hmm, I don't think users will be looking in options.txt for this. Best I can think of is at ":help plugin-details". How about this: Note that when using a plugin manager or |packages| many directories will be added to 'runtimepath'. These plugins earch require their own directory, don't put them directly in ~/.vim/plugin. But it's really part of the plugin manager to have instructions on how to install a plugin. -- hundred-and-one symptoms of being an internet addict: 216. Your pet rock leaves home. /// 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.
