On Jul 5, 10:30 am, "Edward K. Ream" <[email protected]> wrote:
> There is a nasty interaction between @all (and > probably similar sentinels) and caching...I think it can be fixed, but it may > be tricky. What an understatement. In some sense the essence of the problem is that the call to c.cacher.writeFile(root,fileKey) happens "too soon", that is in at.read rather than, say, at.readAll. Thus, the read code must be extremely careful to cache the body text of nodes **as they are defined in the file being read**. One would think that all cloned text would agree, and yes, that is correct, but things are not so simple as text is being slurped in. Anyway, I can see what is happening, and that's a start :-) EKR -- 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.
