<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/CHANGELOG.md, branch 1.15.0</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.15.0</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.15.0'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2023-07-14T10:25:16Z</updated>
<entry>
<title>changelog: prepare for 1.15.0</title>
<updated>2023-07-14T10:25:16Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-07-14T10:25:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=53b0eb8e1b50341d15fcb0957c8dca9af90e6473'/>
<id>urn:sha1:53b0eb8e1b50341d15fcb0957c8dca9af90e6473</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: add csd.double-click-to-maximize=no|yes option</title>
<updated>2023-07-14T10:03:35Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-07-14T10:03:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3f7be59062f00cd99d832eaa5d389b880a3c512e'/>
<id>urn:sha1:3f7be59062f00cd99d832eaa5d389b880a3c512e</id>
<content type='text'>
When enabled, double-clicking the CSD titlebar will (un)maximize the
window.

Defaults to ‘yes’ (since this is the old hard-coded behavior).

Closes #1293
</content>
</entry>
<entry>
<title>config: make ‘starlight’ the default color theme</title>
<updated>2023-07-14T08:11:43Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-07-14T08:11:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=efc619b0afc856c976ea8e4d255ab9e014089510'/>
<id>urn:sha1:efc619b0afc856c976ea8e4d255ab9e014089510</id>
<content type='text'>
Closes #1321
</content>
</entry>
<entry>
<title>render: don’t invert cursor colors when custom colors are being used</title>
<updated>2023-07-14T07:57:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-07-14T07:51:06Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b3745b31c72042adf523b54be7c2a297a82cca7f'/>
<id>urn:sha1:b3745b31c72042adf523b54be7c2a297a82cca7f</id>
<content type='text'>
When the user has configured custom cursor colors (cursor.color is set
in foot.ini), don’t invert those colors when the cell is either
selected, or has the ‘reverse’ attribute set.

This aligns foot’s behavior with Alacritty, Kitty and Wezterm. Contour
also behaves similarly, except mouse selections override the cursor
colors (turning the cursor invisible).

Closes #1347
</content>
</entry>
<entry>
<title>changelog: mention the new default key binding for show-urls-launch under “fixed”</title>
<updated>2023-07-10T10:42:36Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-07-10T10:42:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3609017c383a74bdb142c5e667fdaa35d11e6da6'/>
<id>urn:sha1:3609017c383a74bdb142c5e667fdaa35d11e6da6</id>
<content type='text'>
It “fixes” the key binding conflict seen on e.g. GNOME, and increases
the exposure of the change to, hopefully, more users.
</content>
</entry>
<entry>
<title>changelog: split up key binding changes for show-urls-launch and unicode-input</title>
<updated>2023-07-10T10:42:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-07-10T10:42:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=58898c06339bd1374e975366515d437f22914bd1'/>
<id>urn:sha1:58898c06339bd1374e975366515d437f22914bd1</id>
<content type='text'>
</content>
</entry>
<entry>
<title>bind control-shift-u to unicode-input, move urls to o</title>
<updated>2023-07-10T10:31:51Z</updated>
<author>
<name>Antoine Beaupré</name>
<email>anarcat@debian.org</email>
</author>
<published>2022-12-15T16:49:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=080a11eb7374af3335bde3841789bd2b659237c8'/>
<id>urn:sha1:080a11eb7374af3335bde3841789bd2b659237c8</id>
<content type='text'>
Having a keybinding to invoke arbitrary unicode characters is very
useful. It's often used as a method of last resort to communicate with
people outside of your main language. For example, if you want to type
the last letter of my real name, you can invoke the latin-1 character
0xe9 or unicode 0x00e9.

You can also use this to type special characters, for example, unicode
U+1F4A9 is of course, the infamous PILE OF POO, which is sure to
produce million laughs everywhere you go.

In foot, there's no keybinding by default to invoke the very useful
unicode-input command. There is no "standard" (as in "ISO") keybinding
this either. But there *is* a de-facto standard currently deployed
by *both* GTK and Qt (a rare feat) *and* Chrome OS (an even rarer
feat) and it's control-shift-u.

Alternatives include Control-x 8 (emacs), Control V u (vim),
Alt (Windows, LibreOffice), or Option (Mac). I doubt we want to adopt
any of those.

So let's use control-shift-u for this. Unfortunately, it's currently
assigned to show-urls-launch, which is unfortunate, but
insurmountable. We can reassign this keybinding elsewhere. I have
picked control-shift-o in my configuration, because "o" is a good
mnemonic for "open URLs". Others have suggested "m" instead.

