<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git, branch releases/1.12</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=releases%2F1.12</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=releases%2F1.12'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2022-04-27T18:06:09Z</updated>
<entry>
<title>meson: bump version to 1.12.1</title>
<updated>2022-04-27T18:06:09Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-27T18:06:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e95269447f1b62384dc64707bb19ebe1006386ac'/>
<id>urn:sha1:e95269447f1b62384dc64707bb19ebe1006386ac</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: prepare for 1.12.1</title>
<updated>2022-04-27T18:05:51Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-27T18:05:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=225f8e659e157fcc72e95ed0617e931d8d89fbba'/>
<id>urn:sha1:225f8e659e157fcc72e95ed0617e931d8d89fbba</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'master' into releases/1.12</title>
<updated>2022-04-27T18:03:53Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-27T18:03:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=cd513e1761cffac91e714d691dc70826c82061f3'/>
<id>urn:sha1:cd513e1761cffac91e714d691dc70826c82061f3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: changed behavior of “extend-to-word-boundary”</title>
<updated>2022-04-27T16:52:08Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-27T16:52:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=5308b8cdb8fe3c14c9a48954880b2f858d80df35'/>
<id>urn:sha1:5308b8cdb8fe3c14c9a48954880b2f858d80df35</id>
<content type='text'>
</content>
</entry>
<entry>
<title>selection: find_word_boundary_right: add “stop-on-space-to-word-boundary”</title>
<updated>2022-04-27T16:44:57Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-27T16:44:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=76305104486a90c2320dd102c32fe26831ebb658'/>
<id>urn:sha1:76305104486a90c2320dd102c32fe26831ebb658</id>
<content type='text'>
When true, selection_find_word_boundary_right() behaves as before - it
stops as soon as it encounters a character that isn’t of the
same *type* as the “initial” character (the last character in the
selection).

Take this, for example:

  The Quick Brown Fox

The selection will first stop at the end of “the”, then just *before*
“quick”, then at the end of “quick”. Then just *before* “brown”, and
then at the end of “brown”, and so on.

This suits mouse selections pretty good. But when
selection_find_word_boundary_right() is used to extend a search match,
it’s better to ignore space-to-word character transitions. That is, we
want

  The Quick Brown Fox

to first extend to the end of “the”, then immediately to the end of
“quick”, then to the end of “brown”, and so on.

Setting the ‘stop_to_space_to_word_boundary’ argument to false results
in latter behavior.

This is now done by search, when executing the
“extend-to-word-boundary” and “extend-to-next-whitespace” key
bindings.
</content>
</entry>
<entry>
<title>Disable debug logging</title>
<updated>2022-04-27T16:44:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-27T16:44:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8356dfac2f8afa854bcf2ceaca26e1b3090deeb3'/>
<id>urn:sha1:8356dfac2f8afa854bcf2ceaca26e1b3090deeb3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: reset sixel options when hard resetting the terminal state</title>
<updated>2022-04-26T19:05:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T19:05:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=32d9895697584988056086cbecdc96375b4b9115'/>
<id>urn:sha1:32d9895697584988056086cbecdc96375b4b9115</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add ctrl+shift+v and XF86 paste to SEARCH_CLIPBOARD_PASTE</title>
<updated>2022-04-26T18:37:30Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T16:34:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=aa4c7c5a30a792a9519b971ff14582dc2704b6bc'/>
<id>urn:sha1:aa4c7c5a30a792a9519b971ff14582dc2704b6bc</id>
<content type='text'>
We now bind ctrl+v, ctrl+shift+v, ctrl+y and XF86Paste to pasting from
the clipboard into the scrollback search buffer.

Why all these? Because we can, and because all are common shortcuts
for pasting:

