Codebergdnkl

foot

master
ply5 git calls471 ms37 KiB3 cachedprotocol v2
711 lines24 KiBRaw

Logo: a terminal with a foot shaped prompt foot

The fast, lightweight and minimalistic Wayland terminal emulator.

![CI status](https://ci.codeberg.org/api/badges/dnkl/foot/status.svg)

![Packaging status](https://repology.org/badge/vertical-allrepos/foot.svg?columns=4)

Index

  1. Features
  2. Installing
  3. Configuration
  4. Troubleshooting
  5. Why the name 'foot'?
  6. Fonts
  7. Shortcuts
    1. Keyboard
      1. Normal mode
      2. Scrollback search
    2. Mouse
    3. Touchscreen
  8. Server (daemon) mode
  9. URLs
  10. Shell integration
    1. Current working directory
    2. Jumping between prompts
    3. Piping last command's output
  11. Alt/meta
  12. Backspace
  13. Keypad
  14. DPI and font size
  15. Supported OSCs
  16. Programmatically checking if running in foot
  17. XTGETTCAP
  18. No AI / LLM policy
  19. Contributing
  20. Code of Conduct
  21. Bugs
  22. Contact
    1. IRC
    2. Mastodon
  23. Credits
  24. License

Features

Installing

See INSTALL.md.

Configuration

foot can be configured by creating a file $XDG_CONFIG_HOME/foot/foot.ini (defaulting to ~/.config/foot/foot.ini). A template for that can usually be found in /etc/xdg/foot/foot.ini or here.

Further information can be found in foot's man page foot.ini(5).

Troubleshooting

See the wiki

Why the name 'foot'?

I'm bad at names. Most of my projects usually start out as foo something (for example, yambar was f00bar for a while).

So why foot?

foo terminal → footerm → foot

Pretty bad, I know.

As a side note, if you pronounce the foo part of foot the same way you pronounce foobar, then foot sounds a lot like the Swedish word fot, which incidentally means (you guessed it) foot.

Fonts

foot supports all fonts that can be loaded by freetype, including bitmap fonts and color emoji fonts.

Foot uses fontconfig to locate and configure the font(s) to use. Since fontconfig's fallback mechanism is imperfect, especially for monospace fonts (it doesn't prefer monospace fonts even though the requested font is one), foot allows you, the user, to configure the fallback fonts to use.

This also means you can configure each fallback font individually; you want that fallback font to use this size, and you want that other fallback font to be italic? No problem!

If a glyph cannot be found in any of the user configured fallback fonts, then fontconfig's list is used.

Shortcuts

These are the default shortcuts. See man foot.ini and the example foot.ini to see how these can be changed.

Keyboard

Normal mode

<kbd>shift</kbd>+<kbd>page up</kbd>/<kbd>page down</kbd> : Scroll up/down in history

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>c</kbd>, <kbd>XF86Copy</kbd> : Copy selected text to the clipboard

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>v</kbd>, <kbd>XF86Paste</kbd> : Paste from clipboard

<kbd>shift</kbd>+<kbd>insert</kbd> : Paste from the primary selection

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>r</kbd> : Start a scrollback search

<kbd>ctrl</kbd>+<kbd>+</kbd>, <kbd>ctrl</kbd>+<kbd>=</kbd> : Increase font size

<kbd>ctrl</kbd>+<kbd>-</kbd> : Decrease font size

<kbd>ctrl</kbd>+<kbd>0</kbd> : Reset font size

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>n</kbd> : Spawn a new terminal. If the shell has been configured to emit the OSC 7 escape sequence, the new terminal will start in the current working directory.

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>o</kbd> : Enter URL mode, where all currently visible URLs are tagged with a jump label with a key sequence that will open the URL.

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>u</kbd> : Enter Unicode input mode.

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>z</kbd> : Jump to the previous, currently not visible, prompt. Requires shell integration.

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>x</kbd> : Jump to the next prompt. Requires shell integration.

<kbd>ctrl</kbd>+<kbd>r</kbd> : Search backward for next match

<kbd>ctrl</kbd>+<kbd>s</kbd> : Search forward for next match

<kbd>ctrl</kbd>+<kbd>w</kbd> : Extend current selection (and thus the search criteria) to the end of the word, or the next word if currently at a word separating character.

<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>w</kbd> : Same as <kbd>ctrl</kbd>+<kbd>w</kbd>, except that the only word separating characters are whitespace characters.

<kbd>ctrl</kbd>+<kbd>v</kbd>, <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>v</kbd>, <kbd>ctrl</kbd>+<kbd>y</kbd>, <kbd>XF86Paste</kbd> : Paste from clipboard into the search buffer.

<kbd>shift</kbd>+<kbd>insert</kbd> : Paste from primary selection into the search buffer.

<kbd>escape</kbd>, <kbd>ctrl</kbd>+<kbd>g</kbd> : Cancel the search

<kbd>return</kbd> : Finish the search and copy the current match to the primary selection

URL mode

<kbd>t</kbd> : Toggle whether the URL is displayed in the jump label or not

<kbd>escape</kbd>, <kbd>ctrl</kbd>+<kbd>c</kbd>, <kbd>ctrl</kbd>+<kbd>g</kbd>, <kbd>ctrl</kbd>+<kbd>d</kbd> : Exit URL mode without launching any URLs

Mouse

<kbd>left</kbd> - single-click : Drag to select; when released, the selected text is copied to the primary selection. This feature is disabled when client has enabled mouse tracking. : Holding <kbd>shift</kbd> enables selection in mouse tracking enabled clients. : Holding <kbd>ctrl</kbd> will create a block selection.

<kbd>left</kbd> - double-click : Selects the word (separated by spaces, period, comma, parenthesis etc) under the pointer. Hold <kbd>ctrl</kbd> to select everything under the pointer up to, and until, the next space characters.

<kbd>left</kbd> - triple-click : Selects the everything between enclosing quotes, or the entire row if not inside a quote.

<kbd>left</kbd> - quad-click : Selects the entire row.

<kbd>middle</kbd> : Paste from primary selection

<kbd>right</kbd> : Extend current selection. Clicking immediately extends the selection, while hold-and-drag allows you to interactively resize the selection.

<kbd>ctrl</kbd>+<kbd>right</kbd> : Extend the current selection, but force it to be character wise, rather than depending on the original selection mode.

<kbd>wheel</kbd> : Scroll up/down in history

<kbd>ctrl</kbd>+<kbd>wheel</kbd> : Increase/decrease font size

Touchscreen

<kbd>tap</kbd> : Emulates mouse left button click.

<kbd>drag</kbd> : Scrolls up/down in history. : Holding for a while before dragging (time delay can be configured) emulates mouse dragging with left button held.

Server (daemon) mode

When run normally, foot is a single-window application; if you want another window, start another foot process.

However, foot can also be run in a server mode. In this mode, one process hosts multiple windows. All Wayland communication, VT parsing and rendering is done in the server process.

New windows are opened by running footclient, which remains running until the terminal window is closed, at which point it exits with the exit value of the client process (typically the shell).

The point of this mode is a) reduced memory footprint - all terminal windows will share fonts and glyph cache, and b) reduced startup time - loading fonts and populating the glyph cache takes time, but in server mode it only happens once.

