adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

patch 9.0.1080: the "kitty" terminfo entry is not widespread

Browse Source 
Problem:    The "kitty" terminfo entry is not widespread, resulting in the
            kitty terminal not working properly.
Solution:   Go back to using "xterm-kitty" and avoid the problems it causes in
            another way.
This commit is contained in:
Bram Moolenaar
2022-12-19 18:56:48 +00:00
parent 33e543038b
commit afa3f1cc72
4 changed files with 33 additions and 36 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
runtime/doc/term.txt
View File

@ -306,9 +306,14 @@ One of the problems is that the value for $TERM is set to "xterm-kitty". For
Vim this is an indication that the terminal is xterm-compatible and the
builtin xterm termcap entries should be used. Many other terminals depend on
this. However, Kitty is not fully xterm compatible. The author suggested to
ignore the "xterm-" prefix and use the terminfo entry anyway, but that
conflicts with what is needed for other terminals. Therefore Vim removes the
"xterm-" prefix from "xterm-kitty" when it comes from $TERM.
ignore the "xterm-" prefix and use the terminfo entry anyway, so that is what
happens now, the builtin xterm termcap entries are not used. However, the
t_RV is set, otherwise other things would not work, such as automatically
setting 'ttymouse' to "sgr".
It is not clear why kitty sets $TERM to "xterm-kitty", the terminal isn't
really xterm compatible. "kitty" would be more appropriate, but a terminfo
entry with that name is not widespread.
Note that using the kitty keyboard protocol is a separate feature, see
|kitty-keyboard-protocol|.