On Mon, Nov 6, 2017 at 2:49 PM, Phil <[email protected]> wrote: > It used to be the case that changing a cloned @file-like node would result in those changes being saved to all the paths under which the clone lived in the Leo outline.
I see this behavior. Please file a bug report. > it seems inconsistent that changing an organizer-node-clone would trigger file writes for all files containing that clone, but that changing an @file-node-clone would not do the same. I agree. 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
