Welcome to Vifm Q&A, where you can ask questions about using Vifm. Registration is optional, anonymous posts are moderated. E-mail and GitHub logins are enabled.
0 votes
in vifm by

When I run vifm in kitty, "'xterm-kitty': unknown terminal type" is displayed. I didn't find any information on the Internet about others having this issue. What's the problem?

1 Answer

0 votes
by
 
Best answer

This suggests that you have $TERM set to xterm-kitty, but there is no such entry in the terminfo database (e.g., file /usr/share/terminfo/x/xterm-kitty doesn't exist).

If other applications work in this case, then are you using Vifm via AppImage? AppImage comes with its own terminfo database (inside of it) which lacks xterm-kitty.

by

Exactly I'm using AppImage. Might try other installation instead. Thank you.

by

A found a workaround for AppImage: export TERMINFO_DIRS=/usr/share/terminfo.

ncurses is supposed to look at /usr/share/terminfo, but due to the way it was built for AppImage, it looks in /share/terminfo instead. This will be fixed in the next release, thanks for bringing it up.

by

In fact, in kitty's case, it sets environment variable TERMINFO to point to its own terminfo folder in its distribution. I fixed the issue by copying its terminfo file to a local ~/.terminfo folder. So it might be vifm not reading TERMINFO? Because all other programs (including some AppImage, like neovim) seem to run without problem. Just for your information.

by

A wrapper in AppImage does export TERMINFO=$APPDIR/usr/share/terminfo, which overrides $TERMINFO set externally. Maybe it should set $TERMINFO_DIRS instead.

...