https://codeberg.org/markstos 2026-03-31T05:44:40+02:00 2026-03-24T18:25:25+01:00 114281781: https://codeberg.org/dnkl/fuzzel/issues/750#issuecomment-12032817 Crash in nsvg__initPaint <p dir="auto">Thanks for the report with a backtrace, <a href="/YaLTeR" class="mention" rel="nofollow">@YaLTeR</a>. We&#39;ll take a look.</p>

Crash in nsvg__initPaint <p dir="auto">Thanks for the report with a backtrace, <a href="/YaLTeR" class="mention" rel="nofollow">@YaLTeR</a>. We&#39;ll take a look.</p>

markstos [email protected] 2026-03-23T20:06:16+01:00 113933100: https://codeberg.org/dnkl/fuzzel/issues/749#issuecomment-11999520 Emulate `ANSI` video-revert, provide `selection-match-background` <p dir="auto">I support this. Seems like a nice accessibility feature. Also, <code>fzf</code> supports it.</p>

Emulate `ANSI` video-revert, provide `selection-match-background` <p dir="auto">I support this. Seems like a nice accessibility feature. Also, <code>fzf</code> supports it.</p>

markstos [email protected] 2026-03-23T20:02:46+01:00 113931870: https://codeberg.org/dnkl/fuzzel/issues/744#issuecomment-11999379 Accept ; comments in the INI config (or change extension to .conf) <p dir="auto">I agree the current state isn&#39;t ideal, but I don&#39;t love the options:</p>

Accept ; comments in the INI config (or change extension to .conf) <p dir="auto">I agree the current state isn&#39;t ideal, but I don&#39;t love the options:</p>

markstos [email protected] 2026-03-14T15:01:45+01:00 110070814: https://codeberg.org/dnkl/fuzzel/pulls/747 747#refactor: apply DRY principle in a couple places rendering to centralize code, improve readability#

747#refactor: apply DRY principle in a couple places rendering to centralize code, improve readability#

markstos [email protected] 2026-03-14T15:00:19+01:00 110070439: https://codeberg.org/dnkl/fuzzel/compare/02f73460fab1b6f28885035bc39d12689ec99b9a...7d01cf39972a26f277f3183a7adb6874398b491f <a href="https://codeberg.org/dnkl/fuzzel/commit/7d01cf39972a26f277f3183a7adb6874398b491f" rel="nofollow">7d01cf39972a26f277f3183a7adb6874398b491f</a> refactor: DRY repetive code to calculate row_bg_x() <a href="https://codeberg.org/dnkl/fuzzel/commit/ce2b1db8b697b13323b2cc944d00ae02efbe0b7a" rel="nofollow">ce2b1db8b697b13323b2cc944d00ae02efbe0b7a</a> refactor: call first_row_y() instead of re-implementing

<a href="https://codeberg.org/dnkl/fuzzel/commit/7d01cf39972a26f277f3183a7adb6874398b491f">7d01cf39972a26f277f3183a7adb6874398b491f</a> refactor: DRY repetive code to calculate row_bg_x() <a href="https://codeberg.org/dnkl/fuzzel/commit/ce2b1db8b697b13323b2cc944d00ae02efbe0b7a">ce2b1db8b697b13323b2cc944d00ae02efbe0b7a</a> refactor: call first_row_y() instead of re-implementing

markstos [email protected] 2026-03-14T15:00:18+01:00 110070418: https://codeberg.org/dnkl/fuzzel/src/branch/dry-refactors markstos [email protected] 2026-03-14T04:26:17+01:00 109879354: https://codeberg.org/dnkl/fuzzel/issues/735#issuecomment-11621371 Option to render `message` at the bottom in &#34;footer&#34; area <p dir="auto">I can see the case for this. Positioned at the top, the <code>--mesg</code> serves more like an intro or title, while positioned at the bottom, it serves more like a hint. So it&#39;s not just a design detail, it&#39;s a different functional purpose.</p> <p dir="auto">If we added this, I could see someone quickly following up and asking for both, in which case we should implement <code>--footer-mesg</code> upfront instead. Then if we add this, people will want a new color configuration to adjust the color of this text in particular. For example, as a hint in the footer, perhaps the contrast would be lower.</p> <p dir="auto">I&#39;m 100% sure about adding this. Fuzzel does not strive to have all the layout options of some other options that are fully themeable with CSS and so forth, but it&#39;s not exactly clear where the boundary is to stop accepting &#34;just one more&#34; design customization option.</p> <p dir="auto">To more persuasive , more screenshots / mockups could help, either of a faked Fuzzel or from other launchers that have a feature like this.</p>

