Re: Proposal: @template nodes and related commands

Look at this thread . I have implemented paste command that does what was asked for: keeps the identity of all nodes that have clones outside copied tree. Internal clones treats the same way as past-node. Vitalije -- You receive

Re: Proposal: @template nodes and related commands

On Wed, May 27, 2020 at 2:08 PM Thomas Passin wrote: > I'm liking this proposal. My (limited) experience with writing commands is that at first, I only expect to use them within the one outline file I'm working on. The commands and shortcuts would live in the settings tree of that outline. When

Re: Proposal: @template nodes and related commands

On Wednesday, May 27, 2020 at 12:15:38 PM UTC-4, Edward K. Ream wrote: > > > On Wed, May 27, 2020 at 10:44 AM vitalije > > wrote: > >> I would only suggest to leave out settings file from the proposal. >> > > Sounds reasonable. If people want "global" settings that can be added > later. > > Hmm.

Re: Proposal: @template nodes and related commands

On Wed, May 27, 2020 at 10:44 AM vitalije wrote: > I would only suggest to leave out settings file from the proposal. > Sounds reasonable. If people want "global" settings that can be added later. Hmm. If all templates are local, there is less need for prompt-for-template... Edward -- You re

Re: Proposal: @template nodes and related commands

I would only suggest to leave out settings file from the proposal. It doesn't add anything substantial and it might lead to worse user experience (having to open settings file to change something, then save it and then restart Leo or reload settings). Instead command can look in the current out

Re: Proposal: @template nodes and related commands

On Wednesday, May 27, 2020 at 9:32:41 AM UTC-5, Edward K. Ream wrote: There are several details about the proposal which I forgot to mention: *Writing the template* Writing the template is the tricky part. The write code will allocate new gnx's to all nodes that are *not* descendants of candida

Proposal: @template nodes and related commands

This proposal incorporates ideas from the "Semantics of coping clones" thread. Imo, this proposal solves all the problems that have been discussed, with additional benefits. *Motivating ideas* 1. We want one or more *indivisible* (atomic) operations that copy a template and paste it following