<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git, branch 1.13.0</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.13.0</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.13.0'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2022-08-07T07:32:02Z</updated>
<entry>
<title>meson: bump version to 1.13.0</title>
<updated>2022-08-07T07:32:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-08-07T07:32:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e0465d3a7a0b8d6962462a505f2f8b32c2ee74bc'/>
<id>urn:sha1:e0465d3a7a0b8d6962462a505f2f8b32c2ee74bc</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: prepare for 1.13.0</title>
<updated>2022-08-07T07:31:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-08-07T07:31:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e3eefdacde0182aa2c5e56cf450e3abac094e852'/>
<id>urn:sha1:e3eefdacde0182aa2c5e56cf450e3abac094e852</id>
<content type='text'>
</content>
</entry>
<entry>
<title>grid: get rid of empty row at the bottom after reflowing</title>
<updated>2022-08-05T16:26:37Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-08-05T16:26:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=aaf5894ad9272698cfafeb8e299b925fb9554417'/>
<id>urn:sha1:aaf5894ad9272698cfafeb8e299b925fb9554417</id>
<content type='text'>
When the window is resized and we reflow the text, we ended up
inserting an empty row at the bottom.

This happens whenever the actual last row has a hard linebreak (which
almost always is the case); we then end the reflow with a line break,
causing an extra, empty, row to be allocated and inserted.

This patch fixes this by detecting when:

1) the last row is empty
2) the next to last row has a hard line break

In this case, we roll back the last line break, by adjusting the new
offset we just calculated, and free:ing the empty row.

TODO: it would be nice if we could detect this in the reflow loop
instead, and avoid doing the last line break all together. I haven’t
yet been able to find a way to do this correctly.

Closes #1108
</content>
</entry>
<entry>
<title>Add support for xdg_toplevel.wm_capabilities</title>
<updated>2022-08-04T12:23:03Z</updated>
<author>
<name>Simon Ser</name>
<email>contact@emersion.fr</email>
</author>
<published>2022-05-06T18:05:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=129e1a9b8e23007026d19c970941ccbc8ee2f0ca'/>
<id>urn:sha1:129e1a9b8e23007026d19c970941ccbc8ee2f0ca</id>
<content type='text'>
See https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/122
</content>
</entry>
<entry>
<title>Add no-op xdg_toplevel.configure_bounds handler</title>
<updated>2022-08-03T11:50:13Z</updated>
<author>
<name>Simon Ser</name>
<email>contact@emersion.fr</email>
</author>
<published>2022-05-06T18:03:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2f68b421bfc444c2a713d7418850b67a7e34810f'/>
<id>urn:sha1:2f68b421bfc444c2a713d7418850b67a7e34810f</id>
<content type='text'>
Next commit uses v5.
</content>
</entry>
<entry>
<title>server: Use "normal" socket activation, not inetd</title>
<updated>2022-07-30T13:13:56Z</updated>
<author>
<name>Max Gautier</name>
<email>mg@max.gautier.name</email>
</author>
<published>2022-07-29T18:12:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ffdac61e2a95aa31a9c69eb5152a7dd79346ddf0'/>
<id>urn:sha1:ffdac61e2a95aa31a9c69eb5152a7dd79346ddf0</id>
<content type='text'>
Systemd, when doing socket activation, pass file descriptors in a
non-stable order when there is multiples ones.

But we only use one, so we don't need to identify it, and the file
descriptors always start at 3.
So use 3 for the systemd service.

Source : sd_listen_fds (systemd man pages)

We also need to unset variables systemd pass to socket activated
process, since we don't need them and sub-process (footclient and
theirs forks) could be confused by those.

