On Mon, Mar 16, 2015 at 11:36 AM, vitalije <[email protected]> wrote:
> I think that methods which manipulate nodes on lowest level should check > and alarm user if ever node with same gnx is added, inserted, moved,... in > children (or maybe even in subtree in general). > I agree, although there are already checks in place. Something strange is going on. It may be related to the @clean read logic... The first step will be to allow Leo to load corrupt .leo files. I just filed https://github.com/leo-editor/leo-editor/issues/158. This is the most serious bug in Leo in a long time. The next step will be to add the checks you suggest everywhere. This should help us figure out why Leo is generating duplicate gnx's. 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.
