I got some more clarity about this, and I commented the following on the proposed PR:
I can now see that the concept of operation is simple. Within an outline, for a parent-and-subtree: - Ask for a move, get a move; gnxs do not change; - Cut-paste is the same as a move; - Ask for a copy, get a copy, meaning all nodes get new gnxs. - To paste a copy when the top of the copied tree already exists means *by definition* to ask for a copy. I think that Leo's defaults should act this way. I'd rather that the behaviors not change via a setting because their effect can be invisible until later, when it might be too late. Also, those of us who run several installations (for instance, on a Linux VM for testing purposes) would inevitably forget what state those settings were on what machine. That might end up being very confusing, to say the least! Once we're sure that the paste-copy and paste-clone commands are working as intended, then we can probably make it fairly clear by naming commands and menu items (and also in the docstrings) as to what to expect. On Friday, July 7, 2023 at 7:15:38 AM UTC-4 Edward K. Ream wrote: > On Friday, July 7, 2023 at 3:59:49 AM UTC-5 Edward K. Ream wrote: > > > I'll leave #3429 <https://github.com/leo-editor/leo-editor/issues/3429> > > open > while we continue our discussion. > > I have assigned this issue to Leo 6.7.5. No way will this issue be part of > 6.7.4. > > 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/32a449d4-b64f-4981-b492-1376b6bac4e6n%40googlegroups.com.
