On Tue, May 5, 2015 at 6:38 AM, john lunzer <lun...@gmail.com> wrote:
Here is the real bummer about this approach. Lets say I find a new plugin I > really like. Now I have to go into every Leo file that has a custom > @enabled-plugins node and add a new line to each > . > A valid point, but why have custom @enabled-plugins nodes at all? > I again would say that an @disabled-plugins node is a more elegant > solution to creating this functionality. > Reasonable. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
