On Mon, Jun 21, 2021 at 11:00:54AM -0000, Stuart Henderson wrote: > On 2021-06-20, Björn Gohla <b.go...@gmx.de> wrote: > > > > hi all, > > > > i have the following problem with the kitty terminal emulator: > > > > ---- > > 15:43:39 bgohla@titanic ~ $ doas pkg_add hello > > doas (bgo...@titanic.my.domain) password: > > failed termcap lookup on xterm-kitty at > > /usr/libdata/perl5/OpenBSD/ProgressMeter/Term.pm line 113. > > 15:44:02 bgohla@titanic ~ $ echo $TERM > > xterm-kitty > > 15:44:17 bgohla@titanic ~ $ > > ---- > > > > it seems the problem is that there is no entry for xterm-kitty in > > /etc/termcap. the above pkg_add invocation works when i set TERM=xterm . > > > > i suppose one could just add a termcap entry that redirects to > > xterm. > > > > would this be a patch in the kitty port, or does this require a change > > to the base system? > > > > -- > > cheers, > > björn > > > > > > It would require a change in the base system, /usr/share/misc/termcap is > a system file and isn't something that can be modified from a port. > Additionally it will get overwritten when the OS is updated.
It should be possible to add xterm-kitty from the output of $ infocmp -C xterm-kitty to /usr/share/misc/termcap; similar to what was done over the years for example with rxvt-unicode-256color. The template in src for this seems to be share/termtypes/termtypes.master, but it uses a different format for the entries (commas as separators instead of colons and some differences in capabilities shorthands). termininfo(5) seems to have enough information to construct an entry for termtypes.master if that's desired. Not sure if kitty is important enough to add in there. I've been running with "term xterm-256color" in ~/.config/kitty/kitty.conf for a while without issues. However, xterm-256color doesn't seem to match xterm-kitty 100%. > > Software that uses terminfo will work with kitty as it sets TERMINFO in > the environment pointing at its own special file; that's not possible > with termcap. > >
