On 5/5/2015 9:17 AM, 'Terry Brown' via leo-editor wrote:
Seems to me replacing the whole plugins list loses the current
capability of saying in this outline I want my regular list of plugins
plus this one - after the change you'd have to copy your regular list
of plugins, which would then not
On Tue, May 5, 2015 at 8:17 AM, 'Terry Brown' via leo-editor
leo-editor@googlegroups.com wrote:
Seems to me replacing the whole plugins list loses the current
capability of saying in this outline I want my regular list of plugins
plus this one
Correct.
Would it work to add a @bool
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
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
On Tue, 5 May 2015 06:20:12 -0500
Edward K. Ream edream...@gmail.com wrote:
On Tue, May 5, 2015 at 4:32 AM, Kent Tenney kten...@gmail.com 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
On Tue, 05 May 2015 09:24:59 -0400
Jacob Peck gatesph...@gmail.com wrote:
On 5/5/2015 9:17 AM, 'Terry Brown' via leo-editor wrote:
Seems to me replacing the whole plugins list loses the current
capability of saying in this outline I want my regular list of
plugins plus this one - after the
-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?
On Tue, May 5, 2015 at 12:14 AM, Edward K. Ream edream...@gmail.com wrote:
Leo's plugins manager
Maybe I am also misunderstanding but It seems cumbersome to expect any
users but especially new users to enable plugins per outline.
If you want to do a per outline enable-disable then plugins should be
enabled globally (in myLeoSettings.leo or leoSettings.leo) but *disabled*
locally with a
On Tue, May 5, 2015 at 4:32 AM, Kent Tenney kten...@gmail.com 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
Leo's plugins manager can and imo should dispatch events registered to a
plugin *only *to commanders for which the plugin is enabled in an
@enabled-plugins node.
This would make @enabled-plugins nodes work like all other settings. Not
enabling a plugin in a local (per .leo file)
10 matches
Mail list logo