On Monday, May 10, 2021 at 8:50:39 AM UTC-5 [email protected] wrote: > I added one space to LeoPyRef.leo then saved it. I got the same massive > size reduction. Then I looked at the before-after files with kdiff3. > There were big chunks of code missing. Often they were entire nodes, but I > think not always. So not just a matter of converting spaces to tabs.
Thanks for your continued testing. LeoPyRef.leo is out of sync just now, meaning I changed @clean and @auto nodes to @file in my leoPy.leo, but not LeoPyRef.leo itself (because of the problems re #1926). Things may get worse before they get better :-) BTW, I am still using Qt 6.0.2 and I am seeing byte hash from time to time. I just realized that the view-lossage command will tell me what keys Leo/Qt thinks I typed. This command could be improved in several ways. I'll create a new issue for the proposed improvements. Also, I am pretty sure that Leo's write logic is generally writing too much to the .leo file. I'll create another new issue and a separate branch. The fix might be straightforward, but any change to Leo's write logic is fraught with danger, so no promises when any improvements may become part of Leo. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/157c6956-d518-4eba-b2ba-312c86c8ad80n%40googlegroups.com.