The downside is a performance penalty; all windows' input and output are multiplexed in the same thread (but each window will have its own set of rendering threads). This means that if one window is very busy with, for example, producing output, then other windows will suffer.

And of course, should the server process crash, all windows will be gone.

Typical usage would be to start the server process (foot --server) when starting your Wayland compositor (i.e. logging in to your desktop), and then run footclient instead of foot whenever you want to launch a new terminal.

Foot supports socket activation, which means foot --server will only be started the first time you'll run footclient. (systemd user units are included, but it can work with other supervision suites).

URLs

Foot supports URL detection. But, unlike many other terminal emulators, where URLs are highlighted when they are hovered and opened by clicking on them, foot uses a keyboard driven approach.

Pressing <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>o</kbd> enters "URL mode", where all currently visible URLs are underlined, and is associated with a "jump-label". The jump-label indicates the key sequence (e.g. "AF") to use to activate the URL.

The key binding can, of course, be customized, like all other key bindings in foot. See show-urls-launch and show-urls-copy in the foot.ini man page.

show-urls-launch by default opens the URL with xdg-open. This can be changed with the url-launch option.

show-urls-copy is an alternative to show-urls-launch, that changes what activating a URL does; instead of opening it, it copies it to the clipboard. It is unbound by default.

Jump label colors, the URL underline color, and the letters used in the jump label key sequences can be configured.

Shell integration

Current working directory

New foot terminal instances (bound to <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>n</kbd> by default) will open in the current working directory, if the shell in the "parent" terminal reports directory changes.

This is done with the OSC-7 escape sequence. Most shells can be scripted to do this, if they do not support it natively. See the wiki for details.

Jumping between prompts

Foot can move the current viewport to focus prompts of already executed commands (bound to <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>z</kbd>/<kbd>x</kbd> by default).

For this to work, the shell needs to emit an OSC-133;A (\E]133;A\E\\) sequence before each prompt.

In zsh, one way to do this is to add a precmd hook:

zsh
precmd() {
    print -Pn "\e]133;A\e\\"
}

See the wiki for details, and examples for other shells.

Piping last command's output

The key binding pipe-command-output can pipe the last command's output to an application of your choice (similar to the other pipe-* key bindings):

ini
[key-bindings]
pipe-command-output=[sh -c "f=$(mktemp); cat - > $f; footclient emacsclient -nw $f; rm $f"] Control+Shift+g

When pressing <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>g</kbd>, the last command's output is written to a temporary file, then an emacsclient is started in a new footclient instance. The temporary file is removed after the footclient instance has closed.

For this to work, the shell must emit an OSC-133;C (\E]133;C\E\\) sequence before command output starts, and an OSC-133;D (\E]133;D\E\\) when the command output ends.

In fish, one way to do this is to add preexec and postexec hooks:

fish
function foot_cmd_start --on-event fish_preexec
  echo -en "\e]133;C\e\\"
end

function foot_cmd_end --on-event fish_postexec
  echo -en "\e]133;D\e\\"
end

See the wiki for details, and examples for other shells

Alt/meta

By default, foot prefixes Meta characters with ESC. This corresponds to XTerm's metaSendsEscape option set to true.

