On Sunday, July 9, 2017 at 1:09:57 AM UTC-5, Edward K. Ream wrote: *Danger*: *stashing goes back in time in master*. All of Leo's caches must > be completely cleared! >
And I just came across another danger. If I have written a file in master, I have also written it to *master's* cache. Doing git branch -b doesn't clear that cache. As a result, on several occasions I have gotten this: Internal Leo error in checkForChangedNodes A workaround is to clear the cache for the affected .leo file. Not sure what the real solution is. 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.
