<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git, branch 1.26.0</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.26.0</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.26.0'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2026-03-03T16:35:20Z</updated>
<entry>
<title>meson: bump version to 1.26.0</title>
<updated>2026-03-03T16:35:20Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-03-03T16:35:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=739cf115e6bc014b895bf945afccb88be6971be0'/>
<id>urn:sha1:739cf115e6bc014b895bf945afccb88be6971be0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: prepare for 1.26.0</title>
<updated>2026-03-03T16:35:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-03-03T16:35:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3bbaa64caef285727ff63dcaef614a01c231935c'/>
<id>urn:sha1:3bbaa64caef285727ff63dcaef614a01c231935c</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove metainfo.xml</title>
<updated>2026-03-03T16:32:22Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-03-02T10:38:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c9c5c55745ba067809b26fb98063f46203611955'/>
<id>urn:sha1:c9c5c55745ba067809b26fb98063f46203611955</id>
<content type='text'>
It hasn't been kept up to date for a long time, and no one seems to
care, so lets remove it.
</content>
</entry>
<entry>
<title>readme: update sixel screenshot</title>
<updated>2026-03-02T10:49:54Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-03-02T10:48:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e48178bec3c5fd6bd1b6aa25c28cce2c9ff6874e'/>
<id>urn:sha1:e48178bec3c5fd6bd1b6aa25c28cce2c9ff6874e</id>
<content type='text'>
Closes #2215
</content>
</entry>
<entry>
<title>test: config: blur: fix test failure; use the correct parsing function</title>
<updated>2026-03-02T08:42:31Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-03-02T08:42:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=046898f1b8e89b7ad1677905cc468daa98546b43'/>
<id>urn:sha1:046898f1b8e89b7ad1677905cc468daa98546b43</id>
<content type='text'>
</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>Spawning new terminal with --config from parent instance</title>
<updated>2026-03-02T08:16:36Z</updated>
<author>
<name>Stéphane Klein</name>
<email>contact@stephane-klein.info</email>
</author>
<published>2026-01-08T23:31:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=dc0c8550c38ffd0983789573a1a0d4417016c2c7'/>
<id>urn:sha1:dc0c8550c38ffd0983789573a1a0d4417016c2c7</id>
<content type='text'>
Reference: https://codeberg.org/dnkl/foot/issues/1622
Signed-off-by: Stéphane Klein &lt;contact@stephane-klein.info&gt;
</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>Fix cursor color</title>
<updated>2026-02-23T15:46:36Z</updated>
<author>
<name>valoq</name>
<email>valoq@noreply.codeberg.org</email>
</author>
<published>2026-02-23T15:46:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e24334a8dfdd43a5a26ad59bba0d76409b1de1ea'/>
<id>urn:sha1:e24334a8dfdd43a5a26ad59bba0d76409b1de1ea</id>
<content type='text'>
Default cursor color in alacritty is white (foreground) and not cyan.
</content>
</entry>
<entry>
<title>wayland: wait for pre-apply damage thread before destroying a terminal instance</title>
<updated>2026-02-02T11:40:50Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-01-28T08:44:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c291194a4e593bbbb91420e81fa0111508084448'/>
<id>urn:sha1:c291194a4e593bbbb91420e81fa0111508084448</id>
<content type='text'>
It's possible, but unlikely, that we've pushed a "pre-apply damage"
job to the renderer thread queue (or that we've pushed it, and the
a thread is now working on it) when we shutdown a terminal instance.

This is sometimes caught in an assertion in term_destroy(), where we
check the queue length is 0. Other times, or in release builds, we
might crash in the thread, or in the shutdown logic when freeing the
buffer chains associated with the terminal instance.

Fix by ensuring there's no pre-apply damage operation queued, or
running, before shutting down a terminal instance.

Closes #2263
</content>
</entry>
<entry>
<title>osc-8: don't log URL + ID when closing</title>
<updated>2026-02-02T10:19:07Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-02-02T10:19:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0bf193ef8122b2fd412438c0e405fb085cd62a1e'/>
<id>urn:sha1:0bf193ef8122b2fd412438c0e405fb085cd62a1e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sixel: force a height of at least one sixel when explicitly resizing</title>
<updated>2026-01-28T08:33:16Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-01-28T08:21:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6fbb9b7d3b2b43e69ca3ce56823fdb9f65a74890'/>
<id>urn:sha1:6fbb9b7d3b2b43e69ca3ce56823fdb9f65a74890</id>
<content type='text'>
Applications often prefix the sixel with a raster attributes (RA)
sequence, where they tell us how large the sixel is. Strictly
speaking, this just tells us the size of the area to clear, but we use
it as a hint and pre-allocates the image buffer.

