On Sat, Aug 29, 2009 at 12:40 AM, Edward K. Ream<[email protected]> wrote:
> I was able to see some reversions due to clones in leoProjects.txt not being > in synch. It was a big mistake not to pay more attention to that file. I > can now load leoPy.leo and force a write of all files three times in a row > with no changes. That wasn't true before. Let's consider this a valuable warning about inherent unreliability of non-obviously modifying cloned trees across thin files. It comes up a lot, and we really need to either implement a priority system or let the user choose the more important file on load. It might be a good idea to priorize this after one-node stuff works fine. In any case, the warning needs to be much louder than "changed: " - this is something we could push to 4.6.3 too. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
