<feed xmlns='http://www.w3.org/2005/Atom'>
<title>mirrors/foot.git/terminal.c, branch 1.6.4</title>
<subtitle>A fast, lightweight and minimalistic Wayland terminal emulator</subtitle>
<id>https://git.0x0f.dev/mirrors/foot.git/atom?h=1.6.4</id>
<link rel='self' href='https://git.0x0f.dev/mirrors/foot.git/atom?h=1.6.4'/>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/'/>
<updated>2021-02-12T09:53:10Z</updated>
<entry>
<title>reaper: monitor SIGCHLD using the FDM instead of via a signalfd</title>
<updated>2021-02-12T09:53:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-02-10T15:22:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=79e3a4694365b58b482f2f437052773711ec67dc'/>
<id>urn:sha1:79e3a4694365b58b482f2f437052773711ec67dc</id>
<content type='text'>
In addition to letting the FDM do the low-level signal watching, this
patch also fixes a bug; multiple SIGCHLDs, be it delivered either through a
signal, or via a signalfd, can be coalesced, like all signals.

This means we need to loop on waitpid() with WNOHANG until there are
no more processes to reap.

This in turn requires a small change to the way reaper callbacks are
implemented.

Previously, the callback was allowed to do the wait(). This was
signalled back to the reaper through the callback’s return value.

Now, since we’ve already wait():ed, the process’ exit status is passed
as an argument to the reaper callback.

The callback for the client application has been updated accordingly;
it sets a flag in the terminal struct, telling term_destroy() that the
process has already been wait():ed on, and also stores the exit
status.
</content>
</entry>
<entry>
<title>Send text_input_rectangle requests for text-input</title>
<updated>2021-01-29T18:39:48Z</updated>
<author>
<name>Tadeo Kondrak</name>
<email>me@tadeo.ca</email>
</author>
<published>2020-12-20T22:01:21Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8f0a3ee7a9cbb1b0fc8011875a0895bfd331e0a8'/>
<id>urn:sha1:8f0a3ee7a9cbb1b0fc8011875a0895bfd331e0a8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>terminal: fix encoding of mouse buttons 6 and 7 in mouse events</title>
<updated>2021-01-26T19:41:25Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-01-22T16:03:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=3252131dd4330a5eacd4053f850c249e0b153308'/>
<id>urn:sha1:3252131dd4330a5eacd4053f850c249e0b153308</id>
<content type='text'>
These two buttons were encoded using the *exact* same numbers as
button 4 and 5 (scroll wheel up/down), making it impossible to
distinguish them.

The relevant section from XTerm’s control sequences documentation is:

    Some wheel mice can send additional button events, e.g., by tilting the
    scroll wheel left and right.

    Additional buttons are encoded like the wheel mice,

    o  by adding 64 (for buttons 6 and 7), or

    o  by adding 128 (for buttons 8 through 11).
</content>
</entry>
<entry>
<title>terminal: add/exclude missing headers</title>
<updated>2021-01-23T09:16:23Z</updated>
<author>
<name>Jan Beich</name>
<email>jbeich@FreeBSD.org</email>
</author>
<published>2021-01-19T15:05:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=14e761179b8cdafc6088bf221c8a5f7d70ca56ec'/>
<id>urn:sha1:14e761179b8cdafc6088bf221c8a5f7d70ca56ec</id>
<content type='text'>
terminal.c:3:10: fatal error: 'malloc.h' file not found
 #include &lt;malloc.h&gt;
          ^~~~~~~~~~
terminal.c:1512:9: error: implicit declaration of function 'sigaction' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
        sigaction(SIGALRM, &amp;(const struct sigaction){.sa_handler = &amp;sig_alarm}, NULL);
        ^
terminal.c:1532:21: error: implicit declaration of function 'kill' is invalid in C99 [-Werror,-Wimplicit-function-declaration]
                    kill(term-&gt;slave, kill_signal);
                    ^
</content>
</entry>
<entry>
<title>term: remove client application’s pid from reaper when shutting down</title>
<updated>2021-01-21T10:55:20Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2021-01-12T08:21:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e563c863d174ecdf924ab9bb4fc19a248748e8b8'/>
<id>urn:sha1:e563c863d174ecdf924ab9bb4fc19a248748e8b8</id>
<content type='text'>
When we are shutting down the terminal, we explicitly wait for the
child application to terminate (with a timeout, after which the child
process is killed).