It's important to stress that it is valid to emit a MxN RA, and then
write sixel data outside of that area.

Foot handles this, in _most_ cases. We didn't handle the corner case
Mx0. I.e. a width &gt; 0, but height == 0. No image buffer was allocated,
and we also failed to detect a resize was necessary when the
application started printing sixel data.

Much of this is for performance reason; we only check the minimum
necessary. For example, we only check if going outside the
pre-allocated *column* while printing sixels. *Rows* are checked on a
graphical newline.

In other words, the *current* row has to be valid when writing
sixels. And in case of Mx0, it wasn't.

Fix by forcing a height of at least one sixel (typically 6 pixels).

Closes #2267
</content>
</entry>
<entry>
<title>input: ignore release events after a keyboard shortcut was triggered</title>
<updated>2026-01-28T08:31:32Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-01-10T06:36:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3a2eb80d83d59d194a3d07da227431c634892ff5'/>
<id>urn:sha1:3a2eb80d83d59d194a3d07da227431c634892ff5</id>
<content type='text'>
This fixes an issue with the kitty keyboard protocol, where 'release'
events associated with a shortcut was sent to the client application.

Example: user triggers "scroll up". We scroll up. No key event(s) are
sent to the client application. Then the user releases the keys. we
don't do any shortcut handling on release events, and so we continue
with the normal input processing. If the kitty keyboard protocol has
been enabled (and specifically, release event reporting has been
enabled), then we'll emit a 'release' escape sequence. This in itself
is wrong, since the client application never saw the corresponding
press event. But we _also_ reset the viewport. The effect (in this
example), is that it's impossible to scroll up in the scrollback
history.

Note that we don't ignore _any_ release event, only the release event
for the (final) symbol that triggered the shortcut.

This should allow e.g. modifier keys release events to be processed
normally, if released before the shortcut key.

This is somewhat important, since the client application will have
received press events for the modifier keys leading up to the
shortcut (if modifier press/release events have been enabled in the
kitty keyboard protocol - _Report all keys as escape codes_).

Closes #2257
</content>
</entry>
<entry>
<title>input: execute: add missing 'return true' to a couple of switch cases</title>
<updated>2026-01-10T06:35:25Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-01-10T06:35:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e2a989785ab32a39aaa8d49a45b8a94b12a12fa3'/>
<id>urn:sha1:e2a989785ab32a39aaa8d49a45b8a94b12a12fa3</id>
<content type='text'>
Without this, the input handling code won't understand the key/mouse
event was consumed (i.e. triggered a shortcut), and will continue
processing normally (e.g. sending event to the client application).
</content>
</entry>
<entry>
<title>shm: don't bother with xrgb surfaces, always use argb</title>
<updated>2026-01-04T17:59:20Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-01-04T06:57:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b78cc92322dd2ae431dbbb70bc681b4d603d844d'/>
<id>urn:sha1:b78cc92322dd2ae431dbbb70bc681b4d603d844d</id>
<content type='text'>
Before this patch, foot used xrgb surfaces for all fully opaque
surfaces, and only used argb surfaces for the main window when the
user enabled translucency.

However, several compositors have damage-like issues when we switch
between opaque and non-opaque surfaces (for example, when switching
color theme, or when toggling fullscreen).

Since the performance benefit of using non-alpha aware surfaces are
likely minor (if there's any measurable performance difference at
all!), lets workaround these compositor issues by always using argb
surfaces.
</content>
</entry>
<entry>
<title>csi: secondary DA: fix comment; we don't use an XTerm version number</title>
<updated>2025-12-28T10:37:54Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-12-28T10:37:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=42e04c5c8741f739295f7da0b1bb1effda95547f'/>
<id>urn:sha1:42e04c5c8741f739295f7da0b1bb1effda95547f</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ci: python: upgrade pip before installing python packages</title>
<updated>2025-12-26T16:26:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-12-26T16:25:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=53e8fbbdec5779d59341b37e0b630b06ecf6951a'/>
<id>urn:sha1:53e8fbbdec5779d59341b37e0b630b06ecf6951a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ci: combine the codespell and mypy stages</title>
<updated>2025-12-26T16:26:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-12-26T16:23:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=bb6968c2847e99ba89a7597ff5b8a31fb5dd9434'/>
<id>urn:sha1:bb6968c2847e99ba89a7597ff5b8a31fb5dd9434</id>
<content type='text'>
They both need python and a venv, so let's combine them, to avoid
having to install the same things twice.
</content>
</entry>
</feed>
