This still seems like it's creating a lot of repetition and potentially violating DRY. @enabled-plugins nodes usually contain a ton of plugins.
What the proposed change would involve is me copying my @enabled-plugins node from myLeoSettings.leo and commenting out a few lines. I'm not sure what typical usage is be it seems more likely that people would be wanting to selectively disable only a few plugins. 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. This could potentially cause a lot of frustration. I again would say that an @disabled-plugins node is a more elegant solution to creating this functionality. On Tuesday, May 5, 2015 at 7:20:13 AM UTC-4, Edward K. Ream wrote: > > On Tue, May 5, 2015 at 4:32 AM, Kent Tenney <kte...@gmail.com > <javascript:>> wrote: > >> -1 as I understand it, but maybe I don't understand. >> >> Other settings are active if applied in myLeoSettings.leo, you're >> saying plugins would need to be mentioned in every .leo file which >> uses them? >> > > No. If x.leo contains no @enabled-plugins node, the @enabled-plugins > node in myLeoSettings.leo is used. > > But if x.leo *does* contain an @enabled-plugins node, then only those > plugins in that particular @enabled-plugins node become active for x.leo, > regardless of how many plugins may have been loaded in other commanders. > > This would make @enabled-plugins work more like all other settings nodes, > including @data nodes. > > 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.