Closes: #1183
</content>
</entry>
<entry>
<title>input: add basic support for touchscreen input</title>
<updated>2023-07-05T14:22:28Z</updated>
<author>
<name>CismonX</name>
<email>admin@cismon.net</email>
</author>
<published>2023-07-04T16:19:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d2fcb5343f57c132abec9a21ad89d1505a32c47c'/>
<id>urn:sha1:d2fcb5343f57c132abec9a21ad89d1505a32c47c</id>
<content type='text'>
Closes #517
</content>
</entry>
<entry>
<title>changelog: fractional-scaling-v1 -&gt; fractional-scale-v1</title>
<updated>2023-07-04T06:38:07Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-07-04T06:38:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=4a7382891112d898d4ba0f8d445439b8ad86477e'/>
<id>urn:sha1:4a7382891112d898d4ba0f8d445439b8ad86477e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>cursor-shape: add support for server side cursor shapes</title>
<updated>2023-07-03T12:36:32Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-27T15:25:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=c8e13ad3938d68635693d0b0f4bf1054628e8387'/>
<id>urn:sha1:c8e13ad3938d68635693d0b0f4bf1054628e8387</id>
<content type='text'>
This implements support for the new cursor-shape-v1 protocol. When
available, we use it, instead of client-side cursor surfaces, to
select the xcursor shape.

Note that we still need to keep client side pointers, for:

* backward compatibility
* to be able to "hide" the cursor

Closes #1379
</content>
</entry>
<entry>
<title>sixel: re-scale images when the cell dimensions change</title>
<updated>2023-06-30T06:29:35Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-29T12:49:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=49fb0cf359bb2486bbdf58df62c66c890d7e31cd'/>
<id>urn:sha1:49fb0cf359bb2486bbdf58df62c66c890d7e31cd</id>
<content type='text'>
Before this patch, when the cell dimensions changed (i.e. when the
font size changes), sixel images were either removed (the new cell
dimensions are smaller than the old), or simply kept at their original
size (new cell dimensions are larger).

With this patch, sixels are instead resized. This means a
sixel *always* occupies the same number of rows and columns,
regardless of how much the font size is changed.

This is done by maintaining two sets of image data and pixman images,
as well as their dimensions. These two sets are the new ‘original’ and
‘scaled’ members of the sixel struct.

The "top-level" pixman image pointer, and the ‘width’ and ‘height’
members either point to the "original", or the "scaled" version.

They are invalidated as soon as the cell dimensions change. They, and
the ‘scaled’ image is updated on-demand (when we need to render a
sixel).

Note that the ‘scaled’ image is always NULL when the current cell
dimensions matches the ones used when emitting the sixel (to save
run-time memory).

Closes #1383
</content>
</entry>
<entry>
<title>changelog: dpi-aware’s default value is now ‘no’</title>
<updated>2023-06-29T13:38:23Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-26T15:55:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=27a92b11588203c90c0ec4c61a1a6c7a741b2935'/>
<id>urn:sha1:27a92b11588203c90c0ec4c61a1a6c7a741b2935</id>
<content type='text'>
</content>
</entry>
<entry>
<title>changelog: mention the newly added support for fractional-scaling-v1</title>
<updated>2023-06-29T13:38:23Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-26T15:34:20Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=32b8c5c9b6628f3dd1b9f25f9b13a6d016de86cb'/>
<id>urn:sha1:32b8c5c9b6628f3dd1b9f25f9b13a6d016de86cb</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sixel: stop cropping images to the last non-transparent row</title>
<updated>2023-06-24T05:31:08Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-19T17:09:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=774570ec41a3c585f40b03467eaada786a2e97d3'/>
<id>urn:sha1:774570ec41a3c585f40b03467eaada786a2e97d3</id>
<content type='text'>
</content>
</entry>
<entry>
<title>sixel: respect sixel aspect ratio</title>
<updated>2023-06-24T05:31:08Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-19T17:06:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=d6d143e2a6916178d1ea74551617cf8a5cddc39e'/>
<id>urn:sha1:d6d143e2a6916178d1ea74551617cf8a5cddc39e</id>
<content type='text'>
That is, parse P1 when initializing a new sixel, and don’t ignore
pad/pad in the raster attributes command.

The default aspect ratio is 2:1, but most sixels will override it in
the raster attributes command (to 1:1).
</content>
</entry>
<entry>
<title>sixel: fix cursor positioning logic</title>
<updated>2023-06-24T05:31:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-16T14:20:37Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=66d9b8da604e4fd3aa6ee96da3609ff6b9896f50'/>
<id>urn:sha1:66d9b8da604e4fd3aa6ee96da3609ff6b9896f50</id>
<content type='text'>
This adjusts the logic that positions the text cursor after emitting a
sixel, when sixel scrolling mode is *enabled*.

