> What I want to avoid is a situation in which two different .leo files or > @thin nodes each have a presumptive claim to "own" a node.
Its clear that problems can arise if a Leo file has a cloned node in multiple @thin files and one or more of those @thin files are being edited in an external editor including another Leo file. However, many Leo users are working on "one man" projects where they are the only person editing the @thin files and they only edit them using that Leo file. In that case, I don't see a problem using clones across @thin files. TL --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
