On 2020-11-20 20:08 -0500, Thomas Dickey wrote:
> On Fri, Nov 20, 2020 at 10:42:51PM +0100, Yuri D'Elia wrote:
>> On Fri, Nov 20 2020, Sven Joachim wrote:
>> > Which version of mlterm do you use?
>>
>> I'm also using mlterm 3.9.0-1.
>>
>> So after some scrambling, I have a custom ~/.mlterm/termcap config to
>> override the sequence sent by F[1-4]:
>>
>> mlterm-256color:\
>> k1=\E[11~:k2=\E[12~:k3=\E[13~:k4=\E[14~
>>
>> Removing this (so that mlterm sends it's usual \EOP/*) fixes the
>> background-color rendering.
>>
>> I'm puzzled as of why this override would influence this at all?
>
> It sounds like a problem in mlterm, e.g., in the way it stores the "ut"
> (terminfo "bce") capability. It doesn't appear to read the ncurses
> terminal database, which (since bce worked when I tested it) says it
> does back-color-erase, while the compiled-in termcap says it does not.
>
> If the mlterm package changed that ut-default setting, then providing your
> own termcap settings may have reset the behavior to match the compiled-in
> NON-ut default.
That seems to have hit the mark. Indeed, if ":ut" is added to Yuri's
termcap example, mlterm works correctly again.
Yuri, would you like to bring this to the attention of the mlterm
developers?
Cheers,
Sven
