2018-06-03 13:37:40 +03:00
|
|
|
:tocdepth: 2
|
|
|
|
|
2018-05-29 18:33:50 +03:00
|
|
|
Configuring kitty
|
|
|
|
===============================
|
|
|
|
|
2018-06-05 10:07:04 +03:00
|
|
|
.. highlight:: conf
|
2018-06-03 13:37:40 +03:00
|
|
|
|
2018-05-29 18:33:50 +03:00
|
|
|
|kitty| is highly customizable, everything from keyboard shortcuts, to painting
|
2018-06-03 13:37:40 +03:00
|
|
|
frames-per-second. See below for an overview of all customization
|
|
|
|
possibilities.
|
2018-05-29 18:33:50 +03:00
|
|
|
|
2018-06-05 05:43:28 +03:00
|
|
|
You can open the config file within kitty by pressing :sc:`edit_config_file`.
|
2018-05-29 18:33:50 +03:00
|
|
|
You can also display the current configuration by running ``kitty
|
|
|
|
--debug-config``.
|
|
|
|
|
2018-06-03 13:37:40 +03:00
|
|
|
.. _confloc:
|
2018-05-29 18:33:50 +03:00
|
|
|
|
2018-06-03 13:37:40 +03:00
|
|
|
|kitty| looks for a config file in the OS config directories (usually
|
|
|
|
:file:`~/.config/kitty/kitty.conf`) but you can pass a specific path via the
|
|
|
|
:option:`kitty --config` option or use the ``KITTY_CONFIG_DIRECTORY``
|
|
|
|
environment variable. See the :option:`kitty --config` option for full details.
|
2018-05-29 18:33:50 +03:00
|
|
|
|
2018-06-03 13:37:40 +03:00
|
|
|
You can include secondary config files via the :code:`include` directive. If
|
|
|
|
you use a relative path for include, it is resolved with respect to the
|
|
|
|
location of the current config file. Note that environment variables are
|
|
|
|
expanded, so :code:`${USER}.conf` becomes :file:`name.conf` if
|
|
|
|
:code:`USER=name`. For example::
|
2018-05-29 18:33:50 +03:00
|
|
|
|
2018-06-03 13:37:40 +03:00
|
|
|
include other.conf
|
2018-05-29 18:33:50 +03:00
|
|
|
|
2018-05-31 06:10:32 +03:00
|
|
|
|
2018-06-03 13:37:40 +03:00
|
|
|
.. include:: /generated/conf-kitty.rst
|