.. highlight:: conf

.. default-domain:: conf


.. _conf-kitty-fonts:

Fonts
^^^^^^^^^^^^^^^^^^^^^^^^^

kitty has very powerful font management. You can configure individual
font faces and even specify special fonts for particular characters.

.. opt:: kitty.font_family, kitty.bold_font, kitty.italic_font, kitty.bold_italic_font
.. code-block:: conf

    font_family      monospace
    bold_font        auto
    italic_font      auto
    bold_italic_font auto

You can specify different fonts for the bold/italic/bold-italic variants.
To get a full list of supported fonts use the `kitty list-fonts` command.
By default they are derived automatically, by the OSes font system. Setting
them manually is useful for font families that have many weight variants like
Book, Medium, Thick, etc. For example::

    font_family      Operator Mono Book
    bold_font        Operator Mono Medium
    italic_font      Operator Mono Book Italic
    bold_italic_font Operator Mono Medium Italic

.. opt:: kitty.font_size
.. code-block:: conf

    font_size 11.0

Font size (in pts)

.. opt:: kitty.force_ltr
.. code-block:: conf

    force_ltr no

kitty does not support BIDI (bidirectional text), however, for RTL scripts,
words are automatically displayed in RTL. That is
to say, in an RTL script, the words "HELLO WORLD" display in kitty as "WORLD
HELLO", and if you try to select a substring of an RTL-shaped string, you will
get the character that would be there had the the string been LTR. For example,
assuming the Hebrew word ירושלים, selecting the character that on the screen
appears to be ם actually writes into the selection buffer the character י.

kitty's default behavior is useful in conjunction with a filter to reverse the
word order, however, if you wish to manipulate RTL glyphs, it can be very
challenging to work with, so this option is provided to turn it off.
Furthermore, this option can be used with the command line program
:link:`GNU FriBidi <https://github.com/fribidi/fribidi#executable>` to get BIDI
support, because it will force kitty to always treat the text as LTR, which
FriBidi expects for terminals.

.. opt:: kitty.adjust_line_height, kitty.adjust_column_width
.. code-block:: conf

    adjust_line_height  0
    adjust_column_width 0

Change the size of each character cell kitty renders. You can use either numbers,
which are interpreted as pixels or percentages (number followed by %), which
are interpreted as percentages of the unmodified values. You can use negative
pixels or percentages less than 100% to reduce sizes (but this might cause
rendering artifacts).

.. opt:: kitty.symbol_map
.. code-block:: conf

    symbol_map U+E0A0-U+E0A3,U+E0C0-U+E0C7 PowerlineSymbols

Map the specified unicode codepoints to a particular font. Useful if you need
special rendering for some symbols, such as for Powerline. Avoids the need for
patched fonts. Each unicode code point is specified in the form :code:`U+<code point
in hexadecimal>`. You can specify multiple code points, separated by commas and
ranges separated by hyphens. :code:`symbol_map` itself can be specified multiple times.
Syntax is::

    symbol_map codepoints Font Family Name

.. opt:: kitty.disable_ligatures
.. code-block:: conf

    disable_ligatures never

Choose how you want to handle multi-character ligatures. The default is to
always render them.  You can tell kitty to not render them when the cursor is
over them by using :code:`cursor` to make editing easier, or have kitty never
render them at all by using :code:`always`, if you don't like them. The ligature
strategy can be set per-window either using the kitty remote control facility
or by defining shortcuts for it in kitty.conf, for example::

    map alt+1 disable_ligatures_in active always
    map alt+2 disable_ligatures_in all never
    map alt+3 disable_ligatures_in tab cursor

Note that this refers to programming ligatures, typically implemented using the
:code:`calt` OpenType feature. For disabling general ligatures, use the
:opt:`font_features <kitty.font_features>` setting.

.. opt:: kitty.font_features
.. code-block:: conf

    font_features none

Choose exactly which OpenType features to enable or disable. This is useful as
some fonts might have features worthwhile in a terminal. For example, Fira
Code Retina includes a discretionary feature, :code:`zero`, which in that font
changes the appearance of the zero (0), to make it more easily distinguishable
from Ø. Fira Code Retina also includes other discretionary features known as
Stylistic Sets which have the tags :code:`ss01` through :code:`ss20`.

Note that this code is indexed by PostScript name, and not the font
family. This allows you to define very precise feature settings; e.g. you can
disable a feature in the italic font but not in the regular font.

On Linux, these are read from the FontConfig database first and then this,
setting is applied, so they can be configured in a single, central place.

To get the PostScript name for a font, use :code:`kitty + list-fonts --psnames`:

.. code-block:: sh

    $ kitty + list-fonts --psnames | grep Fira
    Fira Code
    Fira Code Bold (FiraCode-Bold)
    Fira Code Light (FiraCode-Light)
    Fira Code Medium (FiraCode-Medium)
    Fira Code Regular (FiraCode-Regular)
    Fira Code Retina (FiraCode-Retina)

The part in brackets is the PostScript name.

Enable alternate zero and oldstyle numerals::

    font_features FiraCode-Retina +zero +onum

Enable only alternate zero::

    font_features FiraCode-Retina +zero

Disable the normal ligatures, but keep the :code:`calt` feature which (in this
font) breaks up monotony::

    font_features TT2020StyleB-Regular -liga +calt

In conjunction with :opt:`force_ltr <kitty.force_ltr>`, you may want to disable Arabic shaping
entirely, and only look at their isolated forms if they show up in a document.
You can do this with e.g.::

    font_features UnifontMedium +isol -medi -fina -init

.. opt:: kitty.box_drawing_scale
.. code-block:: conf

    box_drawing_scale 0.001, 1, 1.5, 2

Change the sizes of the lines used for the box drawing unicode characters
These values are in pts. They will be scaled by the monitor DPI to arrive at
a pixel value. There must be four values corresponding to thin, normal, thick,
and very thick lines.


.. _conf-kitty-cursor:

Cursor customization
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.cursor
.. code-block:: conf

    cursor #cccccc

Default cursor color

.. opt:: kitty.cursor_text_color
.. code-block:: conf

    cursor_text_color #111111

Choose the color of text under the cursor. If you want it rendered with the
background color of the cell underneath instead, use the special keyword: background

.. opt:: kitty.cursor_shape
.. code-block:: conf

    cursor_shape block

The cursor shape can be one of (block, beam, underline)

.. opt:: kitty.cursor_beam_thickness
.. code-block:: conf

    cursor_beam_thickness 1.5

Defines the thickness of the beam cursor (in pts)

.. opt:: kitty.cursor_underline_thickness
.. code-block:: conf

    cursor_underline_thickness 2.0

Defines the thickness of the underline cursor (in pts)

.. opt:: kitty.cursor_blink_interval
.. code-block:: conf

    cursor_blink_interval -1