Option to render `message` at the bottom in "footer" area <p dir="auto">I can see the case for this. Positioned at the top, the <code>--mesg</code> serves more like an intro or title, while positioned at the bottom, it serves more like a hint. So it&#39;s not just a design detail, it&#39;s a different functional purpose.</p> <p dir="auto">If we added this, I could see someone quickly following up and asking for both, in which case we should implement <code>--footer-mesg</code> upfront instead. Then if we add this, people will want a new color configuration to adjust the color of this text in particular. For example, as a hint in the footer, perhaps the contrast would be lower.</p> <p dir="auto">I&#39;m 100% sure about adding this. Fuzzel does not strive to have all the layout options of some other options that are fully themeable with CSS and so forth, but it&#39;s not exactly clear where the boundary is to stop accepting &#34;just one more&#34; design customization option.</p> <p dir="auto">To more persuasive , more screenshots / mockups could help, either of a faked Fuzzel or from other launchers that have a feature like this.</p>

markstos [email protected] 2026-03-14T04:16:30+01:00 109876363: https://codeberg.org/dnkl/fuzzel/pulls/743#issuecomment-11621266 ✨ wayland: implement text-input-unstable-v3 for IME support <p dir="auto">I reviewed this as well.</p>

✨ wayland: implement text-input-unstable-v3 for IME support <p dir="auto">I reviewed this as well.</p>

markstos [email protected] 2026-03-14T04:16:27+01:00 109876312: https://codeberg.org/dnkl/fuzzel/commit/d14699d217e8b2da2228698b4f63862d5bfb962c <a href="https://codeberg.org/dnkl/fuzzel/commit/d14699d217e8b2da2228698b4f63862d5bfb962c" rel="nofollow">d14699d217e8b2da2228698b4f63862d5bfb962c</a> fixup: add docs for IME

<a href="https://codeberg.org/dnkl/fuzzel/commit/d14699d217e8b2da2228698b4f63862d5bfb962c">d14699d217e8b2da2228698b4f63862d5bfb962c</a> fixup: add docs for IME

markstos [email protected] 2026-03-14T03:24:44+01:00 109865308: https://codeberg.org/dnkl/fuzzel/issues/739#issuecomment-11620474 Fuzzel crashes in resvg_render when searching things (resvg backend) (solved) <p dir="auto">There&#39;s a PR open to handle the image-size-ratio=0 case, which might prevent the crash. Trying to render a 0x0 image didn&#39;t make sense in any case.</p>

Fuzzel crashes in resvg_render when searching things (resvg backend) (solved) <p dir="auto">There&#39;s a PR open to handle the image-size-ratio=0 case, which might prevent the crash. Trying to render a 0x0 image didn&#39;t make sense in any case.</p>

markstos [email protected] 2026-03-14T03:21:42+01:00 109864696: https://codeberg.org/dnkl/fuzzel/pulls/746 <p dir="auto"><span class="issue-keyword">fixes</span> <a href="/dnkl/fuzzel/issues/739" class="ref-issue" rel="nofollow">#739</a></p> <p dir="auto">Treat it like 1 and disable the feature.</p>

746#render: handle non-sensical image-size-ratio=0 case#

markstos [email protected] 2026-03-14T03:21:19+01:00 109864522: https://codeberg.org/dnkl/fuzzel/src/branch/issue-739-zero-size-image markstos [email protected] 2026-03-14T03:21:19+01:00 109864519: https://codeberg.org/dnkl/fuzzel/commit/8a9af50676280aa236280e00a57dd8b6928dbae7 <a href="https://codeberg.org/dnkl/fuzzel/commit/8a9af50676280aa236280e00a57dd8b6928dbae7" rel="nofollow">8a9af50676280aa236280e00a57dd8b6928dbae7</a> render: handle non-sensical image-size-ratio=0 case

