<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/doc, branch releases/1.14</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=releases%2F1.14</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=releases%2F1.14'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2023-03-28T21:45:18Z</updated>
<entry>
<title>fix typos</title>
<updated>2023-03-28T21:45:18Z</updated>
<author>
<name>Harri Nieminen</name>
<email>moiman@posteo.net</email>
</author>
<published>2023-03-28T21:31:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ae26915916731813edc2aefeb18a5754e8c79cd4'/>
<id>urn:sha1:ae26915916731813edc2aefeb18a5754e8c79cd4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>slave: set $TERM_PROGRAM and $TERM_PROGRAM_VERSION environment variables</title>
<updated>2023-03-20T14:40:36Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2023-03-20T14:40:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=5b2f02d826d8043b6b89860c56802ea5fed0f3bd'/>
<id>urn:sha1:5b2f02d826d8043b6b89860c56802ea5fed0f3bd</id>
<content type='text'>
These are already being set by iTerm2, WezTerm, tmux and likely some
others. Even though using yet more environment variables seems rather
questionable, if we don't set these we run the risk of inheriting them
from other terminals.

See also:

* https://gitlab.com/gnachman/iterm2/-/blob/97a6078df8e822da165e91737a01c0b9e115dd16/sources/PTYSession.m#L2568-2570
* https://github.com/tmux/tmux/blob/1d0f68dee9f71c504e03616fa472a408a6caa49b/environ.c#L263-L264
* https://github.com/search?q=TERM_PROGRAM&amp;type=code
</content>
</entry>
<entry>
<title>doc: foot.ini: fix spelling mistake in [bell].urgent description</title>
<updated>2023-02-16T09:12:53Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2023-02-16T09:09:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=f2356adee392edefa54009c9932a37e6c5a45b20'/>
<id>urn:sha1:f2356adee392edefa54009c9932a37e6c5a45b20</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: ctlseq: fix capitalization in description of DA3 sequence</title>
<updated>2023-02-16T08:50:53Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2023-02-16T08:50:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=25154a81509934074934bd71c986d9866103f293'/>
<id>urn:sha1:25154a81509934074934bd71c986d9866103f293</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: fix a typo</title>
<updated>2023-01-07T21:55:01Z</updated>
<author>
<name>Grigory Kirillov</name>
<email>txgk@bk.ru</email>
</author>
<published>2023-01-07T21:55:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=a38b8d02227f13ce1da5125905a262e298875a0d'/>
<id>urn:sha1:a38b8d02227f13ce1da5125905a262e298875a0d</id>
<content type='text'>
</content>
</entry>
<entry>
<title>config: change default grapheme-width-method from wcswidth to double-width</title>
<updated>2023-01-01T09:29:27Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-12-16T15:56:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6259d59b4d82b0e8b7705759e04262130a3426c8'/>
<id>urn:sha1:6259d59b4d82b0e8b7705759e04262130a3426c8</id>
<content type='text'>
The old default, wcswidth, simply calls wcswidth() on the grapheme
cluster. This was supposedly the implementation with the highest
application compatibility. Except we never even tried to measure
it. It was just assumed.

A lot of modern applications have better implementations. Let’s try to
push support for better emoji support by changing our default method
from wcswith to double-width.

While far from correct (it’s not based on the Unicode tables), the
‘double-width’ method produces accurate results anyway.

double-width is like wcswidth(), in that it adds together the
individual wcwidths of all codepoints in the grapheme cluster. But, it
limits the maximum width to 2.
</content>
</entry>
<entry>
<title>config: add ‘font-size-adjustment=N[px|%]’ option</title>
<updated>2022-12-17T09:59:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-12-15T10:10:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=f6ca8c90e11d9b1ecdfe8a5bf69b1b793376a91c'/>
<id>urn:sha1:f6ca8c90e11d9b1ecdfe8a5bf69b1b793376a91c</id>
<content type='text'>
This patch adds a new config option, font-size-adjustment.

It lets you configure how much the font size should be
incremented/decremented when zooming in or out (ctrl-+, ctrl+-).

Values can be specified in points, pixels or percent.

