<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/doc/foot.ini.5.scd, branch master</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=master</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2026-09-05T13:00:33Z</updated>
<entry>
<title>doc: foot.ini: colors.cursor: tweak wording of the default value</title>
<updated>2026-09-05T13:00:33Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-09-05T13:00:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=180df200a35ce94cb2b38ae84d40b53c63467bd6'/>
<id>urn:sha1:180df200a35ce94cb2b38ae84d40b53c63467bd6</id>
<content type='text'>
Try to make it clearer that it is the *current* fg/bg inversed, not
the *default* fg/bg.

Related: #2455
</content>
</entry>
<entry>
<title>config: fix modifiers conflict check</title>
<updated>2026-09-02T05:51:03Z</updated>
<author>
<name>CismonX</name>
<email>admin@cismon.net</email>
</author>
<published>2026-08-30T23:41:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1c4cfc2dfce5698411a552f056535f9a2fb2a6f6'/>
<id>urn:sha1:1c4cfc2dfce5698411a552f056535f9a2fb2a6f6</id>
<content type='text'>
Currently, if a mouse binding contains _any_ modifier key set in
config 'selection-override-modifiers', it does not work since
these modifiers get unset in function 'match_mouse_binding()'.

Function 'resolve_key_binding_collisions()' is supposed to detect
this and display an error message, however, it does not work unless
the conflicting modifiers are identical.

For example, given the following config options:

  selection-override-modifiers=Control+Shift
  select-begin-block=Control+BTN_LEFT

Foot does not display an error message for this, but if you try to
select text with 'Control+BTN_LEFT', it behaves as if only 'BTN_LEFT'
is pressed.

This is due to function 'modifiers_disjoint()' being implemented as
"not equal" rather than "disjoint".
Fixed by properly implementing this function. Also clarify the
'selection-override-modifiers' config option in the man page.

As a side effect, this also fixes 'selection-override-modifiers=none'
conflicting with mouse bindings that do not contain modifier keys
(an empty set is disjoint with itself).
</content>
</entry>
<entry>
<title>config: update default URL regex</title>
<updated>2026-07-26T17:37:54Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-07-26T14:07:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ef5ef6148fc2345b4a4fd2d5e6b775a423f360c3'/>
<id>urn:sha1:ef5ef6148fc2345b4a4fd2d5e6b775a423f360c3</id>
<content type='text'>
* Allow single-quotes _inside_ URLs (but still not at the end)
* Require at least one character inside balanced parenthesis or
  quotes.

Closes #2417
</content>
</entry>
<entry>
<title>doc: add fyi example configuration, as an alternative to notify-send</title>
<updated>2026-07-26T16:32:42Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-07-26T16:32:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6d1d3324eb5b91416b6f034b91bfc67a28f32428'/>
<id>urn:sha1:6d1d3324eb5b91416b6f034b91bfc67a28f32428</id>
<content type='text'>
Closes #2401
</content>
</entry>
<entry>
<title>config: add url.style=none|single|double|curly|dotted|dashed</title>
<updated>2026-04-06T13:47:26Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-04-06T13:47:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2c454a71f14da912f5623336b93ec8f48f2d1cf9'/>
<id>urn:sha1:2c454a71f14da912f5623336b93ec8f48f2d1cf9</id>
<content type='text'>
This option allows you to configure which underline style to use with
URLs.

The default is dotted. Since before this patch, URL underlines were
always plain underlines, this means the default URL underline style
has changed, from single to dotted.

Closes #2302
</content>
</entry>
<entry>
<title>doc: foot.ini: fix default value of initial-color-theme</title>
<updated>2026-03-05T15:17:09Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-03-05T15:17:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c05bd55029b8a9bb57df246fec9acc786d71d16f'/>
<id>urn:sha1:c05bd55029b8a9bb57df246fec9acc786d71d16f</id>
<content type='text'>
Closes #2292
</content>
</entry>
<entry>
<title>Add support for background blur</title>
<updated>2026-03-02T08:39:09Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-10-16T11:43:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=dea10e2e48162c6ab48ca564ceeca88dea886a04'/>
<id>urn:sha1:dea10e2e48162c6ab48ca564ceeca88dea886a04</id>
<content type='text'>
This patch adds a new config option: colors{,2}.blur=no|yes. When
enabled, transparent background are also blurred.