<a href="https://codeberg.org/dnkl/fuzzel/commit/8a9af50676280aa236280e00a57dd8b6928dbae7">8a9af50676280aa236280e00a57dd8b6928dbae7</a> render: handle non-sensical image-size-ratio=0 case

markstos [email protected] 2026-03-14T03:03:10+01:00 109861150: https://codeberg.org/dnkl/fuzzel/issues/744#issuecomment-11620234 Accept ; comments in the INI config (or change extension to .conf) <p dir="auto">Although INI is not a standardized format, popular parsers to seem to all support the <code>;</code>. With the <code>.ini</code> extension, it&#39;s reasonable to assume that Fuzzel would, too. The <code>man fuzzel.ini</code> docs could be clearer on this point as well. It does not seem to document what the comment character is, only describing the format as the &#34;standard unix configuration format&#34;. I&#39;m sure I&#39;d say there&#39;s a standard Unix config file format, but there are still a lot of config files under <code>/etc/</code> that use simple key=value format with <code>#</code> as the comment.</p> <p dir="auto">Against adding this: Fuzzel has been around for seven years and this is the first report I can recall of someone being confused about this. Probably a lot of people start with the default config file and modify it, or start with some example and follow the example. Also, <code>#</code> is definitely far more common a comment delimiter in Unix config files.</p> <p dir="auto">So, I&#39;m on the fence about this. At a minimum, the docs could be improved to clarify more comments in the file.</p> <p dir="auto">One of the Unix philosophies is to &#34;be liberal in what you accept, strict in what you produce&#34;. Following that, it&#39;s reasonable to support <code>;</code> in a <code>.ini</code> file.</p> <p dir="auto">But given the general lack of interest, I&#39;m also inclined to keep the software a bit simpler. To that end, we can leave this open and see if anyone else comes along to express interest.</p>

Accept ; comments in the INI config (or change extension to .conf) <p dir="auto">Although INI is not a standardized format, popular parsers to seem to all support the <code>;</code>. With the <code>.ini</code> extension, it&#39;s reasonable to assume that Fuzzel would, too. The <code>man fuzzel.ini</code> docs could be clearer on this point as well. It does not seem to document what the comment character is, only describing the format as the &#34;standard unix configuration format&#34;. I&#39;m sure I&#39;d say there&#39;s a standard Unix config file format, but there are still a lot of config files under <code>/etc/</code> that use simple key=value format with <code>#</code> as the comment.</p> <p dir="auto">Against adding this: Fuzzel has been around for seven years and this is the first report I can recall of someone being confused about this. Probably a lot of people start with the default config file and modify it, or start with some example and follow the example. Also, <code>#</code> is definitely far more common a comment delimiter in Unix config files.</p> <p dir="auto">So, I&#39;m on the fence about this. At a minimum, the docs could be improved to clarify more comments in the file.</p> <p dir="auto">One of the Unix philosophies is to &#34;be liberal in what you accept, strict in what you produce&#34;. Following that, it&#39;s reasonable to support <code>;</code> in a <code>.ini</code> file.</p> <p dir="auto">But given the general lack of interest, I&#39;m also inclined to keep the software a bit simpler. To that end, we can leave this open and see if anyone else comes along to express interest.</p>

markstos [email protected] 2026-03-09T15:23:35+01:00 107796652: https://codeberg.org/dnkl/fuzzel/pulls/743#issuecomment-11421421 ✨ wayland: implement text-input-unstable-v3 for IME support <p dir="auto">Thanks. I&#39;m out of time this morning, but will debug more when I can.</p>

✨ wayland: implement text-input-unstable-v3 for IME support <p dir="auto">Thanks. I&#39;m out of time this morning, but will debug more when I can.</p>

markstos [email protected] 2026-03-09T15:15:58+01:00 107793364: https://codeberg.org/dnkl/fuzzel/pulls/743#issuecomment-11421193 ✨ wayland: implement text-input-unstable-v3 for IME support <p dir="auto"><a href="/DreamMaoMao" class="mention" rel="nofollow">@DreamMaoMao</a> Thanks for the rapid feedback. I&#39;ve confirmed this was a bug on Fuzzel&#39;s end and pushed a possible fix for you to try.</p>

