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.
The @files in this part of the workbook are under version control so I saved the .leo file and checked git diff - zero difference. I wonder what would have happened though if I'd saved before 'Refresh from disk'. This .leo file is using Terry's leo_cloud.py plugin, so that may be involved or implicated somehow. However it reminds strongly of "@auto re-asserts over @file" (https://github.com/leo-editor/leo-editor/issues/580) also which doesn't use that plugin. Before: @path d:/matt/code/leo-editor -> @file setup.py ->->imports ->->docstring After: @path d:/matt/code/leo-editor -> @file setup.py ->->@file ../../setup.py ->->->imports ->->->docstring Matt -- 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.
