On Monday, July 10, 2017 at 10:05:54 AM UTC-5, Edward K. Ream wrote: 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 >
New code in master simply omits this warning. Experiments show that this policy is reasonable. Indeed, Leo will create recovered nodes for "unexpected" changes that arise when switching branches. These alert the user of *potential* problems. Leo will alert the user of *actual* problems when writing changed files. And if that isn't enough, the user can always restore code using git's recovery mechanisms. In short, the only real problem with the previous read logic was a way-too-alarming internal error message. I have once again closed #505: Leo's read code must be rewritten. <https://github.com/leo-editor/leo-editor/issues/505> The new-read branch is now dormant. Btw, my new policy is to retain dormant branches indefinitely on GitHub. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
