On Tuesday, June 20, 2017 at 6:28:00 AM UTC-5, Edward K. Ream wrote:

>> This is...Engineering Notebook post...will form the basis of an urgent 
enhancement item.

> Done at #505 <https://github.com/leo-editor/leo-editor/issues/505>: Leo's 
read code must be rewritten.

In the interests of reaching the widest possible audience, here is a 
shorter summary of my intentions, from #505:

**Clone precedence**
    
- 1 (top): clones in external files not containing @all
- 2 (medium): clones in external files containing @all.
- 3 (bottom): clones existing only in the .leo file.

**Design**

- Leo should warn about clone conflicts (and create recovered nodes) only 
when the conflict arises from two conflicting external files of the same 
priority. Otherwise, the **data in the higher-priority external file must 
rule**.
- The "last clone wins" rule must go. Position within the outline is 
unimportant.
- Headlines must *always* come from sentinels (for @file nodes).
- Leo should *never* report resurrected" nodes.

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.

Reply via email to