The interval (in seconds) at which to blink the cursor. Set to zero to disable
blinking. Negative values mean use system default. Note that numbers smaller
than :opt:`repaint_delay <kitty.repaint_delay>` will be limited to :opt:`repaint_delay <kitty.repaint_delay>`.

.. opt:: kitty.cursor_stop_blinking_after
.. code-block:: conf

    cursor_stop_blinking_after 15.0

Stop blinking cursor after the specified number of seconds of keyboard
inactivity.  Set to zero to never stop blinking.


.. _conf-kitty-scrollback:

Scrollback
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.scrollback_lines
.. code-block:: conf

    scrollback_lines 2000

Number of lines of history to keep in memory for scrolling back. Memory is allocated
on demand. Negative numbers are (effectively) infinite scrollback. Note that using
very large scrollback is not recommended as it can slow down performance of the terminal
and also use large amounts of RAM. Instead, consider using :opt:`scrollback_pager_history_size <kitty.scrollback_pager_history_size>`.

.. opt:: kitty.scrollback_pager
.. code-block:: conf

    scrollback_pager less --chop-long-lines --RAW-CONTROL-CHARS +INPUT_LINE_NUMBER

Program with which to view scrollback in a new window. The scrollback buffer is
passed as STDIN to this program. If you change it, make sure the program you
use can handle ANSI escape sequences for colors and text formatting.
INPUT_LINE_NUMBER in the command line above will be replaced by an integer
representing which line should be at the top of the screen. Similarly CURSOR_LINE and CURSOR_COLUMN
will be replaced by the current cursor position.

.. opt:: kitty.scrollback_pager_history_size
.. code-block:: conf

    scrollback_pager_history_size 0

Separate scrollback history size, used only for browsing the scrollback buffer (in MB).
This separate buffer is not available for interactive scrolling but will be
piped to the pager program when viewing scrollback buffer in a separate window.
The current implementation stores the data in UTF-8, so approximatively
10000 lines per megabyte at 100 chars per line, for pure ASCII text, unformatted text.
A value of zero or less disables this feature. The maximum allowed size is 4GB.

.. opt:: kitty.wheel_scroll_multiplier
.. code-block:: conf

    wheel_scroll_multiplier 5.0

Modify the amount scrolled by the mouse wheel. Note this is only used for low
precision scrolling devices, not for high precision scrolling on platforms such
as macOS and Wayland. Use negative numbers to change scroll direction.

.. opt:: kitty.touch_scroll_multiplier
.. code-block:: conf

    touch_scroll_multiplier 1.0

Modify the amount scrolled by a touchpad. Note this is only used for high
precision scrolling devices on platforms such as macOS and Wayland.
Use negative numbers to change scroll direction.


.. _conf-kitty-mouse:

Mouse
^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.mouse_hide_wait
.. code-block:: conf

    mouse_hide_wait 3.0

Hide mouse cursor after the specified number of seconds
of the mouse not being used. Set to zero to disable mouse cursor hiding.
Set to a negative value to hide the mouse cursor immediately when typing text.
Disabled by default on macOS as getting it to work robustly with
the ever-changing sea of bugs that is Cocoa is too much effort.

.. opt:: kitty.url_color, kitty.url_style
.. code-block:: conf

    url_color #0087bd
    url_style curly

The color and style for highlighting URLs on mouse-over.
:code:`url_style` can be one of: none, single, double, curly

.. opt:: kitty.open_url_modifiers
.. code-block:: conf

    open_url_modifiers kitty_mod

The modifier keys to press when clicking with the
mouse on URLs to open the URL

.. opt:: kitty.open_url_with
.. code-block:: conf

    open_url_with default

The program with which to open URLs that are clicked on.
The special value :code:`default` means to use the
operating system's default URL handler.

.. opt:: kitty.url_prefixes
.. code-block:: conf

    url_prefixes http https file ftp

The set of URL prefixes to look for when detecting a URL under the mouse cursor.

.. opt:: kitty.detect_urls
.. code-block:: conf

    detect_urls yes

Detect URLs under the mouse. Detected URLs are highlighted
with an underline and the mouse cursor becomes a hand over them.
Even if this option is disabled, URLs are still clickable.

.. opt:: kitty.copy_on_select
.. code-block:: conf

    copy_on_select no

Copy to clipboard or a private buffer on select. With this set to
:code:`clipboard`, simply selecting text with the mouse will cause the text to
be copied to clipboard. Useful on platforms such as macOS that do not have the
concept of primary selections. You can instead specify a name such as :code:`a1` to
copy to a private kitty buffer instead. Map a shortcut with the
:code:`paste_from_buffer` action to paste from this private buffer.
For example::

    map cmd+shift+v paste_from_buffer a1

Note that copying to the clipboard is a security risk, as all programs,
including websites open in your browser can read the contents of the
system clipboard.

.. opt:: kitty.strip_trailing_spaces
.. code-block:: conf

    strip_trailing_spaces never

Remove spaces at the end of lines when copying to clipboard.
A value of :code:`smart` will do it when using normal selections, but not rectangle
selections. :code:`always` will always do it.

.. opt:: kitty.rectangle_select_modifiers
.. code-block:: conf

    rectangle_select_modifiers ctrl+alt

The modifiers to use rectangular selection (i.e. to select text in a
rectangular block with the mouse)

.. opt:: kitty.terminal_select_modifiers
.. code-block:: conf

    terminal_select_modifiers shift

The modifiers to override mouse selection even when a terminal application has grabbed the mouse

.. opt:: kitty.select_by_word_characters
.. code-block:: conf

    select_by_word_characters @-./_~?&=%+#

Characters considered part of a word when double clicking. In addition to these characters
any character that is marked as an alphanumeric character in the unicode
database will be matched.

.. opt:: kitty.click_interval
.. code-block:: conf

    click_interval -1.0

The interval between successive clicks to detect double/triple clicks (in seconds).
Negative numbers will use the system default instead, if available, or fallback to 0.5.

.. opt:: kitty.focus_follows_mouse
.. code-block:: conf

    focus_follows_mouse no

Set the active window to the window under the mouse when
moving the mouse around

.. opt:: kitty.pointer_shape_when_grabbed
.. code-block:: conf

    pointer_shape_when_grabbed arrow

The shape of the mouse pointer when the program running in the terminal grabs the mouse.
Valid values are: :code:`arrow`, :code:`beam` and :code:`hand`

.. opt:: kitty.default_pointer_shape
.. code-block:: conf

    default_pointer_shape beam

The default shape of the mouse pointer.
Valid values are: :code:`arrow`, :code:`beam` and :code:`hand`

.. opt:: kitty.pointer_shape_when_dragging
.. code-block:: conf

    pointer_shape_when_dragging beam

The default shape of the mouse pointer when dragging across text.
Valid values are: :code:`arrow`, :code:`beam` and :code:`hand`


.. _conf-kitty-performance:

Performance tuning
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.repaint_delay
.. code-block:: conf

    repaint_delay 10

