Open ghost opened 6 years ago
If you are using micro 1.4.0, micro should read the terminfo entry with infocmp. Are you using a prebuilt binary or did you build from source?
I have a similar problem. The package is installed from AUR
[~]$ micro -version *[master]
Version: 1.4.0
Commit hash: af520cf
Compiled on January 26, 2018
[~]$ micro *[master]
terminal entry not found
Micro does not recognize your terminal: dvtm-256color
Please go to https://github.com/zyedidia/mkinfo to read about how to fix this problem (it should be easy to fix).
[~]$ ./mkinfo_linux64 *[master]
./mkinfo_linux64: /usr/lib/libtinfo.so.5: no version information available (required by ./mkinfo_linux64)
UPD: micro-git(1.4.1-66) package works well, but depends on fat go
@Jipok you might need to install libtinfo
in order to use mkinfo
to generate the information for terminal
Suddenly getting this issue myself. Using 1.4.1 nightly (from AUR pkg).
$TERM is xterm-termite
micro -version
Version: 1.4.1
Commit hash: 1856891
Compiled on August 11, 2018
EDIT: Bandaid fix by alias micro as mentioned in https://github.com/zyedidia/micro/issues/20#issuecomment-243279582
I also see the same with micro 1.4.1 on openSUSE Tumbleweed x86_64. When launching micro with TERM=rxvt-265color, it works. With TERM=tmux-256color or TERM=kitty, I get:
terminal entry not found
Fatal: Micro could not initialize a screen.
It would help if micro would be permissive in what values of TERM it accepts. I think a list of known-good TERM values in the docs would be fine, and users with less-common TERM configurations can be advised to look there first when encountering display oddities
This problem is resolved for me by using the latest nightly build. Currently micro 1.4.2-dev 29
From reading some other issues as well I think that you have to use 1.4.2 or newer for some terminals like Termite, there was still some unsharpness in 1.4.1
(Archlinux / Termite)
1.4.1 still doesn't recognize st-256color
Guess I'll give compilation from source a shot. (I have an xterm-256color but I can't use it since OBS refuses to Window capture it...)
I had the same problem with kitty and micro 1.4.1-1. Upgrading to the git version (currently 1.4.2-61) fixed it.
Can confirm @Mark-Weston's first post - adding TERM=xterm-256color
to my .bashrc fixed the "terminal entry not found" issue for me on 1.4.0. The error only happened when running micro in screen.
I just tested the linux64 binary of the last release on Alpine Linux Vanilla, with st installed and
TERM=st-256color
. Micro complains with the error in the title. The workaround is settingTERM=xterm-256color
before launching micro.More details on #1077, where I thought it was an issue of outdated micro, but even with the newest release the error persists.