Re: Contract Node and Descendants

Success! :-) On Mon, 2020-08-24 at 17:45 -0500, Edward K. Ream wrote: > > > > On Mon, Aug 24, 2020 at 5:41 PM wrote: > > I did actually see that under the tree options in leoSettings but > > it appears to be set to true by default, > > might there be something else that could be unsetting

Re: Contract Node and Descendants

On Mon, Aug 24, 2020 at 5:41 PM wrote: > I did actually see that under the tree options in leoSettings but it > appears to be set to true by default, > might there be something else that could be unsetting it? > > How might I go about checking its currently assigned value? > show-settings. In

Re: Contract Node and Descendants

On Mon, Aug 24, 2020 at 4:18 PM wrote: > > I can't seem to find anything on how @command (within settings/commands) > should work though. > The body text of any @command node can contain any Leonine script. It could be a series of calls to k.simulateCommand. Here is tested code: @command

Re: Contract Node and Descendants

I did actually see that under the tree options in leoSettings but it appears to be set to true by default,might there be something else that could be unsetting it? How might I go about checking its currently assigned value? On Mon, 2020-08-24 at 17:34 -0500, Edward K. Ream wrote: > > On Mon,

Re: Contract Node and Descendants

On Mon, Aug 24, 2020 at 4:18 PM wrote: > So, what i'd ultimately like is for the left arrow key to first > 'collapse-all-subheads' and then 'contract-or-go-left', maybe called > 'collapse-or-go-left'. > This is almost what the default action of @bool collapse-on-lt-arrow is. Edward -- You

Re: Contract Node and Descendants

So, what i'd ultimately like is for the left arrow key to first 'collapse-all-subheads' and then 'contract-or-go-left', maybe called 'collapse-or-go-left'.I'm quite sure that I could accomplish this by creating a custom command in my myLeoSettings file and then binding that to hotkey.I can't seem

Re: leo\doc\LeoDocs.leo.orig

On Mon, Aug 24, 2020 at 3:44 PM George Zipperlen wrote: PR #1630 deletes this >> file. Edward >> > > Gitignore is your friend. > Right. That's why I said that I would delete or ignore the file. In this case, deleting was better, imo, because

Re: leo\doc\LeoDocs.leo.orig

On Monday, 24 August 2020 10:27:58 UTC-4, Edward K. Ream wrote: > > > > On Sunday, August 23, 2020 at 7:37:26 AM UTC-5, Thomas Passin wrote: >> >> >> So I don't know if it came from me, or if I got it via an update from >> Leo-editor. But it can be deleted. It's just like a .bak file created

Re: Contract Node and Descendants

On Mon, Aug 24, 2020 at 2:19 PM wrote: > Wow, that was fast - thank you so much! > You're welcome. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: Contract Node and Descendants

Wow, that was fast - thank you so much! On Mon, 2020-08-24 at 11:32 -0700, Edward K. Ream wrote: > On Monday, August 24, 2020 at 1:07:10 PM UTC-5, Edward K. Ream wrote: > > > Leo does have an expand-all-subheads command. It should have the > > corresponding contract-all-subheads command. I've

Re: Contract Node and Descendants

On Monday, August 24, 2020 at 1:07:10 PM UTC-5, Edward K. Ream wrote: Leo does have an expand-all-subheads command. It should have the > corresponding contract-all-subheads command. I've just created #1632 > for this. Expect > it later

Re: Contract Node and Descendants

On Mon, Aug 24, 2020 at 10:40 AM k-hen wrote: > Is there an option or function for Leo to contract all descendants of the > selected node? > No there isn't, as you can see with contract. Leo does have an expand-all-subheads command. It should have the corresponding contract-all-subheads

Re: Contract Node and Descendants

So you want "contract this node and all subtrees"? On Monday, August 24, 2020 at 12:47:48 PM UTC-4, k-hen wrote: > > That doesn't seem to be exactly what I'm looking for, when you expand it > again, its children are still expanded :-/ > > > On Monday, August 24, 2020 at 11:57:18 AM UTC-4

