On Wed, 14 Jan 2009 16:01:51 -0800 "Kayvan A. Sylvan" <[email protected]> wrote:
> > How about this simplification? > > Each @enabled-plugins node adds to (does not replace!!) the current > plugin list. > > Each @enabled-plugins section can optionally starts with a > "@clear-plugins" line which would clear the list of plugins to load. > > This would make the most common case (where a user just wants to > enable a plugin without losing the standard ones) easy: Simply list > the plugin in an @enabled-plugins node of ~/.mySettings.leo > > Note that this also has the added benefit that if the global plugin > list changes, the user does not have to fix their private > @enabled-plugins. This sounds interesting in general. One specific issue - most plugins can't be unloaded, so @clear-plugins would only work at startup as the lists were parsed for the first time, when loading additional files later it wouldn't work, and something that works sometimes and not other times is confusing. Cheers -Terry > Best regards, > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
