Ok, thanks. So 1: there doesn't seem to be an inherent issue with @nosent, it's just that doing so in conjunction with cloned nodes from @auto could be unstable. Re: the 'multiple update problem', I was thinking this would have to do with multiple read/write nodes which is why i was trying to build a stream with 1 reader and multiple writers. Is there something else here to be aware of?
I can/will look into scripting though but that seems to really up the level of difficulty, not so much for my benefit, but for others I might want to share this with. On Friday, August 21, 2020 at 1:00:03 PM UTC-4 Edward K. Ream wrote: > On Fri, Aug 21, 2020 at 9:08 AM k-hen <[email protected]> wrote: > > I feel like maybe I'm missing something with @nosent though, why is it >> much harder to use? >> > > Clones are fragile in @auto trees, even when @persistence is enabled. > > Also, so-called cross-file clones can be problematic, due to a fairly > nasty version of the multiple update problem. > > It sounds to me like a script-based solution might be best. You could, > say, populate some specially marked nodes (of your own choosing) with > content. Examples might be @header and @footer. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/eff1651d-83cd-4318-b810-4efc706d07f2n%40googlegroups.com.