I.e. there’s no need to let the reaper handle it. In fact, doing so
leads to a crash since we will have destroyed (and thus free:d) the
terminal instance when the reaper callback is called.
</content>
</entry>
<entry>
<title>terminal: reaper callback: don’t close ptmx if already closed</title>
<updated>2021-01-21T10:44:06Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-26T00:35:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=981fb0a755f3fb29c5634d3050492426f26f97c9'/>
<id>urn:sha1:981fb0a755f3fb29c5634d3050492426f26f97c9</id>
<content type='text'>
</content>
</entry>
<entry>
<title>terminal: shutdown (or --hold) when the client process terminates</title>
<updated>2021-01-21T10:44:04Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-26T00:29:40Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ce90480011c9d78275a069e0514e9a03813edffc'/>
<id>urn:sha1:ce90480011c9d78275a069e0514e9a03813edffc</id>
<content type='text'>
Shutdown the terminal when the client process terminates, not when the
ptmx file descriptor is closed.

This fixes an issue where the terminal remains running after the
client process has terminated, if it spawned child processes that
inherited the ptmx file descriptor.
</content>
</entry>
<entry>
<title>term: fix builds with debug logging enabled</title>
<updated>2020-12-20T14:43:26Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-18T16:32:54Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=eadc1c58a2a556ba094facf2824433345f7d96c8'/>
<id>urn:sha1:eadc1c58a2a556ba094facf2824433345f7d96c8</id>
<content type='text'>
DPI_AWARE_ON has been renamed to DPI_AWARE_YES
</content>
</entry>
<entry>
<title>fonts: size fonts using the scaling factor when output scaling is enabled</title>
<updated>2020-12-17T11:05:22Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-17T11:05:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0a821f2ed44f46086650a20a39c28f077d954aa2'/>
<id>urn:sha1:0a821f2ed44f46086650a20a39c28f077d954aa2</id>
<content type='text'>
This extends the new ‘dpi-aware’ option with a new default value,
‘auto’.

When set to ‘auto’, fonts are sized using monitors’ DPI when output
scaling is disabled. When output scaling is enabled, fonts are instead
sized using the scaling factor.

The reasoning here is that a user that has enabled output scaling is
obviously *not* relying on DPI scaling.

Output scaling can also be a way to compensate for different viewing
distances, in which case we do *not* want to break that by using DPI
scaling.

Users can still force DPI-only font sizing by setting ‘dpi-aware=yes’,
or disable it completely by setting ‘dpi-aware=no’.
</content>
</entry>
<entry>
<title>term: enabling application synchronized updates clear pending grid refresh</title>
<updated>2020-12-14T18:05:54Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-14T18:05:03Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=6c8b034affae251cdb6645633c1b965c67e78850'/>
<id>urn:sha1:6c8b034affae251cdb6645633c1b965c67e78850</id>
<content type='text'>
This fixes issues with de-synchronized frames being rendered; we may
have scheduled a redraw earlier, that hasn’t yet triggered (probably
because we’re waiting for a frame callback), when we enable
application synchronized updates.

This means we risk rendering a partially updated state when the frame
callback finally arrives, if the application hasn’t yet ended its
synchronized update.
</content>
</entry>
<entry>
<title>config: add ‘notify’ to possible values for ‘bell’ in foot.ini</title>
<updated>2020-12-10T17:22:48Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-10T17:22:48Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=15d20af2a24664b09604f1ec5f121c38f1500c32'/>
<id>urn:sha1:15d20af2a24664b09604f1ec5f121c38f1500c32</id>
<content type='text'>
When `bell=notify`, foot will trigger a desktop notification when it
receives a BEL in an unfocused window.
</content>
</entry>
<entry>
<title>ime: store wchar version of pre-edit string in terminal struct</title>
<updated>2020-12-07T19:44:14Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-06T11:17:52Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=194fbff883e605a3a9afac4ecc66c6cf3cc6b7fa'/>
<id>urn:sha1:194fbff883e605a3a9afac4ecc66c6cf3cc6b7fa</id>
<content type='text'>
</content>
</entry>
<entry>
<title>codespell: currenly -&gt; currently, second instance</title>
<updated>2020-12-07T19:44:11Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-04T19:33:15Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=e3b5a98ade9817a0288bdd4b78263c9961e77241'/>
<id>urn:sha1:e3b5a98ade9817a0288bdd4b78263c9961e77241</id>
<content type='text'>
</content>
</entry>
<entry>
<title>codespell: currenly -&gt; currently</title>
<updated>2020-12-07T19:44:11Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-04T19:08:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=0fc2a1188c2d7400be63debaf16339af49fa804a'/>
<id>urn:sha1:0fc2a1188c2d7400be63debaf16339af49fa804a</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ime: add functions to enable/disable IME, simplify code that enables IME</title>
<updated>2020-12-07T19:44:11Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-04T17:39:11Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=b59d695b2b00157e403399af78b3128848a65e0f'/>
<id>urn:sha1:b59d695b2b00157e403399af78b3128848a65e0f</id>
<content type='text'>
We may want to be able to enable/disable IME run-time, even though we
have received an ‘enter’ IME event.

