On Saturday, August 12, 2017 at 1:52:00 PM UTC+2, Edward K. Ream wrote:
> > wrote:
> Something is not right. When load my local copy of leoPy.leo, @file
> leoAtFile.py does not contain checkExternalFileAgainstDb.
> I see this method (in an external editor), in the node:
> #@+node:vitalije.20170701155512.1: *6* at.checkExternalFileAgainstDb
> Clearing all caches does not help. Such a thing has never happened before.
> Saving the .leo file deletes the node from the external file. git
> checkout leo restores it.
> Vitalije, what might be causing this?
> Have you tried opening LeoPyRef.leo?
Is it possible that some plugin that you have enabled and I don't can cause
I hope we can find what is causing this strange thing, but it is something
that I was complaining in #538 and #540. Perhaps it is not usual thing that
you encounter this problem, because most of the time your copy of LeoPy.leo
is fresher and richer than copy of others.
The only thing that comes in my mind is that when g.SQLITE is true,
retrieving from cache is skipped. Can you test once again clearing cache,
then git checkout -f, so that all external files are unchanged and then
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to email@example.com.
Visit this group at https://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.