Closes #1107
</content>
</entry>
<entry>
<title>config: reset errno before calling getline() again</title>
<updated>2022-07-29T19:27:27Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-29T19:27:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c0a7c7bf0d4412fd9436962704cb26f9596e529f'/>
<id>urn:sha1:c0a7c7bf0d4412fd9436962704cb26f9596e529f</id>
<content type='text'>
Related to #1107
</content>
</entry>
<entry>
<title>unicode-mode: ‘q’ aborts Unicode input mode</title>
<updated>2022-07-29T09:56:41Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-29T09:56:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0cbd99710b9d9ff5116c39e1d989556a6d7c27a8'/>
<id>urn:sha1:0cbd99710b9d9ff5116c39e1d989556a6d7c27a8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>unicode-input: move input (key press) handling to unicode_mode_input()</title>
<updated>2022-07-29T07:26:42Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T17:34:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=001f96c4e3ae26a9b2807b549c782a094a36ff3a'/>
<id>urn:sha1:001f96c4e3ae26a9b2807b549c782a094a36ff3a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: add new Unicode input mode</title>
<updated>2022-07-29T07:26:31Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T16:09:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8967dd9cfe51276d63ef8ff64e8fc76f80a6fa3d'/>
<id>urn:sha1:8967dd9cfe51276d63ef8ff64e8fc76f80a6fa3d</id>
<content type='text'>
This mode is activated through the new key-bindings.unicode-input and
search-bindings.unicode-input key bindings.

When active, the user can “build” a Unicode codepoint by typing its
hexadecimal value.

Note that there’s no visual feedback in this mode. This is
intentional. This mode is intended to be a fallback for users that
don’t use an IME.

Closes #1116
</content>
</entry>
<entry>
<title>selection: rework how we update a selection</title>
<updated>2022-07-28T19:06:58Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T16:45:25Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=fa2d9f86996467ba33cc381f810ea966a4323381'/>
<id>urn:sha1:fa2d9f86996467ba33cc381f810ea966a4323381</id>
<content type='text'>
Before this patch, each selection update would result in grid covered
by the selection being walked *three* times. First to “premark” the
area that *will* be selected after the update, then again to unmark
the previous selection (excluding the cells that were premarked - but
the cells are still iterated), and then one more time to finalize the
selection state in the grid.

Furthermore, each time a frame is rendered, the entire selection were
iterated again, to ensure all the cells have their ‘selected’ bit
set.

This quickly gets *very* slow.

This patch takes a completely different approach. Instead of looking
at the selection as a range of cells to iterate, we view it as an
area, or region. Thus, on each update, we have to regions: the region
representing the previous selection, and the region representing the
to-be selection.

By diffing these two regions, we get two new regions: one that
represents the cells that were selected, but aren’t any more, and one
that represents the cells that previously were not selected, but now
will be.

We implement the regions using pixman regions. By subtracting the
current selection from the previous selection, we get the region
representing the cells that are no longer selected, and that should be
unmarked.

By subtracting the previous selection from the current, we get the
region representing the cells that was added to the selection in this
update, and that should be marked.

selection_dirty_cells() is rewritten in a similar manner. We create
pixman regions for the selection, and the current scrollback view. The
intersection represents the (selected) cells that are visible. These
need to iterated and marked as being selected.

Closes #1114
</content>
</entry>
<entry>
<title>selection: extend: use scrollback relative coordinates</title>
<updated>2022-07-28T19:06:58Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T16:32:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b8506bbea049548310552e210e9cb363195fe74b'/>
<id>urn:sha1:b8506bbea049548310552e210e9cb363195fe74b</id>
<content type='text'>
When extending a selection, we determine *how* to extend it (which
endpoint to move, and whether to grow or shrink the selection) by
comparing the extension point with the old start and end coordinates.

For this to work correctly, we need to use scrollback relative
coordinates.

This fixes an issue where extending a very large selection (covering
many pages) sometimes shrunk the selection instead of growing it, or
just misbehaving in general.
</content>
</entry>
<entry>
<title>selection: foreach_selected_*(): refactor: use grid_row_abs_to_sb()</title>
<updated>2022-07-28T19:06:58Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T16:31:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6ebf55572e765394e90c96b5fec0e2c55b3b434e'/>
<id>urn:sha1:6ebf55572e765394e90c96b5fec0e2c55b3b434e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>selection: selection_on_rows(): use scrollback relative coords</title>
<updated>2022-07-28T19:06:57Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T16:27:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=a05eaf28bdeea793829bddb6cc99220b1adb1d6f'/>
<id>urn:sha1:a05eaf28bdeea793829bddb6cc99220b1adb1d6f</id>
<content type='text'>
When checking if the current selection intersects with the
region (passed as parameter to the function), use scrollback relative
coordinates.

