On Mon, Dec 12, 2016 at 2:11 PM, Richard Twyning <
service.management.addr...@gmail.com> wrote:
>
> I'm very new to Leo and I think I'm trying to do something similar to what
> was asked in this post.
>
I've just re-read this thread. It doesn't seem to come to any firm
conclusions. I'll t
Hi Edward,
I'm very new to Leo and I think I'm trying to do something similar to what
was asked in this post.
I'm trying to use Leo to create batch files. The release number has to
repeat throughout the file. How can I store it in a header node and
reference it from a sub node?
Many thank
This is good to know about but, similarly to Edwards suggestion, likely
solves a different issue. Terry's suggestion with the otters example is
exactly what I'm talking about.
On Tuesday, May 5, 2015 at 4:19:57 AM UTC-4, reinhard...@googlemail.com
wrote:
>
>
>
> On Monday, May 4, 2015 at 1:14:4
On Monday, May 4, 2015 at 1:14:47 PM UTC+2, john lunzer wrote:
>
>
> Could Leo have something like @int/@bool/@string/etc simple settings types
> but applicable to any node in an outline?
>
> Section references do what I'm talking about but in reverse. In a section
> reference you can reference
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
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
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
19 matches
Mail list logo
