Hi,
I think that using Joe's work as inspiration and showcase of what Leo
DOM can be used for is pretty good. It conveys panoramic information in
an easy way, using images and animation and interested readers can go to
for more details into the manual. Leo documentation could learn from
Joe's
On Wed, Sep 26, 2018 at 10:25 AM Edward K. Ream wrote:
>
> On Wednesday, September 26, 2018 at 5:58:18 AM UTC-5, Edward K. Ream wrote:
>
>> It highlights the problem of learning and remembering what Leo can do.
>>
>> Words are not the answer: there are too many of them already.
>>
>> I think
On Wednesday, September 26, 2018 at 5:58:18 AM UTC-5, Edward K. Ream wrote:
It highlights the problem of learning and remembering what Leo can do.
>
> Words are not the answer: there are too many of them already.
>
> I think pictures would work better. I've created a project called
>
On Friday, September 21, 2018 at 9:43:14 AM UTC-5, Kent Tenney wrote:
OK, that's embarrassing.
>
It highlights the problem of learning and remembering what Leo can do.
Words are not the answer: there are too many of them already.
I think pictures would work better. I've created a project
OK, that's embarrassing.
:-[
Thanks,
Kent
On Fri, Sep 21, 2018 at 1:24 AM Edward K. Ream wrote:
>
>
> On Mon, Sep 17, 2018 at 10:58 AM Kent Tenney wrote:
>
>> Howdy,
>>
>> p.gnx doesn't work, a new one is generated each time the
>> Leo file is loaded.
>>
>
> @persistence does a pretty good
On Mon, Sep 17, 2018 at 10:58 AM Kent Tenney wrote:
> Howdy,
>
> p.gnx doesn't work, a new one is generated each time the
> Leo file is loaded.
>
@persistence does a pretty good job of remembering gnx's in @auto nodes.
You were the one who requested this major feature.
Set @bool
Howdy,
p.gnx doesn't work, a new one is generated each time the
Leo file is loaded. It looks like a way around this would be
switching to at_clean, but I'd like to stick to at_auto if possible.
One approach would be to check for p.anyAtFileNodeName, and
if it's not none, parse parents until the