Closes #1188
</content>
</entry>
<entry>
<title>doc: foot-ctlseq: expand last column to fill screen in all tables</title>
<updated>2022-12-14T11:20:52Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-12-14T11:20:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3b9aca6a3d0caef3c0a5070f7684687e8c5d0c1a'/>
<id>urn:sha1:3b9aca6a3d0caef3c0a5070f7684687e8c5d0c1a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: foot.ini: add example, and mention string options can be quoted</title>
<updated>2022-12-06T18:36:07Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-12-02T14:03:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=646314469afd96eda346b6a296037d5430e5f121'/>
<id>urn:sha1:646314469afd96eda346b6a296037d5430e5f121</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: foot: add PWD to list of env vars set in child process</title>
<updated>2022-12-04T18:49:02Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-12-04T18:49:02Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1486c57bdb084e5c41f917fd542a3605dcaa90a0'/>
<id>urn:sha1:1486c57bdb084e5c41f917fd542a3605dcaa90a0</id>
<content type='text'>
</content>
</entry>
<entry>
<title>doc: ctlseq: add trailing space to fix XTGETTCAP entry in DCS table</title>
<updated>2022-11-24T20:34:41Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2022-11-24T20:34:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=1b24cf4fcb8a32a9c20eb607c2015542eb2753d4'/>
<id>urn:sha1:1b24cf4fcb8a32a9c20eb607c2015542eb2753d4</id>
<content type='text'>
Without the trailing space, both the sequence and the description
were getting packed into a single table column.
</content>
</entry>
<entry>
<title>readme/foot.1: mention that we now need “-d info” to get log output</title>
<updated>2022-11-23T15:27:50Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-11-23T15:27:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=dfabc5d75423c863a7e9a930b9a8aac593784e02'/>
<id>urn:sha1:dfabc5d75423c863a7e9a930b9a8aac593784e02</id>
<content type='text'>
</content>
</entry>
<entry>
<title>change default log level to WARNING</title>
<updated>2022-11-22T15:22:22Z</updated>
<author>
<name>Antoine Beaupré</name>
<email>anarcat@debian.org</email>
</author>
<published>2022-11-18T16:07:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b80c7f75fea0c1a69471d1f67aa97b584d3e48b2'/>
<id>urn:sha1:b80c7f75fea0c1a69471d1f67aa97b584d3e48b2</id>
<content type='text'>
The default foot output looks like this, in Debian testing "bookworm"
at the time of writing:

    anarcat@angela:pubpaste$ foot true
    info: main.c:421: version: 1.13.1 +pgo +ime +graphemes -assertions
    info: main.c:428: arch: Linux x86_64/64-bit
    info: main.c:440: locale: fr_CA.UTF-8
    info: config.c:3003: loading configuration from /home/anarcat/.config/foot/foot.ini
    info: fcft.c:338: fcft: 3.1.5 +graphemes -runs +svg(nanosvg) -assertions
    info: fcft.c:377: fontconfig: 2.13.1, freetype: 2.12.1, harfbuzz: 5.2.0
    info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Regular.otf: size=8.00pt/8px, dpi=75.00
    info: wayland.c:1353: eDP-1: 2256x1504+0x0@60Hz 0x095F 13.32" scale=2 PPI=205x214 (physical) PPI=136x143 (logical), DPI=271.31
    info: wayland.c:1509: requesting SSD decorations
    info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Bold.otf: size=24.00pt/32px, dpi=96.00
    info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Regular.otf: size=24.00pt/32px, dpi=96.00
    info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Bold.otf: size=24.00pt/32px, dpi=96.00
    info: fcft.c:838: /home/anarcat/.local/share/fonts/Fira-4.202/otf/FiraMono-Regular.otf: size=24.00pt/32px, dpi=96.00
    info: terminal.c:700: cell width=19, height=39
    info: terminal.c:588: using 16 rendering threads
    info: wayland.c:859: using SSD decorations
    info: main.c:680: goodbye
    anarcat@angela:pubpaste$

That's 17 lines of output that are *mostly* useless for most use
cases. I might understand having this output during the project's
startup, when it's helpful for diagnostics, but now Foot just mostly
works everywhere, and I've never had a use for any of that stuff in
the (arguably short) time I've been using Foot so far.

And if I do, there's the `--log-level` commandline option to tweak
this. At first, I looked at tweaking the log level through the config
file. But as explained in this issue:

https://codeberg.org/dnkl/foot/issues/1142

... there's a chicken and egg problem there that makes it hard to
implement and possibly confusing for users as well.

There's also the possibility for users to change the shortcut with
which they start foot, for example a `.desktop` file so that menu
systems that support those start foot properly. But that only works in
that environment, and not through the so many things that will just
call `foot` and hope it will do the right thing.

In my case, I have `foot` hardcoded in a lot of places now, between
sway and waybar, and this is only going to grow. Others have suggested
adding the flag to a $TERMINAL global variable, but that won't help
.desktop users.

So, instead of playing whack-a-mole with the log levels, just make it
so that, by default, foot is silent. This is actually one of the
[basics of UNIX philosophy][1]:

&gt; Rule of Silence: When a program has nothing surprising to say, it
&gt; should say nothing.

And yes, I am aware I am severely violating that principle by writing
a way too long commit log for a one-line patch, but there you go, I
figured it was good to document the why of this properly.