Re: Contract Node and Descendants

That doesn't seem to be exactly what I'm looking for, when you expand it again, its children are still expanded :-/ On Monday, August 24, 2020 at 11:57:18 AM UTC-4 tbp1...@gmail.com wrote: > Outline/"Expand/Contract"/"Contract Node". > > > On Monday, August 24, 2020 at 11:40:14 AM UTC-4, k-hen

Re: Leo Write-Only Mode

Right, good point!, thanks Tom :-) On Monday, August 24, 2020 at 11:55:12 AM UTC-4 tbp1...@gmail.com wrote: > Don't forget, viewrendered3 already uses @rst, @md, and @asciidoc. Please > don't make these mean something else. > > > On Monday, August 24, 2020 at 10:36:54 AM UTC-4, vitalije

Re: Contract Node and Descendants

Outline/"Expand/Contract"/"Contract Node". On Monday, August 24, 2020 at 11:40:14 AM UTC-4, k-hen wrote: > > Is there an option or function for Leo to contract all descendants of the > selected node? > > e.g. if use this option on B, then D would collapse as well, but not G. > Collapse other

Re: Leo Write-Only Mode

Don't forget, viewrendered3 already uses @rst, @md, and @asciidoc. Please don't make these mean something else. On Monday, August 24, 2020 at 10:36:54 AM UTC-4, vitalije wrote: > > > > On Monday, August 24, 2020 at 3:15:50 PM UTC+2, k-hen wrote: >> >> >> Pardon the beginner question, but are

Contract Node and Descendants

Is there an option or function for Leo to contract all descendants of the selected node? e.g. if use this option on B, then D would collapse as well, but not G. Collapse other nodes isn't quite what I want since that would do everything. A .. B C D .. E .. F .. G H

Re: Leo Write-Only Mode

Ok, makes sense, thanks. On Monday, August 24, 2020 at 10:36:54 AM UTC-4 vitalije wrote: > > > On Monday, August 24, 2020 at 3:15:50 PM UTC+2, k-hen wrote: >> >> >> Pardon the beginner question, but are you defining @coffee, @pug, etc >> yourself? >> Why not @md then instead of md: on the

Re: Nodes arbitrairily contract when inserting near the root node

On Sunday, August 16, 2020 at 11:46:39 PM UTC-5, vitalije wrote: > ...the behavior that you see is just a consequence of the position instability. When you insert a node in to the tree (or delete one), positions of all following siblings and their subtrees become invalid. Leo decides which

Re: Leo Write-Only Mode

On Monday, August 24, 2020 at 3:15:50 PM UTC+2, k-hen wrote: > > > Pardon the beginner question, but are you defining @coffee, @pug, etc > yourself? > Why not @md then instead of md: on the headline? > Either's fine of course, just trying to understand the differences and the > best

Re: leo\doc\LeoDocs.leo.orig

On Sunday, August 23, 2020 at 7:37:26 AM UTC-5, Thomas Passin wrote: > > > So I don't know if it came from me, or if I got it via an update from > Leo-editor. But it can be deleted. It's just like a .bak file created by > some other program that someone used on the file. > PR #1630

Re: Leo Write-Only Mode

On Mon, Aug 24, 2020 at 7:51 AM k-hen wrote: > > Re: the 'multiple update problem', I was thinking this would have to do > with multiple read/write nodes which is why i was trying to build a stream > with 1 reader and multiple writers. > Is there something else here to be aware of? > No.

Re: Leo Write-Only Mode

Thanks Vitalije, I'll have a look at that - thanks! Pardon the beginner question, but are you defining @coffee, @pug, etc yourself? Why not @md then instead of md: on the headline? Either's fine of course, just trying to understand the differences and the best practices. I'm trying to use

Re: Leo Write-Only Mode

Ok, thanks. So 1: there doesn't seem to be an inherent issue with @nosent, it's just that doing so in conjunction with cloned nodes from @auto could be unstable. Re: the 'multiple update problem', I was thinking this would have to do with multiple read/write nodes which is why i was trying to