Note that this requires the brand new ext-background-effect-v1
protocol, and specifically, that the compositor implements the blur
effect.
</content>
</entry>
<entry>
<title>support four-sided padding (left/top/right/bottom)</title>
<updated>2026-03-02T08:13:01Z</updated>
<author>
<name>pi66</name>
<email>pixel2176@proton.me</email>
</author>
<published>2025-12-19T11:17:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=21485fa66d9b7026bfd1dd2764431805cdb17cf1'/>
<id>urn:sha1:21485fa66d9b7026bfd1dd2764431805cdb17cf1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: foot.ini: mention titlebar text color in button-color</title>
<updated>2026-03-02T07:55:50Z</updated>
<author>
<name>nariby</name>
<email>nariby@noreply.codeberg.org</email>
</author>
<published>2026-02-08T14:12:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fbf430473146bdb6f9ab6afefa4aab4c57a3d9a4'/>
<id>urn:sha1:fbf430473146bdb6f9ab6afefa4aab4c57a3d9a4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: fix typos in foot.ini.5.scd</title>
<updated>2026-03-02T07:52:44Z</updated>
<author>
<name>Barinderpreet Singh</name>
<email>64461700+knownasnaffy@users.noreply.github.com</email>
</author>
<published>2026-02-27T13:28:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1f31b43db7acd5ea5f7e88d0408f043a78df17fe'/>
<id>urn:sha1:1f31b43db7acd5ea5f7e88d0408f043a78df17fe</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add [colors-dark] and [colors-light], replacing [colors] and [colors2]</title>
<updated>2025-12-20T14:51:30Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-12-19T08:29:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=cf2b390f6e096e7a2ca93d4dece153eb13261a2e'/>
<id>urn:sha1:cf2b390f6e096e7a2ca93d4dece153eb13261a2e</id>
<content type='text'>
The main reason for having two color sections is to be able to switch
between dark and light. Thus, it's better if the section names reflect
this, rather than the more generic 'colors' and 'colors2' (which was
the dark one and which was the light one, now again?)

When the second color section was added, we kept the original name,
colors, to make sure we didn't break existing configurations, and
third-party themes.

However, in the long run, it's probably better to be specific in the
section naming, to avoid confusion.

So, add 'colors-dark', and 'colors-light'. Keep 'colors' and 'colors2'
as aliases for now, but mark them as deprecated. They WILL be removed
in a future release.

Also rename the option values for initial-color-theme, from 1/2, to
dark/light. Keep the old ones for now, marked as deprecated.

Update all bundled themes to use the new names. In the light-only
themes (i.e. themes that define a single, light, theme), use
colors-light, and set initial-color-theme=light.

Possible improvements: disable color switching if only one color
section has been explicitly configured (todo: figure out how to handle
the default color theme values...)
</content>
</entry>
<entry>
<title>config: add toplevel-tag=TAG</title>
<updated>2025-11-12T10:04:25Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-11-12T10:04:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fc9625678fc7e295e7a7e03a5d47db21d4be3010'/>
<id>urn:sha1:fc9625678fc7e295e7a7e03a5d47db21d4be3010</id>
<content type='text'>
Add support for the new xdg-toplevel-tag-v1 Wayland protocol, by
exposing a new config option, `toplevel-tag`, and a corresponding
command option, `--toplevel-tag` (in both `foot` and `footclient`).

This can help the compositor with session management, or custom window
rules.

Closes #2212
</content>
</entry>
<entry>
<title>doc: foot.ini: fix typo</title>
<updated>2025-10-24T18:11:52Z</updated>
<author>
<name>Andrei</name>
<email>andreisva2023@gmail.com</email>
</author>
<published>2025-10-24T18:08:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=19466a21d8b7e580ef611ca56b81e7568fc44b37'/>
<id>urn:sha1:19466a21d8b7e580ef611ca56b81e7568fc44b37</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add colors.dim-blend-towards=black|white</title>
<updated>2025-10-10T09:10:38Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-10-10T09:10:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7ed36c10334c0b2480fa026238f8f1791d2f9439'/>
<id>urn:sha1:7ed36c10334c0b2480fa026238f8f1791d2f9439</id>
<content type='text'>
Before this patch, we always blended towards black when dimming
text. However, with light color themes, it usually looks better if we
dim towards white instead.

This option allows you to choose which color to blend towards.

The default is 'black' in '[colors]', and 'white' in '[colors2]'.

Closes #2187
</content>
</entry>
<entry>
<title>render: when double-buffering, pre-apply previous frame's damage early</title>
<updated>2025-10-10T08:23:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-10-05T08:48:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=299186a6547f6e038ee6f3822caf9a0fdfabceef'/>
<id>urn:sha1:299186a6547f6e038ee6f3822caf9a0fdfabceef</id>
<content type='text'>
Foot likes it when compositor releases buffer immediately, as that
means we only have to re-render the cells that have changed since the
last frame.