We’ve always mimicked XTerm’s behavior. However, XTerm recently
changed its behavior, to better match that of an VT382.

Now, the cursor is placed *on* the last row of the sixel, instead of
on a new row after the sixel.

This allows applications to print sixels to the bottom row of the
terminal, without causing the content to scroll.

Finally, there was a bug in the horizontal positioning of the cursor;
it was placed on the *first* column of the row, instead of on the
first column of the sixel.
</content>
</entry>
<entry>
<title>term: scroll: only record scroll damage when viewport is at the bottom</title>
<updated>2023-06-23T18:38:03Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-23T18:20:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8a3620bafaa4119b9f6d3f74189c2dac78614d3c'/>
<id>urn:sha1:8a3620bafaa4119b9f6d3f74189c2dac78614d3c</id>
<content type='text'>
We don’t need to record scroll damage if the viewport isn’t at the
bottom, since in this case, the renderer ignores the scroll damage
anyway.

This fixes a performance corner case, when the viewport is at the top
of the scrollback history.

When application scrolls the terminal contents, and the scrollback
history is full, and the viewport is at top of the history, then the
viewport needs to be moved (the scrollback history is a circular
buffer, and thus the top of the history “moves” when we’re scrolling
in new contents).

Moving the viewport typically results in another type of scroll
damage (DAMAGE_SCROLL_IN_VIEW, instead of the “normal” DAMAGE_SCROLL).

Thus, each application triggered scroll, will result in two scroll
damage records: one DAMAGE_SCROLL, and one
DAMAGE_SCROLL_IN_VIEW. These two are incompatible, meaning they can’t
be merged. What’s worse, it also means the DAMAGE_SCROLL records from
two application triggered scrolls cannot be merged (since there’s a
DAMAGE_SCROLL_IN_VIEW in between).

As a result, the renderer will not see one, or “a few” scroll damage
events, but a *ton*. _Each_ one typically a single line, or so. And
each one resulting in lots of traffic on the wayland socket, as we
create and destroy new buffer pools, when doing “shm scrolling”.

This eventually leads to the socket not being able to keep up, and the
socket is closed on us, forcing us to exit.

The fix is really simple: don’t record “normal” scroll damage when
scrolling, _unless_ the viewport is at the bottom (and thus “follows”
the application output).

As soon as the user scrolls up in the history, we’ll stop emitting
normal scroll damage records. This is just fine, since, as mentioned
above, the renderer ignores them when the viewport isn’t at the
bottom.

What if the viewport is moved back down again, before the next frame
has been rendered? Wont there be “missing” scroll damage records? No,
because moving the viewport results in scroll damage records by
itself.

Closes #1380
</content>
</entry>
<entry>
<title>render: resize: fix crash when reflowing the alt screen</title>
<updated>2023-06-20T13:59:16Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-06-20T13:59:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3a59cbbaa3906da6f9ab73ad949bc598318be7e4'/>
<id>urn:sha1:3a59cbbaa3906da6f9ab73ad949bc598318be7e4</id>
<content type='text'>
When doing an interactive resize, and `resize-delay-ms` &gt; 0 (the
default), we would crash if the original screen size (i.e. the size
before the interactive resize started) was larger than the last window
size.

For example, if we interactively go from 85 rows to 75, and then
non-interactively went from 75 to 80, we’d crash.

The resizes had to be made in a single go. One way to trigger this was
to start an interactive resize on a floating window, and then *while
resizing* toggle the window’s floating mode.

Closes #1377
</content>
</entry>
<entry>
<title>meson: use meson feed feature for scdoc input</title>
<updated>2023-06-14T17:15:20Z</updated>
<author>
<name>sewn</name>
<email>sewn@disroot.org</email>
</author>
<published>2023-06-14T12:26:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=16872ecc4137a5a58f9da8e62990d5587afbec21'/>
<id>urn:sha1:16872ecc4137a5a58f9da8e62990d5587afbec21</id>
<content type='text'>
Removes the need for a shell dependency.
</content>
</entry>
<entry>
<title>sixel: apply background alpha when P2=0 or P2=2, and current bg color is the default bg color</title>
<updated>2023-05-31T14:27:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2023-05-31T14:27:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1433a81c08d696cad8c5460ca739bc0cd97a9a5c'/>
<id>urn:sha1:1433a81c08d696cad8c5460ca739bc0cd97a9a5c</id>
<content type='text'>
Closes #1360
</content>
</entry>
</feed>
