---------- Forwarded message --------- From: Matt Wilkie <[email protected]> Date: Sun, Oct 14, 2018 at 6:21 PM Subject: warning: bug in cached @file and/or Leo Cloud plugin? To: leo-editor <[email protected]>
Heads up: > I've just had this weird situation where I noticed the @file contents were definitely NOT the most recent version of the file. There were several sections of old content in nodes I know I'd changed over the last few days. I used "refresh from disk", after which the I saw the new content I expected. At least I'm pretty sure it's the newest content. At the same time the hierarchy changed to have nested @file nodes. A nested @file node is an indication that the gnx in the external file does not match the gnx in the outline. I'm quite sure of this because it was an issue in the new debugger code. The node "function: get_gnx_from_file" in leoDebugger.py scans the external file and sets the gnx (v.fileIndex) of a just-created @file node to the gnx in the first @+node sentinel of the external file. Leo's new read code does *not* have this logic, which results in the nested @file node. Imo, it's probably not going to help much to change Leo's read code. In fact, the strange nesting is a good indication that something is amiss. The downloaded workbook doesn't indicate much because the corresponding external files are not attached. 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.