This can be disabled programmatically with \E[?1036l (and enabled again with \E[?1036h).

When disabled, foot will instead set the 8:th bit of meta character and then UTF-8 encode it. This corresponds to XTerm's eightBitMeta option set to true.

This can also be disabled programmatically with rmm (reset meta mode, \E[?1034l), and enabled again with smm (set meta mode, \E[?1034h).

Backspace

Foot transmits DEL (^?) on <kbd>backspace</kbd>. This corresponds to XTerm's backarrowKey option set to false, and to DECBKM being reset.

To instead transmit BS (^H), press <kbd>ctrl</kbd>+<kbd>backspace</kbd>.

Note that foot does not implement DECBKM, and that the behavior described above cannot be changed.

Finally, pressing <kbd>alt</kbd> will prefix the transmitted byte with ESC.

Keypad

By default, <kbd>Num Lock</kbd> overrides the run-time configuration keypad mode; when active, the keypad is always considered to be in numerical mode. This corresponds to XTerm's numLock option set to true.

In this mode, the keypad keys always sends either numbers (<kbd>Num Lock</kbd> is active) or cursor movement keys (<kbd>Up</kbd>, <kbd>Down</kbd>, <kbd>Left</kbd>, <kbd>Right</kbd>, <kbd>Page Up</kbd>, <kbd>Page Down</kbd> etc).

This can be disabled programmatically with \E[?1035l (and enabled again with \E[?1035h).

When disabled, the keypad sends custom escape sequences instead of numbers, when in application mode.

DPI and font size

Font sizes are apparently a complex thing. Many applications use a fixed DPI of 96. They may also multiply it with the monitor's scale factor.

This results in fonts with different physical sizes (i.e. if measured by a ruler) when rendered on screens with different DPI values. Even if the configured font size is the same.

This is not how it is meant to be. Fonts are measured in point sizes for a reason; a given point size should have the same height on all mediums, be it printers or monitors, regardless of their DPI.

That said, on Wayland, Hi-DPI monitors are typically handled by configuring a "scaling factor" in the compositor. This is usually expressed as either a rational value (e.g. 1.5), or as a percentage (e.g. 150%), by which all fonts and window sizes are supposed to be multiplied.

For this reason, and because of the new fractional scaling protocol (see below for details), and because this is how Wayland applications are expected to behave, foot >= 1.15 will default to scaling fonts using the compositor's scaling factor, and not the monitor DPI.

This means the (assuming the monitors are at the same viewing distance) the font size will appear to change when you move the foot window across different monitors, unless you have configured the monitors' scaling factors correctly in the compositor.

This can be changed by setting the dpi-aware option to yes in foot.ini. When enabled, fonts will not be sized using the scaling factor, but will instead be sized using the monitor's DPI. When the foot window is moved across monitors, the font size is updated for the current monitor's DPI.

This means that, assuming the monitors are at the same viewing distance, the font size will appear to be the same, at all times.

Note: if you configure pixelsize, rather than size, then DPI changes will not change the font size. Pixels are always pixels.

Fractional scaling on Wayland

For a long time, there was no true support for fractional scaling. That is, values like 1.5 (150%), 1.8 (180%) etc, only integer values, like 2 (200%).

Compositors that did support fractional scaling did so using a hack; all applications were told to scale to 200%, and then the compositor would down-scale the rendered image to e.g. 150%. This works OK for everything except fonts, which ended up blurry.

With wayland-protocols 1.32, a new protocol was introduced, that allows compositors to tell applications the actual scaling factor. Applications can then scale the image using a viewport object, instead of setting a scale factor on the raw pixel buffer.

Supported OSCs

OSC, Operating System Command, are escape sequences that interacts with the terminal emulator itself. Foot implements the following OSCs:

  • OSC 0 - change window icon + title (but only title is actually supported)
  • OSC 2 - change window title
  • OSC 4 - change color palette
  • OSC 7 - report CWD (see shell integration)
  • OSC 8 - hyperlink
  • OSC 9 - desktop notification
  • OSC 10 - change (default) foreground color
  • OSC 11 - change (default) background color
  • OSC 12 - change cursor color
  • OSC 17 - change highlight (selection) background color
  • OSC 19 - change highlight (selection) foreground color
  • OSC 22 - set the xcursor (mouse) pointer
  • OSC 52 - copy/paste clipboard data
  • OSC 104 - reset color palette
  • OSC 110 - reset default foreground color
  • OSC 111 - reset default background color
  • OSC 112 - reset cursor color
  • OSC 117 - reset highlight background color
  • OSC 119 - reset highlight foreground color
  • OSC 133 - shell integration
  • OSC 176 - set app ID
  • OSC 555 - flash screen (foot specific)
  • OSC 777 - desktop notification (only the ;notify sub-command of OSC 777 is supported.)

See the foot-ctlseqs(7) man page for a complete list of supported control sequences.

Programmatically checking if running in foot

Foot does not set any environment variables that can be used to identify foot (reading TERM is not reliable since the user may have chosen to use a different terminfo).

You can instead use the escape sequences to read the Secondary and Tertiary Device Attributes (secondary/tertiary DA, for short).

The tertiary DA response is always \EP!|464f4f54\E\\, where 464f4f54 is FOOT in hex.

The secondary DA response is \E[>1;XXYYZZ;0c, where XXYYZZ is foot's major, minor and patch version numbers, in decimal, using two digits for each number. For example, foot-1.4.2 would respond with \E[>1;010402;0c.

Note: not all terminal emulators implement tertiary DA. Most implement secondary DA, but not all. All should however implement Primary DA.

Thus, a safe way to query the terminal is to request the tertiary, secondary and primary DA all at once, in that order. All terminals should ignore escape sequences they do not recognize. You will have to parse the response (which in foot will consist of all three DA responses, all at once) to determine which requests the terminal emulator actually responded to.

Starting with version 1.7.0, foot also implements XTVERSION, to which it will reply with \EP>|foot(version)\E\\. Version is e.g. "1.8.2" for a regular release, or "1.8.2-36-g7db8e06f" for a git build.

XTGETTCAP

XTGETTCAP is an escape sequence initially introduced by XTerm, and also implemented (and extended, to some degree) by Kitty.

It allows querying the terminal for terminfo capabilities. Applications using this feature do not need to use the classic, file-based, terminfo definition. For example, if all applications used this feature, you would no longer have to install foot's terminfo on remote hosts you SSH into.

XTerm's implementation (as of XTerm-370) only supports querying key (as in keyboard keys) capabilities, and three custom capabilities:

  • TN - terminal name
  • Co - number of colors (alias for the colors capability)
  • RGB - number of bits per color channel (different semantics from the RGB capability in file-based terminfo definitions!).

Kitty has extended this, and also supports querying all integer and string capabilities.

Foot supports this, and extends it even further, to also include boolean capabilities. This means foot's entire terminfo can be queried via XTGETTCAP.

Note that both Kitty and foot handles responses to multi-capability queries slightly differently, compared to XTerm.

XTerm will send a single DCS reply, with ;-separated capability/value pairs. There are a couple of issues with this:

  • The success/fail flag in the beginning of the response is always 1 (success), unless the very first queried capability is invalid.
  • XTerm will not respond at all to an invalid capability, unless it's the first one in the XTGETTCAP query.
  • XTerm will end the response at the first invalid capability.

In other words, if you send a large multi-capability query, you will only get responses up to, but not including, the first invalid capability. All subsequent capabilities will be dropped.

Kitty and foot on the other hand, send one DCS response for each capability in the multi query. This allows us to send a proper success/fail flag for each queried capability. Responses for all queried capabilities are always sent. No queries are ever dropped.

All replies are in tigetstr() format. That is, given the same capability name, foot's reply is identical to what tigetstr() would have returned.

In addition to queries for terminfo entries, the query-os-name query will be answered with a response of the form uname=$(uname -s), where $(uname -s) is the name of the OS foot was compiled for.

No AI / LLM policy

Use of generative AI/LLMs is strictly forbidden for all contributions to foot.

This includes bug reports and comments on the issue and pull request trackers.

Contributing

See Contributing

Code of Conduct

See Code of Conduct

Bugs

Please report bugs to https://codeberg.org/dnkl/foot/issues

Before you open a new issue, please search existing bug reports, both open and closed ones. Chances are someone else has already reported the same issue.

The report should contain the following:

  • Foot version (foot --version).
  • Log output from foot (run foot -d info from another terminal).
  • Which Wayland compositor (and version) you are running.
  • If reporting a crash, please try to provide a bt full backtrace with symbols.
  • Steps to reproduce. The more details the better.

Contact

IRC

Ask questions, hang out, sing praise or just say hi in the #foot channel on irc.libera.chat. Logs are available at https://libera.irclog.whitequark.org/foot.

Mastodon

Every now and then I post foot related updates on @dnkl@social.treehouse.systems

Credits

License

Foot is released under the MIT license.

1# ![Logo: a terminal with a foot shaped prompt](icons/hicolor/48x48/apps/foot.png) foot
3The fast, lightweight and minimalistic Wayland terminal emulator.
5[![CI status](https://ci.codeberg.org/api/badges/dnkl/foot/status.svg)](https://ci.codeberg.org/dnkl/foot)
7[![Packaging status](https://repology.org/badge/vertical-allrepos/foot.svg?columns=4)](https://repology.org/project/foot/versions)
10## Index
121. [Features](#features)
131. [Installing](#installing)
141. [Configuration](#configuration)
151. [Troubleshooting](#troubleshooting)
161. [Why the name 'foot'?](#why-the-name-foot)
171. [Fonts](#fonts)
181. [Shortcuts](#shortcuts)
19 1. [Keyboard](#keyboard)
20 1. [Normal mode](#normal-mode)
21 1. [Scrollback search](#scrollback-search)
22 1. [Mouse](#mouse)
23 1. [Touchscreen](#touchscreen)
241. [Server (daemon) mode](#server-daemon-mode)
251. [URLs](#urls)
261. [Shell integration](#shell-integration)
27 1. [Current working directory](#current-working-directory)
28 1. [Jumping between prompts](#jumping-between-prompts)
29 1. [Piping last command's output](#piping-last-command-s-output)
301. [Alt/meta](#alt-meta)
311. [Backspace](#backspace)
321. [Keypad](#keypad)
331. [DPI and font size](#dpi-and-font-size)
341. [Supported OSCs](#supported-oscs)
351. [Programmatically checking if running in foot](#programmatically-checking-if-running-in-foot)
361. [XTGETTCAP](#xtgettcap)
371. [No AI / LLM policy](#no-ai-llm-policy)
381. [Contributing](#contributing)
391. [Code of Conduct](#code-of-conduct)
401. [Bugs](#bugs)
411. [Contact](#contact)
42 1. [IRC](#irc)
43 1. [Mastodon](#mastodon)
441. [Credits](#Credits)
451. [License](#license)
48## Features
50* Fast (see [benchmarks](doc/benchmark.md), and
51 [performance](https://codeberg.org/dnkl/foot/wiki/Performance))
52* Lightweight, in dependencies, on-disk and in-memory
53* Wayland native
54* DE agnostic
55* Server/daemon mode
56* User configurable font fallback
57* On-the-fly font resize
58* On-the-fly DPI font size adjustment
59* Scrollback search
60* Keyboard driven URL detection
61* Color emoji support
62* IME (via `text-input-v3`)
63* Multi-seat
64* True Color (24bpp)
65* [Styled and colored underlines](https://sw.kovidgoyal.net/kitty/underlines/)
66* [Synchronized Updates](https://gitlab.freedesktop.org/terminal-wg/specifications/-/merge_requests/2) support
67* [Sixel image support](https://en.wikipedia.org/wiki/Sixel)
69 ![tux-with-foot](doc/sixel-tux-foot.png "Sixel screenshot")
72# Installing
74See [INSTALL.md](INSTALL.md).
77## Configuration
79**foot** can be configured by creating a file
80`$XDG_CONFIG_HOME/foot/foot.ini` (defaulting to
81`~/.config/foot/foot.ini`). A template for that can usually be found
82in `/etc/xdg/foot/foot.ini` or
83[here](https://codeberg.org/dnkl/foot/src/branch/master/foot.ini).
85Further information can be found in foot's man page `foot.ini(5)`.
88## Troubleshooting
90See the [wiki](https://codeberg.org/dnkl/foot/wiki#user-content-troubleshooting)
93## Why the name 'foot'?
95I'm bad at names. Most of my projects usually start out as _foo
96something_ (for example, [yambar](https://codeberg.org/dnkl/yambar)
97was _f00bar_ for a while).
99So why _foot_?
101_foo terminal_ → _footerm_ → _foot_
103Pretty bad, I know.
105As a side note, if you pronounce the _foo_ part of _foot_ the same way
106you pronounce _foobar_, then _foot_ sounds a lot like the Swedish word
107_fot_, which incidentally means (you guessed it) _foot_.
110## Fonts
112**foot** supports all fonts that can be loaded by _freetype_,
113including **bitmap** fonts and **color emoji** fonts.
115Foot uses _fontconfig_ to locate and configure the font(s) to
116use. Since fontconfig's fallback mechanism is imperfect, especially
117for monospace fonts (it doesn't prefer monospace fonts even though the
118requested font is one), foot allows you, the user, to configure the
119fallback fonts to use.
121This also means you can configure _each_ fallback font individually;
122you want _that_ fallback font to use _this_ size, and you want that
123_other_ fallback font to be _italic_? No problem!
125If a glyph cannot be found in _any_ of the user configured fallback
126fonts, _then_ fontconfig's list is used.
129## Shortcuts
131These are the default shortcuts. See `man foot.ini` and the example
132`foot.ini` to see how these can be changed.
135### Keyboard
137#### Normal mode
139<kbd>shift</kbd>+<kbd>page up</kbd>/<kbd>page down</kbd>
140: Scroll up/down in history
142<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>c</kbd>, <kbd>XF86Copy</kbd>
143: Copy selected text to the _clipboard_
145<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>v</kbd>, <kbd>XF86Paste</kbd>
146: Paste from _clipboard_
148<kbd>shift</kbd>+<kbd>insert</kbd>
149: Paste from the _primary selection_
151<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>r</kbd>
152: Start a scrollback search
154<kbd>ctrl</kbd>+<kbd>+</kbd>, <kbd>ctrl</kbd>+<kbd>=</kbd>
155: Increase font size
157<kbd>ctrl</kbd>+<kbd>-</kbd>
158: Decrease font size
160<kbd>ctrl</kbd>+<kbd>0</kbd>
161: Reset font size
163<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>n</kbd>
164: Spawn a new terminal. If the shell has been [configured to emit the
165 OSC 7 escape
166 sequence](https://codeberg.org/dnkl/foot/wiki#user-content-spawning-new-terminal-instances-in-the-current-working-directory),
167 the new terminal will start in the current working directory.
169<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>o</kbd>
170: Enter URL mode, where all currently visible URLs are tagged with a
171 jump label with a key sequence that will open the URL.
173<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>u</kbd>
174: Enter Unicode input mode.
176<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>z</kbd>
177: Jump to the previous, currently not visible, prompt. Requires [shell
178 integration](https://codeberg.org/dnkl/foot/wiki#user-content-jumping-between-prompts).
180<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>x</kbd>
181: Jump to the next prompt. Requires [shell
182 integration](https://codeberg.org/dnkl/foot/wiki#user-content-jumping-between-prompts).
185#### Scrollback search
187<kbd>ctrl</kbd>+<kbd>r</kbd>
188: Search _backward_ for next match
190<kbd>ctrl</kbd>+<kbd>s</kbd>
191: Search _forward_ for next match
193<kbd>ctrl</kbd>+<kbd>w</kbd>
194: Extend current selection (and thus the search criteria) to the end
195 of the word, or the next word if currently at a word separating
196 character.
198<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>w</kbd>
199: Same as <kbd>ctrl</kbd>+<kbd>w</kbd>, except that the only word
200 separating characters are whitespace characters.
202<kbd>ctrl</kbd>+<kbd>v</kbd>, <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>v</kbd>, <kbd>ctrl</kbd>+<kbd>y</kbd>, <kbd>XF86Paste</kbd>
203: Paste from clipboard into the search buffer.
205<kbd>shift</kbd>+<kbd>insert</kbd>
206: Paste from primary selection into the search buffer.
208<kbd>escape</kbd>, <kbd>ctrl</kbd>+<kbd>g</kbd>
209: Cancel the search
211<kbd>return</kbd>
212: Finish the search and copy the current match to the primary
213 selection
216### URL mode
218<kbd>t</kbd>
219: Toggle whether the URL is displayed in the jump label or not
221<kbd>escape</kbd>, <kbd>ctrl</kbd>+<kbd>c</kbd>, <kbd>ctrl</kbd>+<kbd>g</kbd>, <kbd>ctrl</kbd>+<kbd>d</kbd>
222: Exit URL mode without launching any URLs
225### Mouse
227<kbd>left</kbd> - **single-click**
228: Drag to select; when released, the selected text is copied to the
229 _primary_ selection. This feature is **disabled** when client has
230 enabled _mouse tracking_.
231: Holding <kbd>shift</kbd> enables selection in mouse tracking enabled
232 clients.
233: Holding <kbd>ctrl</kbd> will create a block selection.
235<kbd>left</kbd> - **double-click**
236: Selects the _word_ (separated by spaces, period, comma, parenthesis
237 etc) under the pointer. Hold <kbd>ctrl</kbd> to select everything
238 under the pointer up to, and until, the next space characters.
240<kbd>left</kbd> - **triple-click**
241: Selects the everything between enclosing quotes, or the entire row
242 if not inside a quote.
244<kbd>left</kbd> - **quad-click**
245: Selects the entire row.
247<kbd>middle</kbd>
248: Paste from _primary_ selection
250<kbd>right</kbd>
251: Extend current selection. Clicking immediately extends the
252 selection, while hold-and-drag allows you to interactively resize
253 the selection.
255<kbd>ctrl</kbd>+<kbd>right</kbd>
256: Extend the current selection, but force it to be character wise,
257 rather than depending on the original selection mode.
259<kbd>wheel</kbd>
260: Scroll up/down in history
262<kbd>ctrl</kbd>+<kbd>wheel</kbd>
263: Increase/decrease font size
266### Touchscreen
268<kbd>tap</kbd>
269: Emulates mouse left button click.
271<kbd>drag</kbd>
272: Scrolls up/down in history.
273: Holding for a while before dragging (time delay can be configured)
274 emulates mouse dragging with left button held.
277## Server (daemon) mode
279When run normally, **foot** is a single-window application; if you
280want another window, start another foot process.
282However, foot can also be run in a _server_ mode. In this mode, one
283process hosts multiple windows. All Wayland communication, VT parsing
284and rendering is done in the server process.
286New windows are opened by running `footclient`, which remains running
287until the terminal window is closed, at which point it exits with the
288exit value of the client process (typically the shell).
290The point of this mode is **a)** reduced memory footprint - all
291terminal windows will share fonts and glyph cache, and **b)** reduced
292startup time - loading fonts and populating the glyph cache takes
293time, but in server mode it only happens once.
295The downside is a performance penalty; all windows' input and output
296are multiplexed in the same thread (but each window will have its own
297set of rendering threads). This means that if one window is very busy
298with, for example, producing output, then other windows will suffer.
300And of course, should the server process crash, **all** windows will
301be gone.
303Typical usage would be to start the server process (`foot --server`)
304when starting your Wayland compositor (i.e. logging in to your
305desktop), and then run `footclient` instead of `foot` whenever you
306want to launch a new terminal.
308Foot supports socket activation, which means `foot --server` will only be
309started the first time you'll run `footclient`. (systemd user units are
310included, but it can work with other supervision suites).
312## URLs
314Foot supports URL detection. But, unlike many other terminal
315emulators, where URLs are highlighted when they are hovered and opened
316by clicking on them, foot uses a keyboard driven approach.
318Pressing <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>o</kbd> enters _"URL
319mode"_, where all currently visible URLs are underlined, and is
320associated with a _"jump-label"_. The jump-label indicates the _key
321sequence_ (e.g. **"AF"**) to use to activate the URL.
323The key binding can, of course, be customized, like all other key
324bindings in foot. See `show-urls-launch` and `show-urls-copy` in the
325`foot.ini` man page.
327`show-urls-launch` by default opens the URL with `xdg-open`. This can
328be changed with the `url-launch` option.
330`show-urls-copy` is an alternative to `show-urls-launch`, that changes
331what activating a URL _does_; instead of opening it, it copies it to
332the clipboard. It is unbound by default.
334Jump label colors, the URL underline color, and the letters used in
335the jump label key sequences can be configured.
338## Shell integration
340### Current working directory
342New foot terminal instances (bound to
343<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>n</kbd> by default) will open in
344the current working directory, **if** the shell in the "parent"
345terminal reports directory changes.
347This is done with the OSC-7 escape sequence. Most shells can be
348scripted to do this, if they do not support it natively. See the
349[wiki](https://codeberg.org/dnkl/foot/wiki#user-content-spawning-new-terminal-instances-in-the-current-working-directory)
350for details.
353### Jumping between prompts
355Foot can move the current viewport to focus prompts of already
356executed commands (bound to
357<kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>z</kbd>/<kbd>x</kbd> by
358default).
360For this to work, the shell needs to emit an OSC-133;A
361(`\E]133;A\E\\`) sequence before each prompt.
363In zsh, one way to do this is to add a `precmd` hook:
365```zsh
366precmd() {
367 print -Pn "\e]133;A\e\\"
369```
371See the
372[wiki](https://codeberg.org/dnkl/foot/wiki#user-content-jumping-between-prompts)
373for details, and examples for other shells.
375### Piping last command's output
377The key binding `pipe-command-output` can pipe the last command's
378output to an application of your choice (similar to the other `pipe-*`
379key bindings):
381```ini
382[key-bindings]
383pipe-command-output=[sh -c "f=$(mktemp); cat - > $f; footclient emacsclient -nw $f; rm $f"] Control+Shift+g
384```
386When pressing <kbd>ctrl</kbd>+<kbd>shift</kbd>+<kbd>g</kbd>, the last
387command's output is written to a temporary file, then an emacsclient
388is started in a new footclient instance. The temporary file is removed
389after the footclient instance has closed.
391For this to work, the shell must emit an OSC-133;C (`\E]133;C\E\\`)
392sequence before command output starts, and an OSC-133;D
393(`\E]133;D\E\\`) when the command output ends.
395In fish, one way to do this is to add `preexec` and `postexec` hooks:
397```fish
398function foot_cmd_start --on-event fish_preexec
399 echo -en "\e]133;C\e\\"
400end
402function foot_cmd_end --on-event fish_postexec
403 echo -en "\e]133;D\e\\"
404end
405```
407See the
408[wiki](https://codeberg.org/dnkl/foot/wiki#user-content-piping-last-command-s-output)
409for details, and examples for other shells
412## Alt/meta
414By default, foot prefixes _Meta characters_ with ESC. This corresponds
415to XTerm's `metaSendsEscape` option set to `true`.
417This can be disabled programmatically with `\E[?1036l` (and enabled
418again with `\E[?1036h`).
420When disabled, foot will instead set the 8:th bit of meta character
421and then UTF-8 encode it. This corresponds to XTerm's `eightBitMeta`
422option set to `true`.
424This can also be disabled programmatically with `rmm` (_reset meta
425mode_, `\E[?1034l`), and enabled again with `smm` (_set meta mode_,
426`\E[?1034h`).
429## Backspace
431Foot transmits DEL (`^?`) on <kbd>backspace</kbd>. This corresponds to
432XTerm's `backarrowKey` option set to `false`, and to
433[`DECBKM`](https://vt100.net/docs/vt510-rm/DECBKM.html) being _reset_.
435To instead transmit BS (`^H`), press
436<kbd>ctrl</kbd>+<kbd>backspace</kbd>.
438Note that foot does **not** implement `DECBKM`, and that the behavior
439described above **cannot** be changed.
441Finally, pressing <kbd>alt</kbd> will prefix the transmitted byte with
442ESC.
445## Keypad
447By default, <kbd>Num Lock</kbd> overrides the run-time configuration
448keypad mode; when active, the keypad is always considered to be in
449_numerical_ mode. This corresponds to XTerm's `numLock` option set to
450`true`.
452In this mode, the keypad keys always sends either numbers (<kbd>Num
453Lock</kbd> is **active**) or cursor movement keys (<kbd>Up</kbd>,
454<kbd>Down</kbd>, <kbd>Left</kbd>, <kbd>Right</kbd>, <kbd>Page
455Up</kbd>, <kbd>Page Down</kbd> etc).
457This can be disabled programmatically with `\E[?1035l` (and enabled
458again with `\E[?1035h`).
460When disabled, the keypad sends custom escape sequences instead of
461numbers, when in _application_ mode.
464## DPI and font size
466Font sizes are apparently a complex thing. Many applications use a
467fixed DPI of 96. They may also multiply it with the monitor's scale
468factor.
470This results in fonts with different **physical** sizes (i.e. if
471measured by a ruler) when rendered on screens with different DPI
472values. Even if the configured font size is the same.
474This is not how it is meant to be. Fonts are measured in _point sizes_
475**for a reason**; a given point size should have the same height on
476all mediums, be it printers or monitors, regardless of their DPI.
478That said, on Wayland, Hi-DPI monitors are typically handled by
479configuring a _"scaling factor"_ in the compositor. This is usually
480expressed as either a rational value (e.g. _1.5_), or as a percentage
481(e.g. _150%_), by which all fonts and window sizes are supposed to be
482multiplied.
484For this reason, and because of the new _fractional scaling_ protocol
485(see below for details), and because this is how Wayland applications
486are expected to behave, foot >= 1.15 will default to scaling fonts
487using the compositor's scaling factor, and **not** the monitor
488DPI.
490This means the (assuming the monitors are at the same viewing
491distance) the font size will appear to change when you move the foot
492window across different monitors, **unless** you have configured the
493monitors' scaling factors correctly in the compositor.
495This can be changed by setting the `dpi-aware` option to `yes` in
496`foot.ini`. When enabled, fonts will **not** be sized using the
497scaling factor, but will instead be sized using the monitor's
498DPI. When the foot window is moved across monitors, the font size is
499updated for the current monitor's DPI.
501This means that, assuming the monitors are **at the same viewing
502distance**, the font size will appear to be the same, at all times.
504_Note_: if you configure **pixelsize**, rather than **size**, then DPI
505changes will **not** change the font size. Pixels are always pixels.
508### Fractional scaling on Wayland
510For a long time, there was no **true** support for _fractional
511scaling_. That is, values like 1.5 (150%), 1.8 (180%) etc, only
512integer values, like 2 (200%).
514Compositors that _did_ support fractional scaling did so using a hack;
515all applications were told to scale to 200%, and then the compositor
516would down-scale the rendered image to e.g. 150%. This works OK for
517everything **except fonts**, which ended up blurry.
519With _wayland-protocols 1.32_, a new protocol was introduced, that
520allows compositors to tell applications the _actual_ scaling
521factor. Applications can then scale the image using a _viewport_
522object, instead of setting a scale factor on the raw pixel buffer.
525## Supported OSCs
527OSC, _Operating System Command_, are escape sequences that interacts
528with the terminal emulator itself. Foot implements the following OSCs:
530* `OSC 0` - change window icon + title (but only title is actually
531 supported)
532* `OSC 2` - change window title
533* `OSC 4` - change color palette
534* `OSC 7` - report CWD (see [shell integration](#shell-integration))
535* `OSC 8` - hyperlink
536* `OSC 9` - desktop notification
537* `OSC 10` - change (default) foreground color
538* `OSC 11` - change (default) background color
539* `OSC 12` - change cursor color
540* `OSC 17` - change highlight (selection) background color
541* `OSC 19` - change highlight (selection) foreground color
542* `OSC 22` - set the xcursor (mouse) pointer
543* `OSC 52` - copy/paste clipboard data
544* `OSC 104` - reset color palette
545* `OSC 110` - reset default foreground color
546* `OSC 111` - reset default background color
547* `OSC 112` - reset cursor color
548* `OSC 117` - reset highlight background color
549* `OSC 119` - reset highlight foreground color
550* `OSC 133` - [shell integration](#shell-integration)
551* `OSC 176` - set app ID
552* `OSC 555` - flash screen (**foot specific**)
553* `OSC 777` - desktop notification (only the `;notify` sub-command of
554 OSC 777 is supported.)
556See the **foot-ctlseqs**(7) man page for a complete list of supported
557control sequences.
560## Programmatically checking if running in foot
562Foot does **not** set any environment variables that can be used to
563identify foot (reading `TERM` is not reliable since the user may have
564chosen to use a different terminfo).
566You can instead use the escape sequences to read the _Secondary_ and
567_Tertiary Device Attributes_ (secondary/tertiary DA, for short).
569The tertiary DA response is always `\EP!|464f4f54\E\\`, where
570`464f4f54` is `FOOT` in hex.
572The secondary DA response is `\E[>1;XXYYZZ;0c`, where `XXYYZZ` is
573foot's major, minor and patch version numbers, in decimal, using two
574digits for each number. For example, foot-1.4.2 would respond with
575`\E[>1;010402;0c`.
577**Note**: not all terminal emulators implement tertiary DA. Most
578implement secondary DA, but not all. All _should_ however implement
579_Primary DA_.
581Thus, a safe way to query the terminal is to request the tertiary,
582secondary and primary DA all at once, in that order. All terminals
583should ignore escape sequences they do not recognize. You will have to
584parse the response (which in foot will consist of all three DA
585responses, all at once) to determine which requests the terminal
586emulator actually responded to.
588Starting with version 1.7.0, foot also implements `XTVERSION`, to
589which it will reply with `\EP>|foot(version)\E\\`. Version is
590e.g. "1.8.2" for a regular release, or "1.8.2-36-g7db8e06f" for a git
591build.
594# XTGETTCAP
596`XTGETTCAP` is an escape sequence initially introduced by XTerm, and
597also implemented (and extended, to some degree) by Kitty.
599It allows querying the terminal for terminfo
600capabilities. Applications using this feature do not need to use the
601classic, file-based, terminfo definition. For example, if all
602applications used this feature, you would no longer have to install
603foot's terminfo on remote hosts you SSH into.
605XTerm's implementation (as of XTerm-370) only supports querying key
606(as in keyboard keys) capabilities, and three custom capabilities:
608* `TN` - terminal name
609* `Co` - number of colors (alias for the `colors` capability)
610* `RGB` - number of bits per color channel (different semantics from
611 the `RGB` capability in file-based terminfo definitions!).
613Kitty has extended this, and also supports querying all integer and
614string capabilities.
616Foot supports this, and extends it even further, to also include
617boolean capabilities. This means foot's entire terminfo can be queried
618via `XTGETTCAP`.
620Note that both Kitty and foot handles **responses** to
621multi-capability queries slightly differently, compared to XTerm.
623XTerm will send a single DCS reply, with `;`-separated
624capability/value pairs. There are a couple of issues with this:
626* The success/fail flag in the beginning of the response is always `1`
627 (success), unless the very **first** queried capability is invalid.
628* XTerm will not respond **at all** to an invalid capability, unless
629 it's the first one in the `XTGETTCAP` query.
630* XTerm will end the response at the first invalid capability.
632In other words, if you send a large multi-capability query, you will
633only get responses up to, but not including, the first invalid
634capability. All subsequent capabilities will be dropped.
636Kitty and foot on the other hand, send one DCS response for **each**
637capability in the multi query. This allows us to send a proper
638success/fail flag for each queried capability. Responses for **all**
639queried capabilities are **always** sent. No queries are ever dropped.
641All replies are in `tigetstr()` format. That is, given the same
642capability name, foot's reply is identical to what `tigetstr()` would
643have returned.
645In addition to queries for terminfo entries, the `query-os-name` query
646will be answered with a response of the form `uname=$(uname -s)`,
647where `$(uname -s)` is the name of the OS foot was compiled for.
650# No AI / LLM policy
652Use of generative AI/LLMs is strictly forbidden for **all**
653contributions to foot.
655This includes bug reports and comments on the issue and pull request
656trackers.
659# Contributing
661See [Contributing](CONTRIBUTING.md)
664# Code of Conduct
666See [Code of Conduct](CODE_OF_CONDUCT.md)
669# Bugs
671Please report bugs to https://codeberg.org/dnkl/foot/issues
673Before you open a new issue, please search existing bug reports, both
674open **and** closed ones. Chances are someone else has already
675reported the same issue.
677The report should contain the following:
679- Foot version (`foot --version`).
680- Log output from foot (run `foot -d info` from another terminal).
681- Which Wayland compositor (and version) you are running.
682- If reporting a crash, please try to provide a `bt full` backtrace
683 with symbols.
684- Steps to reproduce. The more details the better.
687# Contact
689## IRC
691Ask questions, hang out, sing praise or just say hi in the `#foot`
692channel on
693[irc.libera.chat](https://web.libera.chat/?channels=#foot). Logs are
694available at https://libera.irclog.whitequark.org/foot.
697## Mastodon
699Every now and then I post foot related updates on
700[@dnkl@social.treehouse.systems](https://social.treehouse.systems/@dnkl)
703# Credits
705* [Ordoviz](https://codeberg.org/Ordoviz), for designing and
706contributing foot's [logo](icons/hicolor/48x48/apps/foot.png).
709# License
711Foot is released under the [MIT license](LICENSE).
Diagnostics5 git calls · 471 ms
CallStatusSizeTime0471 ms
discover200178 B3 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=178
git.server.agent=git/2.56.1-Linux
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch server-option object-format
git.server.fetch=shallow wait-for-done filter
git.protocol.version=2
git.pkt.frames=9
git.pkt.data=7
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=178
git.pkt.payload.max=35
ls-refs20010 KiB465 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=383
git.response.bytes=10322
git.response.cache=EXPIRED
git.response.duration_ms=465
git.protocol.version=2
git.pkt.frames=108
git.pkt.data=107
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=10322
git.pkt.payload.max=106
git.ls_refs.count=107
git.ls_refs.head=refs/heads/master
fetchtree:0 · deepen 102009.3 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=9489
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=tree:0
git.fetch.wants=c0d2c3e95d74cb60526ff28aec9f34ee3df545e0
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=7
git.pkt.data=5
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=9489
git.pkt.payload.max=9389
git.sideband.band1.bytes=9389
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=10
git.pack.bytes=9389
git.pack.ofs_delta=0
git.pack.ref_delta=0
git.pack.chain.max=0
git.pack.trailer=de930681b6073ba5b599a0f956bfbd114762ad5a
git.pack.full=10
Open pack map
fetchcombine:blob:none+tree:2 · deepen 12008.6 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=8830
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.filter=combine:blob:none+tree:2
git.fetch.wants=c0d2c3e95d74cb60526ff28aec9f34ee3df545e0
git.fetch.haves.count=0
git.fetch.deepen=1
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=7
git.pkt.data=5
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=8830
git.pkt.payload.max=8730
git.sideband.band1.bytes=8730
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=14
git.pack.bytes=8730
git.fetch.wide.objects=14
git.fetch.wide.extra_bytes=9909
git.fetch.wide.blobs=0
fetch2009.0 KiB · hit3 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=3
git.response.bytes=9263
git.response.cache=HIT
git.response.duration_ms=3
git.fetch.wants=1eb70ec53d9822a3459c9ede69d9a760cd13cc55
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=4
git.pkt.data=3
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=9263
git.pkt.payload.max=9236
git.sideband.band1.bytes=9236
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://codeberg.org/dnkl/foot
Ref
refs/heads/master
Commit
c0d2c3e95d74cb60526ff28aec9f34ee3df545e0
cf-ray
a5e224295c93a87d
Request
7c1db894…
Protocol
v2 · sha1
Agent
git/2.56.1-Linux
Filter
advertised
Fetch
shallow wait-for-done filter
Capabilities
agent ls-refs fetch server-option object-format