For various reasons, not all compositors do this. In this case, foot
is typically forced to switch between two buffers, i.e. double-buffer.

In this case, each frame starts with copying over the damage from the
previous frame, to the new frame. Then we start rendering the updated
cells.

Bringing over the previous frame's damage can be slow, if the changed
area was large (e.g. when scrolling one or a few lines, or on full
screen updates). It's also done single-threaded. Thus it not only
slows down frame rendering, but pauses everything else (i.e. input
processing). All in all, it reduces performance and increases input
latency.

But we don't have to wait until it's time to render a frame to copy
over the previous frame's damage. We can do that as soon as the
compositor has released the buffer (for the frame _before_ the
previous frame). And we can do this in a thread.

This frees up foot to continue processing input, and reduces frame
rendering time since we can now start rendering the modified cells
immediately, without first doing a large memcpy(3).

In worst case scenarios (or perhaps we should consider them best case
scenarios...), I've seen up to a 10x performance increase in frame
rendering times (this obviously does *not* include the time it takes
to copy over the previous frame's damage, since that doesn't affect
neither input processing nor frame rendering).

Implemented by adding a callback mechanism to the shm abstraction
layer. Use it for the grid buffers, and kick off a thread that copies
the previous frame's damage, and resets the buffers age to 0 (so that
foot understands it can start render to it immediately when it later
needs to render a frame).

Since we have certain way of knowing if a compositor releases buffers
immediately or not, use a bit of heuristics; if we see 10 consecutive
non-immediate releases (that is, we reset the counter as soon as we do
see an immediate release), this new "pre-apply damage" logic is
enabled. It can be force-disabled with tweak.pre-apply-damage=no.

We also need to take care to wait for the thread before resetting the
render's "last_buf" pointer (or we'll SEGFAULT in the thread...).

We must also ensure we wait for the thread to finish before we start
rendering a new frame. Under normal circumstances, the wait time is
always 0, the thread has almost always finished long before we need to
render the next frame. But it _can_ happen.

Closes #2188
</content>
</entry>
<entry>
<title>doc: foot.ini: document tweak.min-stride-alignment</title>
<updated>2025-10-05T07:40:51Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-10-04T13:38:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e43ea3676fe359864a8a22a31beed5bf289f367c'/>
<id>urn:sha1:e43ea3676fe359864a8a22a31beed5bf289f367c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: foot.ini: typo: upppercase -&gt; uppercase</title>
<updated>2025-08-31T09:42:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-08-31T09:42:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1d9ac3f611f1b81983b095a2f96e36dba4d24da9'/>
<id>urn:sha1:1d9ac3f611f1b81983b095a2f96e36dba4d24da9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add 'uppercase-regex-insert'</title>
<updated>2025-08-31T09:36:28Z</updated>
<author>
<name>Ryan Roden-Corrent</name>
<email>git@rrc.codes</email>
</author>
<published>2025-08-07T12:18:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=298196365c06c13dd16a74e34e03d9de93670473'/>
<id>urn:sha1:298196365c06c13dd16a74e34e03d9de93670473</id>
<content type='text'>
This makes the "uppercase hint character inserts selected text"
behavior added in #1975 configurable, as it can have unexpected
behavior for some users.

It defaults to "on", preserving the new behavior of `foot`, after

Fixes #2159.
</content>
</entry>
<entry>
<title>doc: foot.ini: mention SIGUSR1/SIGUSR2 and reference foot(1)</title>
<updated>2025-07-30T10:36:32Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-07-30T10:25:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b1b2162416cc0633b6432b0af48e79de6a5540d2'/>
<id>urn:sha1:b1b2162416cc0633b6432b0af48e79de6a5540d2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>conf: pad: add center-when-fullscreen and center-when-maximized-and-fullscreen</title>
<updated>2025-05-24T07:56:16Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-05-23T06:38:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=5a84f8d841d09e9aa91befbbb8e8b634b7f8959a'/>
<id>urn:sha1:5a84f8d841d09e9aa91befbbb8e8b634b7f8959a</id>
<content type='text'>
Before this patch, the grid content was *always* centered when the
window was maximized or fullscreened, regardless of how the user had
configured padding.

Now, the behavior is controlled by the 'pad' option. Before this
patch, the syntax was

    pad MxN [center]

Now it is

    pad MxN [center|center-when-fullscreen|center-when-maximized-and-fullscreen]

The default is "pad 0x0 center-when-maximized-and-fullscreen", to
match current behavior.

Closes #2111
</content>
</entry>
</feed>
