> A) ... Leo never attempts to disable a plugin while processing enabled > plugin strings. Thus, plugins enabled in an @enabled-plugins node in > leoSettings.leo *will* be enabled regardless of the contents of any other > @enabled-plugins node.
Note A) implies that there is no way to disable the default plugins enabled in the leoSettings.leo file except to edit the leoSettings.leo file itself. Not a good solution when any edits to the leoSettings.leo file can be lost when a new Leo version is downloaded. I suggest that any @enabled-plugins node found in a myLeoSettings.leo file causes the @enabled-plugins node in the leoSettings.leo file to be ignored. Users can then copy-paste the @enabled-plugins node from the leoSettings.leo file to their myLeoSettings.leo file and then enable/disable the plugins to meet their needs. Additional flexibility could be achieved by supporting configuration of plugins at the Leo project file level. For example, placing an @enabled-plugins node in a project's .leo file would contain a short list of plugins to be added in addition to those found in the myLeoSettings.leo file. TL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
