Last night Leo reported duplicate gnx's after cutting an outline from leoSettings.leo to leoPy.leo. I reported the details here <https://github.com/leo-editor/leo-editor/issues/158>. This is an extremely serious bug. It's also perversely good news.
Here is the plan: 1. *Discover why the gnx's collided*. The gnx's report that the colliding vnodes were created yesterday, 20150320 at 233042. Folks, this makes no sense. Imo, a botch in gnx caching likely caused this collision. It's *essential *to find the cause of this bug before doing anything else. 2. *Permanently activate all gnx checks*, as discussed in this thread <https://groups.google.com/forum/#!topic/leo-editor/9STvVMI5Ku4>. 3. *Get rid of the gnx caching scheme!* It will no longer be needed when Leo calls check-outline regularly. Imo, gnx caching is dubious engineering. I am so looking forward to killing it. Recall that gnx caching arose from a bizarre special case in which a Leo bridge opens several .leo files within the same second. check-outline can handle those special cases. The bridge won't mind the warnings -) 4. *Fix paste-retaining-clones*. It is fortunate that this issue <https://github.com/leo-editor/leo-editor/issues/141> has not yet been addressed. *Summary*: We have come full circle. The problems with the bridge resulted in gnx caching. Problems with gnx caching prompted continuous checking of .leo files. *Permanent, continuous* checking will eliminate the need for gnx caching. The result will be a simpler, more robust Leo. This work has top priority: we must test the resulting code for at least another work before releasing b1. 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
