On 2014-03-24, LCD 47 wrote:
> On 24 March 2014, Gary Johnson 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"?
>
> I believe that was answered just below the text you quoted:
>
> On 24 March 2014, Nikolay Pavlov wrote:
> [...]
> > And check out :scriptnames. Recording its output at VimLeave makes
> > such functionality rather easy.
> [...]
I saw that, but it wasn't clear to me that that addressed item #13
because I apparently misunderstood item #13. I thought the idea was
for the PM to determine which plugins the user actually made use of,
that is, executed some part of their contents. Instead, "used"
meant "sourced".
I'm sure I have a number of plugins that I always source but never
actually "use".
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 vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment