Merge branch 'docs' of https://github.com/page-down/kitty
This commit is contained in:
commit
7de1a145aa
11
docs/faq.rst
11
docs/faq.rst
@ -58,8 +58,9 @@ servers)::
|
|||||||
|
|
||||||
infocmp -a xterm-kitty | ssh myserver tic -x -o \~/.terminfo /dev/stdin
|
infocmp -a xterm-kitty | ssh myserver tic -x -o \~/.terminfo /dev/stdin
|
||||||
|
|
||||||
If you are behind a proxy (like Balabit) that prevents this, you must redirect the
|
If you are behind a proxy (like Balabit) that prevents this, or ``tic`` comes
|
||||||
1st command to a file, copy that to the server and run ``tic`` manually. If you
|
with macOS that does not support reading from STDIN, you must redirect the 1st
|
||||||
|
command to a file, copy that to the server and run ``tic`` manually. If you
|
||||||
connect to a server, embedded or Android system that doesn't have ``tic``, copy over
|
connect to a server, embedded or Android system that doesn't have ``tic``, copy over
|
||||||
your local file terminfo to the other system as :file:`~/.terminfo/x/xterm-kitty`.
|
your local file terminfo to the other system as :file:`~/.terminfo/x/xterm-kitty`.
|
||||||
|
|
||||||
@ -87,6 +88,12 @@ Make sure the TERM environment variable, is ``xterm-kitty``. And either the
|
|||||||
TERMINFO environment variable points to a directory containing :file:`x/xterm-kitty`
|
TERMINFO environment variable points to a directory containing :file:`x/xterm-kitty`
|
||||||
or that file is under :file:`~/.terminfo/x/`.
|
or that file is under :file:`~/.terminfo/x/`.
|
||||||
|
|
||||||
|
For macOS, you may also need to put that file under :file:`~/.terminfo/78/`::
|
||||||
|
|
||||||
|
mkdir -p ~/.terminfo/{78,x}
|
||||||
|
ln -snf ../x/xterm-kitty ~/.terminfo/78/xterm-kitty
|
||||||
|
tic -x -o ~/.terminfo $KITTY_INSTALLATION_DIR/terminfo/kitty.terminfo
|
||||||
|
|
||||||
Note that ``sudo`` might remove TERMINFO. Then setting it at the shell prompt can
|
Note that ``sudo`` might remove TERMINFO. Then setting it at the shell prompt can
|
||||||
be too late, because command line editing may not be reinitialized. In that case
|
be too late, because command line editing may not be reinitialized. In that case
|
||||||
you can either ask ``sudo`` to set it or if that is not supported, insert an ``env``
|
you can either ask ``sudo`` to set it or if that is not supported, insert an ``env``
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user