On Mi, 18 Apr 2018, Bram Moolenaar wrote: > > 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.
Okay, that is probably good enough. > > > But it's really part of the plugin manager to have instructions on how > to install a plugin. Okay, Vim Plug has been fixed https://github.com/junegunn/vim-plug/commit/449b4f1ed6084f81a1d0c2c1136cd242ec938625 I created a separate issue for Vundle. Hopefully they fix at too (or at least mention that this is discouraged). Best, Christian -- Nichts schrecklicher kann den Menschen geschehn Als das absurde verkörpert zu sehn. -- Johann Wolfgang von Goethe (Zahme Xenien) -- -- 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.
