>
> A nested @file node is an indication that the gnx in the external file
> does not match the gnx in the outline.
>
In a "refresh from disk" circumstance I would expect the external file to
"win", ie. assume it's the most correct and discard remembered information.
The downloaded workbook
-- Forwarded message -
From: Matt Wilkie
Date: Sun, Oct 14, 2018 at 6:21 PM
Subject: warning: bug in cached @file and/or Leo Cloud plugin?
To: leo-editor
Heads up:
> I've just had this weird situation where I noticed the @file contents
were definitely NOT the most rec
My workbook.leo attached, post "refresh-from-disk" behaviour talked about
last message, and post removing all the other private nodes that were in
this file.
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and
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
