Here's what I tried in my workbook: 1. Create a node for testing. 2. Copy its gnx to clipboard using a tiny script. * 3. Paste that gnx into the node's body for future reference. 4. Cut the node using the Outline/cut-node item. 5. Paste the node somewhere else in the same outline. 6. Copy the node's gnx to the clipboard. 7. Paste the gnx into the node's body. 8. Observe the 2nd gnx is not the same as the first.
* If you are having the statusbar show the gnx form of the unl, you can of course copy that from the clipboard instead of using a little script. A screenshot of the test node is attached. On Thursday, July 6, 2023 at 8:31:07 AM UTC-4 Edward K. Ream wrote: > On Thu, Jul 6, 2023 at 6:40 AM Thomas Passin <[email protected]> wrote: > > Maybe a paste of a node should always maintain the gnx unless it would >> create a clone. >> > > Hmm. Under what circumstance would a paste-node *not* create a clone? > > I sometimes use paste-node to create an independent copy of a node (and > its descendants). It's a way of cherry-picking a node from one branch to > another: > > - Copy and paste a node *N* in branch A to a copy of N, say *N-Copy*. > - Close Leo, change to branch B. *Never leave Leo open when changing > branches*. > - Open Leo. Now we're in branch B, but *N-Copy* contains the > cherry-picked node from branch A. > - Copy the body text of nodes from *N-Copy* to N. This changes N's text > while preserving N's gnx. > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3ae02cba-ac44-4384-a466-5c97d74754c6n%40googlegroups.com.