* ctrl+v: “normal” apps use this by default
* ctrl+shift+v: used in terminals (including foot)
* ctrl+y: Emacs
* XF86Paste: special keyboard key, for pasting
</content>
</entry>
<entry>
<title>search: fix infinite loop when highlighting all matches</title>
<updated>2022-04-26T18:36:28Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T16:24:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0e9ebf433b589c15e17bd37f73991ecc71e9b3d6'/>
<id>urn:sha1:0e9ebf433b589c15e17bd37f73991ecc71e9b3d6</id>
<content type='text'>
find_next() did not always terminate correctly, causing
search_matches_next() to never terminate, which finally leads to an
infinite loop when rendering the search overlay surface, while finding
all matches to highlight.

The problem is that find_next(), after having found the initial
matching characters, enters a nested while loop that tries to match
the rest of the search criteria. This inner while loop did not check
if we’ve reached the last cell, and happily continued past
it (eventually wrappping around the scrollback buffer).

Closes #1047
</content>
</entry>
<entry>
<title>search: assert that the match is *inside* the new viewport</title>
<updated>2022-04-26T17:47:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T17:47:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=694938b85bed679c95ac506711475bf06cd80b0e'/>
<id>urn:sha1:694938b85bed679c95ac506711475bf06cd80b0e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>search: regression: crash when moving viewport</title>
<updated>2022-04-26T17:32:08Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T17:32:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c82c6116ede2706a9d5b28d43e8271ec13be2794'/>
<id>urn:sha1:c82c6116ede2706a9d5b28d43e8271ec13be2794</id>
<content type='text'>
5c4ddebc3c57724bd89b959a33f5ad0bd97f482b refactored
search_update_selection(), specifically, the logic that moves the
viewport.

It did so by converting the absolute row number (of the match) to
scrollback relative coordinates. This way we could ensure the viewport
wasn’t moved “too much” (e.g. beyond the scrollback start).

However, grid_row_abs_to_sb() and grid_row_sb_to_abs() doesn’t take a
partially filled scrollback into account. This means the row (numbers)
it returns may refer to *uninitialized* rows.

Since:

* The match row itself is valid (we *know* it has text on it)
* We *subtract* from it, when setting the new viewport (to center the
  match on the screen).

it’s only the *upper* part of the new viewport that may be
uninitialized. I.e. we may have adjusted it too much.

So, what we need to do is move the viewport forward until its *first*
row is initialized. Then we know the rest will be too.
</content>
</entry>
<entry>
<title>changelog: typo: space on the wrong side of the parenthesis</title>
<updated>2022-04-26T15:52:00Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T15:52:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=93dcb7dc9cf753462bfea40b890a9d68945a5d58'/>
<id>urn:sha1:93dcb7dc9cf753462bfea40b890a9d68945a5d58</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Merge branch 'sway-sub-surface-damage-workaround'</title>
<updated>2022-04-26T15:44:16Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T15:44:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=29f07c791e7ec4d1d6ba4136edeb0a3ad71d33c9'/>
<id>urn:sha1:29f07c791e7ec4d1d6ba4136edeb0a3ad71d33c9</id>
<content type='text'>
Closes #1046
</content>
</entry>
<entry>
<title>changelog: workaround for Sway bug #6960</title>
<updated>2022-04-26T15:42:46Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T15:28:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3abb23c81c5da902587b5b639eff555fcab5a337'/>
<id>urn:sha1:3abb23c81c5da902587b5b639eff555fcab5a337</id>
<content type='text'>
</content>
</entry>
<entry>
<title>term: flash: work around Sway sub-surface unmap bug</title>
<updated>2022-04-26T15:41:38Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T15:24:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=398d96fdb2a18f7652c116639dc17741f5e24404'/>
<id>urn:sha1:398d96fdb2a18f7652c116639dc17741f5e24404</id>
<content type='text'>
Unmapping a sub-surface in Sway does not damage the underlying
surface.

As a result, the OSC-555 escape (“flash”) will leave yellow margins on
~every second frame.

Out of sway, river, weston and mutter, only Sway needs this
workaround.

This is a workaround for https://github.com/swaywm/sway/issues/6960

