On Friday, November 15, 2024 at 8:07:07 AM UTC-5 Edward K. Ream wrote: On Fri, Nov 15, 2024 at 6:03 AM Thomas Passin <[email protected]> wrote:
> I was not able to reproduce this bug using yesterday's version of devel. Issue #4181 <https://github.com/leo-editor/leo-editor/issues/4181> now more clearly describes how to reproduce the bug. I read that issue before trying to repro the bug. I saw text that looked right under both the headings " **Completing the proof**" and "**Discussion **". I suppose you did some additional action that wasn't written down in the steps in the Issue. > You wrote that you encountered the bug in a private branch. I was seriously confused at first. I wasn't very clear about the sequence of events. The bug undoubtedly exists. It happens reliably (in devel) *if* one knows how to make it happen. I examined this bug for about 8 hours yesterday. I now know exactly *when *the bug happens, but I still do not understand *why *it happened or *exactly *why the PR makes it go away. To repeat: - This is one of the most mysterious bugs in Leo's history. I wonder if you checked out a version of devel, or an earlier release branch, from before you started changing the colorizer, whether you would be able to trigger the same behavior using the same steps, now that you know how. I'm not going to try that myself because I can't reproduce the behavior. - I have only conjectures about the bug's ultimate cause. See PR #4182 <https://github.com/leo-editor/leo-editor/pull/4182> for my latest thoughts. > After you do this merge, is this bug going to appear in devel? No. It should *disappear,* subject to the caveats above. 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 visit https://groups.google.com/d/msgid/leo-editor/21acfbdb-92ce-46f8-8aa5-b1899a871ac6n%40googlegroups.com.
