On Fri, Aug 28, 2009 at 5:21 PM, Ville M. Vainio <[email protected]> wrote:
> > 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. You literally took the words out of my mouth. Somehow the problem has become much worse with caching. I don't understand the cause at present, but imo, this absolutely must be fixed before Leo 4.6.3, that is, both in the 46-maint branch and in the trunk. > It might be a good idea to priorize this after one-node stuff works fine. Imo, this is independent of the one-node stuff. I don't believe g.unified_nodes was ever in effect while these problems were occurring, or rather, I am certain that they happened at least some of the time when g.unified_nodes was False. > In any case, the warning needs to be much louder than "changed: " - > this is something we could push to 4.6.3 too. Warnings are never effective in this kind of situation. We must find a way to ensure that the problem will never arise in normal operation. That was the situation previously. To repeat, this problem has suddenly become much worse. I am quite surprised that it can happen. Obviously, I am greatly mistaken about some key aspect of how Leo reads files in the presence of caching. 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 -~----------~----~----~----~------~----~------~--~---
