<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/osc.c, branch sixel-heap-buffer-overflow</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=sixel-heap-buffer-overflow</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=sixel-heap-buffer-overflow'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2026-05-14T14:03:16Z</updated>
<entry>
<title>osc: kitty notifications: increase query reply buffer size</title>
<updated>2026-05-14T14:03:16Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-05-14T10:41:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ab6ffd1344d1d19f4c7275fcb3c1429a11881381'/>
<id>urn:sha1:ab6ffd1344d1d19f4c7275fcb3c1429a11881381</id>
<content type='text'>
When we initially implemented the kitty notification protocol, 128
bytes was enough.

Since then, the protocol has grown, and 128 bytes is no longer enough,
resulting in a crash when you try to query the protocol:

    printf "\e]99;i=123:p=?;\e\\"

Results in

    #0 0x7fe4fad3dcde in __sanitizer_print_stack_trace (/usr/lib/libasan.so.8+0x13dcde) (BuildId: 38f5643355445a477f07ffa9b6a83a55c87415a0)
    #1 0x561ec61454e8 in print_stack_trace ../../debug.c:20
    #2 0x561ec6145550 in fatal_error ../../debug.c:28
    #3 0x561ec61462d0 in xvsnprintf ../../xsnprintf.c:42
    #4 0x561ec614640a in xsnprintf ../../xsnprintf.c:52
    #5 0x561ec6131fe6 in kitty_notification ../../osc.c:765
    #6 0x561ec6139fec in osc_dispatch ../../osc.c:1511
    #7 0x561ec60fcac8 in action_osc_end ../../vt.c:614
    #8 0x561ec60fe6bb in state_osc_string_switch ../../vt.c:924
    #9 0x561ec60ff437 in vt_from_slave ../../vt.c:1115
    #10 0x561ec6078748 in fdm_ptmx ../../terminal.c:297
    #11 0x561ec5ee6ed0 in fdm_poll ../../fdm.c:483
    #12 0x561ec5f344d3 in main ../../main.c:676
    #13 0x7fe4f9e2777d  (/usr/lib/libc.so.6+0x2777d) (BuildId: 674f3ebbcb651fbc7d1189cb300acfd7d007849a)
    #14 0x7fe4f9e278bb in __libc_start_main (/usr/lib/libc.so.6+0x278bb) (BuildId: 674f3ebbcb651fbc7d1189cb300acfd7d007849a)
    #15 0x561ec5e77a14 in _start (/home/daniel/src/foot/bld/debug/foot+0x4b8a14) (BuildId: 9fca511350f3745edd3546ff800a763c1957e673)

Closes #2335
</content>
</entry>
<entry>
<title>osc-52: don't strip any control characters, and don't do newline conversion</title>
<updated>2026-03-22T17:57:49Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2026-03-02T07:11:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=46a9cb8aab3145c8d4083aea485eaf7e2d44bf51'/>
<id>urn:sha1:46a9cb8aab3145c8d4083aea485eaf7e2d44bf51</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>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>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>Fix discarded const qualifiers from string functions</title>
<updated>2025-12-17T03:15:03Z</updated>
<author>
<name>Yaakov Selkowitz</name>
<email>yselkowi@redhat.com</email>
</author>
<published>2025-12-17T03:10:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=15ebc433baabd799252609e28bf79afd892b33a4'/>
<id>urn:sha1:15ebc433baabd799252609e28bf79afd892b33a4</id>
<content type='text'>
This is a new warning in GCC 15 that is being promoted to an error due to
the werror=true in meson.build.
</content>
</entry>
<entry>
<title>osc: color reset: read default color from currently active theme</title>
<updated>2025-07-22T11:30:28Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-07-22T11:30:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fcde74a18150a1722f2be2b7990c2f9b45268854'/>
<id>urn:sha1:fcde74a18150a1722f2be2b7990c2f9b45268854</id>
<content type='text'>
</content>
</entry>
<entry>
<title>osc: 52: clear selection if the payload is the empty string</title>
<updated>2025-06-10T05:12:53Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-06-09T07:12:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=499f019deaf6e7b7e7bb6bbb43b93a7296d9b4fe'/>
<id>urn:sha1:499f019deaf6e7b7e7bb6bbb43b93a7296d9b4fe</id>
<content type='text'>
</content>
</entry>
<entry>
<title>render: refactor to allow setting only selection bg or fg</title>
<updated>2025-05-05T11:02:32Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-05-05T10:43:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=073b637d4535cd0dfe92ca1ce954b552ae9f1a4a'/>
<id>urn:sha1:073b637d4535cd0dfe92ca1ce954b552ae9f1a4a</id>
<content type='text'>
Before this, we only applied custom selection colors, if *both* the
selection bg and fg had been set.

Since the options are already split up into two separate options, and
since it makes sense to at least be able to keep the foreground colors
unchanged (i.e. only setting the selection background), let's allow
only having one of the selection colors set.