✨ wayland: implement text-input-unstable-v3 for IME support <p dir="auto"><a href="/DreamMaoMao" class="mention" rel="nofollow">@DreamMaoMao</a> Thanks for the rapid feedback. I&#39;ve confirmed this was a bug on Fuzzel&#39;s end and pushed a possible fix for you to try.</p>

markstos [email protected] 2026-03-09T15:15:03+01:00 107793028: https://codeberg.org/dnkl/fuzzel/commit/1d5c674a84245e7c9171e735e6e77d27d47b8340 <a href="https://codeberg.org/dnkl/fuzzel/commit/1d5c674a84245e7c9171e735e6e77d27d47b8340" rel="nofollow">1d5c674a84245e7c9171e735e6e77d27d47b8340</a> fixup: disable text-input before destroying it on exit

<a href="https://codeberg.org/dnkl/fuzzel/commit/1d5c674a84245e7c9171e735e6e77d27d47b8340">1d5c674a84245e7c9171e735e6e77d27d47b8340</a> fixup: disable text-input before destroying it on exit

markstos [email protected] 2026-03-09T14:33:48+01:00 107774962: https://codeberg.org/dnkl/fuzzel/issues/615#issuecomment-11420053 Add IME (e.g. fcitx5) support <p dir="auto">There&#39;s a PR for you to test now, based on the foot and rofi implementations. In basic testing it worked for me, but I&#39;m not a regular IME user, so this needs more testing.</p>

Add IME (e.g. fcitx5) support <p dir="auto">There&#39;s a PR for you to test now, based on the foot and rofi implementations. In basic testing it worked for me, but I&#39;m not a regular IME user, so this needs more testing.</p>

markstos [email protected] 2026-03-09T14:32:32+01:00 107774401: https://codeberg.org/dnkl/fuzzel/pulls/743 <p dir="auto"><span class="issue-keyword">fixes</span> <a href="/dnkl/fuzzel/issues/615" class="ref-issue" rel="nofollow">#615</a></p> <p dir="auto">Adds IME input method support (fcitx5, ibus, etc.) using the<br/> text-input-unstable-v3 Wayland protocol, following the approach<br/> used by foot and rofi.</p>

743#✨ wayland: implement text-input-unstable-v3 for IME support#

markstos [email protected] 2026-03-09T14:31:43+01:00 107774026: https://codeberg.org/dnkl/fuzzel/src/branch/issue-615-ime markstos [email protected] 2026-03-09T14:31:43+01:00 107774011: https://codeberg.org/dnkl/fuzzel/commit/1cbe051bca8f6681dd70c8e64194b5f356022b55 <a href="https://codeberg.org/dnkl/fuzzel/commit/1cbe051bca8f6681dd70c8e64194b5f356022b55" rel="nofollow">1cbe051bca8f6681dd70c8e64194b5f356022b55</a> wayland: implement text-input-unstable-v3 for IME support

<a href="https://codeberg.org/dnkl/fuzzel/commit/1cbe051bca8f6681dd70c8e64194b5f356022b55">1cbe051bca8f6681dd70c8e64194b5f356022b55</a> wayland: implement text-input-unstable-v3 for IME support

markstos [email protected] 2026-03-09T13:11:12+01:00 107747818: https://codeberg.org/dnkl/fuzzel/commit/9e42e3e770677553a6d37e1f450dad13be97bfa1 <a href="https://codeberg.org/dnkl/fuzzel/commit/9e42e3e770677553a6d37e1f450dad13be97bfa1" rel="nofollow">9e42e3e770677553a6d37e1f450dad13be97bfa1</a> docs: fuzzel.ini add auto-select default

<a href="https://codeberg.org/dnkl/fuzzel/commit/9e42e3e770677553a6d37e1f450dad13be97bfa1">9e42e3e770677553a6d37e1f450dad13be97bfa1</a> docs: fuzzel.ini add auto-select default

markstos [email protected] 2026-03-09T13:11:11+01:00 107747815: https://codeberg.org/dnkl/fuzzel/pulls/741 docs: fuzzel.ini add auto-select default

docs: fuzzel.ini add auto-select default

