On Wed, Nov 8, 2017 at 1:03 PM, vitalije <[email protected]> wrote:
I am not 100% sure, but I believe that this restriction is dictated with > the present read or write algorithm. > Imo, the problem is a fairly straightforward bug in in at.writeAll. Indeed, this method suppresses writes of any @<file> node p if p.v has already been written. The "seen" set contains all previously-written vnodes. But this test fails if p.v refers to two different paths. It looks like the "seen" set should contain tuples (p.v, path) where path is the full path to the to-be-written file. I'll attempt a fix immediately. 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.
