BTW: I am sure I am not the first to say this, but having once used 'git bisect', there is no going back...
On Friday, February 13, 2026 at 10:42:09 PM UTC jkn wrote: > Yes, that is the error I am seeing (I think it is not 'intermittent' - I > had different versions on different machines...) > > It was working fine in > > > Leo 6.8.7-devel, devel branch, build 6f915ea462 > > On Friday, February 13, 2026 at 9:41:28 PM UTC [email protected] wrote: > >> I just tried to insert an abbreviation into a headline and it failed. >> Instead, the command inserted the key string up the the first ";" of the >> trailing two. >> >> On Friday, February 13, 2026 at 11:41:48 AM UTC-5 Edward K. Ream wrote: >> >>> On Fri, Feb 13, 2026 at 8:25 AM jkn <[email protected]> wrote: >>> >>>> Hi Edward >>>> FYI: 'git bisect' identifies the problem as coming from this commit: >>>> >>>> 477ec61d24a0d90ebb90fcdf8d248c956287ef40 is the first bad commit >>>> commit 477ec61d24a0d90ebb90fcdf8d248c956287ef40 >>>> Author: Edward K. Ream <[email protected]> >>>> Date: Thu Oct 23 09:06:33 2025 -0500 >>>> >>>> Handle headlines separately and more simply >>>> >>> >>> Not surprising, as that was the only commit that tried to fix *another* >>> bug. >>> >>> Maybe back to the drawing board. I'll await more info. >>> >>> 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/656ae8ab-ffad-434c-b0d3-58bcd8ebc9d2n%40googlegroups.com.
