leoCommands.py and leoEditCommands.py are too large and contain a mishmash
of code.
I propose to replace the leo.core.leoEditCommands module with a
leo/userCommands directory containing something like the following files:
- abbreviationCommands.py
- baseCommands.py
- cursorCommands.py
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) @enabled-plugi
On Monday, May 4, 2015 at 4:30:45 PM UTC-5, Edward K. Ream wrote:
>
>
> http://doc.qt.io/qt-4.8/qlayout-members.html doesn't list .setMargin as
>> a member (even inherited) of QLayout, so I'd need more context to
>> comment, but calling not a member seems wrong :-)
>>
>
> Ok. I'll just go ahead a
On Sunday, May 3, 2015 at 7:09:36 AM UTC-5, Steve Zatz wrote:
>
> Latest version of Leo: commit = 014cfd569ad8
>
> If you do vim-open-node on two different nodes, the first opens without a
> problem. Trying to open the second node produces...
>
> File "c:\users\szatz\leo-editor\leo\core\leoAp
On Mon, May 4, 2015 at 9:54 AM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
>
> http://doc.qt.io/qt-4.8/qlayout-members.html doesn't list .setMargin as
> a member (even inherited) of QLayout, so I'd need more context to
> comment, but calling not a member seems wrong :-)
>
The valuespace/jinja combination is precisely the behavior I'm trying to
achieve. My concern is the level of integration that solutions offers. This
seems like a powerful concept and I'm interested if there would be any
interest in a core Leo implementation.
For documentation purposes I'd like
On Mon, 4 May 2015 11:55:00 -0500
"'Terry Brown' via leo-editor" wrote:
> with no body would assign 'internal only' to `distribution`, without
> the harder to scan placement of distribution in the body.
should read:
visually-harder-to-scan placement of 'internal only' in the body.
Cheers -Terr
On Mon, 4 May 2015 04:14:47 -0700 (PDT)
john lunzer wrote:
> I've been using Leo to help me organize hundreds of bash scripts.
> Some scripts share common data. One might say my project (and my
> reason for seeking out Leo) was to find a way to organize all these
> scripts. It's been a resounding
On Mon, 4 May 2015 09:59:55 -0500
"'Terry Brown' via leo-editor" wrote:
> On Mon, 4 May 2015 09:46:27 -0500
> "Edward K. Ream" wrote:
>
> > On Mon, May 4, 2015 at 7:03 AM, john lunzer
> > wrote:
> >
> > Specifically what I'm trying to do is say have a node:
> > >
> > > Headline:
> > > @data m
It's not really sharing data in the sense of running one script and another
script having access to data created by the first script. I'd liken what
I'm talking about to setting environmental variables in a Linux environment
and being able to access that variable from any shell script.
I guess
On Mon, 4 May 2015 09:46:27 -0500
"Edward K. Ream" wrote:
> On Mon, May 4, 2015 at 7:03 AM, john lunzer wrote:
>
> Specifically what I'm trying to do is say have a node:
> >
> > Headline:
> > @data myString1
> > Body:
> > This is Common Data
> >
> > Then in a child of an @clean myfile.txt node
On Mon, 4 May 2015 09:48:13 -0500
"Edward K. Ream" wrote:
> > Sure, do whatever you want to it - it's Jake's code, not mine ;-)
>
> I'm talking about the Qt code in Leo's code, not Jake's plugin code.
Oh :-) see what you get for being smart - I'm not sure that's my code
either, if you're talki
On Mon, May 4, 2015 at 9:40 AM, 'Terry Brown' via leo-editor <
leo-editor@googlegroups.com> wrote:
>
> > Second, it appears that in PyQt5 the correct call is
> > aLayout.setContentsMargins(QtCore.QMargins(0,0,0,0)) rather than
> > aLayout.setMargin(0). I just made this change in the python_termin
On Mon, 4 May 2015 05:33:47 -0700 (PDT)
"Edward K. Ream" wrote:
> First, saying no-to-all just hard crashed Leo on Windows. This is
> not ok with me. We should either fix this or get rid of the "to all"
> options.
I know reproducibility is a problem here, but last time we worked on
this the bu
It appears it might do what I want.
It seems the plugin is partially broken, which is my fear because it was
written by Ville Vainio and because he has not contributed in a long time.
I'll have to dig deeper into this.
On Monday, May 4, 2015 at 10:32:26 AM UTC-4, Terry Brown wrote:
>
> On Mon,
On Mon, May 4, 2015 at 7:03 AM, john lunzer wrote:
Specifically what I'm trying to do is say have a node:
>
> Headline:
> @data myString1
> Body:
> This is Common Data
>
> Then in a child of an @clean myfile.txt node be able to reference
> "myString1" by name somehow and be replaced by "This is C
On Mon, 4 May 2015 05:03:48 -0700 (PDT)
john lunzer wrote:
> I thought Leo might already have a way to do this which is why I
> asked.
>
> I guess I'm still confused on the "get them as usual" part.
I'm not sure Edward's answer addressed your question - I think the
valuespace plugin might, but
First, saying no-to-all just hard crashed Leo on Windows. This is not ok
with me. We should either fix this or get rid of the "to all" options.
Second, it appears that in PyQt5 the correct call is
aLayout.setContentsMargins(QtCore.QMargins(0,0,0,0)) rather than
aLayout.setMargin(0). I just m
Hey Terry vs-create-tree is not perform as stated in the doc string:
*Creates a tree whose root node is named 'valuespace' containing one child
node for every entry in the namespace.*
That is, it's not create a root node named valuespace. Is there anything
special about this command or can I
I will check this out Terry, sorry I hadn't seen this post before I
responded to Edward.
On Monday, May 4, 2015 at 8:01:51 AM UTC-4, Terry Brown wrote:
>
> Have a look at the valuespace plug in, I think it does outline wide
> substitution. Not sure if the results are syntax agnostic.
> Cheers -
I thought Leo might already have a way to do this which is why I asked.
I guess I'm still confused on the "get them as usual" part.
It's not clear to me how I would use an @data node in an @settings
node and have it be accessible/read via some named reference to it in any
arbitrary node and che
Have a look at the valuespace plug in, I think it does outline wide
substitution. Not sure if the results are syntax agnostic.
Cheers -Terry
On May 4, 2015 6:14:47 AM CDT, john lunzer wrote:
>I've been using Leo to help me organize hundreds of bash scripts. Some
>scripts share common data. One
On Mon, May 4, 2015 at 6:14 AM, john lunzer wrote:
Could Leo have something like @int/@bool/@string/etc simple settings types
> but applicable to any node in an outline?
>
Anything is possible, but I won't do this. Settings are complex and
capable enough as it is.
Put common data in settings i
I've been using Leo to help me organize hundreds of bash scripts. Some
scripts share common data. One might say my project (and my reason for
seeking out Leo) was to find a way to organize all these scripts. It's been
a resounding success.
I'd like to find a way to consolidate common pieces of
24 matches
Mail list logo
