On Wed, Jan 14, 2009 at 9:13 AM, Kent Tenney <[email protected]> wrote:

>
>
>
> > In the first case, Leo will use the *last* found @enabled-plugins node
> from
> > the list leoSettings.leo, myLeoSettings.leo, x.leo.  See the docs for
> full
> > details about search order.
> >
> > So, in the *first* case, it *is* possible to disable any or all plugins.
> > For example, you could put an empty @enabled-plugins node in x.leo.  If
> > x.leo contains no @enabled-plugins node, you could put an empty
> > @enabled-plugins node in myLeoSettings.leo.
>
> OK, will that empty @enabled-plugins node disable all the
> plugins mentioned in LeoSettings.leo?


Yes.  I don't know how much clearer I can say this.

I tested this myself this morning.

>
>
> Sounds like the only @enabled-plugins node which has any effect the
> last one encountered.
>
> Is this correct?


Yes.  That's what I said, and that's what I meant.

But you don't have to take my word for it.  Try it.

Edward

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/leo-editor?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to