Delay (in milliseconds) between screen updates. Decreasing it, increases
frames-per-second (FPS) at the cost of more CPU usage. The default value
yields ~100 FPS which is more than sufficient for most uses. Note that to
actually achieve 100 FPS you have to either set :opt:`sync_to_monitor <kitty.sync_to_monitor>` to no
or use a monitor with a high refresh rate. Also, to minimize latency
when there is pending input to be processed, repaint_delay is ignored.

.. opt:: kitty.input_delay
.. code-block:: conf

    input_delay 3

Delay (in milliseconds) before input from the program running in the terminal
is processed. Note that decreasing it will increase responsiveness, but also
increase CPU usage and might cause flicker in full screen programs that
redraw the entire screen on each loop, because kitty is so fast that partial
screen updates will be drawn.

.. opt:: kitty.sync_to_monitor
.. code-block:: conf

    sync_to_monitor yes

Sync screen updates to the refresh rate of the monitor. This prevents
tearing (https://en.wikipedia.org/wiki/Screen_tearing) when scrolling. However,
it limits the rendering speed to the refresh rate of your monitor. With a
very high speed mouse/high keyboard repeat rate, you may notice some slight input latency.
If so, set this to no.


.. _conf-kitty-bell:

Terminal bell
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.enable_audio_bell
.. code-block:: conf

    enable_audio_bell yes

Enable/disable the audio bell. Useful in environments that require silence.

.. opt:: kitty.visual_bell_duration
.. code-block:: conf

    visual_bell_duration 0.0

Visual bell duration. Flash the screen when a bell occurs for the specified number of
seconds. Set to zero to disable.

.. opt:: kitty.window_alert_on_bell
.. code-block:: conf

    window_alert_on_bell yes

Request window attention on bell.
Makes the dock icon bounce on macOS or the taskbar flash on linux.

.. opt:: kitty.bell_on_tab
.. code-block:: conf

    bell_on_tab yes

Show a bell symbol on the tab if a bell occurs in one of the windows in the
tab and the window is not the currently focused window

.. opt:: kitty.command_on_bell
.. code-block:: conf

    command_on_bell none

Program to run when a bell occurs.


.. _conf-kitty-window:

Window layout
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.remember_window_size, kitty.initial_window_width, kitty.initial_window_height
.. code-block:: conf

    remember_window_size  yes
    initial_window_width  640
    initial_window_height 400

If enabled, the window size will be remembered so that new instances of kitty
will have the same size as the previous instance. If disabled, the window will
initially have size configured by initial_window_width/height, in pixels. You
can use a suffix of "c" on the width/height values to have them interpreted as
number of cells instead of pixels.

.. opt:: kitty.enabled_layouts
.. code-block:: conf

    enabled_layouts *

The enabled window layouts. A comma separated list of layout names. The special
value :code:`all` means all layouts. The first listed layout will be used as the
startup layout. Default configuration is all layouts in alphabetical order.
For a list of available layouts, see the :ref:`layouts`.

.. opt:: kitty.window_resize_step_cells, kitty.window_resize_step_lines
.. code-block:: conf

    window_resize_step_cells 2
    window_resize_step_lines 2

The step size (in units of cell width/cell height) to use when resizing
windows. The cells value is used for horizontal resizing and the lines value
for vertical resizing.

.. opt:: kitty.window_border_width
.. code-block:: conf

    window_border_width 0.5pt

The width of window borders. Can be either in pixels (px) or pts (pt). Values
in pts will be rounded to the nearest number of pixels based on screen
resolution. If not specified the unit is assumed to be pts.
Note that borders are displayed only when more than one window
is visible. They are meant to separate multiple windows.

.. opt:: kitty.draw_minimal_borders
.. code-block:: conf

    draw_minimal_borders yes

Draw only the minimum borders needed. This means that only the minimum
needed borders for inactive windows are drawn. That is only the borders
that separate the inactive window from a neighbor. Note that setting
a non-zero window margin overrides this and causes all borders to be drawn.

.. opt:: kitty.window_margin_width
.. code-block:: conf

    window_margin_width 0

The window margin (in pts) (blank area outside the border). A single value sets all four sides. Two values set the vertical and horizontal sides. Three values set top, horizontal and bottom. Four values set top, right, bottom and left.

.. opt:: kitty.single_window_margin_width
.. code-block:: conf

    single_window_margin_width -1

The window margin (in pts) to use when only a single window is visible.
Negative values will cause the value of :opt:`window_margin_width <kitty.window_margin_width>` to be used instead. A single value sets all four sides. Two values set the vertical and horizontal sides. Three values set top, horizontal and bottom. Four values set top, right, bottom and left.

.. opt:: kitty.window_padding_width
.. code-block:: conf

    window_padding_width 0

The window padding (in pts) (blank area between the text and the window border). A single value sets all four sides. Two values set the vertical and horizontal sides. Three values set top, horizontal and bottom. Four values set top, right, bottom and left.

.. opt:: kitty.placement_strategy
.. code-block:: conf

    placement_strategy center

When the window size is not an exact multiple of the cell size, the cell area of the terminal
window will have some extra padding on the sides. You can control how that padding is
distributed with this option. Using a value of :code:`center` means the cell area will
be placed centrally. A value of :code:`top-left` means the padding will be on only
the bottom and right edges.

.. opt:: kitty.active_border_color
.. code-block:: conf

    active_border_color #00ff00

The color for the border of the active window. Set this to none to not draw borders
around the active window.

.. opt:: kitty.inactive_border_color
.. code-block:: conf

    inactive_border_color #cccccc

The color for the border of inactive windows

.. opt:: kitty.bell_border_color
.. code-block:: conf

    bell_border_color #ff5a00

The color for the border of inactive windows in which a bell has occurred

.. opt:: kitty.inactive_text_alpha
.. code-block:: conf

    inactive_text_alpha 1.0

Fade the text in inactive windows by the specified amount (a number between
zero and one, with zero being fully faded).

.. opt:: kitty.hide_window_decorations
.. code-block:: conf

    hide_window_decorations no

Hide the window decorations (title-bar and window borders) with :code:`yes`.
On macOS, :code:`titlebar-only` can be used to only hide the titlebar.
Whether this works and exactly what effect it has depends on the
window manager/operating system.

.. opt:: kitty.resize_debounce_time
.. code-block:: conf

    resize_debounce_time 0.1

The time (in seconds) to wait before redrawing the screen when a
resize event is received. On platforms such as macOS, where the
operating system sends events corresponding to the start and end
of a resize, this number is ignored.

.. opt:: kitty.resize_draw_strategy
.. code-block:: conf

    resize_draw_strategy static

Choose how kitty draws a window while a resize is in progress.
A value of :code:`static` means draw the current window contents, mostly unchanged.
A value of :code:`scale` means draw the current window contents scaled.
A value of :code:`blank` means draw a blank window.
A value of :code:`size` means show the window size in cells.

.. opt:: kitty.resize_in_steps
.. code-block:: conf

    resize_in_steps no

Resize the OS window in steps as large as the cells, instead of with the usual pixel accuracy.
Combined with an :opt:`initial_window_width <kitty.initial_window_width>` and :opt:`initial_window_height <kitty.initial_window_height>` in number of cells,
this option can be used to keep the margins as small as possible when resizing the OS window.
Note that this does not currently work on Wayland.

.. opt:: kitty.confirm_os_window_close
.. code-block:: conf

    confirm_os_window_close 0

Ask for confirmation when closing an OS window or a tab that has at least this
number of kitty windows in it. A value of zero disables confirmation.
This confirmation also applies to requests to quit the entire application (all
OS windows, via the quit action).


.. _conf-kitty-tabbar:

Tab bar
^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.tab_bar_edge
.. code-block:: conf

    tab_bar_edge bottom

Which edge to show the tab bar on, top or bottom

.. opt:: kitty.tab_bar_margin_width
.. code-block:: conf

    tab_bar_margin_width 0.0

The margin to the left and right of the tab bar (in pts)

.. opt:: kitty.tab_bar_style
.. code-block:: conf

    tab_bar_style fade

The tab bar style, can be one of: :code:`fade`, :code:`separator`, :code:`powerline`, or :code:`hidden`.
In the fade style, each tab's edges fade into the background color, in the separator style, tabs are
separated by a configurable separator, and the powerline shows the tabs as a continuous line.
If you use the hidden style, you might want to create a mapping for the :code:`select_tab` action which
presents you with a list of tabs and allows for easy switching to a tab.

.. opt:: kitty.tab_bar_min_tabs
.. code-block:: conf

    tab_bar_min_tabs 2

The minimum number of tabs that must exist before the tab bar is shown

.. opt:: kitty.tab_switch_strategy
.. code-block:: conf

    tab_switch_strategy previous

The algorithm to use when switching to a tab when the current tab is closed.
The default of :code:`previous` will switch to the last used tab. A value of
:code:`left` will switch to the tab to the left of the closed tab. A value
of :code:`right` will switch to the tab to the right of the closed tab.
A value of :code:`last` will switch to the right-most tab.

.. opt:: kitty.tab_fade
.. code-block:: conf

    tab_fade 0.25 0.5 0.75 1

Control how each tab fades into the background when using :code:`fade` for the
:opt:`tab_bar_style <kitty.tab_bar_style>`. Each number is an alpha (between zero and one) that controls
how much the corresponding cell fades into the background, with zero being no fade
and one being full fade. You can change the number of cells used by adding/removing
entries to this list.

.. opt:: kitty.tab_separator
.. code-block:: conf

    tab_separator " ┇"

The separator between tabs in the tab bar when using :code:`separator` as the :opt:`tab_bar_style <kitty.tab_bar_style>`.

.. opt:: kitty.tab_activity_symbol
.. code-block:: conf

    tab_activity_symbol none

Some text or a unicode symbol to show on the tab if a window in the tab that does
not have focus has some activity.

.. opt:: kitty.tab_title_template
.. code-block:: conf

    tab_title_template "{title}"

A template to render the tab title. The default just renders
the title. If you wish to include the tab-index as well,
use something like: :code:`{index}: {title}`. Useful
if you have shortcuts mapped for :code:`goto_tab N`.
In addition you can use :code:`{layout_name}` for the current
layout name and :code:`{num_windows}` for the number of windows
in the tab. Note that formatting is done by Python's string formatting
machinery, so you can use, for instance, :code:`{layout_name[:2].upper()}` to
show only the first two letters of the layout name, upper-cased.
If you want to style the text, you can use styling directives, for example:
:code:`{fmt.fg.red}red{fmt.fg.default}normal{fmt.bg._00FF00}green bg{fmt.bg.normal}`.
Similarly, for bold and italic:
:code:`{fmt.bold}bold{fmt.nobold}normal{fmt.italic}italic{fmt.noitalic}`.

.. opt:: kitty.active_tab_title_template
.. code-block:: conf

    active_tab_title_template none

Template to use for active tabs, if not specified falls back
to :opt:`tab_title_template <kitty.tab_title_template>`.

.. opt:: kitty.active_tab_foreground, kitty.active_tab_background, kitty.active_tab_font_style, kitty.inactive_tab_foreground, kitty.inactive_tab_background, kitty.inactive_tab_font_style
.. code-block:: conf

    active_tab_foreground   #000
    active_tab_background   #eee
    active_tab_font_style   bold-italic
    inactive_tab_foreground #444
    inactive_tab_background #999
    inactive_tab_font_style normal

Tab bar colors and styles

.. opt:: kitty.tab_bar_background
.. code-block:: conf

    tab_bar_background none

Background color for the tab bar. Defaults to using the terminal background color.


.. _conf-kitty-colors:

Color scheme
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.foreground, kitty.background
.. code-block:: conf

    foreground #dddddd
    background #000000

The foreground and background colors

.. opt:: kitty.background_opacity
.. code-block:: conf

    background_opacity 1.0

The opacity of the background. A number between 0 and 1, where 1 is opaque and
0 is fully transparent.  This will only work if supported by the OS (for
instance, when using a compositor under X11). Note that it only sets the
background color's opacity in cells that have the same background color as
the default terminal background. This is so that things like the status bar
in vim, powerline prompts, etc. still look good.  But it means that if you use
a color theme with a background color in your editor, it will not be rendered
as transparent.  Instead you should change the default background color in your
kitty config and not use a background color in the editor color scheme. Or use
the escape codes to set the terminals default colors in a shell script to
launch your editor.  Be aware that using a value less than 1.0 is a (possibly
significant) performance hit.  If you want to dynamically change transparency
of windows set :opt:`dynamic_background_opacity <kitty.dynamic_background_opacity>` to :code:`yes` (this is off by
default as it has a performance cost)

.. opt:: kitty.background_image
.. code-block:: conf

    background_image none

Path to a background image. Must be in PNG format.

.. opt:: kitty.background_image_layout
.. code-block:: conf

    background_image_layout tiled

Whether to tile or scale the background image.

.. opt:: kitty.background_image_linear
.. code-block:: conf

    background_image_linear no

When background image is scaled, whether linear interpolation should be used.

.. opt:: kitty.dynamic_background_opacity
.. code-block:: conf

    dynamic_background_opacity no

Allow changing of the :opt:`background_opacity <kitty.background_opacity>` dynamically, using either keyboard
shortcuts (:sc:`increase_background_opacity` and :sc:`decrease_background_opacity`)
or the remote control facility.

.. opt:: kitty.background_tint
.. code-block:: conf

    background_tint 0.0

How much to tint the background image by the background color. The tint is applied
only under the text area, not margin/borders. Makes it easier to read the text.
Tinting is done using the current background color for each window. This setting
applies only if :opt:`background_opacity <kitty.background_opacity>` is set and transparent windows are supported
or :opt:`background_image <kitty.background_image>` is set.

.. opt:: kitty.dim_opacity
.. code-block:: conf

    dim_opacity 0.75

How much to dim text that has the DIM/FAINT attribute set. One means no dimming and
zero means fully dimmed (i.e. invisible).

.. opt:: kitty.selection_foreground
.. code-block:: conf

    selection_foreground #000000

The foreground for text selected with the mouse. A value of none means to leave the color unchanged.

.. opt:: kitty.selection_background
.. code-block:: conf

    selection_background #fffacd

The background for text selected with the mouse.


.. _conf-kitty-colors.table:

The color table
+++++++++++++++++++++++++++++++++++

The 16 terminal colors. There are 8 basic colors, each color has a dull and
bright version. You can also set the remaining colors from the 256 color table
as color16 to color255.

.. opt:: kitty.color0, kitty.color8
.. code-block:: conf

    color0 #000000
    color8 #767676

black

.. opt:: kitty.color1, kitty.color9
.. code-block:: conf

    color1 #cc0403
    color9 #f2201f

red

.. opt:: kitty.color2, kitty.color10
.. code-block:: conf

    color2  #19cb00
    color10 #23fd00

green

.. opt:: kitty.color3, kitty.color11
.. code-block:: conf

    color3  #cecb00
    color11 #fffd00

yellow

.. opt:: kitty.color4, kitty.color12
.. code-block:: conf

    color4  #0d73cc
    color12 #1a8fff

blue

.. opt:: kitty.color5, kitty.color13
.. code-block:: conf

    color5  #cb1ed1
    color13 #fd28ff

magenta

.. opt:: kitty.color6, kitty.color14
.. code-block:: conf

    color6  #0dcdcd
    color14 #14ffff

cyan

.. opt:: kitty.color7, kitty.color15
.. code-block:: conf

    color7  #dddddd
    color15 #ffffff

white

.. opt:: kitty.mark1_foreground
.. code-block:: conf

    mark1_foreground black

Color for marks of type 1

.. opt:: kitty.mark1_background
.. code-block:: conf

    mark1_background #98d3cb

Color for marks of type 1 (light steel blue)

.. opt:: kitty.mark2_foreground
.. code-block:: conf

    mark2_foreground black

Color for marks of type 2

.. opt:: kitty.mark2_background
.. code-block:: conf

    mark2_background #f2dcd3

Color for marks of type 1 (beige)

.. opt:: kitty.mark3_foreground
.. code-block:: conf

    mark3_foreground black

Color for marks of type 3

.. opt:: kitty.mark3_background
.. code-block:: conf

    mark3_background #f274bc

Color for marks of type 1 (violet)


.. _conf-kitty-advanced:

Advanced
^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.shell
.. code-block:: conf

    shell .

The shell program to execute. The default value of . means
to use whatever shell is set as the default shell for the current user.
Note that on macOS if you change this, you might need to add :code:`--login` to
ensure that the shell starts in interactive mode and reads its startup rc files.

.. opt:: kitty.editor
.. code-block:: conf

    editor .

The console editor to use when editing the kitty config file or similar tasks.
A value of . means to use the environment variables VISUAL and EDITOR in that
order. Note that this environment variable has to be set not just in your shell
startup scripts but system-wide, otherwise kitty will not see it.

.. opt:: kitty.close_on_child_death
.. code-block:: conf

    close_on_child_death no

Close the window when the child process (shell) exits. If no (the default), the
terminal will remain open when the child exits as long as there are still
processes outputting to the terminal (for example disowned or backgrounded
processes). If yes, the window will close as soon as the child process exits.
Note that setting it to yes means that any background processes still using the
terminal can fail silently because their stdout/stderr/stdin no longer work.

.. opt:: kitty.allow_remote_control
.. code-block:: conf

    allow_remote_control no

Allow other programs to control kitty. If you turn this on other programs can
control all aspects of kitty, including sending text to kitty windows, opening
new windows, closing windows, reading the content of windows, etc.  Note that
this even works over ssh connections. You can chose to either allow any program
running within kitty to control it, with :code:`yes` or only programs that
connect to the socket specified with the :option:`kitty --listen-on` command
line option, if you use the value :code:`socket-only`. The latter is useful if
you want to prevent programs running on a remote computer over ssh from
controlling kitty.

.. opt:: kitty.listen_on
.. code-block:: conf

    listen_on none

Tell kitty to listen to the specified unix/tcp socket for remote control
connections. Note that this will apply to all kitty instances. It can be
overridden by the :option:`kitty --listen-on` command line flag. This
option accepts only UNIX sockets, such as unix:${TEMP}/mykitty or (on Linux)
unix:@mykitty. Environment variables are expanded. If {kitty_pid} is present
then it is replaced by the PID of the kitty process, otherwise the PID of the kitty
process is appended to the value, with a hyphen. This option is ignored unless
you also set :opt:`allow_remote_control <kitty.allow_remote_control>` to enable remote control. See the
help for :option:`kitty --listen-on` for more details.

.. opt:: kitty.env
.. code-block:: conf

    env 

Specify environment variables to set in all child processes. Note that
environment variables are expanded recursively, so if you use::

    env MYVAR1=a
    env MYVAR2=${MYVAR1}/${HOME}/b

The value of MYVAR2 will be :code:`a/<path to home directory>/b`.

.. opt:: kitty.update_check_interval
.. code-block:: conf

    update_check_interval 24

Periodically check if an update to kitty is available. If an update is found
a system notification is displayed informing you of the available update.
The default is to check every 24 hrs, set to zero to disable.

.. opt:: kitty.startup_session
.. code-block:: conf

    startup_session none

Path to a session file to use for all kitty instances. Can be overridden
by using the :option:`kitty --session` command line option for individual
instances. See :ref:`sessions` in the kitty documentation for details. Note
that relative paths are interpreted with respect to the kitty config directory.
Environment variables in the path are expanded.

.. opt:: kitty.clipboard_control
.. code-block:: conf

    clipboard_control write-clipboard write-primary

Allow programs running in kitty to read and write from the clipboard. You can
control exactly which actions are allowed. The set of possible actions is:
write-clipboard read-clipboard write-primary read-primary. You can
additionally specify no-append to disable kitty's protocol extension
for clipboard concatenation. The default is to allow writing to the
clipboard and primary selection with concatenation enabled. Note
that enabling the read functionality is a security risk as it means that any
program, even one running on a remote server via SSH can read your clipboard.

.. opt:: kitty.allow_hyperlinks
.. code-block:: conf

    allow_hyperlinks yes

Process hyperlink (OSC 8) escape sequences. If disabled OSC 8 escape
sequences are ignored. Otherwise they become clickable links, that you
can click by holding down ctrl+shift and clicking with the mouse. The special
value of ``ask`` means that kitty will ask before opening the link.

.. opt:: kitty.term
.. code-block:: conf

    term xterm-kitty

The value of the TERM environment variable to set. Changing this can break many
terminal programs, only change it if you know what you are doing, not because
you read some advice on Stack Overflow to change it. The TERM variable is used
by various programs to get information about the capabilities and behavior of
the terminal. If you change it, depending on what programs you run, and how
different the terminal you are changing it to is, various things from
key-presses, to colors, to various advanced features may not work.


.. _conf-kitty-os:

OS specific tweaks
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

.. opt:: kitty.macos_titlebar_color
.. code-block:: conf

    macos_titlebar_color system

Change the color of the kitty window's titlebar on macOS. A value of :code:`system`
means to use the default system color, a value of :code:`background` means to use
the background color of the currently active window and finally you can use
an arbitrary color, such as :code:`#12af59` or :code:`red`. WARNING: This option works by
using a hack, as there is no proper Cocoa API for it. It sets the background
color of the entire window and makes the titlebar transparent. As such it is
incompatible with :opt:`background_opacity <kitty.background_opacity>`. If you want to use both, you are
probably better off just hiding the titlebar with :opt:`hide_window_decorations <kitty.hide_window_decorations>`.

.. opt:: kitty.macos_option_as_alt
.. code-block:: conf

    macos_option_as_alt no

Use the option key as an alt key. With this set to :code:`no`, kitty will use
the macOS native :kbd:`Option+Key` = unicode character behavior. This will
break any :kbd:`Alt+key` keyboard shortcuts in your terminal programs, but you
can use the macOS unicode input technique. You can use the values:
:code:`left`, :code:`right`, or :code:`both` to use only the left, right or
both Option keys as Alt, instead.

.. opt:: kitty.macos_hide_from_tasks
.. code-block:: conf

    macos_hide_from_tasks no

Hide the kitty window from running tasks (:kbd:`Option+Tab`) on macOS.

.. opt:: kitty.macos_quit_when_last_window_closed
.. code-block:: conf

    macos_quit_when_last_window_closed no

Have kitty quit when all the top-level windows are closed. By default,
kitty will stay running, even with no open windows, as is the expected
behavior on macOS.

.. opt:: kitty.macos_window_resizable
.. code-block:: conf

    macos_window_resizable yes

Disable this if you want kitty top-level (OS) windows to not be resizable
on macOS.

.. opt:: kitty.macos_thicken_font
.. code-block:: conf

    macos_thicken_font 0

Draw an extra border around the font with the given width, to increase
legibility at small font sizes. For example, a value of 0.75 will
result in rendering that looks similar to sub-pixel antialiasing at
common font sizes.

.. opt:: kitty.macos_traditional_fullscreen
.. code-block:: conf

    macos_traditional_fullscreen no

Use the traditional full-screen transition, that is faster, but less pretty.

.. opt:: kitty.macos_show_window_title_in
.. code-block:: conf

    macos_show_window_title_in all

Show or hide the window title in the macOS window or menu-bar.
A value of :code:`window` will show the title of the currently
active window at the top of the macOS window. A value of
:code:`menubar` will show the title of the currently active window
in the macOS menu-bar, making use of otherwise wasted space.
:code:`all` will show the title everywhere and :code:`none`
hides the title in the window and the menu-bar.

.. opt:: kitty.macos_custom_beam_cursor
.. code-block:: conf

    macos_custom_beam_cursor no

Enable/disable custom mouse cursor for macOS that is easier to see on both
light and dark backgrounds. WARNING: this might make your mouse cursor
invisible on dual GPU machines.

.. opt:: kitty.linux_display_server
.. code-block:: conf

    linux_display_server auto

Choose between Wayland and X11 backends. By default, an
appropriate backend based on the system state is chosen
automatically. Set it to :code:`x11` or :code:`wayland`
to force the choice.


.. _conf-kitty-shortcuts:

Keyboard shortcuts
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

For a list of key names, see: :link:`the GLFW key macros
<https://github.com/kovidgoyal/kitty/blob/master/glfw/glfw3.h#L349>`.
The name to use is the part after the :code:`GLFW_KEY_` prefix.
For a list of modifier names, see:
:link:`GLFW mods <https://www.glfw.org/docs/latest/group__mods.html>`

On Linux you can also use XKB key names to bind keys that are not supported by
GLFW. See :link:`XKB keys
<https://github.com/xkbcommon/libxkbcommon/blob/master/xkbcommon/xkbcommon-keysyms.h>`
for a list of key names. The name to use is the part after the :code:`XKB_KEY_`
prefix. Note that you can only use an XKB key name for keys that are not known
as GLFW keys.

Finally, you can use raw system key codes to map keys, again only for keys that are not
known as GLFW keys. To see the system key code
for a key, start kitty with the :option:`kitty --debug-keyboard` option. Then kitty will
output some debug text for every key event. In that text look for ``native_code``
the value of that becomes the key name in the shortcut. For example:

.. code-block:: none

    on_key_input: glfw key: 65 native_code: 0x61 action: PRESS mods: 0x0 text: 'a'

Here, the key name for the :kbd:`A` key is :kbd:`0x61` and you can use it with::

    map ctrl+0x61 something

to map :kbd:`ctrl+a` to something.

You can use the special action :code:`no_op` to unmap a keyboard shortcut that is
assigned in the default configuration::

    map kitty_mod+space no_op

You can combine multiple actions to be triggered by a single shortcut, using the
syntax below::

    map key combine <separator> action1 <separator> action2 <separator> action3 ...

For example::

    map kitty_mod+e combine : new_window : next_layout

this will create a new window and switch to the next available layout

You can use multi-key shortcuts using the syntax shown below::

    map key1>key2>key3 action

For example::

    map ctrl+f>2 set_font_size 20

.. opt:: kitty.kitty_mod
.. code-block:: conf

    kitty_mod ctrl+shift

The value of :code:`kitty_mod` is used as the modifier for all default shortcuts, you
can change it in your kitty.conf to change the modifiers for all the default
shortcuts.

.. opt:: kitty.clear_all_shortcuts
.. code-block:: conf

    clear_all_shortcuts no

You can have kitty remove all shortcut definition seen up to this point. Useful, for
instance, to remove the default shortcuts.

.. opt:: kitty.kitten_alias
.. code-block:: conf

    kitten_alias hints hints --hints-offset=0

You can create aliases for kitten names, this allows overriding the defaults
for kitten options and can also be used to shorten repeated mappings of the same
kitten with a specific group of options. For example, the above alias
changes the default value of :option:`kitty +kitten hints --hints-offset`
to zero for all mappings, including the builtin ones.


.. _conf-kitty-shortcuts.clipboard:

Clipboard
+++++++++++++++++++++++++++++

.. shortcut:: kitty.Copy to clipboard
.. code-block:: conf

    map ctrl+shift+c copy_to_clipboard


There is also a :code:`copy_or_interrupt` action that can be optionally mapped to :kbd:`Ctrl+c`.
It will copy only if there is a selection and send an interrupt otherwise. Similarly, :code:`copy_and_clear_or_interrupt`
will copy and clear the selection or send an interrupt if there is no selection.

.. shortcut:: kitty.Paste from clipboard
.. code-block:: conf

    map ctrl+shift+v paste_from_clipboard

.. shortcut:: kitty.Paste from selection
.. code-block:: conf

    map ctrl+shift+s paste_from_selection
    map shift+insert paste_from_selection

.. shortcut:: kitty.Pass selection to program
.. code-block:: conf

    map ctrl+shift+o pass_selection_to_program


You can also pass the contents of the current selection to any program using
:code:`pass_selection_to_program`. By default, the system's open program is used, but
you can specify your own, the selection will be passed as a command line argument to the program,
for example::

    map kitty_mod+o pass_selection_to_program firefox

You can pass the current selection to a terminal program running in a new kitty
window, by using the @selection placeholder::

    map kitty_mod+y new_window less @selection



.. _conf-kitty-shortcuts.scrolling:

Scrolling
+++++++++++++++++++++++++++++

.. shortcut:: kitty.Scroll line up
.. code-block:: conf

    map ctrl+shift+up scroll_line_up
    map ctrl+shift+k scroll_line_up

.. shortcut:: kitty.Scroll line down
.. code-block:: conf

    map ctrl+shift+down scroll_line_down
    map ctrl+shift+j scroll_line_down

.. shortcut:: kitty.Scroll page up
.. code-block:: conf

    map ctrl+shift+page_up scroll_page_up

.. shortcut:: kitty.Scroll page down
.. code-block:: conf

    map ctrl+shift+page_down scroll_page_down

.. shortcut:: kitty.Scroll to top
.. code-block:: conf

    map ctrl+shift+home scroll_home

.. shortcut:: kitty.Scroll to bottom
.. code-block:: conf

    map ctrl+shift+end scroll_end

.. shortcut:: kitty.Browse scrollback buffer in less
.. code-block:: conf

    map ctrl+shift+h show_scrollback



You can pipe the contents of the current screen + history buffer as
:file:`STDIN` to an arbitrary program using the ``launch`` function. For example,
the following opens the scrollback buffer in less in an overlay window::

    map f1 launch --stdin-source=@screen_scrollback --stdin-add-formatting --type=overlay less +G -R

For more details on piping screen and buffer contents to external programs,
see :doc:`launch`.



.. _conf-kitty-shortcuts.window:

Window management
+++++++++++++++++++++++++++++++++++++

.. shortcut:: kitty.
.. code-block:: conf

    map ctrl+shift+enter new_window


You can open a new window running an arbitrary program, for example::

    map kitty_mod+y      launch mutt

You can open a new window with the current working directory set to the
working directory of the current window using::

    map ctrl+alt+enter    launch --cwd=current

You can open a new window that is allowed to control kitty via
the kitty remote control facility by prefixing the command line with @.
Any programs running in that window will be allowed to control kitty.
For example::

    map ctrl+enter launch --allow-remote-control some_program

You can open a new window next to the currently active window or as the first window,
with::

    map ctrl+n launch --location=neighbor some_program
    map ctrl+f launch --location=first some_program

For more details, see :doc:`launch`.


.. shortcut:: kitty.New OS window
.. code-block:: conf

    map ctrl+shift+n new_os_window

Works like new_window above, except that it opens a top level OS kitty window. In particular you can use new_os_window_with_cwd to open a window with the current working directory.

.. shortcut:: kitty.Close window
.. code-block:: conf

    map ctrl+shift+w close_window

.. shortcut:: kitty.Next window
.. code-block:: conf

    map ctrl+shift+] next_window