Closes #1846
</content>
</entry>
<entry>
<title>osc: restore configured alpha if OSC-11 has no alpha value</title>
<updated>2025-05-02T16:54:03Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-05-02T06:53:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7354b94f737c9f589803b23714e7eddfb2f0fd69'/>
<id>urn:sha1:7354b94f737c9f589803b23714e7eddfb2f0fd69</id>
<content type='text'>
When parsing an OSC-11 without an alpha value (i.e. standard OSC-11,
not rxvt's extended variant), restore the alpha value from the
configuration, rather than keeping whatever the current alpha is.
</content>
</entry>
<entry>
<title>config: move cursor.color to colors.cursor</title>
<updated>2025-04-26T08:46:39Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-04-20T05:16:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=624c383a1f45a4fbd5ebf687613c509e6c22d909'/>
<id>urn:sha1:624c383a1f45a4fbd5ebf687613c509e6c22d909</id>
<content type='text'>
</content>
</entry>
<entry>
<title>osc: text-size: disable optimization</title>
<updated>2025-02-06T13:02:38Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-02-03T14:30:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0f93766614bde055ce61e1b7ffc8f6b5aeef91d3'/>
<id>urn:sha1:0f93766614bde055ce61e1b7ffc8f6b5aeef91d3</id>
<content type='text'>
The optimization prevents the forced-width to be set on the new
combining character, causing issues when followed by more zero-width
codepoints.
</content>
</entry>
<entry>
<title>osc: text-sizing: implement w=0, plus optimize single-codepoint cases</title>
<updated>2025-02-06T06:45:58Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-01-26T06:36:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1260004330359619113aac3cb3ea1a7fe2fddb2b'/>
<id>urn:sha1:1260004330359619113aac3cb3ea1a7fe2fddb2b</id>
<content type='text'>
If there's a single codepoint in the text portion of the OSC sequence,
and its calculated width matches the forced width, print it directly
to the grid instead of emitting a combining character.

When w=0, we split up the text string "as we normally would". Since we
don't support any other text-sizing parameters, this means simply
printing each codepoint to the grid.
</content>
</entry>
<entry>
<title>term+vt: refactor: move "utf8" char processing to term_process_and_print_non_ascii()</title>
<updated>2025-02-06T06:45:20Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-01-26T06:33:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d3f692990ef66f550bb3a0ade2e84107cfbeca47'/>
<id>urn:sha1:d3f692990ef66f550bb3a0ade2e84107cfbeca47</id>
<content type='text'>
This function "prints" any non-ascii character (i.e. any character
that ends up in the action_utf8_print() function in vt.c) to the
grid. This includes grapheme cluster processing etc.

action_utf8_print() now simply calls this function.

This allows us to re-use the same functionality from other
places (like the text-sizing protocol).
</content>
</entry>
<entry>
<title>osc: wip: kitty text size protocol</title>
<updated>2025-02-06T06:42:38Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-01-25T13:09:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=7a8d2b5e012636def9545075e01cdf9a6f309355'/>
<id>urn:sha1:7a8d2b5e012636def9545075e01cdf9a6f309355</id>
<content type='text'>
This brings initial support for the new kitty text-sizing
protocol. Note hat only the width-parameter ('w') is supported. That
is, no font scaling, and no multi-line cells.

For now, only explicit widths are supported. That is, w=0 does not yet
work.

There are a couple of changes to the renderer, to handle e.g.

    OSC 66 ; w=6 ; foobar ST

There are two ways this can get rendered, depending on whether
grapheme shaping has been enabled. We either shape it, and get an
array of glyphs back that we render. Or, we rasterize each codepoint
ourselves, and render each resulting glyph.

The two cases ends up in two different renderer loops, that worked
somewhat different. In particular, the first case has probably never
been tested/used at all...

With this patch, both are changed, and now uses some heuristic to
differentiate between multi-cell text strings (like in the example
above), or single-cell combining characters. The difference is mainly
in which offset to use for the secondary glyphs.

In a multi-cell string, each glyph is mapped to its own cell, while in
the combining case, we try to map all glyphs to the same cell.
</content>
</entry>
<entry>
<title>osc: ignore 'OSC 176 ?' - report app ID</title>
<updated>2025-01-07T12:01:21Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-01-07T12:00:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=06a32d553e8d2613e3b4582199a317219f5cfc8b'/>
<id>urn:sha1:06a32d553e8d2613e3b4582199a317219f5cfc8b</id>
<content type='text'>
It's not widely used (don't know _any_ application that uses it), and
can be used to trick users to run unwanted commands.
</content>
</entry>
<entry>
<title>osc: disable debug logging</title>
<updated>2025-01-02T08:12:11Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2025-01-02T08:12:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=9f5be55d1cdf2a25fa3bb47247420cc658e646f8'/>
<id>urn:sha1:9f5be55d1cdf2a25fa3bb47247420cc658e646f8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>osc: add option to disable OSC-52, partially or fully</title>
<updated>2024-12-22T06:16:12Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-12-21T05:52:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e38ec79be15fe355bf50670bc9066210ae0ed211'/>
<id>urn:sha1:e38ec79be15fe355bf50670bc9066210ae0ed211</id>
<content type='text'>
Closes #1867
</content>
</entry>
<entry>
<title>osc: 9: ignore ConEmu/Windows Terminal sequences</title>
<updated>2024-11-02T07:33:03Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2024-11-02T07:10:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=f3e443ea4709f94d5a5865d567f5e3647c8cf870'/>
<id>urn:sha1:f3e443ea4709f94d5a5865d567f5e3647c8cf870</id>
<content type='text'>
OSC-9 sequences starting with "&lt;number&gt;;" are now ignored, as they are
ConEmu sequences, and not iTerm notifications.
</content>
</entry>
<entry>
<title>osc: notify: fix crash with no message</title>
<updated>2024-10-31T06:03:04Z</updated>
<author>
<name>Jack Wilsdon</name>
<email>jack@wilsdon.me</email>
</author>
<published>2024-10-28T17:52:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=689549bb1f85f2ff7e1710d527dc2ead4cb3bb5b'/>
<id>urn:sha1:689549bb1f85f2ff7e1710d527dc2ead4cb3bb5b</id>
<content type='text'>
Closes #1866
</content>
</entry>
</feed>