Closes #1046
</content>
</entry>
<entry>
<title>search: work around Sway sub-surface unmap bug</title>
<updated>2022-04-26T15:41:38Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-25T17:55:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1e87dbc4dc87c9567a7851135d91728796b0696f'/>
<id>urn:sha1:1e87dbc4dc87c9567a7851135d91728796b0696f</id>
<content type='text'>
Unmapping a sub-surface in Sway does not damage the underlying
surface.

As a result, "committing" a scrollback search will typically leave
most of the foot window dimmed.

It can be seen when "cancelling" a search as well, but there it's less
obvious - only the margins are left dimmed. This is because cancelling
a search damaged the current viewport (something that shouldn't be
needed).

Out of sway, river, weston and mutter, only Sway needs this
workaround.

This is a workaround for https://github.com/swaywm/sway/issues/6960
</content>
</entry>
<entry>
<title>Merge branch 'search-crashes'</title>
<updated>2022-04-26T15:40:58Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T15:40:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=57543c4290f3380a8d49e9256afd9fa6ef67a638'/>
<id>urn:sha1:57543c4290f3380a8d49e9256afd9fa6ef67a638</id>
<content type='text'>
Closes #1036
</content>
</entry>
<entry>
<title>changelog: search mode not always highlighting all matches correctly</title>
<updated>2022-04-26T15:40:20Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T15:40:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b94f540113dd10e4b34f5dda826f732b29b47217'/>
<id>urn:sha1:b94f540113dd10e4b34f5dda826f732b29b47217</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: crash when extending selection in search mode</title>
<updated>2022-04-26T15:40:00Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-26T15:40:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1b5b1d5d925f296619c511a5b12a10f48717efce'/>
<id>urn:sha1:1b5b1d5d925f296619c511a5b12a10f48717efce</id>
<content type='text'>
</content>
</entry>
<entry>
<title>search: fix multiple crashes</title>
<updated>2022-04-25T18:00:47Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-04-25T18:00:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=5c4ddebc3c57724bd89b959a33f5ad0bd97f482b'/>
<id>urn:sha1:5c4ddebc3c57724bd89b959a33f5ad0bd97f482b</id>
<content type='text'>
* When extending the selection to the next word boundary, ensure the
  row numbers are valid:

  - use selection_get_end() when retrieving the current end
    coordinate. This alone fixes a crash where we previously would
    crash in an out-of-bounds array access in grid-&gt;rows[], due to
    term-&gt;selection.coords.end being unbounded.

  - ensure the new end coordinate is bounded before and after calling
    selection_find_word_boundary_right().

* When moving the viewport (to ensure a new match is visible), make
  sure we don’t end up with the match outside the new viewport.

  Under certain, unusual, circumstances, the moved viewport _still_
  did not contain the match. This resulted in assertions triggering
  later, that assumed the match(es) are *always* visible.

  It’s fairly easy to trigger this one by running foot with e.g.

    foot -o scrollback.lines=0 --window-size-chars 25x3

  and then hitting enter a couple of times, to fill the scrollback
  history (which should consist of a single row in the example above),
  and the do a scrollback search for (part of) the prompt, and keep
  searching backward until it crashes.

  This would happen if calculated (new) viewport had to be adjusted
  (for example, to ensure it didn’t go past the scrollback end).

  This patch changes the logic used when calculating the new
  viewport. Instead of calculating the wanted viewport (match is
  vertically centered) and then trying to adjust it to ensure the new
  viewport is valid, start with a “safe” new viewport value, and then
  determine how much we can move it, if at all, to center the match.

  This is done by using scrollback relative coordinates. In this
  coordinate system, the new viewport must be

    &gt;= 0, and &lt; grid-&gt;num_lines - term-&gt;rows

  This makes it very easy to limit the amount by which the viewport is
  adjusted.

  As a side-effect, we can remove all the old re-adjustment logic.

* The match iterator no longer special cases the primary match. This
  was needed before, when the search iterator did not handle
  overlapping matches correctly. Now that we do, the iterator is
  guaranteed to find the primary match, and thus we no longer need to
  special case it.

  This fixes a bug where the primary match was returned twice, due to
  the logic checking if a secondary match is the same as the primary
  match was flawed...

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