.. shortcut:: kitty.Previous window
.. code-block:: conf

    map ctrl+shift+[ previous_window

.. shortcut:: kitty.Move window forward
.. code-block:: conf

    map ctrl+shift+f move_window_forward

.. shortcut:: kitty.Move window backward
.. code-block:: conf

    map ctrl+shift+b move_window_backward

.. shortcut:: kitty.Move window to top
.. code-block:: conf

    map ctrl+shift+` move_window_to_top

.. shortcut:: kitty.Start resizing window
.. code-block:: conf

    map ctrl+shift+r start_resizing_window

.. shortcut:: kitty.First window
.. code-block:: conf

    map ctrl+shift+1 first_window

.. shortcut:: kitty.Second window
.. code-block:: conf

    map ctrl+shift+2 second_window

.. shortcut:: kitty.Third window
.. code-block:: conf

    map ctrl+shift+3 third_window

.. shortcut:: kitty.Fourth window
.. code-block:: conf

    map ctrl+shift+4 fourth_window

.. shortcut:: kitty.Fifth window
.. code-block:: conf

    map ctrl+shift+5 fifth_window

.. shortcut:: kitty.Sixth window
.. code-block:: conf

    map ctrl+shift+6 sixth_window

.. shortcut:: kitty.Seventh window
.. code-block:: conf

    map ctrl+shift+7 seventh_window

.. shortcut:: kitty.Eight window
.. code-block:: conf

    map ctrl+shift+8 eighth_window

.. shortcut:: kitty.Ninth window
.. code-block:: conf

    map ctrl+shift+9 ninth_window

.. shortcut:: kitty.Tenth window
.. code-block:: conf

    map ctrl+shift+0 tenth_window


.. _conf-kitty-shortcuts.tab:

Tab management
++++++++++++++++++++++++++++++++++

.. shortcut:: kitty.Next tab
.. code-block:: conf

    map ctrl+shift+right next_tab

.. shortcut:: kitty.Previous tab
.. code-block:: conf

    map ctrl+shift+left previous_tab

.. shortcut:: kitty.New tab
.. code-block:: conf

    map ctrl+shift+t new_tab

.. shortcut:: kitty.Close tab
.. code-block:: conf

    map ctrl+shift+q close_tab

.. shortcut:: kitty.Move tab forward
.. code-block:: conf

    map ctrl+shift+. move_tab_forward

.. shortcut:: kitty.Move tab backward
.. code-block:: conf

    map ctrl+shift+, move_tab_backward

.. shortcut:: kitty.Set tab title
.. code-block:: conf

    map ctrl+shift+alt+t set_tab_title


You can also create shortcuts to go to specific tabs, with 1 being the first
tab, 2 the second tab and -1 being the previously active tab, and any number
larger than the last tab being the last tab::

    map ctrl+alt+1 goto_tab 1
    map ctrl+alt+2 goto_tab 2

Just as with :code:`new_window` above, you can also pass the name of arbitrary
commands to run when using new_tab and use :code:`new_tab_with_cwd`. Finally,
if you want the new tab to open next to the current tab rather than at the
end of the tabs list, use::

    map ctrl+t new_tab !neighbor [optional cmd to run]

.. _conf-kitty-shortcuts.layout:

Layout management
+++++++++++++++++++++++++++++++++++++

.. shortcut:: kitty.Next layout
.. code-block:: conf

    map ctrl+shift+l next_layout


You can also create shortcuts to switch to specific layouts::

    map ctrl+alt+t goto_layout tall
    map ctrl+alt+s goto_layout stack

Similarly, to switch back to the previous layout::

   map ctrl+alt+p last_used_layout

.. _conf-kitty-shortcuts.fonts:

Font sizes
++++++++++++++++++++++++++++++

You can change the font size for all top-level kitty OS windows at a time
or only the current one.

.. shortcut:: kitty.Increase font size
.. code-block:: conf

    map ctrl+shift+equal change_font_size all +2.0

.. shortcut:: kitty.Decrease font size
.. code-block:: conf

    map ctrl+shift+minus change_font_size all -2.0

.. shortcut:: kitty.Reset font size
.. code-block:: conf

    map ctrl+shift+backspace change_font_size all 0


To setup shortcuts for specific font sizes::

    map kitty_mod+f6 change_font_size all 10.0

To setup shortcuts to change only the current OS window's font size::

    map kitty_mod+f6 change_font_size current 10.0

.. _conf-kitty-shortcuts.selection:

Select and act on visible text
++++++++++++++++++++++++++++++++++++++++++++++++++

Use the hints kitten to select text and either pass it to an external program or
insert it into the terminal or copy it to the clipboard.

.. shortcut:: kitty.Open URL
.. code-block:: conf

    map ctrl+shift+e kitten hints


Open a currently visible URL using the keyboard. The program used to open the
URL is specified in :opt:`open_url_with <kitty.open_url_with>`.

.. shortcut:: kitty.Insert selected path
.. code-block:: conf

    map ctrl+shift+p>f kitten hints --type path --program -


Select a path/filename and insert it into the terminal. Useful, for instance to
run git commands on a filename output from a previous git command.

.. shortcut:: kitty.Open selected path
.. code-block:: conf

    map ctrl+shift+p>shift+f kitten hints --type path


Select a path/filename and open it with the default open program.

.. shortcut:: kitty.Insert selected line
.. code-block:: conf

    map ctrl+shift+p>l kitten hints --type line --program -


Select a line of text and insert it into the terminal. Use for the
output of things like: ls -1

.. shortcut:: kitty.Insert selected word
.. code-block:: conf

    map ctrl+shift+p>w kitten hints --type word --program -


Select words and insert into terminal.

.. shortcut:: kitty.Insert selected hash
.. code-block:: conf

    map ctrl+shift+p>h kitten hints --type hash --program -


Select something that looks like a hash and insert it into the terminal.
Useful with git, which uses sha1 hashes to identify commits

.. shortcut:: kitty.Open the selected file at the selected line
.. code-block:: conf

    map ctrl+shift+p>n kitten hints --type linenum


Select something that looks like :code:`filename:linenum` and open it in vim at
the specified line number.

.. shortcut:: kitty.Open the selected hyperlink
.. code-block:: conf

    map ctrl+shift+p>y kitten hints --type hyperlink


Select a hyperlink (i.e. a URL that has been marked as such by the terminal program, for example, by ls --hyperlink=auto).



The hints kitten has many more modes of operation that you can map to different
shortcuts. For a full description see :doc:`kittens/hints`.

.. _conf-kitty-shortcuts.misc:

Miscellaneous
+++++++++++++++++++++++++++++++++

.. shortcut:: kitty.Toggle fullscreen
.. code-block:: conf

    map ctrl+shift+f11 toggle_fullscreen

.. shortcut:: kitty.Toggle maximized
.. code-block:: conf

    map ctrl+shift+f10 toggle_maximized

.. shortcut:: kitty.Unicode input
.. code-block:: conf

    map ctrl+shift+u kitten unicode_input

.. shortcut:: kitty.Edit config file
.. code-block:: conf

    map ctrl+shift+f2 edit_config_file

.. shortcut:: kitty.Open the kitty command shell
.. code-block:: conf

    map ctrl+shift+escape kitty_shell window


Open the kitty shell in a new window/tab/overlay/os_window to control kitty using commands.

.. shortcut:: kitty.Increase background opacity
.. code-block:: conf

    map ctrl+shift+a>m set_background_opacity +0.1

.. shortcut:: kitty.Decrease background opacity
.. code-block:: conf

    map ctrl+shift+a>l set_background_opacity -0.1

.. shortcut:: kitty.Make background fully opaque
.. code-block:: conf

    map ctrl+shift+a>1 set_background_opacity 1

.. shortcut:: kitty.Reset background opacity
.. code-block:: conf

    map ctrl+shift+a>d set_background_opacity default

.. shortcut:: kitty.Reset the terminal
.. code-block:: conf

    map ctrl+shift+delete clear_terminal reset active


You can create shortcuts to clear/reset the terminal. For example::

    # Reset the terminal
    map kitty_mod+f9 clear_terminal reset active
    # Clear the terminal screen by erasing all contents
    map kitty_mod+f10 clear_terminal clear active
    # Clear the terminal scrollback by erasing it
    map kitty_mod+f11 clear_terminal scrollback active
    # Scroll the contents of the screen into the scrollback
    map kitty_mod+f12 clear_terminal scroll active

If you want to operate on all windows instead of just the current one, use :italic:`all` instead of :italic:`active`.

It is also possible to remap Ctrl+L to both scroll the current screen contents into the scrollback buffer
and clear the screen, instead of just clearing the screen::

    map ctrl+l combine : clear_terminal scroll active : send_text normal,application \x0c


.. shortcut:: kitty.Send arbitrary text on key presses


You can tell kitty to send arbitrary (UTF-8) encoded text to
the client program when pressing specified shortcut keys. For example::

    map ctrl+alt+a send_text all Special text

This will send "Special text" when you press the :kbd:`ctrl+alt+a` key
combination.  The text to be sent is a python string literal so you can use
escapes like :code:`\x1b` to send control codes or :code:`\u21fb` to send
unicode characters (or you can just input the unicode characters directly as
UTF-8 text). The first argument to :code:`send_text` is the keyboard modes in which to
activate the shortcut. The possible values are :code:`normal` or :code:`application` or :code:`kitty`
or a comma separated combination of them.  The special keyword :code:`all` means all
modes. The modes :code:`normal` and :code:`application` refer to the DECCKM cursor key mode for
terminals, and :code:`kitty` refers to the special kitty extended keyboard protocol.

Another example, that outputs a word and then moves the cursor to the start of
the line (same as pressing the Home key)::

    map ctrl+alt+a send_text normal Word\x1b[H
    map ctrl+alt+a send_text application Word\x1bOH