markstos [email protected] 2026-03-09T13:10:42+01:00 107747242: https://codeberg.org/dnkl/fuzzel/pulls/741#issuecomment-11400031 docs: fuzzel.ini add auto-select default <h2 id="user-content-qa-log" dir="auto">QA Log</h2>

docs: fuzzel.ini add auto-select default <h2 id="user-content-qa-log" dir="auto">QA Log</h2>

markstos [email protected] 2026-03-09T13:06:48+01:00 107746360: https://codeberg.org/dnkl/fuzzel/issues/742#issuecomment-11399908 terminal apps just do not open

terminal apps just do not open

markstos [email protected] 2026-03-09T13:06:46+01:00 107746348: https://codeberg.org/dnkl/fuzzel/issues/742#issuecomment-11399905 terminal apps just do not open <p dir="auto">According to <code>man fuzzel</code>, searching for &#34;terminal&#34;, it&#39;s documented that a default terminal is not set, and your config shows that you haven&#39;t set one either.</p>

terminal apps just do not open <p dir="auto">According to <code>man fuzzel</code>, searching for &#34;terminal&#34;, it&#39;s documented that a default terminal is not set, and your config shows that you haven&#39;t set one either.</p>

markstos [email protected] 2026-03-08T02:07:40+01:00 107241796: https://codeberg.org/dnkl/fuzzel/issues/726#issuecomment-11356324 Configurable additional application icon contexts <p dir="auto">I ran into this today when I wanted to use an icon that wasn&#39;t an app icon. I found there&#39;s already a workaround for app launcher mode in that providing the full path to any icon works.</p>

Configurable additional application icon contexts <p dir="auto">I ran into this today when I wanted to use an icon that wasn&#39;t an app icon. I found there&#39;s already a workaround for app launcher mode in that providing the full path to any icon works.</p>

markstos [email protected] 2026-03-03T16:39:39+01:00 105581609: https://codeberg.org/dnkl/fuzzel/commit/9fce807b5ed2a5443e19e1e7bb604b7229a37bfb <a href="https://codeberg.org/dnkl/fuzzel/commit/9fce807b5ed2a5443e19e1e7bb604b7229a37bfb" rel="nofollow">9fce807b5ed2a5443e19e1e7bb604b7229a37bfb</a> wayland: narrow use of transparent-first-frame hack

<a href="https://codeberg.org/dnkl/fuzzel/commit/9fce807b5ed2a5443e19e1e7bb604b7229a37bfb">9fce807b5ed2a5443e19e1e7bb604b7229a37bfb</a> wayland: narrow use of transparent-first-frame hack

markstos [email protected] 2026-03-03T16:39:26+01:00 105581306: https://codeberg.org/dnkl/fuzzel/pulls/738#issuecomment-11165129 wayland: narrow use of transparent-first-frame hack <p dir="auto">Thanks for the catch. On further review, it was not necessary, as it handled just earlier by the wl_display_roundtrip() call. Amending to review.</p>

wayland: narrow use of transparent-first-frame hack <p dir="auto">Thanks for the catch. On further review, it was not necessary, as it handled just earlier by the wl_display_roundtrip() call. Amending to review.</p>

markstos [email protected] 2026-02-25T19:22:29+01:00 103204505: https://codeberg.org/dnkl/fuzzel/issues/739#issuecomment-10990724 Fuzzel crashes in resvg_render when searching things (resvg backend) (solved) <p dir="auto">I see that&#39;s with the <code>resvg</code> SVG backend. See the README about building with a different SVG backend, or you could file a bug with the <code>resvg</code> project. The NixOS packagers have an option to choose a different SVG backend if this one is problematic.</p> <p dir="auto"><code>resvg</code> has some advantages, so hopefully this bug can be worked out.</p>

Fuzzel crashes in resvg_render when searching things (resvg backend) (solved) <p dir="auto">I see that&#39;s with the <code>resvg</code> SVG backend. See the README about building with a different SVG backend, or you could file a bug with the <code>resvg</code> project. The NixOS packagers have an option to choose a different SVG backend if this one is problematic.</p> <p dir="auto"><code>resvg</code> has some advantages, so hopefully this bug can be worked out.</p>

markstos [email protected]