<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/CHANGELOG.md, 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:31:56Z</updated>
<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>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>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: 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>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>csi: clamp color index for ‘CSI 38/48 ; 5 ; idx m’ sequences</title>
<updated>2022-07-22T08:44:33Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-07-22T08:44:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=87e4004960265494fcab21c71fff48b4f8b0af33'/>
<id>urn:sha1:87e4004960265494fcab21c71fff48b4f8b0af33</id>
<content type='text'>
Indexed color values are stored in the cell attributes as color
indices (into the 256-color table). However, the index from the CSI
was not validated in any way, meaning you can do something like this:

  echo -e ‘\e[38:5:1024m CRASH \e[m’

and foot will crash on an out-of-bounds access.

Fix by clamping the color index.

Closes #1111
</content>
</entry>
<entry>
<title>input: don’t ignore keyboard enter/leave events when there’s no keymap</title>
<updated>2022-06-28T18:57:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-06-28T18:57:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d58290ea1213725ddf0f76be129fc5f680d9ccd2'/>
<id>urn:sha1:d58290ea1213725ddf0f76be129fc5f680d9ccd2</id>
<content type='text'>
The compositor _usually_ sends the keymap event *before* the enter
event. But not always.

Not (yet) having a keymap is not a reason to ignore the enter
event (now, on the other hand, getting a key press/release event
without a keymap is a compositor bug).

Closes #1097
</content>
</entry>
<entry>
<title>selection: ignore drag-and-drops with unsupported mime-types</title>
<updated>2022-06-20T18:56:11Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-06-20T17:29:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2e4da6fbf69eb9edafdd74923fc155d16fde2133'/>
<id>urn:sha1:2e4da6fbf69eb9edafdd74923fc155d16fde2133</id>
<content type='text'>
Specifically, make sure we do *not* call wl_data_offer_receive() with
a NULL mime-type, as this causes libwayland to error out, which in
turn causes foot to exit.

Closes #1092
</content>
</entry>
<entry>
<title>osc: add support for OSC 133;A (prompt markers)</title>
<updated>2022-06-16T17:02:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-06-15T16:44:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=bdb79e8b9fb36f627bb204ce2060dd5a877f3712'/>
<id>urn:sha1:bdb79e8b9fb36f627bb204ce2060dd5a877f3712</id>
<content type='text'>
This patch adds support for the OSC-133;A sequence, introduced by
FinalTerm and implemented by iTerm2, Kitty and more. See
https://iterm2.com/documentation-one-page.html#documentation-escape-codes.html.

The shell emits the OSC just before printing the prompt. This lets the
terminal know where, in the scrollback, there are prompts.

We implement this using a simple boolean in the row struct ("this row
has a prompt"). The prompt marker must be reflowed along with the text
on window resizes.

In an ideal world, erasing, or overwriting the cell where the OSC was
emitted, would remove the prompt mark. Since we don't store this
information in the cell struct, we can't do that. The best we can do
is reset it in erase_line(). This works well enough in the "normal"
screen, when used with a "normal" shell. It doesn't really work in
fullscreen apps, on the alt screen. But that doesn't matter since we
don't support jumping between prompts on the alt screen anyway.

To be able to jump between prompts, two new key bindings have been
added: prompt-prev and prompt-next, bound to ctrl+shift+z and
ctrl+shift+x respectively.

prompt-prev will jump to the previous, not currently visible, prompt,
by moving the viewport, ensuring the prompt is at the top of the
screen.

prompt-next jumps to the next prompt, visible or not. Again, by moving
the viewport to ensure the prompt is at the top of the screen. If
we're at the bottom of the scrollback, the viewport is instead moved
as far down as possible.

Closes #30
</content>
</entry>
<entry>
<title>ime: track IME focus independently from keyboard focus</title>
<updated>2022-06-15T17:25:33Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-06-15T16:41:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=96f23b4c6436d314ae4272f5f99c51b8e33556eb'/>
<id>urn:sha1:96f23b4c6436d314ae4272f5f99c51b8e33556eb</id>
<content type='text'>
Replace the seat-&gt;ime.focused boolean with a terminal instace pointer,
seat-&gt;ime_focus.

Set and reset this on ime::enter() and ime::leave() events, and use
this instead of seat-&gt;kbd_focus on all other IME events.

This fixes two issues:

a) buggy compositors that sometimes sends an IME enter event without
  first having sent a keyboard enter event.

b) seats may be IME capable while still lacking the keyboard
  capability. Such seats will *always* see IME enter events without a
  corresponding keyboard enter event.
</content>
</entry>
<entry>
<title>selection: allow HT, VT and FF, disallow NUL in non-bracketed paste mode</title>
<updated>2022-06-15T17:09:40Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-06-13T09:41:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=dbe2c0a068fb0eda9b225f51b1df785d6f076de5'/>
<id>urn:sha1:dbe2c0a068fb0eda9b225f51b1df785d6f076de5</id>
<content type='text'>
This syncs foot with more recent versions of XTerm, where it’s
“disallowedPasteControls” resource has changed its default value to

  BS,DEL,ENQ,EOT,ESC,NULL

Note that we’re already stripping out ENQ,EOT,ESC in all modes.

What does it mean for foot:

* HT, VT and FF are now allowed, regardless of paste mode
* NUL is now stripped in non-bracketed paste mode

Closes #1084
</content>
</entry>
<entry>
<title>changelog: new ‘environment’ section in foot.ini</title>
<updated>2022-06-13T09:55:24Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-05-28T17:28:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=604a3cdd8428afe75318675781cb37aab76c8744'/>
<id>urn:sha1:604a3cdd8428afe75318675781cb37aab76c8744</id>
<content type='text'>
</content>
</entry>
<entry>
<title>grid: reflow: don’t trim trailing empty cells from logical lines</title>
<updated>2022-06-11T10:02:20Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-06-01T17:29:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=9567694bab7149afbb4e4fcc4c754272a8d25aba'/>
<id>urn:sha1:9567694bab7149afbb4e4fcc4c754272a8d25aba</id>
<content type='text'>
When a line in the old grid (the one being reflowed) doesn’t have a
hard linebreak, don’t trim trailing empty cells.

Doing so means we’ll “compress” (remove) empty cells between text
if/when we revert to a larger window size.

The output from neofetch suffers from this; it prints a logo to the
left, and system information to the right. The logo and the system
info column is separated by empty cells (i.e. *not* spaces).

If the window is reduced in size such that the system info is pushed
to a new line, each logo line ends with a number of empty cells. The
next time the window is resized, these empty cells were
ignored (i.e. removed).

That meant that once the window was enlarged again, the system info
column was a) no longer aligned, and b) had been pulled closer to the
logo.

This patch doesn’t special case trailing empty cells when the line
being reflowed doesn’t have a hard linebreak. This means e.g. ‘ls’
output is unaffected.

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