Kitty: Cannot read termcap database

Created on 5 Feb 2018  路  19Comments  路  Source: kovidgoyal/kitty

I am not sure if this is an issue or not but I have the following output when 'brew upgrade'.
Other terminals are quiet.

$ brew upgrade
Cannot read termcap database;
using dumb terminal settings.

Most helpful comment

I just posted about this in #423. What seemed to solve it for me is ln -s /Applications/kitty.app/Contents/Frameworks/kitty/terminfo ~/.terminfo. Perhaps it's worth reporting this as an issue to homebrew, as it doesn't seem to be respecting the environment variables of the user.

All 19 comments

Have you changed the value of TERM?

And what does running the following two comamnd output:

env | grep TERM
infocmp

$ env | grep TERM
COLORTERM=truecolor
TERM=xterm-kitty
TERMINFO=/Applications/kitty.app/Contents/Frameworks/kitty/terminfo

$ infocmp

Reconstructed via infocmp from file: /Applications/kitty.app/Contents/Frameworks/kitty/terminfo/78/xterm-kitty

xterm-kitty|KovIdTTY,
am, ccc, hs, km, mc5i, mir, msgr, npc, xenl,
colors#256, cols#80, it#8, lines#24, pairs#32767,
acsc=++\,\,--..00``aaffgghhiijjkkllmmnnooppqqrrssttuuvvwwxxyyzz{{||}}~~,
bel=^G, bold=\E[1m, cbt=\E[Z, civis=\E[?25l,
clear=\E[H\E[2J, cnorm=\E[?12l\E[?25h, cr=^M,
csr=\E[%i%p1%d;%p2%dr, cub=\E[%p1%dD, cub1=^H,
cud=\E[%p1%dB, cud1=^J, cuf=\E[%p1%dC, cuf1=\E[C,
cup=\E[%i%p1%d;%p2%dH, cuu=\E[%p1%dA, cuu1=\E[A,
cvvis=\E[?12;25h, dch=\E[%p1%dP, dch1=\E[P, dim=\E[2m,
dl=\E[%p1%dM, dl1=\E[M, dsl=\E]2;\007, ech=\E[%p1%dX,
ed=\E[J, el=\E[K, el1=\E[1K, flash=\E[?5h$<100/>\E[?5l,
fsl=^G, home=\E[H, hpa=\E[%i%p1%dG, ht=^I, hts=\EH,
ich=\E[%p1%d@, il=\E[%p1%dL, il1=\E[L, ind=^J,
indn=\E[%p1%dS,
initc=\E]4;%p1%d;rgb\:%p2%{255}%%{1000}%/%2.2X/%p3%{255}%%{1000}%/%2.2X/%p4%{255}%*%{1000}%/%2.2X\E\,
kEND=\E[1;2F, kHOM=\E[1;2H, kLFT=\E[1;2D, kRIT=\E[1;2C,
ka1=, ka3=, kbs=\177, kc1=, kc3=, kcbt=\E[Z, kcub1=\EOD,
kcud1=\EOB, kcuf1=\EOC, kcuu1=\EOA, kdch1=\E[3~, kend=\EOF,
kf1=\EOP, kf10=\E[21~, kf11=\E[23~, kf12=\E[24~, kf2=\EOQ,
kf3=\EOR, kf4=\EOS, kf5=\E[15~, kf6=\E[17~, kf7=\E[18~,
kf8=\E[19~, kf9=\E[20~, khlp=, khome=\EOH, kich1=\E[2~,
kind=\E[1;2B, kmous=\E[M, knp=\E[6~, kpp=\E[5~,
kri=\E[1;2A, kund=, oc=\E]104\007, op=\E[39;49m, rc=\E8,
rev=\E[7m, ri=\EM, rin=\E[%p1%dT, ritm=\E[23m, rmacs=\E(B,
rmam=\E[?7l, rmcup=\E[?1049l, rmir=\E[4l, rmkx=\E[?1l,
rmso=\E[27m, rmul=\E[24m, rs1=\Ec, sc=\E7,
setab=\E[%?%p1%{8}%<%t4%p1%d%e%p1%{16}%<%t10%p1%{8}%-%d%e48;5;%p1%d%;m,
setaf=\E[%?%p1%{8}%<%t3%p1%d%e%p1%{16}%<%t9%p1%{8}%-%d%e38;5;%p1%d%;m,
sgr=%?%p9%t\E(0%e\E(B%;\E[0%?%p6%t;1%;%?%p2%t;4%;%?%p1%p3%|%t;7%;%?%p4%t;5%;%?%p7%t;8%;m,
sgr0=\E(B\E[m, sitm=\E[3m, smacs=\E(0, smam=\E[?7h,
smcup=\E[?1049h, smir=\E[4h, smkx=\E[?1h, smso=\E[7m,
smul=\E[4m, tbc=\E[3g, tsl=\E]2;, vpa=\E[%i%p1%dd,

According to that, terminfo is accessible, so I have no idea why brew is giving you that message. You'd have to ask it's maintainers, or more properly, the maintainers of whatever terminal UI library it uses.

Closing, as far as I can see, this is not a bug in kitty.

Can this be of any use? Sorry to post to a closed post.
diff.txt

I dont see what use that would be. kitty is not xterm, it does not and must not have the same terminfo as xterm.

I just posted about this in #423. What seemed to solve it for me is ln -s /Applications/kitty.app/Contents/Frameworks/kitty/terminfo ~/.terminfo. Perhaps it's worth reporting this as an issue to homebrew, as it doesn't seem to be respecting the environment variables of the user.

Yeah, as I said in https://github.com/kovidgoyal/kitty/issues/310#issuecomment-363355515 it should be reported to brew or more properly to the maintainers of whatever terminal UI library it uses.

I got following error in the latest ver.

Cannot read termcap database;
using dumb terminal settings.

I think that it's because xterm-kitty doesn't exit on my PC.
I can't find xterm-kitty file on my Mac(/usr/share/terminfo/). Where can I get this file?

env | grep TERMINFO

Thank you so much. I confirmed, but the error was shown if TERM is xterm-kitty. Nothing error when I changed TERM to xterm-256color for run brew command.

@k010c1232 have you tried ln -s /Applications/kitty.app/Contents/Frameworks/kitty/terminfo ~/.terminfo?

@k010c1232 have you tried ln -s /Applications/kitty.app/Contents/Frameworks/kitty/terminfo ~/.terminfo?

Thanks @zoidbergwill
I tried, but I can't. Now I'm using Alacritty.

This was caused by Homebrew clearing $TERMINFO. Fixed upstream: https://github.com/Homebrew/brew/pull/5445.

Wicked cool, bro! 馃帀

This was caused by Homebrew clearing $TERMINFO. Fixed upstream: Homebrew/brew#5445.

Cool! Do you know fixed ver when will release?

@k010c1232 Homebrew 1.9.0 has been released and includes the fix.

The TERMINFO environment variable is passed through to Homebrew to enable support for some terminal emulators.

https://brew.sh/2019/01/09/homebrew-1.9.0/

as of 2019-11-01 , this issue seems still existing with my kitty on macosx ...

Was this page helpful?
0 / 5 - 0 ratings

Related issues

wavexx picture wavexx  路  3Comments

keyofnight picture keyofnight  路  3Comments

Jomik picture Jomik  路  4Comments

metalelf0 picture metalelf0  路  4Comments

atomsymbol picture atomsymbol  路  3Comments