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 

leo/commands/abbrevCommands.py | 48 +++++++++++++++++
------------------------- 
1 file changed, 19 insertions(+), 29 deletions(-) 

Thanks and Regards
    J^n



On Friday, February 6, 2026 at 10:35:59 AM UTC jkn wrote:

> Hi Edward
>     sure - will do once I can be a bit more definitive. It is working fine 
> today (on this machine...).
>
> I tried starting up leo explicitly:
>
>     $ python3 launchLeo.py
>
> but didn't see any errors when misbehaviour occurred. I will see if I can 
> learn more.
>
>     J^n
>
>
> On Friday, February 6, 2026 at 10:24:56 AM UTC Edward K. Ream wrote:
>
>> On Thu, Feb 5, 2026 at 5:11 AM jkn <[email protected]> wrote:
>>
>>> Hi all
>>>     I am seeing an odd error related to abbreviations recently.
>>>
>>> I have some simple abbreviations to just quickly insert boilerplate 
>>> text. There are defined in myLeoSettings.leo
>>>
>>> On some invocations of Leo, ie. only sometimes, these do not seem to be 
>>> working properly when editing a headline (which is their use case)
>>>
>>
>> Thanks for this report. Please file an issue with as much detail as 
>> possible.
>>
>> Editing headlines is inherently tricky. I'll review recent changes to the 
>> abbreviation code.
>>
>> 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/813a542e-a014-4ab1-a976-bb23dcdd2a02n%40googlegroups.com.

Reply via email to