On Wed, Jun 24, 2009 at 6:41 PM, James A. Donald <[email protected]> wrote:
> > Edward K. Ream wrote: > > I have often said that at most one @thin tree should be responsible for > each > > clone. > > doubtless, but there is nothing to mark or record a clone as which @thin > tree is the right one for editing it, should one edit it outside of leo, > or, as is quite likely, someone else edit it outside of leo. I don't think Leo can, or should, do anything more in this area. You should arrange your .leo file so that editing the "master" files externally will have the desired result. For leoPy.leo, this means putting @thin leoProjects.txt before all the other @thin nodes. It's as simple as that. Edward --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
