On Mon, Mar 16, 2015 at 10:00 AM, vitalije <[email protected]> wrote:
> It happened again. Right now I have the same situation. > Rev 60d61e1 allows Leo to read the last file you sent. It's just a hack: it only checks whether the *immediate* parent of a to-be-created node has the same gnx. If so, allocates an entirely new node and issues a warning. As I look at the bad outline, it looks to me that some part of the @clean write logic may be to blame. For example, writing the root twice will cause problems with gnx's even if the actual gnx logic is sound. Many thanks for continuing to test Leo in its present buggy state. 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.
