On Tue, Aug 18, 2009 at 10:30 AM, Edward K. Ream <[email protected]>wrote:
> > > On Tue, Aug 18, 2009 at 10:22 AM, Ville M. Vainio <[email protected]>wrote: > >> >> On Tue, Aug 18, 2009 at 5:34 PM, Edward K. Ream<[email protected]> >> wrote: >> >> > 5. I strongly suspect caching is the problem. If I pull a clean copy >> > of lp:leo-editor into a new (but previously existing) directory, >> > opening leoPy.leo does not re-read all the source files, but instead >> > uses cached values. After clearing all the contents home/.leo/db, >> > opening leoPy.leo does, in fact, re-read all the sources files. >> >> If we can reproduce this, we could perhaps try limiting it to problems >> with leoTodo.txt / leoNotes.txt - that is, nodes cloned across >> multiple external files. The implementation of caching is not on 100% >> solid foundation when those are involved. > > > That is indeed what happened. The clones were likely in leoProjects.txt. > I forgot to mention that it seems ok to commit to the trunk now. 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 -~----------~----~----~----~------~----~------~--~---
