One last detail, there doesn't need to be a parent collecting node, the most intuitive option is behaving just like copy/cut/paste.
On Tuesday, April 5, 2016 at 7:45:58 AM UTC-4, john lunzer wrote: > > Ah, this is why I thought clone-marked-nodes moved it to the bottom, > because cffm is similar to clone-marked-nodes but moves the node to the > bottom and collapses the tree. > > I disagree that this is the answer. cffm is clunky in this context, here > is the sequence if I want to clone marked nodes to a specific place: > > 1. Mark my nodes (1 command) > 2. Execute cffm (all nodes have been collapsed except for the cffm > parent node) (1 command) > 3. Navigate to the cffm parent node (my focus was at the first node in > the outline). > 4. Cut the cffm parent node (1 command) > 5. Navigate to where I want the cffm node to be > 6. Execute paste-retaining-clones (1 command) > > Using clone-marked-nodes: > > 1. Mark my nodes. (1 command) > 2. Navigate to where I want my marked nodes to go > 3. Execute clone-marked-nodes (1 command) > > Comparing the two, the first sequence requires twice as many steps and > twice as many commands. In second sequence the command name tells me what I > wanted to do in the first place, making it more more discoverable to new > users. Additionally in the first sequence the context of my outline has > been destroyed because the outline was collapsed. Edward I believe you are > using cffm differently than what I am proposing which is why it doesn't > work well here. > > That is just for cloning, there remains no "simplest" > non-work-around-plugin options for moving and copying multiple nodes, which > follows the same simplest possible sequence as I have proposed. > > Leo already has clone-marked-nodes (but it doesn't follow Leo's > copy/cut/paste positioning rules). *My proposal: create move-marked and > copy-marked and make clone-marked-nodes match their behavior.* And > possibly even rename clone-marked-nodes to simply clone-marked. > > I am interested to hear where my proposal fails to improve Leo's > functionality while remaining as simple as possible? > > On Monday, April 4, 2016 at 6:19:39 PM UTC-4, Edward K. Ream wrote: >> >> On Mon, Apr 4, 2016 at 12:08 PM, john lunzer <lun...@gmail.com> wrote: >> >> > >> I find it near impossible to move multiple nodes around in Leo. >> >> The new cffm command makes this a snap. Mark the nodes you are >> interested in. Do cffm. Now you have a node containing clones of all the >> nodes. Move that node where you will, or copy and paste it. >> >> This is a major improvement to Leo's work flow. Everyone should be aware >> of it. I've just made a note to document it in Leo's tutorial, along with >> cff. >> >> EKR >> > -- 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