This enables us to do that.

Also add functions to enable/disable IME on a per-terminal instance
basis.

A terminal may have multiple seats focusing it, and enabling/disabling
IME in a terminal instance enables/disables IME on all those seats.

Finally, the code to enable IME is simplified; the *only* surface that
can ever receive ‘enter’ IME events is the main grid. All other
surfaces are sub-surfaces, without their own keyboard focus.
</content>
</entry>
<entry>
<title>ime: make IME compile-time optional</title>
<updated>2020-12-07T19:44:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-03T17:36:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=05083110c3fad046ccf0838a364150b8d2bab888'/>
<id>urn:sha1:05083110c3fad046ccf0838a364150b8d2bab888</id>
<content type='text'>
</content>
</entry>
<entry>
<title>ime: render pre-edit text</title>
<updated>2020-12-07T19:44:10Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-12-02T17:52:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=8c3d48c5cdb2ae4e8bdbdc48f155f53d1a92973b'/>
<id>urn:sha1:8c3d48c5cdb2ae4e8bdbdc48f155f53d1a92973b</id>
<content type='text'>
This is done by allocating cells for the pre-edit text when receiving
the text-input::done() call, and populating them by converting the
utf-8 formatted pre-edit text to wchars.

We also convert the pre-edit cursor position to cell positions (it can
cover multiple cells).

When rendering, we simply render the pre-edit cells on-top off the
regular grid. While doing so, we also mark the underlying, “real”,
cells as dirty, to ensure they are re-rendered when the pre-edit text
is modified or removed.
</content>
</entry>
<entry>
<title>csi: add new private mode that makes the Escape key emit "\E[27;1;27~"</title>
<updated>2020-11-29T04:04:57Z</updated>
<author>
<name>Craig Barnes</name>
<email>craigbarnes@protonmail.com</email>
</author>
<published>2020-11-29T04:04:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=31c73f0cf01e1d0bdcd1435136b010c1c1ab442c'/>
<id>urn:sha1:31c73f0cf01e1d0bdcd1435136b010c1c1ab442c</id>
<content type='text'>
This mode can be set by client programs with the DECSET, DECRST,
XTSAVE and XTRESTORE sequences by using 27127 as the parameter.

The sequence "\E[27;1;27~" is encoded in the same way as is done by
xterm's "modifyOtherKeys" mode. Even though xterm itself never emits
such a sequence for the Escape key, many programs already have
support for parsing this style of key sequence.
</content>
</entry>
<entry>
<title>term: remove read-only properties copied from the config</title>
<updated>2020-11-26T17:08:28Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-11-26T17:08:28Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=360cc8e6de8802015b3a4a744289c311beb8d82d'/>
<id>urn:sha1:360cc8e6de8802015b3a4a744289c311beb8d82d</id>
<content type='text'>
Use the config directly instead.
</content>
</entry>
<entry>
<title>sixel: change default max size to 10000x10000</title>
<updated>2020-11-23T19:10:55Z</updated>
<author>
<name>Daniel Eklöf</name>
<email>daniel@ekloef.se</email>
</author>
<published>2020-11-23T19:10:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0x0f.dev/mirrors/foot.git/commit/?id=ba8b15d67592c3dfde264ccd441699377948c4cf'/>
<id>urn:sha1:ba8b15d67592c3dfde264ccd441699377948c4cf</id>
<content type='text'>
It used to be the size of the window. This caused images to be cropped
when the application emitting them didn’t change the max size.
</content>
</entry>
</feed>
