On Sat, Nov 21 2020, Sven Joachim wrote:
>> 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?
So I think there's another problem here. The reason I had to change
~/.mlterm/termcap was to fix the behavior of F[1-4] keys by making
mlterm send a different sequence.
mlterm sends ^[OP for F1, but all mlterm terminfo definitions seem to
expect \[[11~
ls mlterm* | xargs -l infocmp | grep kf1=
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\E[11~, kf10=\E[21~,
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\E[11~, kf10=\E[21~,
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\E[11~, kf10=\E[21~,
kcuu1=\EOA, kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\E[11~,
kdch1=\E[3~, kend=\EOF, kent=\EOM, kf1=\E[11~, kf10=\E[21~,
Either all these definitions are broken, or I need some enlightenment?
If I remove my customization, bce works as it should, but F[1-4] are
broken.
Sure I can also add :ut to my ~/.mlterm/termcap, then mlterm sends what
the terminfo says, but it doesn't look like I'm fixing the right thing
here.
