On Mar 24, 2014 10:19 PM, "Gary Johnson" <[email protected]> wrote: > > On 2014-03-24, Nikolay Pavlov wrote: > > > > On Mar 24, 2014 11:08 AM, "LCD 47" wrote: > > > > > > On 23 March 2014, ZyX wrote: > > > > > 13. Ability to list and remove unused plugins. Reason: it is just > > > > convenient. > > > > Low priority. > > > > > > That would imply keeping stats about when each plugin is actually > > > used. A complicated, expensive, and tricky task, for very little gain. > > > > Simplest implementation is just taking a list of currently active plugins and > > remove everything but them. VAM/Vundle/NeoBundle have everything what is > > necessary to perform such a task. It is not so easy for FHS-based > > installations, but it is easy to implement if you just do not provide this > > functionality for this task. > > How do you know whether or not a plugin is "actually used"?
Just how PM knows whether it needs to add certain path to &runtimepath or not. > > Regards, > Gary > > -- > -- > 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]. > For more options, visit https://groups.google.com/d/optout. -- -- 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]. For more options, visit https://groups.google.com/d/optout.
