> My apologies for the delay in responding. No worries, I know my post was long and somewhat ambitious.
> > Envision solution: > > There are three capabilities that Leo would need that don't exist > > now that could make this possible: > > 1) A procedure to copy a full path-to-node to the clipboard > > Easily done. Naturally, any path can break. In this case the path > could break in at least two ways: if the clone repository moved, or > if you move the .leo file to a different machine with a different > repository path. Both of these could cause problems, but let's assume > that you can live with the potential problems. Of course, no different than what exists now where a path may break for a variety of reasons. Easy enough to change it. > I think this approach has merit. Certainly, it has no global impact > on Leo. Synced nodes are simple ordinary nodes as far as Leo is > concerned. They could be cloned as well, probably without any ill > effects. > I've just filed a wishlist bug referencing this conversation: > > https://bugs.launchpad.net/leo-editor/+bug/816996 Thanks! Rob......... -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