This fixes an issue where selections crossing the scrollback
wrap-around being misdetected, resulting in either the selection being
canceled while scrolling, even though it wasn’t scrolled out, or the
selection _not_ being canceled, when it _was_ scrolled out.
</content>
</entry>
<entry>
<title>search: find_next(): handle trailing SPACER cells</title>
<updated>2022-07-28T19:05:06Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T16:56:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=632c4839cdb1c673bfb3903e1d43802bfdcbf03f'/>
<id>urn:sha1:632c4839cdb1c673bfb3903e1d43802bfdcbf03f</id>
<content type='text'>
Make sure to increment match_end_col to account for trailing SPACER
cells after a match.

This fixes an issue where search matches weren’t highlighted correctly
when the match *ends* with a double-width character.
</content>
</entry>
<entry>
<title>config: add colors.search-box-{no-,}match</title>
<updated>2022-07-28T17:02:56Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-27T17:14:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d79a3b9350ba864464229a1c188e2f696fac5a26'/>
<id>urn:sha1:d79a3b9350ba864464229a1c188e2f696fac5a26</id>
<content type='text'>
Closes #1112
</content>
</entry>
<entry>
<title>test: config: test colors.{jump-labels,scrollback-indicator}</title>
<updated>2022-07-28T17:02:55Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-27T17:13:39Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=4873004c379f9f06babd65ffc65ba4f99fa62906'/>
<id>urn:sha1:4873004c379f9f06babd65ffc65ba4f99fa62906</id>
<content type='text'>
</content>
</entry>
<entry>
<title>input: kitty: always treat composed characters as ‘printable’</title>
<updated>2022-07-28T17:02:25Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-26T16:44:29Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=801970aa332da5786f91d2f9410d4ed9f440c6ec'/>
<id>urn:sha1:801970aa332da5786f91d2f9410d4ed9f440c6ec</id>
<content type='text'>
Certain dead key combinations results different escape sequences in
foot, compared to kitty, when the kitty keyboard protocol is used.

        if (composed &amp;&amp; is_text)
            key = utf32;
        else {
            key = xkb_keysym_to_utf32(sym_to_use);
            if (key == 0)
                return false;

            /* The *shifted* key. May be the same as the unshifted
             * key - if so, this is filtered out below, when
             * emitting the CSI */
            alternate = xkb_keysym_to_utf32(sym);
        }

If is_text=false, we’ll fall through to the non-composed
logic. is_text is set to true if the character is printable *and*
there aren’t any non-consumed modifiers enabled.

shift+space is one example where shift is *not* consumed (typically -
may be layouts where it is).

As a result, pressing ", followed by shift+space with the
international english keyboard layout (where " is a dead key) results
in different sequences in foot and kitty.

This patch fixes this by always treating composed characters as
printable.

Closes #1120
</content>
</entry>
<entry>
<title>keymap: change alt+escape to emit \E\E instead of a CSI 27 sequence</title>
<updated>2022-07-28T17:02:05Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-26T16:19:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=4abf46955f259ed392c5c7fbfbb931cbc7cc2b8e'/>
<id>urn:sha1:4abf46955f259ed392c5c7fbfbb931cbc7cc2b8e</id>
<content type='text'>
Closes #1105
</content>
</entry>
<entry>
<title>render: it’s unlikely() the current cell is where the cursor is</title>
<updated>2022-07-28T16:55:34Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-28T16:55:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=24c2d568042c6fb0533071aaf72b64405ca2c324'/>
<id>urn:sha1:24c2d568042c6fb0533071aaf72b64405ca2c324</id>
<content type='text'>
</content>
</entry>
</feed>
