On Fri, Aug 28, 2009 at 6:00 PM, Ville M. Vainio <[email protected]> wrote:

>
> On Sat, Aug 29, 2009 at 1:28 AM, Edward K. Ream<[email protected]>
> wrote:
>
> > surprised that it can happen.  Obviously, I am greatly mistaken about
> some
> > key aspect of how Leo reads files in the presence of caching.
>
> Study g.fast_add_last_child. It actually considers the first node read
> as the authoritary one, so the fix should probably be done there.


Thanks for this tip.  The bug should be easy to fix once it can be
reproduced reliably.

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
-~----------~----~----~----~------~----~------~--~---

Reply via email to