On Jan 13, 6:34 am, "Edward K. Ream" <[email protected]> wrote:
> >> To summarize my current situation, currently I don't use clones at all, > >> and I restricted my project.leo to non-nested @shadow nodes, containing > >> multi-level tree of <<sections>> and occasionally @others. Nothing else, > >> yet I still get some "uncached read node changed" messages every time I am > >> refreshing shadow nodes from changed external files. > > > Sounds like a bug to me. I'll look into it. > > Afaik, this is the expected behavior. Indeed, Leo will generate a > "Revered Nodes" nodes containing inner nodes for all such > externally-changed nodes, for all @<file> trees that recreate outlines > using sentinels. This includes @file and @shadow, but not @auto (it > uses import logic). This is an important feature of Leo. At present, > there is no option for disabling it. On second thought, @shadow should work more like @auto than @file in this regard. In other words, @shadow should not create *recovered* (not revered) nodes. I plan to do this today. 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.