[1]: https://web.archive.org/web/20031102053334/http://www.faqs.org/docs/artu/ch01s06.html
</content>
</entry>
<entry>
<title>doc: foot.ini: improve documentation of cursor.color</title>
<updated>2022-10-17T18:16:53Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-10-17T18:16:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b0c30c7ed22acbf4033db18949ea43f50edd1382'/>
<id>urn:sha1:b0c30c7ed22acbf4033db18949ea43f50edd1382</id>
<content type='text'>
</content>
</entry>
<entry>
<title>render: delay reflow for ‘resize-delay-ms’ milliseconds</title>
<updated>2022-10-10T15:19:17Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-10-05T15:05:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8179d73daa95dc3b3bdd76eaecc78e456bb4686a'/>
<id>urn:sha1:8179d73daa95dc3b3bdd76eaecc78e456bb4686a</id>
<content type='text'>
Reflowing a large scrollback is *slow*. During an interactive resize,
it can easily take long enough that the compositor fills the Wayland
socket with configure events. Eventually, the socket becomes full and
the compositor terminates the connection, causing foot to exit.

This patch is work-in-progress, and the first step towards alleviating
this.

It delays the reflow by:

* Snapshotting (copying) the original grid when an interactive resize
  is started.
* While resizing, we apply a simple truncation resize of the
  grid (like we handle the alt screen).
* When the resize is done, or paused for ‘resize-delay-ms’, the grid
  is reflowed.

TODO: we *must* not allow any changes to the temporary (truncated)
grid during the resize. Any changes to the grid would be lost when the
final reflow is applied. That is, we must completely pause the ptmx
pipe while a resize is in progress.

Future improvements:

The initial copy can be slow. We should be able to avoid it by
rewriting the reflow algorithm to not free anything. This is
complicated by the fact that some resources (e.g. sixel images) are
currently *moved* to the new grid. They’d instead have to be copied.
</content>
</entry>
<entry>
<title>doc: fix tiny typo</title>
<updated>2022-10-04T04:04:03Z</updated>
<author>
<name>Nick Hastings</name>
<email>nicholaschastings@gmail.com</email>
</author>
<published>2022-10-04T04:04:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=cbebafbfe8d43415fa6baeb59d44bd3be0b593bf'/>
<id>urn:sha1:cbebafbfe8d43415fa6baeb59d44bd3be0b593bf</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add support for creating utmp records</title>
<updated>2022-09-23T21:02:25Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-09-23T18:24:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=aa10b1d2da3ecf9672ae915a49073bd30ee0a785'/>
<id>urn:sha1:aa10b1d2da3ecf9672ae915a49073bd30ee0a785</id>
<content type='text'>
This patch adds support for creating utmp records using the ‘utempter’
helper binary from the ‘libutempter’ package.

* New config option ‘main.utempter’
* New meson command line option, -Ddefault-utempter-path. Defaults to
  auto-detecting the path.

The default value of the new ‘main.utempter’ config option depends on
the meson command line option ‘-Ddefault-utempter-path’.

If ‘main.utempter’ is *not* set to ‘none’, foot will try to execute
the utempter helper binary to create utmp records when a new terminal
is instantiated. The record is removed when the terminal instance is
destroyed.
</content>
</entry>
<entry>
<title>config: change default ‘pad’ to 0x0 (i.e. no padding)</title>
<updated>2022-09-03T10:17:46Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-09-03T10:16:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=2d1ded183ac1c79b93f2674fed3ec7c0def65075'/>
<id>urn:sha1:2d1ded183ac1c79b93f2674fed3ec7c0def65075</id>
<content type='text'>
</content>
</entry>
<entry>
<title>theme: change default color theme to solarized-dark-normal-brights</title>
<updated>2022-08-22T11:37:12Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2022-08-17T16:12:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3cf11bfea9e4787998c538bd312c456fd8287fd1'/>
<id>urn:sha1:3cf11bfea9e4787998c538bd312c456fd8287fd1</id>
<content type='text'>
This is my variant of the solarized theme, were only the first eight
colors (i.e. the "normal") colors are from the solarized theme. The
remaining eight (the "bright" colors) are brightened versions of the
"normal" colors. This results in a theme that is usually in all
applications, not just those that are "aware" that the terminal color
theme is "solarized".
</content>
</entry>
<entry>
<title>config: add setting for underline thickness</title>
<updated>2022-08-20T20:16:32Z</updated>
<author>
<name>Yorick Peterse</name>
<email>git@yorickpeterse.com</email>
</author>
<published>2022-08-19T00:54:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=a0942f950df3b8826db4b1a3f149b7d0ed45adcf'/>
<id>urn:sha1:a0942f950df3b8826db4b1a3f149b7d0ed45adcf</id>
<content type='text'>
This adds an "underline-thickness" setting to the "main" section,
similar to the existing "underline-offset" setting. This setting is used
to specify a custom height for regular (= non-cursor) underlines.

Fixes #1136
</content>
</entry>
</feed>
