On 2026-06-14 04:50 -0400, Thomas Dickey wrote:
> On Sun, Jun 14, 2026 at 08:46:40AM +0200, Sven Joachim wrote:
>> I also did a quick test on neovim with TERM=xterm-256color. The good
>> news is that it starts up and seems to work, but there might be subtle
>> bugs because unibilium did not read in the complete file.
>
> The likely problem would be that some of the extended capabilities are
> not read.
>
> I don't have a test case, but suppose it would be in this chunk:
>
> kPrint7=\E[25;7~, kRIT3=\E[1;3C, kRIT4=\E[1;4C,
> kRIT5=\E[1;5C, kRIT6=\E[1;6C, kRIT7=\E[1;7C,
> kScroll=\E[28;2~, kUP=\E[1;2A, kUP3=\E[1;3A,
> kUP4=\E[1;4A, kUP5=\E[1;5A, kUP6=\E[1;6A, kUP7=\E[1;7A,
> ka2=\EOx, kb1=\EOt, kb3=\EOv, kc2=\EOr, kp5=\EOE, kpADD=\EOk,
> kpCMA=\EOl, kpDIV=\EOo, kpDOT=\EOn, kpMUL=\EOj, kpSUB=\EOm,
> kpZRO=\EOp, kxIN=\E[I, kxOUT=\E[O, rmxx=\E[29m,
> rv=\E\\[>41;[1-6][0-9][0-9];0c, smxx=\E[9m,
> xm=\E[<%i%p3%d;%p1%d;%p2%d;%?%p4%tM%em%;,
> xr=\EP>\\|XTerm\\(([1-9][0-9]+)\\)\E\\\\,
I suspect so. I tried to run "infocmp -x" on a truncated xterm-256color
entry, but infocmp refused to process that file.
,----
| $ mkdir -p /tmp/terminfo/x
| $ dd if=/usr/share/terminfo/x/xterm-256color
of=/tmp/terminfo/x/xterm-256color bs=4096 count=1
| [...]
| $ infocmp -A /usr/share/terminfo -B /tmp/terminfo xterm-256color
xterm-256color
| comparing xterm-256color to xterm-256color.
| comparing booleans.
| comparing numbers.
| comparing strings.
| $ infocmp -x -A /usr/share/terminfo -B /tmp/terminfo xterm-256color
xterm-256color
| infocmp: error: no match in terminfo database for terminal type
"xterm-256color"
`----
Cheers,
Sven
