mirrors/foot
1
0
Fork 0
mirror of https://codeberg.org/dnkl/foot.git synced 2026-02-05 04:06:08 -05:00
Code Issues Projects Releases Packages Wiki Activity Actions
foot/CHANGELOG.md

2546 lines
95 KiB
Markdown
Raw Normal View History

changelog: template
2020-03-06 19:45:04 +01:00
# Changelog
changelog: add new 'unreleased' section
2023-10-11 18:19:31 +02:00
* [Unreleased](#unreleased)
changelog: prepare for 1.16.0
2023-10-11 18:14:40 +02:00
* [1.16.0](#1-16-0)
changelog: prepare for 1.15.3
2023-08-07 16:39:42 +02:00
* [1.15.3](#1-15-3)
changelog: prepare for 1.15.2
2023-07-30 13:18:41 +02:00
* [1.15.2](#1-15-2)
changelog: prepare for 1.15.1
2023-07-21 08:56:49 +02:00
* [1.15.1](#1-15-1)
changelog: prepare for 1.15.0
2023-07-14 12:25:16 +02:00
* [1.15.0](#1-15-0)
changelog: prepare for 1.14.0
2023-04-03 18:52:22 +02:00
* [1.14.0](#1-14-0)
changelog: prepare for 1.13.1
2022-08-31 19:17:38 +02:00
* [1.13.1](#1-13-1)
changelog: prepare for 1.13.0
2022-08-07 09:31:56 +02:00
* [1.13.0](#1-13-0)
changelog: prepare for 1.12.1
2022-04-27 20:05:51 +02:00
* [1.12.1](#1-12-1)
changelog: prepare for 1.12.0
2022-04-22 17:14:00 +02:00
* [1.12.0](#1-12-0)
changelog: prepare for 1.11.0
2022-02-05 17:19:43 +01:00
* [1.11.0](#1-11-0)
changelog: prepare for 1.10.3
2021-12-08 18:08:45 +01:00
* [1.10.3](#1-10-3)
changelog: prepare for 1.10.2
2021-12-02 20:26:42 +01:00
* [1.10.2](#1-10-2)
changelog: prepare for 1.10.1
2021-11-22 21:56:38 +01:00
* [1.10.1](#1-10-1)
changelog: prepare for 1.10.0
2021-11-14 18:10:43 +01:00
* [1.10.0](#1-10-0)
changelog: prepare for 1.9.2
2021-10-02 14:46:42 +02:00
* [1.9.2](#1-9-2)
changelog: prepare for 1.9.1
2021-10-01 20:52:19 +02:00
* [1.9.1](#1-9-1)
changelog: prepare for 1.9.0
2021-08-27 12:45:22 +02:00
* [1.9.0](#1-9-0)
changelog: prepare for 1.8.2
2021-07-18 17:57:42 +02:00
* [1.8.2](#1-8-2)
changelog: prepare for 1.8.1
2021-07-01 20:14:20 +02:00
* [1.8.1](#1-8-1)
changelog: prepare for 1.8.0
2021-06-25 08:23:36 +02:00
* [1.8.0](#1-8-0)
changelog: prepare for 1.7.2
2021-04-18 20:12:26 +02:00
* [1.7.2](#1-7-2)
changelog: prepare for 1.7.1
2021-03-28 14:25:09 +02:00
* [1.7.1](#1-7-1)
changelog: 1.7.0
2021-03-20 14:02:12 +01:00
* [1.7.0](#1-7-0)
changelog: add section for 1.6.4
2021-02-12 10:44:42 +01:00
* [1.6.4](#1-6-4)
changelog: add empty 1.6.3 section
2021-01-21 11:43:22 +01:00
* [1.6.3](#1-6-3)
meson/pkgbuild: bump version to 1.6.2
2020-12-21 15:58:25 +01:00
* [1.6.2](#1-6-2)
changelog: add 1.6.1 section
2020-12-20 15:46:05 +01:00
* [1.6.1](#1-6-1)
changelog: fix link to "1.6.0" heading
2020-12-19 22:50:18 +00:00
* [1.6.0](#1-6-0)
changelog: add entry for 1.5.4
2020-12-01 19:33:22 +01:00
* [1.5.4](#1-5-4)
changelog: prepare for 1.5.3
2020-11-06 20:06:31 +01:00
* [1.5.3](#1-5-3)
input: regression: don’t pass on mouse click to application if we consumed it When we ‘consume’ a mouse button event (i.e. when we have a shortcut mapped to it), the event should *not* be passed on to the client application. In 5f64c5c33590a41afd3f621870c6abd89b859073, button handling was refactored and unfortunately introduced a regression where we once again started passing consumed button presses to the client application. Fixes #168
2020-10-13 08:02:09 +02:00
* [1.5.2](#1-5-2)
changelog: prepare for 1.5.1
2020-10-11 19:31:01 +02:00
* [1.5.1](#1-5-1)
changelog: prepare for 1.5.0
2020-09-18 21:22:59 +02:00
* [1.5.0](#1-5-0)
changelog: add 1.4.4 section
2020-07-29 06:55:23 +02:00
* [1.4.4](#1-4-4)
changelog: prepare for 1.4.3
2020-07-27 18:55:12 +02:00
* [1.4.3](#1-4-3)
* [1.4.2](#1-4-2)
changelog: prepare or 1.4.1
2020-07-22 20:03:28 +02:00
* [1.4.1](#1-4-1)
changelog: prepare for 1.4.0
2020-07-22 18:59:19 +02:00
* [1.4.0](#1-4-0)
changelog 1.3.0
2020-05-13 13:09:12 +02:00
* [1.3.0](#1-3-0)
changelog: add index
2020-03-15 11:39:11 +01:00
* [1.2.3](#1-2-3)
* [1.2.2](#1-2-2)
* [1.2.1](#1-2-1)
* [1.2.0](#1-2-0)
changelog: add new ‘unreleased’ section
2020-09-18 21:29:39 +02:00
changelog: add new 'unreleased' section
2023-10-11 18:19:31 +02:00
## Unreleased
### Added
### Changed
### Deprecated
### Removed
### Fixed
shm: memfd_create: fallback to not using MFD_NOEXEC_SEAL MFD_NOEXEC_SEAL was introduced in linux 6.3. Kernels before that will *reject* memfd_create() calls that set it. This caused foot to exit (i.e. not start at all), when compiled on linux >= 6.3, but run on linux < 6.3. We _do_ want to use MFD_NOEXEC_SEAL, since a) our memory mapped really shouldn't be executable, and b) to silence a warning on linux >= 6.3. To handle all cases, first try *with* MFD_NOEXEC_SEAL. If that fails with EINVAL, retry *without* it. Closes #1514
2023-10-12 16:16:11 +02:00
* Foot not starting on linux kernels before 6.3 ([#1514][1514]).
[1514]: https://codeberg.org/dnkl/foot/issues/1514
changelog: add new 'unreleased' section
2023-10-11 18:19:31 +02:00
### Security
### Contributors
changelog: prepare for 1.16.0
2023-10-11 18:14:40 +02:00
## 1.16.0
changelog: add new ‘unreleased section’
2023-07-30 13:27:42 +02:00
### Added
meson: allow building with wayland-protocols as a subproject
2023-08-08 19:32:45 +02:00
* Support for building with _wayland-protocols_ as a subproject.
input: make wheel events mappable Un-grabbed wheel events are now passed through the mouse binding matching logic, instead of being hardcoded to scrolling the terminal contents. They are mappable through the BTN_BACK and BTN_FORWARD buttons. Since they're not actually button *presses*, they never generate a click count other than 1. This limitation is documented, but not checked in the config. This means it's possible to create bindings like "BTN_BACK+3" (i.e. triple "click"). They will however never trigger. The old, hardcoded logic is now accessible through the new scrollback-up-mouse and scrollback-down-mouse mouse bindings. They (obiously) default to BTN_BACK and BTN_FORWARD, respectively. Example usage: keep the default of scrolling terminal contents with the wheel, when used without modifiers, but map Control+wheel to font zoom in/out: [mouse-bindings] font-increase=Control+BTN_FORWARD font-decrease=Control+BTN_BACK (this also keeps the default key bindings to zoom in/out; ctrl-+ and ctrl+-) Closes #1077
2023-09-18 16:36:39 +02:00
* Mouse wheel scrolls can now be used in `mouse-bindings`
changelog: fix link to issue 1077
2023-10-11 18:39:43 +02:00
([#1077][1077]).
input: make wheel events mappable Un-grabbed wheel events are now passed through the mouse binding matching logic, instead of being hardcoded to scrolling the terminal contents. They are mappable through the BTN_BACK and BTN_FORWARD buttons. Since they're not actually button *presses*, they never generate a click count other than 1. This limitation is documented, but not checked in the config. This means it's possible to create bindings like "BTN_BACK+3" (i.e. triple "click"). They will however never trigger. The old, hardcoded logic is now accessible through the new scrollback-up-mouse and scrollback-down-mouse mouse bindings. They (obiously) default to BTN_BACK and BTN_FORWARD, respectively. Example usage: keep the default of scrolling terminal contents with the wheel, when used without modifiers, but map Control+wheel to font zoom in/out: [mouse-bindings] font-increase=Control+BTN_FORWARD font-decrease=Control+BTN_BACK (this also keeps the default key bindings to zoom in/out; ctrl-+ and ctrl+-) Closes #1077
2023-09-18 16:36:39 +02:00
* New mouse bindings: `scrollback-up-mouse` and
`scrollback-down-mouse`, bound to `BTN_BACK` and `BTN_FORWARD`
respectively.
selection: add support for selecting the contents of a quote This patch changes the default of triple clicking, from selecting the current logical row, to first trying to select the contents of the quote under the cursor, and if failing to find a quote, selecting the current row (like before). This is implemented by adding a new key binding, 'select-quote'. It will search for surrounding quote characters, and if one is found on each side of the cursor, the quote is selected. If not, the entire row is selected instead. Subsequent selection operations will behave as if the selection is either a word selection (a quote was found), or a row selection (no quote found). Escaped quote characters are not supported: "foo \" bar" will match 'foo \', and not 'foo " bar'. Mismatched quotes are not custom handled. They will simply not match. Nested quotes ("123 'abc def' 456") are supported. Closes #1364
2023-09-19 16:23:34 +02:00
* New key binding: `select-quote`. This key binding selects text
between quote characters, and falls back to selecting the entire
row ([#1364][1364]).
csi: implement DECSET/DECRST/DECRQM 2027 - grapheme cluster processing This implements private mode 2027 - grapheme cluster processing, as defined in the "Terminal Unicode Core"[1] specification. Internally, we just flip the already existing option "grapheme shaping". Since it's now runtime changeable, we need a copy of it in the terminal struct, rather than referencing the conf object. [1]: https://github.com/contour-terminal/terminal-unicode-core/blob/13fc5a8993a033ff10c1f3433d08cb618cde4ac2/spec/terminal-unicode-core.tex#L50-L53
2023-09-20 13:45:06 +02:00
* Support for DECSET/DECRST/DECRQM 2027 (_Grapheme cluster
processing_).
changelog: emphasize the new key bindings are for search mode
2023-10-11 18:12:18 +02:00
* New **search mode** key bindings (along with their defaults)
search: add more key bindings to extend the current match This patch adds the following new search key bindings: * extend-char (shift+right) * extend-line-down (shift+down) * extend-backward-char (shift+left) * extend-backward-to-word-boundary (ctrl+shift+left) * extend-backward-to-next-whitespace (ctrl+shift+alt+left) * extend-line-up (shift+up) They can be used to extend the search match (i.e. the selection). This patch also adds an initial set of key bindings to scroll in the scrollback history: * scrollback-up-page * scrollback-down-page These work just like the key bindings for the normal mode. Also note that it was already possible to scroll using the mouse. This patch also fixes a couple of search mode bugs: * crashing when a search match ends in the last column * grapheme clusters not being matched correctly * Search match not being "extendable" after a pointer leave event * A few others, related to either large matches, or extending matches after moving the viewport. There are still a couple of (known) issues: * A search match isn't correctly highlighted if its *starting* point is outside the viewport. * Extending the match to end of the scrollback (i.e. the most recent output) is simply buggy. Related to #419
2023-09-26 17:54:03 +02:00
([#419][419]):
- `extend-char` (shift+right)
- `extend-line-down` (shift+down)
- `extend-backward-char` (shift+left)
- `extend-backward-to-word-boundary` (ctrl+shift+left)
changelog: add the remaining scrollback-up/down bindings
2023-10-08 10:39:57 +02:00
- `extend-backward-to-next-whitespace` (none)
search: add more key bindings to extend the current match This patch adds the following new search key bindings: * extend-char (shift+right) * extend-line-down (shift+down) * extend-backward-char (shift+left) * extend-backward-to-word-boundary (ctrl+shift+left) * extend-backward-to-next-whitespace (ctrl+shift+alt+left) * extend-line-up (shift+up) They can be used to extend the search match (i.e. the selection). This patch also adds an initial set of key bindings to scroll in the scrollback history: * scrollback-up-page * scrollback-down-page These work just like the key bindings for the normal mode. Also note that it was already possible to scroll using the mouse. This patch also fixes a couple of search mode bugs: * crashing when a search match ends in the last column * grapheme clusters not being matched correctly * Search match not being "extendable" after a pointer leave event * A few others, related to either large matches, or extending matches after moving the viewport. There are still a couple of (known) issues: * A search match isn't correctly highlighted if its *starting* point is outside the viewport. * Extending the match to end of the scrollback (i.e. the most recent output) is simply buggy. Related to #419
2023-09-26 17:54:03 +02:00
- `extend-line-up` (shift+up)
- `scrollback-up-page` (shift+page-up)
changelog: add the remaining scrollback-up/down bindings
2023-10-08 10:39:57 +02:00
- `scrollback-up-half-page` (none)
- `scrollback-up-line` (none)
search: add more key bindings to extend the current match This patch adds the following new search key bindings: * extend-char (shift+right) * extend-line-down (shift+down) * extend-backward-char (shift+left) * extend-backward-to-word-boundary (ctrl+shift+left) * extend-backward-to-next-whitespace (ctrl+shift+alt+left) * extend-line-up (shift+up) They can be used to extend the search match (i.e. the selection). This patch also adds an initial set of key bindings to scroll in the scrollback history: * scrollback-up-page * scrollback-down-page These work just like the key bindings for the normal mode. Also note that it was already possible to scroll using the mouse. This patch also fixes a couple of search mode bugs: * crashing when a search match ends in the last column * grapheme clusters not being matched correctly * Search match not being "extendable" after a pointer leave event * A few others, related to either large matches, or extending matches after moving the viewport. There are still a couple of (known) issues: * A search match isn't correctly highlighted if its *starting* point is outside the viewport. * Extending the match to end of the scrollback (i.e. the most recent output) is simply buggy. Related to #419
2023-09-26 17:54:03 +02:00
- `scrollback-down-page` (shift+page-down)
changelog: add the remaining scrollback-up/down bindings
2023-10-08 10:39:57 +02:00
- `scrollback-down-half-page` (none)
- `scrollback-down-line` (none)
Enable the use of flash as visual bell With this patch we can configure flash in the bell section. The colors section allow now to configure the color and translucency of the flash.
2023-10-07 19:37:04 +02:00
* Support for visual bell which flashes the terminal window.
changelog: fix issue number for visual bell 1508 refers to the pull request, not the feature request.
2023-10-10 08:14:43 +02:00
([#1337][1337]).
input: make wheel events mappable Un-grabbed wheel events are now passed through the mouse binding matching logic, instead of being hardcoded to scrolling the terminal contents. They are mappable through the BTN_BACK and BTN_FORWARD buttons. Since they're not actually button *presses*, they never generate a click count other than 1. This limitation is documented, but not checked in the config. This means it's possible to create bindings like "BTN_BACK+3" (i.e. triple "click"). They will however never trigger. The old, hardcoded logic is now accessible through the new scrollback-up-mouse and scrollback-down-mouse mouse bindings. They (obiously) default to BTN_BACK and BTN_FORWARD, respectively. Example usage: keep the default of scrolling terminal contents with the wheel, when used without modifiers, but map Control+wheel to font zoom in/out: [mouse-bindings] font-increase=Control+BTN_FORWARD font-decrease=Control+BTN_BACK (this also keeps the default key bindings to zoom in/out; ctrl-+ and ctrl+-) Closes #1077
2023-09-18 16:36:39 +02:00
[1077]: https://codeberg.org/dnkl/foot/issues/1077
selection: add support for selecting the contents of a quote This patch changes the default of triple clicking, from selecting the current logical row, to first trying to select the contents of the quote under the cursor, and if failing to find a quote, selecting the current row (like before). This is implemented by adding a new key binding, 'select-quote'. It will search for surrounding quote characters, and if one is found on each side of the cursor, the quote is selected. If not, the entire row is selected instead. Subsequent selection operations will behave as if the selection is either a word selection (a quote was found), or a row selection (no quote found). Escaped quote characters are not supported: "foo \" bar" will match 'foo \', and not 'foo " bar'. Mismatched quotes are not custom handled. They will simply not match. Nested quotes ("123 'abc def' 456") are supported. Closes #1364
2023-09-19 16:23:34 +02:00
[1364]: https://codeberg.org/dnkl/foot/issues/1364
search: add more key bindings to extend the current match This patch adds the following new search key bindings: * extend-char (shift+right) * extend-line-down (shift+down) * extend-backward-char (shift+left) * extend-backward-to-word-boundary (ctrl+shift+left) * extend-backward-to-next-whitespace (ctrl+shift+alt+left) * extend-line-up (shift+up) They can be used to extend the search match (i.e. the selection). This patch also adds an initial set of key bindings to scroll in the scrollback history: * scrollback-up-page * scrollback-down-page These work just like the key bindings for the normal mode. Also note that it was already possible to scroll using the mouse. This patch also fixes a couple of search mode bugs: * crashing when a search match ends in the last column * grapheme clusters not being matched correctly * Search match not being "extendable" after a pointer leave event * A few others, related to either large matches, or extending matches after moving the viewport. There are still a couple of (known) issues: * A search match isn't correctly highlighted if its *starting* point is outside the viewport. * Extending the match to end of the scrollback (i.e. the most recent output) is simply buggy. Related to #419
2023-09-26 17:54:03 +02:00
[419]: https://codeberg.org/dnkl/foot/issues/419
changelog: fix issue number for visual bell 1508 refers to the pull request, not the feature request.
2023-10-10 08:14:43 +02:00
[1337]: https://codeberg.org/dnkl/foot/issues/1337
meson: allow building with wayland-protocols as a subproject
2023-08-08 19:32:45 +02:00
changelog: add new ‘unreleased section’
2023-07-30 13:27:42 +02:00
### Changed
meson: require wayland-protocols >= 1.32
2023-07-31 16:32:06 +02:00
* Minimum required version of _wayland-protocols_ is now 1.32
([#1391][1391]).
changelog: systemd units in GNOME
2023-07-29 20:54:59 +02:00
* `foot-server.service` systemd now checks for
`ConditionEnvironment=WAYLAND_DISPLAY` for consistency with the
socket unit ([#1448][1448])
selection: add support for selecting the contents of a quote This patch changes the default of triple clicking, from selecting the current logical row, to first trying to select the contents of the quote under the cursor, and if failing to find a quote, selecting the current row (like before). This is implemented by adding a new key binding, 'select-quote'. It will search for surrounding quote characters, and if one is found on each side of the cursor, the quote is selected. If not, the entire row is selected instead. Subsequent selection operations will behave as if the selection is either a word selection (a quote was found), or a row selection (no quote found). Escaped quote characters are not supported: "foo \" bar" will match 'foo \', and not 'foo " bar'. Mismatched quotes are not custom handled. They will simply not match. Nested quotes ("123 'abc def' 456") are supported. Closes #1364
2023-09-19 16:23:34 +02:00
* Default key binding for `select-row` is now `BTN_LEFT+4`. However,
in many cases, triple clicking will still be enough to select the
entire row; see the new key binding `select-quote` (mapped to
`BTN_LEFT+3` by default) ([#1364][1364]).
url-mode: don't strip the file:// prefix from localhost URIs Before this patch, the file://<host> prefix was stripped from URIs, when the hostname matched the current host (that is, for "local" URLs). Unfortunately, the way this was done caused other parts of the URI to be stripped as well. For example, the 'query' and 'fragment' parts. This patch simply removes all special casing of file:// URIs. Since the URL is passed to a generic opener (i.e. we don't have a special opener application for file:// URIs), the opener helper must handle the file:// prefix anyway. Closes #1474
2023-09-20 15:29:35 +02:00
* `file://` prefix from URI's are no longer stripped when
opened/activated ([#1474][1474]).
dcs: xtgettcap: ignore queries with invalid hex encodings When we receive an XTGETTCAP query, where the capability is not correctly hex encoded, ignore it. Before this patch, we echo:ed it back to the TTY inside an error resonse.
2023-09-25 16:37:32 +02:00
* `XTGETTCAP` with capabilities that are not properly hex encoded will
be ignored, instead of echo:ed back to the TTY in an error response.
config: apply overrides even if there's no file Previously, foot -a test wouldn't actually set the app ID if there was no config file and the defaults were used, which was very counterintuitive. Now, load_config() will carry on until the end, even if there's no config file, so overrides still work.
2023-09-22 08:23:38 +00:00
* Command line configuration overrides are now applied even if the
configuration file does not exist or can't be
parsed. ([#1495][1495]).
render: more fine-grained wayland surface damage tracking Before this patch. Wayland surface damage tracking was done on a per-row basis. That is, even if just one cell was updated, the entire row was "damaged". Now, damage is per cell. This hopefully results in lower latencies in many use cases, and especially on high DPI monitors.
2023-10-07 16:23:09 +02:00
* Wayland surface damage is now more fine-grained. This should result
in lower latencies in many use cases, especially on high DPI
monitors.
meson: require wayland-protocols >= 1.32
2023-07-31 16:32:06 +02:00
[1391]: https://codeberg.org/dnkl/foot/issues/1391
changelog: systemd units in GNOME
2023-07-29 20:54:59 +02:00
[1448]: https://codeberg.org/dnkl/foot/pulls/1448
url-mode: don't strip the file:// prefix from localhost URIs Before this patch, the file://<host> prefix was stripped from URIs, when the hostname matched the current host (that is, for "local" URLs). Unfortunately, the way this was done caused other parts of the URI to be stripped as well. For example, the 'query' and 'fragment' parts. This patch simply removes all special casing of file:// URIs. Since the URL is passed to a generic opener (i.e. we don't have a special opener application for file:// URIs), the opener helper must handle the file:// prefix anyway. Closes #1474
2023-09-20 15:29:35 +02:00
[1474]: https://codeberg.org/dnkl/foot/pulls/1474
config: apply overrides even if there's no file Previously, foot -a test wouldn't actually set the app ID if there was no config file and the defaults were used, which was very counterintuitive. Now, load_config() will carry on until the end, even if there's no config file, so overrides still work.
2023-09-22 08:23:38 +00:00
[1495]: https://codeberg.org/dnkl/foot/pulls/1495
meson: require wayland-protocols >= 1.32
2023-07-31 16:32:06 +02:00
changelog: add new ‘unreleased section’
2023-07-30 13:27:42 +02:00
### Removed
config: remove deprecated option 'utempter'
2023-07-31 16:28:07 +02:00
changelog: “config” -> “config option”
2023-08-05 07:25:36 +02:00
* `utempter` config option (was deprecated in 1.15.0).
config: remove deprecated option 'utempter'
2023-07-31 16:28:07 +02:00
Merge branch 'releases/1.15'
2023-08-07 16:44:24 +02:00
### Fixed
changelog: systemd units in GNOME
2023-07-29 20:54:59 +02:00
* Race condition for systemd units start in GNOME and KDE
([#1436][1436]).
term: improve fallback logic when selecting scaling factor while unmapped The foot window may, for various reasons, become completely unmapped (that is, being removed from all outputs) at run time. One example is wlroots based compositors; they unmap all other windows when an opaque window is fullscreened. 21d99f8dced335826964ca96b8ba7ccac059e598 introduced a regression, where instead of picking the scaling factor from one of the available outputs (at random), we started falling back to '1' as soon as we were unmapped. This patch restores the original logic, but also improves upon it. As soon as a scaling factor has been assigned to the window, we store a copy of it in the term struct ('scale_before_unmap'). When unmapped, we check if it has a valid value (the only time it doesn't is before the initial map). If so, we use it. Only if it hasn't been set do we fall back to picking an output at random, and using its scaling factor. Closes #1464
2023-08-18 16:39:00 +02:00
* One frame being rendered at the wrong scale after being hidden by
another opaque, maximized window ([#1464][1464]).
url-mode: handle wide chars and grapheme clusters when auto-detecting URLs * Skip spacer cells. This fixes an issue where characters following a double-width character weren't detect properly. * Unpack grapheme clusters (i.e. cells with multiple codepoints), and iterate all their codepoints. Closes #1465
2023-08-21 16:26:18 +02:00
* Double-width characters, and grapheme clusters breaking URL
auto-detection ([#1465][1465]).
changelog: crash when xdg token is set, but compositor does not support activation
2023-09-21 18:31:46 +02:00
* Crash when `XDG_ACTIVATION_TOKEN` is set, but compositor does not
support XDG activation ([#1493][1493]).
term: get_font_dpi(): don't crash when there aren't any available monitors Seen on plasma; monitor is turned off, and then back on again. Before the "new" output global is emitted, the compositor calls fractional_scale::preferred_scale(). This results in a call to get_font_dpi(), where we crash, since it assumes there is at least one monitor available. Fix by falling back to a DPI of 96. Hopefully closes #1498
2023-10-01 09:20:13 +02:00
* Crash when compositor calls `fractional_scale::preferred_scale()`
when there are no monitors (for example, after a monitor has been
turned off and then back on again) ([#1498][1498]).
render: disable transparency in margins when in fullscreen This amends 899b768b744c74e88e54e6d8eb32f53accea79d8, where we started disabling transparency in fullscreen Closes #1503
2023-10-07 07:58:55 +02:00
* Transparency in margins (padding) not being disabled in fullscreen
mode ([#1503][1503]).
search: add more key bindings to extend the current match This patch adds the following new search key bindings: * extend-char (shift+right) * extend-line-down (shift+down) * extend-backward-char (shift+left) * extend-backward-to-word-boundary (ctrl+shift+left) * extend-backward-to-next-whitespace (ctrl+shift+alt+left) * extend-line-up (shift+up) They can be used to extend the search match (i.e. the selection). This patch also adds an initial set of key bindings to scroll in the scrollback history: * scrollback-up-page * scrollback-down-page These work just like the key bindings for the normal mode. Also note that it was already possible to scroll using the mouse. This patch also fixes a couple of search mode bugs: * crashing when a search match ends in the last column * grapheme clusters not being matched correctly * Search match not being "extendable" after a pointer leave event * A few others, related to either large matches, or extending matches after moving the viewport. There are still a couple of (known) issues: * A search match isn't correctly highlighted if its *starting* point is outside the viewport. * Extending the match to end of the scrollback (i.e. the most recent output) is simply buggy. Related to #419
2023-09-26 17:54:03 +02:00
* Crash when a scrollback search match is in the last column.
* Scrollback search: grapheme clusters not matching correctly.
changelog: fixed font baseline calculation
2023-10-10 10:55:26 +02:00
* Wrong baseline offset for some fonts ([#1511][1511]).
changelog: systemd units in GNOME
2023-07-29 20:54:59 +02:00
[1436]: https://codeberg.org/dnkl/foot/issues/1436
term: improve fallback logic when selecting scaling factor while unmapped The foot window may, for various reasons, become completely unmapped (that is, being removed from all outputs) at run time. One example is wlroots based compositors; they unmap all other windows when an opaque window is fullscreened. 21d99f8dced335826964ca96b8ba7ccac059e598 introduced a regression, where instead of picking the scaling factor from one of the available outputs (at random), we started falling back to '1' as soon as we were unmapped. This patch restores the original logic, but also improves upon it. As soon as a scaling factor has been assigned to the window, we store a copy of it in the term struct ('scale_before_unmap'). When unmapped, we check if it has a valid value (the only time it doesn't is before the initial map). If so, we use it. Only if it hasn't been set do we fall back to picking an output at random, and using its scaling factor. Closes #1464
2023-08-18 16:39:00 +02:00
[1464]: https://codeberg.org/dnkl/foot/issues/1464
url-mode: handle wide chars and grapheme clusters when auto-detecting URLs * Skip spacer cells. This fixes an issue where characters following a double-width character weren't detect properly. * Unpack grapheme clusters (i.e. cells with multiple codepoints), and iterate all their codepoints. Closes #1465
2023-08-21 16:26:18 +02:00
[1465]: https://codeberg.org/dnkl/foot/issues/1465
changelog: crash when xdg token is set, but compositor does not support activation
2023-09-21 18:31:46 +02:00
[1493]: https://codeberg.org/dnkl/foot/pulls/1493
term: get_font_dpi(): don't crash when there aren't any available monitors Seen on plasma; monitor is turned off, and then back on again. Before the "new" output global is emitted, the compositor calls fractional_scale::preferred_scale(). This results in a call to get_font_dpi(), where we crash, since it assumes there is at least one monitor available. Fix by falling back to a DPI of 96. Hopefully closes #1498
2023-10-01 09:20:13 +02:00
[1498]: https://codeberg.org/dnkl/foot/issues/1498
render: disable transparency in margins when in fullscreen This amends 899b768b744c74e88e54e6d8eb32f53accea79d8, where we started disabling transparency in fullscreen Closes #1503
2023-10-07 07:58:55 +02:00
[1503]: https://codeberg.org/dnkl/foot/issues/1503
changelog: fixed font baseline calculation
2023-10-10 10:55:26 +02:00
[1511]: https://codeberg.org/dnkl/foot/issues/1511
changelog: systemd units in GNOME
2023-07-29 20:54:59 +02:00
Merge branch 'releases/1.15'
2023-08-07 16:44:24 +02:00
### Contributors
changelog: prepare for 1.16.0
2023-10-11 18:14:40 +02:00
* 6t8k
* Alyssa Ross
* CismonX
* Max Gautier
* raggedmyth
* Raimund Sacherer
* Sertonix
Merge branch 'releases/1.15'
2023-08-07 16:44:24 +02:00
changelog: prepare for 1.15.3
2023-08-07 16:39:42 +02:00
## 1.15.3
changelog: add new ‘unreleased section’
2023-07-30 13:27:42 +02:00
### Fixed
main: translate command line options to overrides Instead of special casing configuration affecting command line options (like --font, --fullscreen, --maximized etc), translate them to overrides, and let the configuration system handle them. This also fixes an issue where -f,--font did not set csd.font, if csd.font were otherwise unset.
2023-07-31 16:26:17 +02:00
* `-f,--font` command line option not affecting `csd.font` (if unset).
render: OSD: center text vertically Rewrite render_osd(), and instead of passing in an y-offset, let render_osd() itself center the text inside the OSD buffer. This is done using the same baseline calculation term_font_baseline() does, except we use the buffer height instead of the line height. Note that most OSDs are sized based on the line height... Closes #1430
2023-07-31 16:29:08 +02:00
* Vertical alignment in URL jump labels, and the scrollback position
indicator. The fix in 1.15.2 was incorrect, and was reverted in the
last minute. But we forgot to remove the entry from the changelog
([#1430][1430]).
main: translate command line options to overrides Instead of special casing configuration affecting command line options (like --font, --fullscreen, --maximized etc), translate them to overrides, and let the configuration system handle them. This also fixes an issue where -f,--font did not set csd.font, if csd.font were otherwise unset.
2023-07-31 16:26:17 +02:00
changelog: prepare for 1.15.2
2023-07-30 13:18:41 +02:00
## 1.15.2
changelog: add new ‘unreleased’ section
2023-07-21 09:00:57 +02:00
### Added
config: add tweak.bold-text-in-bright-amount By how much to increase the luminance when brightening bold fonts. This was previously hard-coded to a factor of 1.3, which is now the default value of the new config option. Closes #1434
2023-07-26 16:12:36 +02:00
* `[tweak].bold-text-in-bright-amount` option ([#1434][1434]).
meson: add -Dterminfo-base-name option This defines the base name of the generated terminfo files. It defaults to the value of -Ddefault-terminfo (i.e. 'foot') Example: meson -Ddefault-terminfo=foot-bananas -Dterminfo-base-name=foot-apples The generated terminfo files will be * terminfo/f/foot-apples * terminfo/f/foot-apples-direct The default value of $TERM will be 'foot-bananas'
2023-07-26 16:14:38 +02:00
* `-Dterminfo-base-name` meson option, allowing you to name the
terminfo files to something other than `-Ddefault-terminfo`. Use
case: have foot default to using the terminfo from ncurses (`foot`,
`foot-direct`), while still packaging foot's terminfo files, but
under a different name (e.g. `foot-extra`, `foot-extra-direct`).
config: add tweak.bold-text-in-bright-amount By how much to increase the luminance when brightening bold fonts. This was previously hard-coded to a factor of 1.3, which is now the default value of the new config option. Closes #1434
2023-07-26 16:12:36 +02:00
[1434]: https://codeberg.org/dnkl/foot/issues/1434
changelog: add new ‘unreleased’ section
2023-07-21 09:00:57 +02:00
### Fixed
changelog: ignore invalid UTF-8 in input
2023-07-22 11:23:22 +02:00
* Crash when copying text that contains invalid UTF-8 ([#1423][1423]).
wayland: update terminals (fonts etc) on xdg_output_handle_done() Monitor DPI depends on information from both the wl_output and the xdg_output interfaces. Before this patch, terminals were only updated after changes to the wl_output interfaces (thus depending on xdg output changes being pushed by the compositor before wl_output changes). That assumption (xdg_output happening before wl_output) isn’t always true. This patch fixes the issue by updating the terminals in the xdg_output’s “done” event. Closes #1431
2023-07-23 20:03:31 +02:00
* Wrong font size after suspending the monitor ([#1431][1431]).
render: apply new baseline calculation everywhere * URL jump labels * Scrollback position indicator * Line/box drawings characters Closes #1430
2023-07-23 17:35:57 +02:00
* Vertical alignment in URL jump labels, and the scrollback position
indicator ([#1430][1430]).
* Regression: line- and box drawing characters not covering the full
height of the line, when a custom `line-height` is being used
([#1430][1430]).
wayland: don't try to use a non-existing viewporter interface When instantiating the viewport for a pointer surface, we didn't first check if the compositor implements the viewporter interface. This triggered a crash when a) foot was compiled with fractional scaling, and b) the compositor did not implement the viewporter interface. Closes #1444
2023-07-28 15:32:42 +02:00
* Crash when compositor does not implement the _viewporter_ interface
([#1444][1444]).
changelog: CSDs with fractional scaling
2023-07-29 09:09:59 +02:00
* CSD rendering with fractional scaling ([#1441][1441]).
--window-size-chars: ensure width/height are valid for current scaling factor Before this patch, we didn’t ensure width and height were valid for the current scaling factor, when fractional scaling _is_ available. That is, we didn’t ensure the width/height values multiplied back to their original values after dividing with the scaling factor. Closes #1446
2023-07-30 07:53:33 +02:00
* Regression: crash with certain combinations of
`--window-size-chars=NxM` and desktop scaling factors
([#1446][1446]).
changelog: ignore invalid UTF-8 in input
2023-07-22 11:23:22 +02:00
[1423]: https://codeberg.org/dnkl/foot/issues/1423
wayland: update terminals (fonts etc) on xdg_output_handle_done() Monitor DPI depends on information from both the wl_output and the xdg_output interfaces. Before this patch, terminals were only updated after changes to the wl_output interfaces (thus depending on xdg output changes being pushed by the compositor before wl_output changes). That assumption (xdg_output happening before wl_output) isn’t always true. This patch fixes the issue by updating the terminals in the xdg_output’s “done” event. Closes #1431
2023-07-23 20:03:31 +02:00
[1431]: https://codeberg.org/dnkl/foot/issues/1431
render: apply new baseline calculation everywhere * URL jump labels * Scrollback position indicator * Line/box drawings characters Closes #1430
2023-07-23 17:35:57 +02:00
[1430]: https://codeberg.org/dnkl/foot/issues/1430
wayland: don't try to use a non-existing viewporter interface When instantiating the viewport for a pointer surface, we didn't first check if the compositor implements the viewporter interface. This triggered a crash when a) foot was compiled with fractional scaling, and b) the compositor did not implement the viewporter interface. Closes #1444
2023-07-28 15:32:42 +02:00
[1444]: https://codeberg.org/dnkl/foot/issues/1444
changelog: CSDs with fractional scaling
2023-07-29 09:09:59 +02:00
[1441]: https://codeberg.org/dnkl/foot/issues/1441
--window-size-chars: ensure width/height are valid for current scaling factor Before this patch, we didn’t ensure width and height were valid for the current scaling factor, when fractional scaling _is_ available. That is, we didn’t ensure the width/height values multiplied back to their original values after dividing with the scaling factor. Closes #1446
2023-07-30 07:53:33 +02:00
[1446]: https://codeberg.org/dnkl/foot/issues/1446
changelog: ignore invalid UTF-8 in input
2023-07-22 11:23:22 +02:00
changelog: prepare for 1.15.1
2023-07-21 08:56:49 +02:00
## 1.15.1
changelog: add new ‘unreleased’ section
2023-07-14 12:40:55 +02:00
### Changed
changelog: monitor metadata is now picked from the one we were last mapped on
2023-07-17 16:31:37 +02:00
* When window is mapped, use metadata (DPI, scaling factor, subpixel
configuration) from the monitor we were most recently mapped on,
instead of the one least recently.
themes: starlight: update to V4 This also updates the default theme in foot, as well as the documentation. Closes #1409
2023-07-18 16:18:53 +02:00
* Starlight theme (the default theme) updated to [V4][starlight-v4]
render: disable transparency when we’re fullscreened The wayland protocol recommends (or mandates?) that compositors render a black background behind fullscreened transparent windows. I.e. you never see what’s _actually_ behind the window. So, if you have a white, but semi-transparent background in foot, it’ll be rendered in a shade of gray. Given this, it’s better to simply disable transparency while we’re fullscreened. That way, we at least get the "correct" background color. Closes #1416
2023-07-19 16:34:42 +02:00
* Background transparency (alpha) is now disabled in fullscreened
windows ([#1416][1416]).
Changelog: standard system target + footclient fallback
2023-02-14 12:04:26 +01:00
* Foot server systemd units now use the standard
graphical-session.target ([#1281][1281]).
* If `$XDG_RUNTIME_DIR/foot-$WAYLAND_DISPLAY.sock` does not exist,
`footclient` now tries `$XDG_RUNTIME_DIR/foot.sock`, then
`/tmp/foot.sock`, even if `$WAYLAND_DISPLAY` and/or
`$XDG_RUNTIME_DIR` are defined ([#1281][1281]).
render: change baseline calculation, to center it within the line Before this patch, fonts were anchored to the top of the line. With this patch, it is instead centered. Closes #1302
2023-07-21 08:17:32 +02:00
* Font baseline calculation: try to center the text within the line,
instead of anchoring it at the top ([#1302][1302]).
themes: starlight: update to V4 This also updates the default theme in foot, as well as the documentation. Closes #1409
2023-07-18 16:18:53 +02:00
[starlight-v4]: https://github.com/CosmicToast/starlight/blob/v4/CHANGELOG.md#v4
render: disable transparency when we’re fullscreened The wayland protocol recommends (or mandates?) that compositors render a black background behind fullscreened transparent windows. I.e. you never see what’s _actually_ behind the window. So, if you have a white, but semi-transparent background in foot, it’ll be rendered in a shade of gray. Given this, it’s better to simply disable transparency while we’re fullscreened. That way, we at least get the "correct" background color. Closes #1416
2023-07-19 16:34:42 +02:00
[1416]: https://codeberg.org/dnkl/foot/issues/1416
Changelog: standard system target + footclient fallback
2023-02-14 12:04:26 +01:00
[1281]: https://codeberg.org/dnkl/foot/pulls/1281
render: change baseline calculation, to center it within the line Before this patch, fonts were anchored to the top of the line. With this patch, it is instead centered. Closes #1302
2023-07-21 08:17:32 +02:00
[1302]: https://codeberg.org/dnkl/foot/issues/1302
changelog: monitor metadata is now picked from the one we were last mapped on
2023-07-17 16:31:37 +02:00
changelog: add new ‘unreleased’ section
2023-07-14 12:40:55 +02:00
### Fixed
render: use rounding for fractional scale If we truncate the buffer dimensions we may accidentally submit a buffer with inappropriate size.
2023-07-14 16:53:50 -07:00
* Use appropriate rounding when applying fractional scales.
render: fix xcursor scaling with fractional-scale-v1 This worked just after the fractional-scaling branch was merged, but was then broken by the cursor-shape branch, due to a bad rebase of that branch.
2023-07-17 20:08:34 +02:00
* Xcursor not being scaled correctly on `fractional-scale-v1` capable
compositors.
changelog: wrong DPI, and wrong initial font size with fractional scaling
2023-07-17 16:31:54 +02:00
* `dpi-aware=yes` being broken on `fractional-scale-v1` capable
changelog: spelling: sacling -> scaling
2023-07-19 16:37:25 +02:00
compositors (and when a fractional scaling factor is being used)
changelog: wrong DPI, and wrong initial font size with fractional scaling
2023-07-17 16:31:54 +02:00
([#1404][1404]).
* Initial font size being wrong on `fractional-scale-v1` capable
compositors, with multiple monitors with different scaling factors
connected ([#1404][1404]).
changelog: crash on pointer capability loss
2023-07-18 16:12:43 +02:00
* Crash when _pointer capability_ is removed from a seat, on
compositors without `cursor-shape-v1 support` ([#1411][1411]).
term: destroy: unref key bindings *after* destroying window This fixes a crash-on-exit on compositors that emit a _"keyboard leave"_ event when a surface is unmapped. In our case, destroying the window (where we unmap it) in term_destroy(), lead to a crash in term_mouse_grabbed(), due to key_binding_for() returning NULL. The call chain in this is case is, roughly: term_destroy() -> wayl_win_destroy() -> keyboard_leave() -> term_xcursor_update_for_seat() -> term_mouse_grabbed()
2023-07-18 16:13:36 +02:00
* Crash on exit, if the mouse is hovering over the foot window (does
not happen on all compositors)
render: OSD: don’t mark surface as being opaque, when it’s not
2023-07-19 16:39:56 +02:00
* Visual glitches when CSD titlebar is transparent.
changelog: wrong DPI, and wrong initial font size with fractional scaling
2023-07-17 16:31:54 +02:00
[1404]: https://codeberg.org/dnkl/foot/issues/1404
changelog: crash on pointer capability loss
2023-07-18 16:12:43 +02:00
[1411]: https://codeberg.org/dnkl/foot/pulls/1411
render: fix xcursor scaling with fractional-scale-v1 This worked just after the fractional-scaling branch was merged, but was then broken by the cursor-shape branch, due to a bad rebase of that branch.
2023-07-17 20:08:34 +02:00
render: use rounding for fractional scale If we truncate the buffer dimensions we may accidentally submit a buffer with inappropriate size.
2023-07-14 16:53:50 -07:00
changelog: add new ‘unreleased’ section
2023-07-14 12:40:55 +02:00
### Contributors
changelog: prepare for 1.15.1
2023-07-21 08:56:49 +02:00
* Ayush Agarwal
* CismonX
* Max Gautier
* Ronan Pigott
* xdavidwu
changelog: add new ‘unreleased’ section
2023-07-14 12:40:55 +02:00
changelog: prepare for 1.15.0
2023-07-14 12:25:16 +02:00
## 1.15.0
changelog: add a new ‘unreleased’ section
2023-04-03 18:57:50 +02:00
### Added
csi: implement "CSI ? m"
2023-04-26 18:30:09 +02:00
* VT: implemented `XTQMODKEYS` query (`CSI ? Pp m`).
utmp: rewrite utmp logging This patch generalizes the utmp support, to not only support libutempter, but also ulog (and in the future, even more interfaces). * Rename config option main.utempter to main.utmp-helper * Add meson option -Dutmp-backend=none|libutempter|ulog|auto * Rename meson option -Ddefault-utempter-path to -Dutmp-default-helper-path * utmp is no longer detected at compile time, but at runtime instead. Meson will configure the following pre-processor macros, based on the selected utmp backend: * UTMP_ADD - argument to pass to utmp helper when adding a record (starting foot) * UTMP_DEL - argument to pass to utmp helper when removing a record (exiting foot) * UTMP_DEL_HAVE_ARGUMENT - if defined, UTMP_DEL expects an extra argument ($WAYLAND_DISPLAY) * UTMP_DEFAULT_HELPER_PATH - path to the default utmp helper binary The documentation has been updated to mention which arguments are passed to the helper binary. Closes #1314
2023-05-17 20:51:40 +02:00
* Meson option `utmp-backend=none|libutempter|ulog|auto`. The default
is `auto`, which will select `libutempter` on Linux, `ulog` on
FreeBSD, and `none` for all others.
sixel: respect sixel aspect ratio 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).
2023-06-19 19:06:38 +02:00
* Sixel aspect ratio.
changelog: fractional-scaling-v1 -> fractional-scale-v1
2023-07-04 08:38:07 +02:00
* Support for the new `fractional-scale-v1` Wayland protocol. This
changelog: mention the newly added support for fractional-scaling-v1
2023-06-26 17:34:20 +02:00
brings true fractional scaling to Wayland in general, and with this
changelog: fractional-scaling-v1 -> fractional-scale-v1
2023-07-04 08:38:07 +02:00
release, to foot.
cursor-shape: add support for server side cursor shapes 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
2023-06-27 17:25:57 +02:00
* Support for the new `cursor-shape-v1` Wayland protocol, i.e. server
side cursor shapes ([#1379][1379]).
input: add basic support for touchscreen input Closes #517
2023-07-05 00:19:21 +08:00
* Support for touchscreen input ([#517][517]).
config: add csd.double-click-to-maximize=no|yes option 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
2023-07-14 12:03:35 +02:00
* `csd.double-click-to-maximize` option to `foot.ini`. Defaults to
`yes` ([#1293][1293]).
cursor-shape: add support for server side cursor shapes 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
2023-06-27 17:25:57 +02:00
[1379]: https://codeberg.org/dnkl/foot/issues/1379
input: add basic support for touchscreen input Closes #517
2023-07-05 00:19:21 +08:00
[517]: https://codeberg.org/dnkl/foot/issues/517
config: add csd.double-click-to-maximize=no|yes option 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
2023-07-14 12:03:35 +02:00
[1293]: https://codeberg.org/dnkl/foot/issues/1293
csi: implement "CSI ? m"
2023-04-26 18:30:09 +02:00
changelog: add a new ‘unreleased’ section
2023-04-03 18:57:50 +02:00
### Changed
kitty: F3 is no longer allowed to emit CSI R The original kitty keyboard specification allowed F3 to emit either CSI R, or CSI 13~. Support for CSI R was removed in later revisions of the protocol, since it collides with "Cursor Position Report" sequences.
2023-04-26 18:28:07 +02:00
config: make ‘starlight’ the default color theme Closes #1321
2023-07-14 10:11:30 +02:00
* Default color theme is now
[starlight](https://github.com/CosmicToast/starlight)
([#1321][1321]).
meson: use meson feed feature for scdoc input Removes the need for a shell dependency.
2023-06-14 12:26:19 +00:00
* Minimum required meson version is now 0.59 ([#1371][1371]).
changelog: split up key binding changes for show-urls-launch and unicode-input
2023-07-10 12:42:10 +02:00
* `Control+Shift+u` is now bound to `unicode-input` instead of
`show-urls-launch`, to follow the convention established in GTK and
Qt ([#1183][1183]).
* `show-urls-launch` now bound to `Control+Shift+o` ([#1183][1183]).
kitty: F3 is no longer allowed to emit CSI R The original kitty keyboard specification allowed F3 to emit either CSI R, or CSI 13~. Support for CSI R was removed in later revisions of the protocol, since it collides with "Cursor Position Report" sequences.
2023-04-26 18:28:07 +02:00
* Kitty keyboard protocol: F3 is now encoded as `CSI 13~` instead of
`CSI R`. The kitty keyboard protocol originally allowed F3 to be
encoded as `CSI R`, but this was removed from the specification
since `CSI R` conflicts with the _”Cursor Position Report”_.
utmp: rewrite utmp logging This patch generalizes the utmp support, to not only support libutempter, but also ulog (and in the future, even more interfaces). * Rename config option main.utempter to main.utmp-helper * Add meson option -Dutmp-backend=none|libutempter|ulog|auto * Rename meson option -Ddefault-utempter-path to -Dutmp-default-helper-path * utmp is no longer detected at compile time, but at runtime instead. Meson will configure the following pre-processor macros, based on the selected utmp backend: * UTMP_ADD - argument to pass to utmp helper when adding a record (starting foot) * UTMP_DEL - argument to pass to utmp helper when removing a record (exiting foot) * UTMP_DEL_HAVE_ARGUMENT - if defined, UTMP_DEL expects an extra argument ($WAYLAND_DISPLAY) * UTMP_DEFAULT_HELPER_PATH - path to the default utmp helper binary The documentation has been updated to mention which arguments are passed to the helper binary. Closes #1314
2023-05-17 20:51:40 +02:00
* `[main].utempter` renamed to `[main].utmp-helper`. The old option
name is still recognized, but will log a deprecation warning.
* Meson option `default-utempter-path` renamed to
`utmp-default-helper-path`.
sixel: apply background alpha when P2=0 or P2=2, and current bg color is the default bg color Closes #1360
2023-05-31 16:27:48 +02:00
* Opaque sixels now retain the background opacity (when current
background color is the **default** background color)
([#1360][1360]).
sixel: fix cursor positioning logic 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.
2023-06-16 16:20:37 +02:00
* Text cursor’s vertical position after emitting a sixel, when sixel
scrolling is **enabled** (the default) has been updated to match
XTerm’s, and the VT382’s behavior: the cursor is positioned **on**
the last sixel row, rather than _after_ it. This allows printing
sixels on the last row without scrolling up, but also means
applications may have to explicitly emit a newline to ensure the
sixel is visible. For example, `cat`:ing a sixel in the shell will
typically result in the last row not being visible, unless a newline
is explicitly added.
sixel: respect sixel aspect ratio 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).
2023-06-19 19:06:38 +02:00
* Default sixel aspect ratio is now 2:1 instead of 1:1.
sixel: stop cropping images to the last non-transparent row
2023-06-19 19:09:58 +02:00
* Sixel images are no longer cropped to the last non-transparent row.
sixel: re-scale images when the cell dimensions change 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
2023-06-29 14:49:54 +02:00
* Sixel images are now re-scaled when the font size is changed
([#1383][1383]).
changelog: dpi-aware’s default value is now ‘no’
2023-06-26 17:55:59 +02:00
* `dpi-aware` now defaults to `no`, and the `auto` value has been
removed.
render: don’t invert cursor colors when custom colors are being used 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
2023-07-14 09:51:06 +02:00
* When using custom cursor colors (`cursor.color` is set in
`foot.ini`), the cursor is no longer inverted when the cell is
selected, or when the cell has the `reverse` (SGR 7) attribute set
([#1347][1347]).
sixel: respect sixel aspect ratio 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).
2023-06-19 19:06:38 +02:00
config: make ‘starlight’ the default color theme Closes #1321
2023-07-14 10:11:30 +02:00
[1321]: https://codeberg.org/dnkl/foot/issues/1321
meson: use meson feed feature for scdoc input Removes the need for a shell dependency.
2023-06-14 12:26:19 +00:00
[1371]: https://codeberg.org/dnkl/foot/pulls/1371
bind control-shift-u to unicode-input, move urls to o 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
2022-12-15 11:49:51 -05:00
[1183]: https://codeberg.org/dnkl/foot/issues/1183
sixel: apply background alpha when P2=0 or P2=2, and current bg color is the default bg color Closes #1360
2023-05-31 16:27:48 +02:00
[1360]: https://codeberg.org/dnkl/foot/issues/1360
sixel: re-scale images when the cell dimensions change 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
2023-06-29 14:49:54 +02:00
[1383]: https://codeberg.org/dnkl/foot/issues/1383
render: don’t invert cursor colors when custom colors are being used 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
2023-07-14 09:51:06 +02:00
[1347]: https://codeberg.org/dnkl/foot/issues/1347
sixel: apply background alpha when P2=0 or P2=2, and current bg color is the default bg color Closes #1360
2023-05-31 16:27:48 +02:00
kitty: F3 is no longer allowed to emit CSI R The original kitty keyboard specification allowed F3 to emit either CSI R, or CSI 13~. Support for CSI R was removed in later revisions of the protocol, since it collides with "Cursor Position Report" sequences.
2023-04-26 18:28:07 +02:00
changelog: add a new ‘unreleased’ section
2023-04-03 18:57:50 +02:00
### Deprecated
utmp: rewrite utmp logging This patch generalizes the utmp support, to not only support libutempter, but also ulog (and in the future, even more interfaces). * Rename config option main.utempter to main.utmp-helper * Add meson option -Dutmp-backend=none|libutempter|ulog|auto * Rename meson option -Ddefault-utempter-path to -Dutmp-default-helper-path * utmp is no longer detected at compile time, but at runtime instead. Meson will configure the following pre-processor macros, based on the selected utmp backend: * UTMP_ADD - argument to pass to utmp helper when adding a record (starting foot) * UTMP_DEL - argument to pass to utmp helper when removing a record (exiting foot) * UTMP_DEL_HAVE_ARGUMENT - if defined, UTMP_DEL expects an extra argument ($WAYLAND_DISPLAY) * UTMP_DEFAULT_HELPER_PATH - path to the default utmp helper binary The documentation has been updated to mention which arguments are passed to the helper binary. Closes #1314
2023-05-17 20:51:40 +02:00
* `[main].utempter` option.
changelog: add a new ‘unreleased’ section
2023-04-03 18:57:50 +02:00
### Removed
changelog: dpi-aware’s default value is now ‘no’
2023-06-26 17:55:59 +02:00
* `auto` value for the `dpi-aware` option.
changelog: add a new ‘unreleased’ section
2023-04-03 18:57:50 +02:00
### Fixed
*.desktop: add StartupWMClass=foot At least Gnome needs this in order to link running instances of foot to their corresponding .desktop file, used e.g. when determining which icon to display for running applications. Closes #1317
2023-04-05 14:39:02 +02:00
* Incorrect icon in dock and window switcher on Gnome ([#1317][1317])
render: ensure scroll region’s endpoint is valid after a window resize If we had a non-empty bottom scroll region, and the window was resized to a smaller size, the scroll region was not reset correctly. This led to a crash when scrolling the screen content. Fix by making sure the scroll region’s endpoint is within range.
2023-04-12 16:39:54 +02:00
* Crash when scrolling after resizing the window with non-zero
scrolling regions.
term: reset: switch modifyOtherKeys back to level 1
2023-05-12 09:42:35 +02:00
* `XTMODKEYS` state not being reset on a terminal reset.
.desktop: remove StartupWMClass from server, use distinct StartupWMClass for foot and footclient For this to work, the default app-id of footclient has been changed from ‘foot’ to ‘footclient’. By using distinct StartupWMClasses, the compositor can connect a running foot/footclient instance to the correct .desktop-file. This ensures the correct icon is being used in e.g. docks, and that actions like “open another window” works correctly. Note that the user can override the app-id, either by setting app-id in foot.ini, or with the -a,--app-id command line option. Closes #1355
2023-05-02 01:53:01 +10:00
* In Gnome dock foot always groups under "foot client". Change
instances of footclient and foot to appear as "foot client" and
osc: update font subpixel mode, and window opaque compositor hint, on alpha changes When background alpha is changed at runtime (using OSC-11), we (may) have to update the opaque hint we send to the compositor. We must also update the subpixel mode used when rendering font glyphs. Why? When the window is fully opaque, we use wl_surface_set_opaque_region() on the entire surface, to hint to the compositor that it doesn’t have to blend the window content with whatever is behind the window. Obviously, if alpha is changed from opaque, to transparent (or semi-transparent), that hint must be removed. Sub-pixel mode is harder to explain, but in short, we can’t do subpixel hinting with a (semi-)transparent background. Thus, similar to the opaque hint, subpixel antialiasing must be enabled/disabled when background alpha is changed.
2023-05-25 18:39:32 +02:00
"foot" respectively. ([#1355][1355]).
* Glitchy rendering when alpha (transparency) is changed between
opaque and non-opaque at runtime (using OSC-11).
render: resize: fix crash when reflowing the alt screen When doing an interactive resize, and `resize-delay-ms` > 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
2023-06-20 15:59:16 +02:00
* Regression: crash when resizing the window when `resize-delay-ms >
0` ([#1377][1377]).
term: scroll: only record scroll damage when viewport is at the bottom 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
2023-06-23 20:20:01 +02:00
* Crash when scrolling up while running something that generates a lot
of output (for example, `yes`) ([#1380][1380]).
changelog: mention the new default key binding for show-urls-launch under “fixed” It “fixes” the key binding conflict seen on e.g. GNOME, and increases the exposure of the change to, hopefully, more users.
2023-07-10 12:42:36 +02:00
* Default key binding for URL mode conflicting with Unicode input on
some DEs; `show-urls-launched` is now mapped to `Control+Shift+o` by
default, instead of `Control+Shift+u` ([#1183][1183]).
*.desktop: add StartupWMClass=foot At least Gnome needs this in order to link running instances of foot to their corresponding .desktop file, used e.g. when determining which icon to display for running applications. Closes #1317
2023-04-05 14:39:02 +02:00
[1317]: https://codeberg.org/dnkl/foot/issues/1317
.desktop: remove StartupWMClass from server, use distinct StartupWMClass for foot and footclient For this to work, the default app-id of footclient has been changed from ‘foot’ to ‘footclient’. By using distinct StartupWMClasses, the compositor can connect a running foot/footclient instance to the correct .desktop-file. This ensures the correct icon is being used in e.g. docks, and that actions like “open another window” works correctly. Note that the user can override the app-id, either by setting app-id in foot.ini, or with the -a,--app-id command line option. Closes #1355
2023-05-02 01:53:01 +10:00
[1355]: https://codeberg.org/dnkl/foot/issues/1355
render: resize: fix crash when reflowing the alt screen When doing an interactive resize, and `resize-delay-ms` > 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
2023-06-20 15:59:16 +02:00
[1377]: https://codeberg.org/dnkl/foot/issues/1377
term: scroll: only record scroll damage when viewport is at the bottom 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
2023-06-23 20:20:01 +02:00
[1380]: https://codeberg.org/dnkl/foot/issues/1380
*.desktop: add StartupWMClass=foot At least Gnome needs this in order to link running instances of foot to their corresponding .desktop file, used e.g. when determining which icon to display for running applications. Closes #1317
2023-04-05 14:39:02 +02:00
changelog: add a new ‘unreleased’ section
2023-04-03 18:57:50 +02:00
### Contributors
changelog: prepare for 1.15.0
2023-07-14 12:25:16 +02:00
* Antoine Beaupré
* CismonX
* Craig Barnes
* Dan Bungert
* jdevdevdev
* Kyle Gunger
* locture
* Phillip Susi
* sewn
* ShugarSkull
* Vivian Szczepanski
* Vladimir Bauer
* wout
* CosmicToast
changelog: add a new ‘unreleased’ section
2023-04-03 18:57:50 +02:00
changelog: prepare for 1.14.0
2023-04-03 18:52:22 +02:00
## 1.14.0
Merge branch 'releases/1.13'
2022-08-31 19:26:21 +02:00
changelog: add new ‘unreleased’ section
2022-08-07 09:38:25 +02:00
### Added
config: add setting for underline thickness 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
2022-08-19 02:54:49 +02:00
* Support for adjusting the thickness of regular underlines ([#1136][1136]).
Add support for creating utmp records 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.
2022-09-23 20:24:04 +02:00
* Support (optional) for utmp logging with libutempter.
terminfo: add kxIN + kxOUT (focus in/out events) These capabilities are not included in the standard ‘xterm’ or ‘xterm-256color’ terminfos. They’re used in ‘xterm+focus’ -> ‘xterm+sm+1002’ -> ‘xterm-1002|xterm+sm+1003’ -> ‘xterm-1003’ (https://invisible-island.net/ncurses/terminfo.ti.html#tic-xterm_focus) However, as far as I can tell, ncurses doesn’t use these capabilities at all.
2022-09-24 12:32:17 +02:00
* `kxIN` and `kxOUT` (focus in/out events) to terminfo.
scripts: generate-builtin-terminfo: add synthetic ‘name’ capability Same as ‘TN’; reports the terminfo name.
2022-09-28 21:09:35 +02:00
* `name` capability to `XTGETTCAP`.
config: allow string values to be quoted * Both double and single quotes are recognized. There’s no difference in how they are handled. * The entire string must be quoted: - “a quoted string” - OK - quotes “in the middle” of a string - NOT ok * Two escape characters are regonized: - Backslash - The quote character itself
2022-12-01 15:00:44 +01:00
* String values in `foot.ini` may now be quoted. This can be used to
set a value to the empty string, for example.
slave: unsetenv() env vars that have been set to the empty string That is, users can now *clear* environment variables by doing: [environment] VAR=”” Note that the quotes are required. Closes #1225
2022-12-01 19:43:38 +01:00
* Environment variables can now be **unset**, by setting
config: add ‘font-size-adjustment=N[px|%]’ option 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
2022-12-15 11:10:32 +01:00
`[environment].<variable>=""` (quotes are required) ([#1225][1225]).
* `font-size-adjustment=N[px]` option, letting you configure how much
to increment/decrement the font size when zooming in or out
([#1188][1188]).
changelog: amend terminfo names, in accordance with previous commit
2023-01-01 15:21:17 +00:00
* Bracketed paste terminfo entries (`BD`, `BE`, `PE` and `PS`, added
terminfo: add entries for bracketed paste Ncurses added these in 2022-12-24, but they have been used/supported by vim since 2017. * BE - Bracketed paste Enable * BD - Bracketed paste Disable * PE - Paste Enable (i.e. "begin") * PD - Paste Disable (i.e. "end")
2023-01-01 10:22:54 +01:00
to ncurses in 2022-12-24). Vim makes use of these.
terminfo: sync with ncurses 2023-01-14 * RV/rv: report DA2 * XR/xr: report version (XTVERSION) * XF: boolean, focus in/out events available
2023-01-15 14:00:06 +01:00
* “Report version” terminfo entries (`XR`/`xr`).
* “Report DA2” terminfo entries (`RV`/`rv`).
* `XF` terminfo capability (focus in/out events available).
slave: set $TERM_PROGRAM and $TERM_PROGRAM_VERSION environment variables 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&type=code
2023-03-20 14:40:36 +00:00
* `$TERM_PROGRAM` and `$TERM_PROGRAM_VERSION` environment variables
slave: unset TERM_PROGRAM{,_VERSION} Foot’s policy is to not set environment variables that identifies it (except the well-known and established `TERM` variable). We encourage applications to use terminfo to determine capabilities, or terminal queries, when available. Or, at least use terminal queries to detect the terminal and its version. Setting environment variables is a bad idea since they are inherited by all applications started by the terminal (which is the whole point). But, this includes other terminal emulators, making it very possible a terminal emulator gets mis-detected just because it was started from another terminal. Since there are a couple of terminal emulators that _do_ set TERM_PROGRAM and TERM_PROGRAM_VERSION, unset these environment variables to avoid being misdetected. Closes #1349
2023-05-12 14:55:55 +02:00
unset in the slave process.
config: add setting for underline thickness 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
2022-08-19 02:54:49 +02:00
[1136]: https://codeberg.org/dnkl/foot/issues/1136
slave: unsetenv() env vars that have been set to the empty string That is, users can now *clear* environment variables by doing: [environment] VAR=”” Note that the quotes are required. Closes #1225
2022-12-01 19:43:38 +01:00
[1225]: https://codeberg.org/dnkl/foot/issues/1225
config: add ‘font-size-adjustment=N[px|%]’ option 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
2022-12-15 11:10:32 +01:00
[1188]: https://codeberg.org/dnkl/foot/issues/1188
config: add setting for underline thickness 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
2022-08-19 02:54:49 +02:00
changelog: add new ‘unreleased’ section
2022-08-07 09:38:25 +02:00
### Changed
render: apply a dimmed overlay while in Unicode input mode
2022-08-08 16:31:28 +02:00
theme: change default color theme to solarized-dark-normal-brights 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".
2022-08-17 18:12:51 +02:00
* Default color theme from a variant of the Zenburn theme, to a
variant of the Solarized dark theme.
config: change default ‘pad’ to 0x0 (i.e. no padding)
2022-09-03 12:16:41 +02:00
* Default `pad` from 2x2 to 0x0 (i.e. no padding at all).
input: pipe-*: set current CWD when spawning the sub-process Closes #1166
2022-09-10 12:04:39 +02:00
* Current working directory (as set by OSC-7) is now passed to the
csi: reply with 4 instead of 2 for DECRQM queries of unsupported modes The status value 4 means "permanently reset", as opposed to 2, which means "reset". The former implies that there's no way to enable the mode because it's unsupported (but recognized). Note: this commit also fixes an unrelated typo in CHANGELOG.md.
2022-09-17 07:17:12 +01:00
program executed by the `pipe-*` key bindings ([#1166][1166]).
* `DECRPM` replies (to `DECRQM` queries) now report a value of `4`
("permanently reset") instead of `2` ("reset") for DEC private
modes that are known but unsupported.
slave: spawn: set PWD environment variable This improves handling of symlinks (in CWD) when launching a new terminal instance, either through ctrl+shift+n, or using the --working-directory command line option. Closes #1179
2022-09-26 19:00:27 +02:00
* Set `PWD` environment variable in the slave process ([#1179][1179]).
wayland: force monitor DPI to 96 when it’s unreasonably high If an output has a bogus physical width or height, the DPI can become so high that the cell width/height is too large for pixman_image_fill_rectangles(), resulting in a crash in pixman_fill(). Since it doesn’t make any sense to use a DPI that is obviously bogus, don’t. Force it 96 instead.
2022-11-04 17:45:43 +01:00
* DPI is now forced to 96 when found to be unreasonably high.
change default log level to WARNING 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]: > Rule of Silence: When a program has nothing surprising to say, it > 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
2022-11-18 11:07:16 -05:00
* Set default log level to warning ([#1215][1215]).
config: change default grapheme-width-method from wcswidth to double-width 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.
2022-12-16 16:56:43 +01:00
* Default `grapheme-width-method` from `wcswidth` to `double-width`.
config: apply fontconfig rules if user didn’t set an explicit font size If the user didn’t explicitly set the font size (e.g. font=monospace, instead of font=monospace:size=12), our initial attempt to read the FC_SIZE and FC_PIXEL_SIZE attributes will fail, and we used to fallback to setting the size to 8pt. Change this slightly, so that when we fail to read the FC_*_SIZE attributes, apply the fontconfig rules, but *without expanding* them (i.e. without calling FcDefaultSubstitute()). Then try reading FC_*_SIZE again. If that too fails, _then_ set size to 8pt. This allows us to pick up rules that set a default {pixel}size: <fontconfig> <match> <edit name="pixelsize" mode="append"><double>14</double></edit> </fontconfig> Closes #1287
2023-03-03 17:21:11 +01:00
* When determining initial font size, do FontConfig config
substitution if the user-provided font pattern has no {pixel}size
option ([#1287][1287]).
terminfo: remove DECRST of DECCOLM+DECSCLM We’ve never supported neither 132-column mode, nor smooth scrolling. But we _did_ recognize the escape sequences. We don’t, anymore. Thus it makes very little sense to include these escapes in any of our terminfo capabilities. So, remove them.
2023-03-31 10:36:43 +02:00
* DECRST of DECCOLM and DECSCLM removed from terminfo.
input: pipe-*: set current CWD when spawning the sub-process Closes #1166
2022-09-10 12:04:39 +02:00
[1166]: https://codeberg.org/dnkl/foot/issues/1166
slave: spawn: set PWD environment variable This improves handling of symlinks (in CWD) when launching a new terminal instance, either through ctrl+shift+n, or using the --working-directory command line option. Closes #1179
2022-09-26 19:00:27 +02:00
[1179]: https://codeberg.org/dnkl/foot/issues/1179
change default log level to WARNING 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]: > Rule of Silence: When a program has nothing surprising to say, it > 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
2022-11-18 11:07:16 -05:00
[1215]: https://codeberg.org/dnkl/foot/pulls/1215
config: apply fontconfig rules if user didn’t set an explicit font size If the user didn’t explicitly set the font size (e.g. font=monospace, instead of font=monospace:size=12), our initial attempt to read the FC_SIZE and FC_PIXEL_SIZE attributes will fail, and we used to fallback to setting the size to 8pt. Change this slightly, so that when we fail to read the FC_*_SIZE attributes, apply the fontconfig rules, but *without expanding* them (i.e. without calling FcDefaultSubstitute()). Then try reading FC_*_SIZE again. If that too fails, _then_ set size to 8pt. This allows us to pick up rules that set a default {pixel}size: <fontconfig> <match> <edit name="pixelsize" mode="append"><double>14</double></edit> </fontconfig> Closes #1287
2023-03-03 17:21:11 +01:00
[1287]: https://codeberg.org/dnkl/foot/issues/1287
render: apply a dimmed overlay while in Unicode input mode
2022-08-08 16:31:28 +02:00
Merge branch 'releases/1.13'
2022-08-31 19:26:21 +02:00
### Fixed
terminal: don’t unref a not-yet-referenced key-binding set Key-binding sets are bound to a seat/configuration pair. The conf reference is done when a new terminal instance is created. When that same terminal instance is destroyed, the key binding set is unref:ed. If the terminal instance is destroyed *before* the key binding set has been referenced, we’ll still unref it. This creates an imbalance. In particular, when the there is exactly one other terminal instance referencing that same key binding set, that terminal instance will trigger a foot server crash as soon as it receives a key press/release event. This happens because the next-to-last terminal instance brought the reference count of the binding set down to 0, causing it to be free:d. Thus, we *must* reference the binding set *before* we can error out (when instantiating a new terminal instance). At this point, we don’t yet have a valid terminal instance. But, that’s ok, because all the key_binding_new_for_term() did with the terminal instance was get the "struct wayland" and "struct config" pointers. So, rename the function and simply pass these pointers explicitly. Similarly, change key_binding_for() to take a "struct config" pointer, rather than a "struct terminal" pointer. Also rename key_binding_unref_term() -> key_binding_unref().
2022-09-05 19:23:40 +02:00
* Crash in `foot --server` on key press, after another `footclient`
has terminated very early (for example, by trying to launch a
non-existing shell/client).
render: fix application of old scroll damage when double buffering On compositors that forces us to double buffer, we need to re-apply the last frame’s damage to the current frame (which uses the buffer from the next-to-last frame). General cell updates are handled by simply copying from the last frame’s pixman buffer to the current frame’s. In an attempt to improve performance, scroll damage were up until now handled by re-playing the last frame’s scroll damage (on the current frame’s buffer). This does not work, and resulted in glitches when scrolling in the scrollback. This patch does the following: * grid_render_scroll{,_reverse}() now update the buffer’s "dirty" region. This means the generic copy-old-frames-buffer handles the scroll damage (albeit in, potentially, a less efficient way). * Tracking of, and re-applying old scroll damage is completely removed. Closes #1173
2022-09-22 18:34:41 +02:00
* Glitchy rendering when scrolling in the scrollback, on compositors
Codespell fixes
2023-10-03 14:11:55 +02:00
that does not allow Wayland buffer reuse (e.g. KDE/plasma)
render: fix application of old scroll damage when double buffering On compositors that forces us to double buffer, we need to re-apply the last frame’s damage to the current frame (which uses the buffer from the next-to-last frame). General cell updates are handled by simply copying from the last frame’s pixman buffer to the current frame’s. In an attempt to improve performance, scroll damage were up until now handled by re-playing the last frame’s scroll damage (on the current frame’s buffer). This does not work, and resulted in glitches when scrolling in the scrollback. This patch does the following: * grid_render_scroll{,_reverse}() now update the buffer’s "dirty" region. This means the generic copy-old-frames-buffer handles the scroll damage (albeit in, potentially, a less efficient way). * Tracking of, and re-applying old scroll damage is completely removed. Closes #1173
2022-09-22 18:34:41 +02:00
([#1173][1173])
render: overlay: fix visual glitches when double buffering When rendering the overlay for scrollback search, the logic assumed buffer re-use. On some compositors this isn’t happening (on e.g. KDE/plasma we’re forced to double buffer). This resulted in matches not being highlighted correctly. The problem is in how we calculated the region for which areas to clear ("un-dim"). It uses the "previous frame’s see-through area" minus the current frame’s see-through area. However, when we’ve detected that the current buffer isn’t the same as the last one, we set the last frame’s see-through region to "the entire buffer". Thus, when calculating the diff, we end up with an empty region, and nothing is highlighted. Fix by simply using the current frame’s see-through region as-is when we’ve detected we’re not re-using the last frame’s buffer.
2022-09-22 18:39:00 +02:00
* Scrollback search matches not being highlighted correctly, on
Codespell fixes
2023-10-03 14:11:55 +02:00
compositors that does not allow Wayland buffer reuse
render: overlay: fix visual glitches when double buffering When rendering the overlay for scrollback search, the logic assumed buffer re-use. On some compositors this isn’t happening (on e.g. KDE/plasma we’re forced to double buffer). This resulted in matches not being highlighted correctly. The problem is in how we calculated the region for which areas to clear ("un-dim"). It uses the "previous frame’s see-through area" minus the current frame’s see-through area. However, when we’ve detected that the current buffer isn’t the same as the last one, we set the last frame’s see-through region to "the entire buffer". Thus, when calculating the diff, we end up with an empty region, and nothing is highlighted. Fix by simply using the current frame’s see-through region as-is when we’ve detected we’re not re-using the last frame’s buffer.
2022-09-22 18:39:00 +02:00
(e.g. KDE/plasma).
render: fix nanosec "overflow" when calculating timeout value
2022-10-03 19:41:13 +03:00
* Nanosecs "overflow" when calculating timeout value for
`resize-delay-ms` option.
scripts: generate-builtin-terminfo: double-escape backslash in ST Fixes an issue with XTGETTCAP, where escape sequences terminated with ST, and containing parameters were missing a trailing backslash.
2022-09-27 19:05:56 +02:00
* Missing backslash in ST terminator in escape sequences in the
built-in terminfo (accessed via XTGETTCAP).
changelog: fixed crash when resizing window with a very large scrollback
2022-10-06 17:26:38 +02:00
* Crash when interactively resizing the window with a very large
scrollback.
sixel: don’t crash when sixel image exceeds current sixel max height When we try to resize a sixel past the current max height, we set col > image-width to signal this. This means ‘width’ could be smaller than ‘col’. When calculating how many sixels to emit in sixel_add_many(), we didnt’ account for this. The resulting value was -1, converted to ‘unsigned’. I.e. a very large value. This resulted in an assert triggering in sixel_add() in debug builds, and a crash in release builds.
2022-10-13 17:52:34 +02:00
* Crash when a sixel image exceeds the current sixel max height.
changelog: crash after reverse-scrolling in the normal screen
2022-10-14 18:05:12 +02:00
* Crash after reverse-scrolling (`CSI Ps T`) in the ‘normal’
(non-alternate) screen ([#1190][1190]).
render: never apply alpha to text color When drawing a block cursor using inversed fg/bg colors, we didn’t strip the alpha from the background color. This meant that the text "behind" the cursor was rendered with transparency. If alpha was set to 0, the text was completely invisible. We should never apply alpha to the text color. So, detect this, and force alpha to 1.0. Normally, when selecting the cursor’s color, we don’t really know _where_ the background color is coming from (or more accurately, _what_ it is). However, the *only* background color that can have a non-1.0 alpha is the *default* background color. This is why we can ignore the bg parameter, and use term->colors.fg/bg instead. Closes #1205
2022-10-30 19:39:09 +01:00
* Background transparency being applied to the text "behind" the
cursor. Only applies to block cursor using inversed fg/bg
colors. ([#1205][1205]).
wayland: use fp math all the way when calculating DPI This fixes an FPE when the monitor’s physical width/height is so small that the conversion from mm to inch resulted in inches being zero.
2022-11-04 17:42:52 +01:00
* Crash when monitor’s physical size is "too small" ([#1209][1209]).
changelog: line-height adjustment with user-set line-height
2022-11-23 16:23:01 +01:00
* Line-height adjustment when incrementing/decrementing the font size
with a user-set line-height ([#1218][1218]).
changelog: scaling factor not being applied when converting px-to-pt
2022-11-24 17:21:53 +01:00
* Scaling factor not being correctly applied when converting pt-or-px
config values (e.g. letter offsets, line height etc).
changelog: remove trailing back-tick
2023-03-31 10:41:17 +02:00
* Selection being stuck visually when `IL` and `DL`.
url-mode: tag cells after snapshot:ing the grid Before this patch, hyperlinked cells were tagged with the “URL” attribute (thus instructing the renderer to draw an underline) *before* the grid was snapshot. When exiting URL mode, the cells were once again updated, this time removing the URL attribute. But what if an escape sequence had modified the grid _while we were in URL mode_? Depending on the sequence, it could move cells around in such a way, that when exiting URL mode, the affected cells weren’t updated correctly. I.e. we left some cells with the URL attribute still set. The fix is simple: tag cells in the snapshot:ed grid only (which isn’t affected by any escape sequence received while in URL mode). Not in the *actual* grid (which _is_ affected).
2022-11-30 10:51:45 +01:00
* URL underlines sometimes still being visible after exiting URL mode.
config: don’t double-free key binding auxiliary data Key bindings with multiple key mappings share auxiliary data (e.g. the command to execute in pipe-* bindings, or the escape sequence in text-bindings). The first one is the designated “master” copy. Only that one should be freed. This fixed a double-free on exit, with e.g. [text-bindings] \x1b\x23=Mod4+space Mod4+equal Closes #1259
2023-01-15 10:24:01 +01:00
* Text-bindings, and pipe-* bindings, with multiple key mappings
causing a crash (double-free) on exit ([#1259][1259]).
render: fix double-width glyphs glitching when surrounding cells overflow into it If cells overflowed (for example, by using an italic font that isn’t truly monospaced) into a double-width glyph (that itself is *not* overflowing), then the double-width glyph would glitch when being rendered; typically the second half of it would occasionally disappear. This happened because we tried to rasterize the second cell of the double-width glyph. This cell contains a special “spacer” value. Rasterizing that typically results the font’s “not available” glyph. If _that_ glyph overflows, things broke; we’d later end up forcing a re-render of it (thus erasing half the double-width glyph). But since the double-width glyph _itself_ doesn’t overflow, _it_ wouldn’t be re-rendered, leaving it half erased. Fix by recognizing spacer cells, and not trying to rasterize them (set glyph count to 0, and cell count to 1). Closes #1256
2023-01-15 14:42:48 +01:00
* Double-width glyphs glitching when surrounded by glyphs overflowing
into the double-width glyph ([#1256][1256]).
wayland: ignore configure events for unmapped surfaces Closes #1249 Note that it is still unclear whether ack:ing a configure event for an unmapped surface is a protocol violation, or something that should be handled by the compositor. According to https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/108, Kwin, Mutter and Weston handles it, while wlroots does not.
2022-12-29 11:32:21 +01:00
* Wayland protocol violation when ack:ing a configure event for an
unmapped surface ([#1249][1249]).
changeloge: remove bad escape char
2023-03-31 10:42:50 +02:00
* `xdg_toplevel::set_min_size()` not being called.
key-binding: sort binding lists Sort bindings such that bindings with the same symbol are sorted with the binding having the most modifiers comes first. This fixes an issue where the “wrong” key binding are triggered when used with “consumed” modifiers. For example: if Control+BackSpace is bound before Control+Shift+BackSpace, then the latter binding is never triggered. Why? Because Shift is a consumed modifier. This means Control+BackSpace is “the same” as Control+Shift+BackSpace. By sorting bindings with more modifiers first, we work around the problem. But note that it is *just* a workaround, and I’m not confident there aren’t cases where it doesn’t work. Closes #1280
2023-02-27 17:56:03 +01:00
* Key bindings with consumed modifiers masking other key bindings
([#1280][1280]).
input: (kitty kbd): the resulting UTF-8 string may translate to multiple UTF-32 codepoints When this happened (for example, by specifying a custom compose sequence), the kitty keyboard protocol didn’t emit any text at all. This was caused by the utf32 codepoint being -1. This in turned was caused by us trying to convert the utf8 sequence to a *single* utf32 codepoint. This patch replaces the use of mbrtoc32() with a call to ambstoc32(), and the utf32 codepoint with an utf32 string. The kitty keyboard protocol is updated: * When determining if we’re dealing with text, check *all* codepoints in the utf32 string. * Add support for multiple codepoints when reporting "associated text". The first codepoint is the actual parameter in the emitted sequence, and the remaining codepoints are sub-parameters. I.e. the codepoints are colon separated. Closes #1288
2023-03-27 16:56:10 +02:00
* Multi-character compose sequences with the kitty keyboard protocol
([#1288][1288]).
render: protect against integer underflow when calculating scroll area When applying scroll damage, we calculate the affected region’s height (in pixels), by subtracting the number of rows to scroll, from the scrolling region, and finally multiply by the cell height. If the number of rows to scroll is very large, the subtraction may underflow, resulting in a very large height value instead of a negative one. This caused the check for "scrolling too many lines" to fail. That in turn resulted in an integer overflow when calculating the source offset into the rendered surface buffer, which typically triggered a segfault. This bug happened when there was continuous output in the terminal without any new frames being rendered. This caused a buildup of scroll damage, that triggered the underflow+overflow when we finally did render a new frame. For example, a compositor that doesn’t send any frame callbacks (for example because the terminal window is minimized, or on a different workspace/tag) would cause this. Closes #1305
2023-03-28 18:31:24 +02:00
* Crash when application output scrolls very fast, e.g. `yes`
([#1305][1305]).
term: protect against integer overflow when accumulating scroll damage When accumulating scroll damage, we check if the last scroll damage’s scrolling region, and type, matches the new/current scroll damage. If so, the number of lines in the last scroll damage is increased, instead of adding a new scroll damage instance to the list. If the scroll damage list isn’t consumed, this build up of scroll damage would eventually overflow. And, even if it didn’t overflow, it could become large enough, that when later used to calculate e.g. the affected surface area, while rendering a frame, would cause an overflow there instead. This patch fixes both issues by: a) do an overflow check before increasing the line count b) limit the line count to UINT16_MAX
2023-03-28 18:37:41 +02:00
* Crash when application scrolls **many** lines (> ~2³¹).
csi: DECCOLM+DECSCLM: remove all support We don’t support neither 132 column mode, nor smooth scrolling. Thus it makes little sense to recognize these control condes. Note that while XTerm does support 132 columns, it is disabled by default. In this mode, XTerm also doesn’t trigger the side-effects (i.e. clearing the screen). Closes #1265
2023-01-19 19:52:57 +01:00
* DECCOLM erasing the screen ([#1265][1265]).
render: fix application of old scroll damage when double buffering On compositors that forces us to double buffer, we need to re-apply the last frame’s damage to the current frame (which uses the buffer from the next-to-last frame). General cell updates are handled by simply copying from the last frame’s pixman buffer to the current frame’s. In an attempt to improve performance, scroll damage were up until now handled by re-playing the last frame’s scroll damage (on the current frame’s buffer). This does not work, and resulted in glitches when scrolling in the scrollback. This patch does the following: * grid_render_scroll{,_reverse}() now update the buffer’s "dirty" region. This means the generic copy-old-frames-buffer handles the scroll damage (albeit in, potentially, a less efficient way). * Tracking of, and re-applying old scroll damage is completely removed. Closes #1173
2022-09-22 18:34:41 +02:00
[1173]: https://codeberg.org/dnkl/foot/issues/1173
changelog: crash after reverse-scrolling in the normal screen
2022-10-14 18:05:12 +02:00
[1190]: https://codeberg.org/dnkl/foot/issues/1190
render: never apply alpha to text color When drawing a block cursor using inversed fg/bg colors, we didn’t strip the alpha from the background color. This meant that the text "behind" the cursor was rendered with transparency. If alpha was set to 0, the text was completely invisible. We should never apply alpha to the text color. So, detect this, and force alpha to 1.0. Normally, when selecting the cursor’s color, we don’t really know _where_ the background color is coming from (or more accurately, _what_ it is). However, the *only* background color that can have a non-1.0 alpha is the *default* background color. This is why we can ignore the bg parameter, and use term->colors.fg/bg instead. Closes #1205
2022-10-30 19:39:09 +01:00
[1205]: https://codeberg.org/dnkl/foot/issues/1205
wayland: use fp math all the way when calculating DPI This fixes an FPE when the monitor’s physical width/height is so small that the conversion from mm to inch resulted in inches being zero.
2022-11-04 17:42:52 +01:00
[1209]: https://codeberg.org/dnkl/foot/issues/1209
changelog: line-height adjustment with user-set line-height
2022-11-23 16:23:01 +01:00
[1218]: https://codeberg.org/dnkl/foot/issues/1218
config: don’t double-free key binding auxiliary data Key bindings with multiple key mappings share auxiliary data (e.g. the command to execute in pipe-* bindings, or the escape sequence in text-bindings). The first one is the designated “master” copy. Only that one should be freed. This fixed a double-free on exit, with e.g. [text-bindings] \x1b\x23=Mod4+space Mod4+equal Closes #1259
2023-01-15 10:24:01 +01:00
[1259]: https://codeberg.org/dnkl/foot/issues/1259
render: fix double-width glyphs glitching when surrounding cells overflow into it If cells overflowed (for example, by using an italic font that isn’t truly monospaced) into a double-width glyph (that itself is *not* overflowing), then the double-width glyph would glitch when being rendered; typically the second half of it would occasionally disappear. This happened because we tried to rasterize the second cell of the double-width glyph. This cell contains a special “spacer” value. Rasterizing that typically results the font’s “not available” glyph. If _that_ glyph overflows, things broke; we’d later end up forcing a re-render of it (thus erasing half the double-width glyph). But since the double-width glyph _itself_ doesn’t overflow, _it_ wouldn’t be re-rendered, leaving it half erased. Fix by recognizing spacer cells, and not trying to rasterize them (set glyph count to 0, and cell count to 1). Closes #1256
2023-01-15 14:42:48 +01:00
[1256]: https://codeberg.org/dnkl/foot/issues/1256
wayland: ignore configure events for unmapped surfaces Closes #1249 Note that it is still unclear whether ack:ing a configure event for an unmapped surface is a protocol violation, or something that should be handled by the compositor. According to https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/108, Kwin, Mutter and Weston handles it, while wlroots does not.
2022-12-29 11:32:21 +01:00
[1249]: https://codeberg.org/dnkl/foot/issues/1249
key-binding: sort binding lists Sort bindings such that bindings with the same symbol are sorted with the binding having the most modifiers comes first. This fixes an issue where the “wrong” key binding are triggered when used with “consumed” modifiers. For example: if Control+BackSpace is bound before Control+Shift+BackSpace, then the latter binding is never triggered. Why? Because Shift is a consumed modifier. This means Control+BackSpace is “the same” as Control+Shift+BackSpace. By sorting bindings with more modifiers first, we work around the problem. But note that it is *just* a workaround, and I’m not confident there aren’t cases where it doesn’t work. Closes #1280
2023-02-27 17:56:03 +01:00
[1280]: https://codeberg.org/dnkl/foot/issues/1280
input: (kitty kbd): the resulting UTF-8 string may translate to multiple UTF-32 codepoints When this happened (for example, by specifying a custom compose sequence), the kitty keyboard protocol didn’t emit any text at all. This was caused by the utf32 codepoint being -1. This in turned was caused by us trying to convert the utf8 sequence to a *single* utf32 codepoint. This patch replaces the use of mbrtoc32() with a call to ambstoc32(), and the utf32 codepoint with an utf32 string. The kitty keyboard protocol is updated: * When determining if we’re dealing with text, check *all* codepoints in the utf32 string. * Add support for multiple codepoints when reporting "associated text". The first codepoint is the actual parameter in the emitted sequence, and the remaining codepoints are sub-parameters. I.e. the codepoints are colon separated. Closes #1288
2023-03-27 16:56:10 +02:00
[1288]: https://codeberg.org/dnkl/foot/issues/1288
render: protect against integer underflow when calculating scroll area When applying scroll damage, we calculate the affected region’s height (in pixels), by subtracting the number of rows to scroll, from the scrolling region, and finally multiply by the cell height. If the number of rows to scroll is very large, the subtraction may underflow, resulting in a very large height value instead of a negative one. This caused the check for "scrolling too many lines" to fail. That in turn resulted in an integer overflow when calculating the source offset into the rendered surface buffer, which typically triggered a segfault. This bug happened when there was continuous output in the terminal without any new frames being rendered. This caused a buildup of scroll damage, that triggered the underflow+overflow when we finally did render a new frame. For example, a compositor that doesn’t send any frame callbacks (for example because the terminal window is minimized, or on a different workspace/tag) would cause this. Closes #1305
2023-03-28 18:31:24 +02:00
[1305]: https://codeberg.org/dnkl/foot/issues/1305
csi: DECCOLM+DECSCLM: remove all support We don’t support neither 132 column mode, nor smooth scrolling. Thus it makes little sense to recognize these control condes. Note that while XTerm does support 132 columns, it is disabled by default. In this mode, XTerm also doesn’t trigger the side-effects (i.e. clearing the screen). Closes #1265
2023-01-19 19:52:57 +01:00
[1265]: https://codeberg.org/dnkl/foot/issues/1265
terminal: don’t unref a not-yet-referenced key-binding set Key-binding sets are bound to a seat/configuration pair. The conf reference is done when a new terminal instance is created. When that same terminal instance is destroyed, the key binding set is unref:ed. If the terminal instance is destroyed *before* the key binding set has been referenced, we’ll still unref it. This creates an imbalance. In particular, when the there is exactly one other terminal instance referencing that same key binding set, that terminal instance will trigger a foot server crash as soon as it receives a key press/release event. This happens because the next-to-last terminal instance brought the reference count of the binding set down to 0, causing it to be free:d. Thus, we *must* reference the binding set *before* we can error out (when instantiating a new terminal instance). At this point, we don’t yet have a valid terminal instance. But, that’s ok, because all the key_binding_new_for_term() did with the terminal instance was get the "struct wayland" and "struct config" pointers. So, rename the function and simply pass these pointers explicitly. Similarly, change key_binding_for() to take a "struct config" pointer, rather than a "struct terminal" pointer. Also rename key_binding_unref_term() -> key_binding_unref().
2022-09-05 19:23:40 +02:00
Merge branch 'releases/1.13'
2022-08-31 19:26:21 +02:00
### Contributors
changelog: prepare for 1.14.0
2023-04-03 18:52:22 +02:00
* Alexey Sakovets
* Andrea Pappacoda
* Antoine Beaupré
* argosatcore
csi: reply with 4 instead of 2 for DECRQM queries of unsupported modes The status value 4 means "permanently reset", as opposed to 2, which means "reset". The former implies that there's no way to enable the mode because it's unsupported (but recognized). Note: this commit also fixes an unrelated typo in CHANGELOG.md.
2022-09-17 07:17:12 +01:00
* Craig Barnes
changelog: prepare for 1.14.0
2023-04-03 18:52:22 +02:00
* EuCaue
* Grigory Kirillov
* Harri Nieminen
* Hugo Osvaldo Barrera
* jaroeichler
* Joakim Nohlgård
* Nick Hastings
* Soren A D
* Torsten Trautwein
* Vladimír Magyar
* woojiq
* Yorick Peterse
csi: reply with 4 instead of 2 for DECRQM queries of unsupported modes The status value 4 means "permanently reset", as opposed to 2, which means "reset". The former implies that there's no way to enable the mode because it's unsupported (but recognized). Note: this commit also fixes an unrelated typo in CHANGELOG.md.
2022-09-17 07:17:12 +01:00
Merge branch 'releases/1.13'
2022-08-31 19:26:21 +02:00
changelog: prepare for 1.13.1
2022-08-31 19:17:38 +02:00
## 1.13.1
changelog: add new ‘unreleased’ section
2022-08-07 09:38:25 +02:00
### Changed
render: apply a dimmed overlay while in Unicode input mode
2022-08-08 16:31:28 +02:00
* Window is now dimmed while in Unicode input mode.
changelog: add new ‘unreleased’ section
2022-08-07 09:38:25 +02:00
### Fixed
wayland: #ifdef on XDG_TOPLEVEL_CONFIGURE_BOUNDS_SINCE_VERSION This enables us to compile against wayland-protocols < 1.25
2022-08-12 16:12:36 +02:00
* Compiling against wayland-protocols < 1.25
input: ignore pointer motion events on unknown surfaces In some cases, the compositor sends a pointer enter event with a NULL surface. It’s unclear if this is a compositor bug, or a race (where the compositor sends an enter event on a CSD surface at the same time foot unmaps the CSDs). Regardless, this causes seat->mouse_focus to be unset, which triggers a crash in foot on the next pointer motion event. This patch does two things: a) log a warning when we receive a pointer event with a NULL surface b) ignore motion events where seat->mouse_focus is NULL
2022-08-12 16:13:25 +02:00
* Crash on buggy compositors (GNOME) that sometimes send pointer-enter
events with a NULL surface. Foot now ignores these events, and the
subsequent motion and leave events.
selection: never highlight selected, empty cells This fixes a regression, where empty cells "between" non-empty cells (i.e. non-trailing empty cells) sometimes were incorrectly highlighted. The idea has always been to highlight exactly those cells that will get extracted when they’re copied. This means we’ve not highlighted trailing empty cells, but we _have_ highlighted other empty cells, since they are converted to spaces when copied (whereas trailing empty cells are skipped). fa2d9f86996467ba33cc381f810ea966a4323381 changed how a selection is updated. That is, which cells gets marked as selected, and which ones gets unmarked. Since we no longer walk all the cells, but instead work with pixman regions representing selection diffs, we can no longer determine (with certainty) which empty cells should be selected and which shouldn’t. Before this patch (but after fa2d9f86996467ba33cc381f810ea966a4323381), we sometimes incorrectly highlighted empty cells that should not have been highlighted. This happened when we’ve first (correctly) highlighted a region of empty cells, but then shrink the selection such that all those empty cells should be de-selected. This patch changes the selection behavior to *never* highlight empty cells. This fixes the regression, but also means slightly different behavior, compared to pre-fa2d9f86996467ba33cc381f810ea966a4323381. The other alternative is to always highlight all empty cells. But, since I personally like the fact that we’re skipping trailing empty cells, I prefer the approach taken by this patch.
2022-08-17 17:36:10 +02:00
* Regression: “random” selected empty cells being highlighted as
selected when they should not.
changelog: crash when resizing window, or scrolling
2022-08-29 21:04:56 +02:00
* Crash when either resizing the terminal window, or scrolling in the
scrollback history ([#1074][1074])
url-mode: connect osc-8 links only when both ID and URI matches Before this, two OSC-8 links with a matching ID would be connected even if their URIs weren’t the same. This is against the spec: The same id is only used for connecting character cells whose URIs is also the same. Character cells pointing to different URIs should never be underlined together when hovering over. https://gist.github.com/egmontkob/eb114294efbcd5adb1944c9f3cb5feda#hover-underlining-and-the-id-parameter
2022-08-30 17:48:04 +02:00
* OSC-8 URLs with matching IDs, but mismatching URIs being incorrectly
connected.
changelog: crash when resizing window, or scrolling
2022-08-29 21:04:56 +02:00
[1074]: https://codeberg.org/dnkl/foot/pulls/1074
wayland: #ifdef on XDG_TOPLEVEL_CONFIGURE_BOUNDS_SINCE_VERSION This enables us to compile against wayland-protocols < 1.25
2022-08-12 16:12:36 +02:00
changelog: prepare for 1.13.0
2022-08-07 09:31:56 +02:00
## 1.13.0
meson: add -Dsystemd-units-dir=<path> meson command line option This allows package maintainers to override the location to which our systemd service files are installed. It’s value is an *absolute* path, and *not* relative ${prefix}. The default is ${systemduserunitdir}.
2022-05-04 17:33:34 +02:00
changelog: add new ‘unreleased’ section
2022-04-27 20:09:16 +02:00
### Added
url-mode: add support for XDG activation when opening URLs First, add a ‘token’ argument to spawn(). When non-NULL, spawn() will set the ‘XDG_ACTIVATION_TOKEN’ environment variable in the forked process. If DISPLAY is non-NULL, we also set DESKTOP_STARTUP_ID, for compatibility with X11 applications. Note that failing to set either of these environment variables are considered non-fatal - i.e. we ignore failures. Next, add a helper function, wayl_get_activation_token(), to generate an XDG activation token, and call a user-provided callback when it’s ‘done (since token generation is asynchronous). This function takes an optional ‘seat’ and ‘serial’ arguments - when both are non-NULL/zero, we set the serial on the token. ‘win’ is a required argument, used to set the surface on the token. Re-write wayl_win_set_urgent() to use the new helper function. Finally, rewrite activate_url() to first try to get an activation token (and spawn the URL launcher in the token callback). If that fails, or if we don’t have XDG activation support, spawn the URL launcher immediately (like before this patch). Closes #1058
2022-05-03 19:37:04 +02:00
* XDG activation support when opening URLs ([#1058][1058]).
meson: add -Dsystemd-units-dir=<path> meson command line option This allows package maintainers to override the location to which our systemd service files are installed. It’s value is an *absolute* path, and *not* relative ${prefix}. The default is ${systemduserunitdir}.
2022-05-04 17:33:34 +02:00
* `-Dsystemd-units-dir=<path>` meson command line option.
changelog: new ‘environment’ section in foot.ini
2022-05-28 19:28:45 +02:00
* Support for custom environment variables in `foot.ini`
([#1070][1070]).
osc: add support for OSC 133;A (prompt markers) 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
2022-06-15 18:44:23 +02:00
* Support for jumping to previous/next prompt (requires shell
integration). By default bound to `ctrl`+`shift`+`z` and
`ctrl`+`shift`+`x` respectively ([#30][30]).
config: add colors.search-box-{no-,}match Closes #1112
2022-07-27 19:14:27 +02:00
* `colors.search-box-no-match` and `colors.search-box-match` options
to `foot.ini` ([#1112][1112]).
input: add new Unicode input mode 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
2022-07-28 18:09:16 +02:00
* Very basic Unicode input mode via the new
`key-bindings.unicode-input` and `search-bindings.unicode-input` key
bindings. Note that there is no visual feedback, as the preferred
way of entering Unicode characters is with an IME ([#1116][1116]).
Add support for xdg_toplevel.wm_capabilities See https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/122
2022-05-06 20:05:04 +02:00
* Support for `xdg_toplevel.wm_capabilities`, to adapt the client-side
decoration buttons to the compositor capabilities ([#1061][1061]).
url-mode: add support for XDG activation when opening URLs First, add a ‘token’ argument to spawn(). When non-NULL, spawn() will set the ‘XDG_ACTIVATION_TOKEN’ environment variable in the forked process. If DISPLAY is non-NULL, we also set DESKTOP_STARTUP_ID, for compatibility with X11 applications. Note that failing to set either of these environment variables are considered non-fatal - i.e. we ignore failures. Next, add a helper function, wayl_get_activation_token(), to generate an XDG activation token, and call a user-provided callback when it’s ‘done (since token generation is asynchronous). This function takes an optional ‘seat’ and ‘serial’ arguments - when both are non-NULL/zero, we set the serial on the token. ‘win’ is a required argument, used to set the surface on the token. Re-write wayl_win_set_urgent() to use the new helper function. Finally, rewrite activate_url() to first try to get an activation token (and spawn the URL launcher in the token callback). If that fails, or if we don’t have XDG activation support, spawn the URL launcher immediately (like before this patch). Closes #1058
2022-05-03 19:37:04 +02:00
[1058]: https://codeberg.org/dnkl/foot/issues/1058
changelog: new ‘environment’ section in foot.ini
2022-05-28 19:28:45 +02:00
[1070]: https://codeberg.org/dnkl/foot/issues/1070
osc: add support for OSC 133;A (prompt markers) 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
2022-06-15 18:44:23 +02:00
[30]: https://codeberg.org/dnkl/foot/issues/30
config: add colors.search-box-{no-,}match Closes #1112
2022-07-27 19:14:27 +02:00
[1112]: https://codeberg.org/dnkl/foot/issues/1112
input: add new Unicode input mode 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
2022-07-28 18:09:16 +02:00
[1116]: https://codeberg.org/dnkl/foot/issues/1116
Add support for xdg_toplevel.wm_capabilities See https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/122
2022-05-06 20:05:04 +02:00
[1061]: https://codeberg.org/dnkl/foot/pulls/1061
url-mode: add support for XDG activation when opening URLs First, add a ‘token’ argument to spawn(). When non-NULL, spawn() will set the ‘XDG_ACTIVATION_TOKEN’ environment variable in the forked process. If DISPLAY is non-NULL, we also set DESKTOP_STARTUP_ID, for compatibility with X11 applications. Note that failing to set either of these environment variables are considered non-fatal - i.e. we ignore failures. Next, add a helper function, wayl_get_activation_token(), to generate an XDG activation token, and call a user-provided callback when it’s ‘done (since token generation is asynchronous). This function takes an optional ‘seat’ and ‘serial’ arguments - when both are non-NULL/zero, we set the serial on the token. ‘win’ is a required argument, used to set the surface on the token. Re-write wayl_win_set_urgent() to use the new helper function. Finally, rewrite activate_url() to first try to get an activation token (and spawn the URL launcher in the token callback). If that fails, or if we don’t have XDG activation support, spawn the URL launcher immediately (like before this patch). Closes #1058
2022-05-03 19:37:04 +02:00
changelog: add new ‘unreleased’ section
2022-04-27 20:09:16 +02:00
### Changed
config: use $HOME instead of getpwuid() to retrieve users’s home dir When searching for foot.ini, use $HOME instead of getpwuid() to retrieve the user’s home directory.
2022-05-24 18:18:15 +02:00
* Use `$HOME` instead of `getpwuid()` to retrieve the user’s home
directory when searching for `foot.ini`.
selection: allow HT, VT and FF, disallow NUL in non-bracketed paste mode 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
2022-06-13 11:41:54 +02:00
* HT, VT and FF are no longer stripped when pasting in non-bracketed
mode ([#1084][1084]).
* NUL is now stripped when pasting in non-bracketed mode
([#1084][1084]).
keymap: change alt+escape to emit \E\E instead of a CSI 27 sequence Closes #1105
2022-07-26 18:19:34 +02:00
* `alt`+`escape` now emits `\E\E` instead of a `CSI 27` sequence
([#1105][1105]).
selection: allow HT, VT and FF, disallow NUL in non-bracketed paste mode 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
2022-06-13 11:41:54 +02:00
[1084]: https://codeberg.org/dnkl/foot/issues/1084
keymap: change alt+escape to emit \E\E instead of a CSI 27 sequence Closes #1105
2022-07-26 18:19:34 +02:00
[1105]: https://codeberg.org/dnkl/foot/issues/1105
config: use $HOME instead of getpwuid() to retrieve users’s home dir When searching for foot.ini, use $HOME instead of getpwuid() to retrieve the user’s home directory.
2022-05-24 18:18:15 +02:00
changelog: add new ‘unreleased’ section
2022-04-27 20:09:16 +02:00
### Fixed
terminal: move viewport when part of it is scrolled out If the viewport is at the top of the scrollback, and a program is scrolling (e.g. by emitting newlines), the viewport needs to be moved. Otherwise, the top of the viewport will show the *bottom* of the scrollback (i.e. the newly emitted lines), and the bottom of the viewport shows the top of the scrollback. How do we detect if the viewport needs to be moved? We convert its absolute row number to a scrollback relative row. This number is also the maximum number of rows we can scroll without the viewport being scrolled out. In other words, if the number of rows to scroll is larger than the viewports scrollback relative row number, the viewport needs to moved. How much do we need to move it? The difference between the number of rows to scroll, and the viewports scrollback relative row number. Example: if the viewport is at the very top of the scrollback, its scrollback relative row number is 0. In this case, it needs to be moved the same number of rows as is being scrolled.
2022-05-11 17:58:18 +02:00
* Graphical corruption when viewport is at the top of the scrollback,
and the output is scrolling.
selection: ignore drag-and-drops with unsupported mime-types 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
2022-06-20 19:29:57 +02:00
* Improved text reflow of logical lines with trailing empty cells
([#1055][1055])
ime: track IME focus independently from keyboard focus Replace the seat->ime.focused boolean with a terminal instace pointer, seat->ime_focus. Set and reset this on ime::enter() and ime::leave() events, and use this instead of seat->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.
2022-06-15 18:41:08 +02:00
* IME focus is now tracked independently from keyboard focus.
selection: ignore drag-and-drops with unsupported mime-types 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
2022-06-20 19:29:57 +02:00
* Workaround for buggy compositors (e.g. some versions of GNOME)
allowing drag-and-drops even though foot has reported it does not
support the offered mime-types ([#1092][1092]).
input: don’t ignore keyboard enter/leave events when there’s no keymap 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
2022-06-28 20:57:48 +02:00
* Keyboard enter/leave events being ignored if there is no keymap
([#1097][1097]).
csi: clamp color index for ‘CSI 38/48 ; 5 ; idx m’ sequences 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
2022-07-22 10:44:33 +02:00
* Crash when application emitted an invalid `CSI 38;5;<idx>m`, `CSI
38:5:<idx>m`, `CSI 48;5;<idx>m` or `CSI 48:5:<idx>m` sequence
([#1111][1111]).
input: kitty: always treat composed characters as ‘printable’ Certain dead key combinations results different escape sequences in foot, compared to kitty, when the kitty keyboard protocol is used. if (composed && 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
2022-07-26 18:44:29 +02:00
* Certain dead-key combinations resulting in different escape
sequences compared to kitty, when the kitty keyboard protocol is
used ([#1120][1120]).
search: find_next(): handle trailing SPACER cells 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.
2022-07-28 18:56:28 +02:00
* Search matches ending with a double-width character not being
highlighted correctly.
selection: selection_on_rows(): use scrollback relative coords 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.
2022-07-28 18:27:13 +02:00
* Selection not being cancelled correctly when scrolled out.
selection: extend: use scrollback relative coordinates 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.
2022-07-28 18:32:17 +02:00
* Extending a multi-page selection behaving inconsistently.
selection: rework how we update a selection 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
2022-07-28 18:45:25 +02:00
* Poor performance when making very large selections ([#1114][1114]).
server: Use "normal" socket activation, not inetd 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
2022-07-29 20:12:47 +02:00
* Bogus error message when using systemd socket activation for server
mode ([#1107][1107])
grid: get rid of empty row at the bottom after reflowing 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
2022-08-05 18:26:37 +02:00
* Empty line at the bottom after a window resize ([#1108][1108]).
grid: reflow: don’t trim trailing empty cells from logical lines 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
2022-06-01 19:29:30 +02:00
[1055]: https://codeberg.org/dnkl/foot/issues/1055
selection: ignore drag-and-drops with unsupported mime-types 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
2022-06-20 19:29:57 +02:00
[1092]: https://codeberg.org/dnkl/foot/issues/1092
input: don’t ignore keyboard enter/leave events when there’s no keymap 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
2022-06-28 20:57:48 +02:00
[1097]: https://codeberg.org/dnkl/foot/issues/1097
csi: clamp color index for ‘CSI 38/48 ; 5 ; idx m’ sequences 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
2022-07-22 10:44:33 +02:00
[1111]: https://codeberg.org/dnkl/foot/issues/1111
input: kitty: always treat composed characters as ‘printable’ Certain dead key combinations results different escape sequences in foot, compared to kitty, when the kitty keyboard protocol is used. if (composed && 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
2022-07-26 18:44:29 +02:00
[1120]: https://codeberg.org/dnkl/foot/issues/1120
selection: rework how we update a selection 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
2022-07-28 18:45:25 +02:00
[1114]: https://codeberg.org/dnkl/foot/issues/1114
server: Use "normal" socket activation, not inetd 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
2022-07-29 20:12:47 +02:00
[1107]: https://codeberg.org/dnkl/foot/issues/1107
grid: get rid of empty row at the bottom after reflowing 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
2022-08-05 18:26:37 +02:00
[1108]: https://codeberg.org/dnkl/foot/issues/1108
terminal: move viewport when part of it is scrolled out If the viewport is at the top of the scrollback, and a program is scrolling (e.g. by emitting newlines), the viewport needs to be moved. Otherwise, the top of the viewport will show the *bottom* of the scrollback (i.e. the newly emitted lines), and the bottom of the viewport shows the top of the scrollback. How do we detect if the viewport needs to be moved? We convert its absolute row number to a scrollback relative row. This number is also the maximum number of rows we can scroll without the viewport being scrolled out. In other words, if the number of rows to scroll is larger than the viewports scrollback relative row number, the viewport needs to moved. How much do we need to move it? The difference between the number of rows to scroll, and the viewports scrollback relative row number. Example: if the viewport is at the very top of the scrollback, its scrollback relative row number is 0. In this case, it needs to be moved the same number of rows as is being scrolled.
2022-05-11 17:58:18 +02:00
changelog: add new ‘unreleased’ section
2022-04-27 20:09:16 +02:00
### Contributors
changelog: prepare for 1.13.0
2022-08-07 09:31:56 +02:00
* Craig Barnes
* Lorenz
* Max Gautier
* Simon Ser
* Stefan Prosiegel
changelog: add new ‘unreleased’ section
2022-04-27 20:09:16 +02:00
changelog: prepare for 1.12.1
2022-04-27 20:05:51 +02:00
## 1.12.1
changelog: add new ‘unreleased’ section
2022-04-22 17:19:04 +02:00
### Added
changelog: workaround for Sway bug #6960
2022-04-26 17:28:36 +02:00
* Workaround for Sway bug [#6960][sway-6960]: scrollback search and
changelog: typo: space on the wrong side of the parenthesis
2022-04-26 17:52:00 +02:00
the OSC-555 (“flash”) escape sequence leaves dimmed (search) and
changelog: workaround for Sway bug #6960
2022-04-26 17:28:36 +02:00
yellow (flash) artifacts ([#1046][1046]).
config: add ctrl+shift+v and XF86 paste to SEARCH_CLIPBOARD_PASTE 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
2022-04-26 18:34:18 +02:00
* `Control+Shift+v` and `XF86Paste` have been added to the default set
of key bindings that paste from the clipboard into the scrollback
search buffer. This is in addition to the pre-existing `Control+v`
and `Control+y` bindings.
changelog: workaround for Sway bug #6960
2022-04-26 17:28:36 +02:00
[sway-6960]: https://github.com/swaywm/sway/issues/6960
[1046]: https://codeberg.org/dnkl/foot/issues/1046
changelog: add new ‘unreleased’ section
2022-04-22 17:19:04 +02:00
### Changed
changelog: changed behavior of “extend-to-word-boundary”
2022-04-27 18:52:08 +02:00
* Scrollback search’s `extend-to-word-boundary` no longer stops at
space-to-word boundaries, making selection extension feel more
natural.
changelog: add new ‘unreleased’ section
2022-04-22 17:19:04 +02:00
### Fixed
changelog: pgo helper binary build fix (missing key-binding stubs)
2022-04-23 00:49:52 +02:00
* build: missing symbols when linking the `pgo` helper binary.
changelog: UI not refreshing when pasting into the scrollback search box
2022-04-24 12:08:23 +02:00
* UI not refreshing when pasting something into the scrollback search
box, that does not result in a grid update (for example, when the
search criteria did not result in any matches) ([#1040][1040]).
search: fix infinite loop when highlighting all matches 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
2022-04-26 18:24:22 +02:00
* foot freezing in scrollback search mode, using 100% CPU
([#1036][1036], [#1047][1047]).
changelog: crash when extending selection in search mode
2022-04-26 17:40:00 +02:00
* Crash when extending a selection to the next word boundary in
scrollback search mode ([#1036][1036]).
changelog: search mode not always highlighting all matches correctly
2022-04-26 17:40:20 +02:00
* Scrollback search mode not always highlighting all matches
correctly.
term: reset sixel options when hard resetting the terminal state
2022-04-26 21:05:17 +02:00
* Sixel options not being reset on hard resets (`\Ec`)
changelog: UI not refreshing when pasting into the scrollback search box
2022-04-24 12:08:23 +02:00
[1040]: https://codeberg.org/dnkl/foot/issues/1040
changelog: scrollback mode freezing, with 100% CPU
2022-04-23 15:19:32 +02:00
[1036]: https://codeberg.org/dnkl/foot/issues/1036
changelog: fix URL in #1047 issue link
2022-04-28 19:29:06 +02:00
[1047]: https://codeberg.org/dnkl/foot/issues/1047
changelog: pgo helper binary build fix (missing key-binding stubs)
2022-04-23 00:49:52 +02:00
changelog: prepare for 1.12.0
2022-04-22 17:14:00 +02:00
## 1.12.0
changelog: OSC-22
2022-01-01 13:59:19 +01:00
changelog: add new ‘unreleased’ section
2022-02-05 17:38:24 +01:00
### Added
changelog: OSC-22
2022-01-01 13:59:19 +01:00
* OSC-22 - set xcursor pointer.
changelog: fallback xcursor
2022-02-07 22:01:23 +05:30
* Add "xterm" as fallback cursor where "text" is not available.
config/input: add scrollback-home|end key bindings (unbound by default)
2022-02-23 19:03:54 +01:00
* `[key-bindings].scrollback-home|end` options.
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
* Socket activation for `foot --server` and accompanying systemd unit
files
changelog: move “re-mapping input” from “changed” to “added”
2022-04-20 20:56:04 +02:00
* Support for re-mapping input, i.e. mapping input to custom escape
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
sequences ([#325][325]).
* Support for [DECNKM](https://vt100.net/docs/vt510-rm/DECNKM.html),
which allows setting/saving/restoring/querying the keypad mode.
config: add tweak option to allow disabling sixels Closes #950
2022-02-27 16:29:35 +01:00
* Sixel support can be disabled by setting `[tweak].sixel=no`
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#950][950]).
client: add -E,--client-environment When this option is used, the child process in the new terminal instance will inherit its environment from the footclient process, instead of the foot server’s. Implemented by sending (yet another) dynamic string list as part of the client -> server setup packet. When the new option is *not* used, the setup packet is now 2 bytes larger than before. On the server side, the slave process now uses execvpe() instead of execvp(). There’s plumbing to propagate a new ‘envp’ argument from term_init() all the way down to slave_exec(). If ‘envp’ is NULL, we use ‘environ’ instead (thus matching the old behavior of execvp()). Closes #1004
2022-04-11 12:19:40 +02:00
* footclient: `-E,--client-environment` command line option. When
used, the child process in the new terminal instance inherits the
environment from the footclient process instead of the server’s
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#1004][1004]).
* `[csd].hide-when-maximized=yes|no` option ([#1019][1019]).
changelog: scrollback search mode highlights all matches
2022-04-17 11:05:14 +02:00
* Scrollback search mode now highlights all matches.
url-mode: add a key binding that enables “persistent” URL mode This is an alternative to ‘show-urls-launch’, where we stay in URL mode after activating an URL. Closes #964
2022-03-22 19:07:06 +01:00
* `[key-binding].show-urls-persistent` action. This key binding action
is similar to `show-urls-launch`, but does not automatically exit
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
URL mode after activating an URL ([#964][964]).
csi: implement CSI > 4n (reset modifyOtherKeys)
2022-04-19 17:25:06 +02:00
* Support for `CSI > 4 n`, disable _modifyOtherKeys_. Note that since
foot only supports level 1 and 2 (and not level 0), this sequence
does not disable _modifyOtherKeys_ completely, but simply reverts it
back to level 1 (the default).
meson: add -Dtests=false|true option When set to false, no test binaries are neither built, nor executed (with “ninja test”). Closes #919
2022-02-06 12:51:54 +01:00
* `-Dtests=false|true` meson command line option. When disabled, test
binaries will neither be built, nor will `ninja test` attempt to
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
execute them. Enabled by default ([#919][919]).
changelog: OSC-22
2022-01-01 13:59:19 +01:00
changelog: hyperlink lists under their corresponding sub-section
2022-04-23 11:13:25 +02:00
[325]: https://codeberg.org/dnkl/foot/issues/325
[950]: https://codeberg.org/dnkl/foot/issues/950
[1004]: https://codeberg.org/dnkl/foot/issues/1004
[1019]: https://codeberg.org/dnkl/foot/issues/1019
[964]: https://codeberg.org/dnkl/foot/issues/964
[919]: https://codeberg.org/dnkl/foot/issues/919
input: get_current_modifiers(): don’t crash if seat has no keyboard Closes #963
2022-03-04 17:54:19 +01:00
changelog: add new ‘unreleased’ section
2022-02-05 17:38:24 +01:00
### Changed
changelog: mouse selections are finalized on window resize
2022-02-07 10:44:00 +01:00
meson: stop using deprecated functions, require meson >= 0.58 * get_pkgconfig_variable() -> get_variable() * prog.path() -> prog.full_path() * meson.build_root() -> meson.global_build_root()
2022-02-27 11:26:40 +01:00
* Minimum required meson version is now 0.58.
changelog: mouse selections are finalized on window resize
2022-02-07 10:44:00 +01:00
* Mouse selections are now finalized when the window is resized
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#922][922]).
osc: use four digits in OSC-4 and OSC-11 rgb:r/g/b replies Closes #971
2022-03-13 09:05:55 +01:00
* OSC-4 and OSC-11 replies now uses four digits instead of 2
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#971][971]).
selection: don’t translate \r to \n when pasting In non-bracketed paste mode, we translate \n to \r, and \r\n to \r. The latter matches XTerm, urxvt, alacritty and kitty. The former matches alacritty and kitty (xterm and urxvt just blindly replaces all \n occurrences with \r, meaning \r\n is translated to \r\r. For some reason, we then unconditionally translated all \r back to \n, regardless of whether bracketed paste was enabled or not. Unsure why/where this comes from, but it doesn't match any of the other terminal emulators I tested. One example where this caused issues is in older versions of nano (at least up to 2.9). Closes #980
2022-03-16 20:17:02 +01:00
* `\r` is no longer translated to `\n` when pasting clipboard data
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#980][980]).
Use circles for rendering light arc box-drawing characters. Ellipses can look weird when the font is narrow. Closes #988
2022-03-23 11:55:16 +01:00
* Use circles for rendering light arc box-drawing characters
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#988][988]).
meson: install foot.ini to /etc/xdg/foot/foot.ini Closes #1001
2022-04-06 19:03:59 +02:00
* Example configuration is now installed to
`${sysconfdir}/xdg/foot/foot.ini`, typically resolving to
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
`/etc/xdg/foot/foot.ini` ([#1001][1001]).
changelog: mouse selections are finalized on window resize
2022-02-07 10:44:00 +01:00
changelog: hyperlink lists under their corresponding sub-section
2022-04-23 11:13:25 +02:00
[922]: https://codeberg.org/dnkl/foot/issues/922
[971]: https://codeberg.org/dnkl/foot/issues/971
[980]: https://codeberg.org/dnkl/foot/issues/980
[988]: https://codeberg.org/dnkl/foot/issues/988
[1001]: https://codeberg.org/dnkl/foot/issues/1001
changelog: mouse selections are finalized on window resize
2022-02-07 10:44:00 +01:00
changelog: add new ‘unreleased’ section
2022-02-05 17:38:24 +01:00
### Removed
csi/input: remove private mode 27127 This effectively reverts commit 31c73f0cf01e1d0bdcd1435136b010c1c1ab442c.
2022-02-09 20:50:20 +00:00
* DECSET mode 27127 (which was first added in release 1.6.0).
The kitty keyboard protocol (added in release 1.10.3) can
be used to similar effect.
input: get_current_modifiers(): don’t crash if seat has no keyboard Closes #963
2022-03-04 17:54:19 +01:00
changelog: add new ‘unreleased’ section
2022-02-05 17:38:24 +01:00
### Fixed
changelog: missing ‘wayland_client’ dependency in test-config
2022-02-06 12:05:01 +01:00
* Build: missing `wayland_client` dependency in `test-config`
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#918][918]).
changelog: “(null)” being logged as font-name
2022-02-06 12:07:05 +01:00
* “(null)” being logged as font-name (for some fonts) when warning
about a non-monospaced primary font.
changelog: mouse selections are finalized on window resize
2022-02-07 10:44:00 +01:00
* Rare crash when the window is resized while a mouse selection is
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
ongoing ([#922][922]).
* Large selections crossing the scrollback wrap-around ([#924][924]).
* Crash in `pipe-scrollback` ([#926][926]).
main: --server: don’t exit with code 0 on failure A foot --server instance would exit with code 0, even on failure, if the number of currently open terminal instances were 0. This is because ‘ret’ assumed failure, and then tried to set it to ‘success’ after the even loop had terminated, basted on the server’s current state. Fix by: * set ‘ret’ to success just before entering the event loop * set ‘ret’ to failure when we detect an FDM failure * don’t try to second-guess success/failure after having exited the event loop Closes #943
2022-02-16 22:40:51 +01:00
* Exit code being 0 when a foot server with no open windows terminate
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
due to e.g. a Wayland connection failure ([#943][943]).
config: do key binding collision handling in overrides This ensures we detect, and handle, collisions also for key-bindings specified as overrides.
2022-02-08 21:21:17 +01:00
* Key binding collisions not detected for bindings specified as option
overrides on the command line.
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
* Crash when seat has no keyboard ([#963][963]).
input: don’t allow non-significant modifiers when matching untranslated symbols When matching “untranslated” bindings (by matching the base symbol of the key, e.g. ctrl+shift+2 in US layout), require that no non-significant modifiers are active. This fixes an issue where AltGr was “ignored”, and would cause certain combinations to match a key binding. Example: ctrl+altgr+0, on many European layouts matched against the default ctrl+0 (reset the font size), instead of emitting ^] To make this work, we now need to filter out “locked” modifiers (e.g. NumLock and CapsLock). Otherwise having e.g. NumLock active would prevent *all* untranslated matching to fail. Closes #983
2022-03-19 18:59:15 +01:00
* Key presses with e.g. `AltGr` triggering key combinations with the
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
base symbol ([#983][983]).
render: ensure an underline cursor is not positioned too low The underline cursor is positioned just below regular underlines. A bug in the positioning logic related to this, sometimes resulted in the cursor being thinner than what it should be, or even invisible. Fixes #1005
2022-04-05 19:18:46 +02:00
* Underline cursor sometimes being positioned too low, either making
it look thinner than what it should be, or being completely
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
invisible ([#1005][1005]).
config: fallback to /etc/xdg if XDG_CONFIG_DIRS is unset Closes #1008
2022-04-06 18:44:09 +02:00
* Fallback to `/etc/xdg` if `XDG_CONFIG_DIRS` is unset
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#1008][1008]).
changelog: improved compatibility with XTerm when modifyOtherKeys=2
2022-04-07 13:03:31 +02:00
* Improved compatibility with XTerm when `modifyOtherKeys=2`
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
([#1009][1009]).
render: take visible border width into account when setting window geometry This fixes e.g. window snapping in GNOME.
2022-04-16 10:47:55 +02:00
* Window geometry when CSDs are enabled and CSD border width set to a
non-zero value. This fixes window snapping in e.g. GNOME.
wayland: take (visible) border width into account on configure events When the compositor is asking us to resize ourselves, take our (visible) CSD borders into account. This is similar to how we already take the titlebar size into account. This fixes an issue where the window size “jumps” when the user starts an interactive resize, when csd.border-width > 0. This as been observed in GNOME.
2022-04-16 11:15:10 +02:00
* Window size “jumping” when starting an interactive resize when CSDs
are enabled, and CSD border width set to a non-zero value.
changelog: key binding overrides having no effect with footclient
2022-04-17 16:01:30 +02:00
* Key binding overrides on the command line having no effect with
changelog: convert all issue links to reference links in the 1.12.0 release
2022-04-22 20:05:33 +02:00
`footclient` instances ([#931][931]).
search: fix next/prev not updating selection correctly when matches overlap When the new match overlapped with the old match, the selection wasn’t updated correctly.
2022-04-17 19:16:47 +02:00
* Search prev/next not updating the selection correctly when the
previous and new match overlaps.
search: don't modify search.start coord *before* finding next match The match logic uses the last start coordinate to determine which end points in the selection to update. This sometimes fails when the start coordinate has been changed by e.g. a key binding - the new start coordinate is incorrectly matched against the old-but-modified start coordinate, causing foot to e.g. *not* upate the selection start coordinate. Example: $ echo 'test\n\test\ntest' Then do a scrollback search for 'test. The first match is found correctly (the last 'test'), but searching for the previous match (ctrl+r) does not select the middle 'test'. Fix by passing the search direction to search_find_next(), and have _it_ calculate the coordinate to start search. There are three possibilities: * forward * backward * "backward", but at the same position The first two are used when searching for next/prev match with ctrl+s and ctrl+r. The last one is used when the search criteria is updated. In this case, we don't want to move to the previous match, *unless* the current match no longer matches.
2022-04-21 18:54:27 +02:00
* Various minor fixes to scrollback search, and how it finds the
next/prev match.
changelog: missing ‘wayland_client’ dependency in test-config
2022-02-06 12:05:01 +01:00
changelog: hyperlink lists under their corresponding sub-section
2022-04-23 11:13:25 +02:00
[918]: https://codeberg.org/dnkl/foot/issues/918
[922]: https://codeberg.org/dnkl/foot/issues/922
[924]: https://codeberg.org/dnkl/foot/issues/924
[926]: https://codeberg.org/dnkl/foot/issues/926
[943]: https://codeberg.org/dnkl/foot/issues/943
[963]: https://codeberg.org/dnkl/foot/issues/963
[983]: https://codeberg.org/dnkl/foot/issues/983
[1005]: https://codeberg.org/dnkl/foot/issues/1005
[1008]: https://codeberg.org/dnkl/foot/issues/1008
[1009]: https://codeberg.org/dnkl/foot/issues/1009
[931]: https://codeberg.org/dnkl/foot/issues/931
changelog: missing ‘wayland_client’ dependency in test-config
2022-02-06 12:05:01 +01:00
changelog: add new ‘unreleased’ section
2022-02-05 17:38:24 +01:00
### Contributors
changelog: prepare for 1.12.0
2022-04-22 17:14:00 +02:00
* Ashish SHUKLA
csi: add support for DECNKM private mode This is equivalent to DECKPAM/DECKPNM when enabled/disabled, but can also be saved/restored/queried with XTSAVE/XTRESTORE/DECRQM. See also: * https://vt100.net/docs/vt510-rm/DECNKM.html * https://vt100.net/docs/vt510-rm/DECKPAM.html * https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-PC-Style-Function-Keys
2022-03-19 13:14:54 +00:00
* Craig Barnes
changelog: prepare for 1.12.0
2022-04-22 17:14:00 +02:00
* Enes Hecan
* Johannes Altmanninger
* L3MON4D3
* Leonardo Neumann
* Mariusz Bialonczyk
* Max Gautier
* Merlin Büge
* jvoisin
* merkix
csi: add support for DECNKM private mode This is equivalent to DECKPAM/DECKPNM when enabled/disabled, but can also be saved/restored/queried with XTSAVE/XTRESTORE/DECRQM. See also: * https://vt100.net/docs/vt510-rm/DECNKM.html * https://vt100.net/docs/vt510-rm/DECKPAM.html * https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-PC-Style-Function-Keys
2022-03-19 13:14:54 +00:00
changelog: add new ‘unreleased’ section
2022-02-05 17:38:24 +01:00
changelog: prepare for 1.11.0
2022-02-05 17:19:43 +01:00
## 1.11.0
changelog: add new ‘unreleased’ section
2021-12-02 20:36:09 +01:00
### Added
changelog: list new mouse.selection-override-modifiers option
2021-10-09 21:40:11 +00:00
config, doc, changelog: move selection-override-modifiers to [mouse-bindings] and validate other case specifically, check for conflicts both when mouse bindings are set and when the selection-override-modifiers setting itself is set
2021-11-29 22:06:35 +00:00
* `[mouse-bindings].selection-override-modifiers` option, specifying
which modifiers to hold to override mouse grabs by client
applications and force selection instead.
changelog: irc+ircs added to default value of url.protocols
2021-12-27 21:13:26 +01:00
* _irc://_ and _ircs://_ to the default set of protocols recognized
when auto-detecting URLs.
SGR-Pixels mouse mode, closes #762
2021-12-30 05:13:45 -06:00
* [SGR-Pixels (1016) mouse extended coordinates](https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Extended-coordinates) is now supported
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#762](https://codeberg.org/dnkl/foot/issues/762)).
changelog: XTGETTCAP
2022-01-14 13:34:23 +01:00
* `XTGETTCAP` - builtin terminfo. See
[README.md::XTGETTCAP](README.md#xtgettcap) for details
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#846](https://codeberg.org/dnkl/foot/issues/846)).
dcs: implement DECRQSS This patch adds support for DECRQSS (request Selection or Setting), for the following sub-queries: * DECSTBM Set Top and Bottom Margins * SGR Set Graphic Rendition * DECSCUSR Set Cursor Style Closes #798
2022-01-13 15:36:27 +01:00
* `DECRQSS` - _Request Selection or Setting_
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#798](https://codeberg.org/dnkl/foot/issues/798)). Implemented settings
dcs: implement DECRQSS This patch adds support for DECRQSS (request Selection or Setting), for the following sub-queries: * DECSTBM Set Top and Bottom Margins * SGR Set Graphic Rendition * DECSCUSR Set Cursor Style Closes #798
2022-01-13 15:36:27 +01:00
are:
- `DECSTBM` - _Set Top and Bottom Margins_
- `SGR` - _Set Graphic Rendition_
- `DECSCUSR` - _Set Cursor Style_
changelog: search for last searched-for string
2022-01-27 18:40:04 +01:00
* Support for searching for the last searched-for string in scrollback
search (search for next/prev match with an empty search string).
dcs: implement DECRQSS This patch adds support for DECRQSS (request Selection or Setting), for the following sub-queries: * DECSTBM Set Top and Bottom Margins * SGR Set Graphic Rendition * DECSCUSR Set Cursor Style Closes #798
2022-01-13 15:36:27 +01:00
changelog: improved handling of incompatible locales
2022-01-11 21:37:41 +01:00
Merge branch 'releases/1.10'
2021-12-08 18:14:44 +01:00
### Changed
themes: consistently use snake-case in theme names
2021-12-18 14:24:30 +01:00
* PaperColorDark and PaperColorLight themes renamed to
paper-color-dark and paper-color-light, for consistency with other
theme names.
input: apply scrollback.multplier in alterate scroll mode Before this patch, foot only applied [scrollback].multiplier on the normal screen, never the alt screen. However, scrolling can be done in two ways on the alt screen: If the application has enabled mouse support, we simply pass on the mouse scroll events to the application. Here, it makes sense to not apply the multiplier, and instead let the application choose how much to scroll for each scroll event. But, if the application has not enabled mouse support, we can still scroll by simulating the arrow keys being pressed - alternate scrolling (private mode 1007). This is enabled by default in foot (but can be disabled in foot.ini with the [mouse].alternate-scroll-mode setting). In this mode, it makes more sense to apply the multiplier. And that’s what this patch changes - the multiplier is now applied, on the alt screen, when the application has not enabled mouse support, and alternate scrolling has been enabled in foot. Closes #859
2021-12-24 15:22:14 +01:00
* `[scrollback].multiplier` is now applied in “alternate scroll” mode,
where scroll events are translated to fake arrow key presses on the
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
alt screen ([#859](https://codeberg.org/dnkl/foot/issues/859)).
render: scale the width out the outline of the unfocused block cursor
2021-12-28 20:51:19 +01:00
* The width of the block cursor’s outline in an unfocused window is
now scaled by the output scaling factor (“desktop
scaling”). Previously, it was always 1px.
changelog: improved handling of incompatible locales
2022-01-11 21:37:41 +01:00
* Foot will now try to change the locale to either “C.UTF-8” or
“en_US.UTF-8” if started with a non-UTF8 locale. If this fails, foot
will start, but only to display a window with an error (user’s shell
is not executed).
replace gettimeofday with clock_gettime POSIX.1-2008 has marked gettimeofday(2) as obsolete, recommending the use of clock_gettime(2) instead. CLOCK_MONOTONIC has been used instead of CLOCK_REALTIME because it is unaffected by manual changes in the system clock. This makes it better for our purposes, namely, measuring the difference between two points in time. tv_sec has been casted to long in most places since POSIX does not define the actual type of time_t.
2022-01-15 14:56:13 +05:30
* `gettimeofday()` has been replaced with `clock_gettime()`, due to it being
marked as obsolete by POSIX.
keymap: alt-tab (C-tab) now emits “ESC tab” by default In our default mode (roughly equivalent to XTerm’s modifyOtherKeys=1), alt-tab now emits ESC-tab instead of CSI 27;3;9~. When modifyOtherKeys=2 is enabled (CSI >4;2m), alt-tab emits the “old” CSI 27 escape. This better matches XTerm’s behavior. Note that other alt-tab combos are ambiguous in XTerm, and thus they are left unchanged here (i.e. we keep emitting CSI 27 escapes for them). Closes #900
2022-02-01 18:37:50 +01:00
* `alt+tab` now emits `ESC \t` instead of `CSI 27;3;9~`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#900](https://codeberg.org/dnkl/foot/issues/900)).
selection: don’t quote file URIs on the alt screen Closes #379
2022-02-02 21:17:01 +01:00
* File pasted, or dropped, on the alt screen is no longer quoted
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#379](https://codeberg.org/dnkl/foot/issues/379)).
extract: ensure line-based selections are terminated with a newline Closes #869
2022-02-02 22:02:56 +01:00
* Line-based selections now include a trailing newline when copied
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#869](https://codeberg.org/dnkl/foot/issues/869)).
main: reset signal mask and signal handlers at startup This ensures processes spawned by us (e.g. the shell, new terminal instances etc) don’t inherit a flawed signal mask, or having signals unknowingly ignored. Closes #854
2022-02-02 21:35:39 +01:00
* Foot now clears the signal mask and resets all signal handlers to
their default handlers at startup
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#854](https://codeberg.org/dnkl/foot/issues/854)).
changelog: XF86Copy+XF86Paste are now recognized by default
2022-02-05 16:42:38 +01:00
* `Copy` and `Paste` keycodes are supported by default for the
clipboard. These are useful for keyboards with custom firmware like
QMK to enable global copy/paste shortcuts that work inside and
outside the terminal (https://codeberg.org/dnkl/foot/pulls/894).
themes: consistently use snake-case in theme names
2021-12-18 14:24:30 +01:00
Merge branch 'releases/1.10'
2021-12-08 18:14:44 +01:00
### Removed
wayland: remove workaround for sway-1.5 bug - slow resizing of hidden windows In Sway-1.5, sway waits for configure ACKs from hidden windows when views are being resized. I.e. if you have e.g. a stacked view, with one or more windows currently not visible, and you resize the stack, then sway will emit configure events to all windows, and then wait for ACKs before rendering the resized view. The problem with this is that sway also does **not** call frame callbacks on hidden windows. So if we have rendered one frame, and thus registered a frame callback, we’ll never render any more frames until the window becomes visible again. Ergo, if you resize the view interactively, only the first resize actually happens. After that, all hidden views are “stuck”, causing ACK timeouts. We worked around this in foot by preempting the frame callback. I.e. destroying it, and rendering the frame anyway. This has fixed in sway-1.6, and thus we can remove the workaround.
2021-05-11 22:09:17 +02:00
* Workaround for slow resize in Sway <= 1.5, when a foot window was
hidden, for example, in a tabbed view
(https://codeberg.org/dnkl/foot/pulls/507).
Merge branch 'releases/1.10'
2021-12-08 18:14:44 +01:00
### Fixed
term: font_size_adjust: use DPI=96 when font is *not* scaled by DPI Closes #842
2021-12-14 17:45:12 +01:00
* Font size adjustment (“zooming”) when font is configured with a
**pixelsize**, and `dpi-aware=no`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#842](https://codeberg.org/dnkl/foot/issues/842)).
changelog: grammar
2021-12-23 14:09:48 +01:00
* Key presses triggering keyboard layout switches also emitting CSI
codes in the Kitty keyboard protocol.
shm: get_buffer(): make sure buffer->busy is set When going through the cached buffers, we only set buffer->busy on the *first* re-usable buffer we found. In some cases, we will find more than one re-usable buffer. In this case, we select the “youngest” one (i.e the one most recently used, in the hopes that we can use damage tracking instead of re-rendering the entire buffer). If the “current” buffer is younger than the previously detected, re-usable, buffer, then we unref:ed the previously selected buffer, and replaced it with the current one. But, we did not sanitize it. That is, we did not: * set buffer->busy * clear its dirty region * clear its scroll damage That buffer would eventually get rendered to, and committed to the compositor. Later, the compositor would free it. And there, in our buffer_release() callback, we’d assert that buffer->busy was set. And fail. Closes #844
2021-12-15 12:37:21 +01:00
* Assertion in `shm.c:buffer_release()`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#844](https://codeberg.org/dnkl/foot/issues/844)).
config: error out on empty key- or mouse binding Closes #851
2021-12-18 20:39:08 +01:00
* Crash when setting a key- or mouse binding to the empty string
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#851](https://codeberg.org/dnkl/foot/issues/851)).
render: make sure ‘maximized’ button doesn’t use negative coordinates
2021-12-22 20:31:38 +01:00
* Crash when maximizing the window and `[csd].size=1`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#857](https://codeberg.org/dnkl/foot/issues/857)).
term: print: erase existing OSC-8 URI If we have an “active” OSC-8 URI, term_print() would correctly replace an existing URI with the new one. But, if we don’t have an active URI, an existing URI was not erased. This can be reproduced with e.g echo -e '\e]8;;http://foo.bar\e\\foobar\e]8;;\e\\\b\b\b\b\b😀\n'
2021-12-26 14:51:26 +01:00
* OSC-8 URIs not getting overwritten (erased) by double-width
characters (e.g. emojis).
render: csd: scale border width when rendering the CSD border’s visible part
2021-12-29 18:11:51 +01:00
* Rendering of CSD borders when `csd.border-width > 0` and desktop
scaling has been enabled.
sixel: DECGRI (repeat) with a count of 0 should emit a single sixel
2022-02-03 19:23:43 +01:00
* Failure to launch when `exec(3)`:ed with an empty argv.
input: reset view when pasting from primary We’re already doing this for keyboard input, and regular clipboard pastes.
2022-01-11 20:26:49 +01:00
* Pasting from the primary clipboard (mouse middle clicking) did not
reset the scrollback view to the bottom.
input: reset mouse button click counter when mouse moves As described in #883, creating a block selection (with ctrl+BTN_LEFT), then *quickly* (within 300ms from) creating a new one, will, in fact, _not_ create a new block selection, but a ‘select-word-whitespace’ selection (ctrl+BTN_LEFT-2). A similar effect can be seen with plain selections (BTN_LEFT). Click and drag to make a selection, but *release*, and make a new selection within 300ms from the initial button press, and the new selection is suddenly a word-based selection. This happens because triggering a binding does *not* reset the button click counter. So, shouldn’t we just do that? No, because we rely on this behavior to handle single-, double- and triple-click actions. If we were to reset the button click handler, then we’d have to instead delay triggering the first action with 300ms, which would make things appear laggy. If we don’t do this, it would be impossible to double- and triple-click, since the single-click action would keep resetting the click counter. This patch takes a slightly different approach; we reset the click counter when the mouse has moved “too much”. For now, “too much” is when the cursor has moved to a different cell. This way, single-, double- and triple-clicks continue to work as before. But, creating actual selections, and then quickly releasing and starting a new selection produces the expected results. Closes #883
2022-01-12 15:38:32 +01:00
* Wrong mouse binding triggered when doing two mouse selections in
very quick (< 300ms) succession
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#883](https://codeberg.org/dnkl/foot/issues/883)).
Fix bash completion for lists of short options
2022-02-03 17:31:57 +01:00
* Bash completion giving an error when completing a list of short
options
sixel: resize: truncate instead of failing, when new size exceeds max size If the size we’re trying to set exceeds the configured max size, truncate instead of failing.
2022-02-03 19:20:41 +01:00
* Sixel: large image resizes (triggered by e.g. large repeat counts in
`DECGRI`) are now truncated instead of ignored.
sixel: DECGRI (repeat) with a count of 0 should emit a single sixel
2022-02-03 19:23:43 +01:00
* Sixel: a repeat count of 0 in `DECGRI` now emits a single sixel.
box-drawing: LIGHT ARC: check for sqrt() failures Closes #914
2022-02-03 22:17:10 +01:00
* LIGHT ARC box drawing characters incorrectly rendered
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
platforms ([#914](https://codeberg.org/dnkl/foot/issues/914)).
term: font_size_adjust: use DPI=96 when font is *not* scaled by DPI Closes #842
2021-12-14 17:45:12 +01:00
Merge branch 'releases/1.10'
2021-12-08 18:14:44 +01:00
### Contributors
SGR-Pixels mouse mode, closes #762
2021-12-30 05:13:45 -06:00
* [lamonte](https://codeberg.org/lamonte)
changelog: prepare for 1.11.0
2022-02-05 17:19:43 +01:00
* Érico Nogueira
* feeptr
* Felix Lechner
* grtcdr
* Mark Stosberg
* Nicolai Dagestad
* Oğuz Ersen
* Pranjal Kole
* Simon Ser
Merge branch 'releases/1.10'
2021-12-08 18:14:44 +01:00
changelog: prepare for 1.10.3
2021-12-08 18:08:45 +01:00
## 1.10.3
changelog: add new ‘unreleased’ section
2021-12-02 20:36:09 +01:00
### Added
changelog: move entry to ‘unreleased’
2021-12-02 20:41:45 +01:00
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
* Kitty keyboard protocol ([#319](https://codeberg.org/dnkl/foot/issues/319)):
changelog: move entry to ‘unreleased’
2021-12-02 20:41:45 +01:00
- [Report event types](https://sw.kovidgoyal.net/kitty/keyboard-protocol/#report-events)
(mode `0b10`)
kitty: initial support for “report alternate key” In this mode, the “shifted” and “base layout” keys are added to the CSIs, as sub-parameters to the “key” parameter. Note that this PR only implements the “shifted” key, not the “base layout key”. This is done by converting the original XKB symbol to it’s corresponding UTF-32 codepoint. If this codepoint is different from the one we use as “key” in the CSI, we add it as a sub-parameter. Related to #319
2021-12-07 19:55:52 +01:00
- [Report alternate keys](https://sw.kovidgoyal.net/kitty/keyboard-protocol/#report-alternates)
changelog: kitty: alternate keys: base layout key is implemented
2021-12-08 18:20:26 +01:00
(mode `0b100`)
input: kitty: add support for “report all keys as escape codes”
2021-11-29 21:03:33 +01:00
- [Report all keys as escape codes](https://sw.kovidgoyal.net/kitty/keyboard-protocol/#report-all-keys)
(mode `0b1000`)
kitty: implement “report associated text” In this mode, key events that generate text now add a third CSI parameter, indicating the actual codepoint. Remember that we always use the *unshifted* key in the CSI escapes. With this mode, those CSI escapes now also included the text codepoint. I.e. what would have been emitted, had we not generated a CSI escape. As far as I can tell, this mode has no effect unless “report all keys as escape sequences” is enabled (reason being, without that, there aren’t any text events that generate CSIs - they’re always emitted as-is). Note that Kitty itself seems to be somewhat buggy in this mode. At least on Wayland, with my Swedish layout. For example ‘a’ and ‘A’ does generate the expected CSIs, but ‘å’ and ‘Å’ appears to be treated as non-text input. Furthermore, Kitty optimizes away the modifier parameter, if no modifiers are pressed (e.g. CSI 97;;97u), while we always emit the modifier (CSI 97;1;97u). Related to #319
2021-12-06 23:01:41 +01:00
- [Report associated text](https://sw.kovidgoyal.net/kitty/keyboard-protocol/#report-text)
(mode `0b10000`)
changelog: list new mouse.selection-override-modifiers option
2021-10-09 21:40:11 +00:00
changelog: add new ‘unreleased’ section
2021-12-02 20:36:09 +01:00
### Fixed
term: ensure cell dimensions are non-zero Closes #830
2021-12-04 18:41:36 +01:00
* Crash when bitmap fonts are scaled down to very small font sizes
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#830](https://codeberg.org/dnkl/foot/issues/830)).
grid: reload pointers into the uri range vector after inserting Inserting elements into the URI range vector typically triggers a vector resize. This is done using realloc(). Sometimes this causes the vector to move, thus invalidating all existing pointers into the vector.
2021-12-08 17:41:29 +01:00
* Crash when overwriting/erasing an OSC-8 URL.
term: ensure cell dimensions are non-zero Closes #830
2021-12-04 18:41:36 +01:00
changelog: prepare for 1.10.2
2021-12-02 20:26:42 +01:00
## 1.10.2
config: add tweak.grapheme-width-method=max ‘max’ is a new value for ‘tweak.grapheme-width-method’. When enabled, the width of a grapheme cluster is that of the cluster’s widest codepoint.
2021-11-22 23:02:25 +01:00
changelog: add new ‘unreleased’ section
2021-11-22 22:24:13 +01:00
### Added
config: add tweak.grapheme-width-method=max ‘max’ is a new value for ‘tweak.grapheme-width-method’. When enabled, the width of a grapheme cluster is that of the cluster’s widest codepoint.
2021-11-22 23:02:25 +01:00
* New value, `max`, for `[tweak].grapheme-width-method`.
changelog: kitty keyboard protocol - disambiguate escape codes
2021-11-27 18:47:20 +01:00
* Initial support for the [Kitty keyboard protocol](https://sw.kovidgoyal.net/kitty/keyboard-protocol/).
Modes supported:
changelog: kitty: report events
2021-11-28 19:03:49 +01:00
- [Disambiguate escape codes](https://sw.kovidgoyal.net/kitty/keyboard-protocol/#disambiguate) (mode `0b1`)
changelog: window-menu
2021-11-30 22:12:17 +01:00
* “Window menu” (compositor provided) on right clicks on the CSD title
bar.
config: add tweak.grapheme-width-method=max ‘max’ is a new value for ‘tweak.grapheme-width-method’. When enabled, the width of a grapheme cluster is that of the cluster’s widest codepoint.
2021-11-22 23:02:25 +01:00
changelog: add new ‘unreleased’ section
2021-11-22 22:24:13 +01:00
### Fixed
input: finalize mouse selection on a pointer-leave event on the GRID surface If a mouse selection was ongoing, and the user switched workspace (probably using the keyboard...), and then back, the selection was still treated as ongoing, while all other mouse state has been reset. This meant the user had to tap at least once to stop the selection.
2021-11-25 15:21:53 +01:00
* An ongoing mouse selection is now finalized on a pointer leave event
(for example by switching workspace while doing a mouse selection).
osc8: update URI ranges as we print data, *not* when the URI is closed At first, an OSC-8 URI range was added when we received the closing OSC-8 escape (i.e. with an empty URI). But, this meant that cursor movements while the OSC-8 escape was in effect wasn’t handled correctly, since we’d add a range that spanned the cursor movements. Attempts were made to handle this in the cursor movement functions, by closing and re-opening the URI. However, there are too many corner cases to make this a viable approach. Scrolling is one such example, line-wrapping another. This patch takes a different approach; emit, or update the URI range when we print to the grid. This models the intended behavior much more closely, where an active OSC-8 URI act like any other SGR attribute - it is applied to all cells printed to, but otherwise have no effect. To avoid killing performance, this is only done in the “generic” printer. This means OSC-8 open/close calls must now “switch” the ASCII printer. Note that the “fast” printer still needs to *erase* pre-existing OSC-8 URIs. Closes #816
2021-11-25 19:22:52 +01:00
* OSC-8 URIs in the last column
* OSC-8 URIs sometimes being applied to too many, and seemingly
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
unrelated cells ([#816](https://codeberg.org/dnkl/foot/issues/816)).
grid: bug: OSC-8 URIs were incorrectly skipped while resizing the alt screen
2021-11-26 20:27:55 +01:00
* OSC-8 URIs incorrectly being dropped when resizing the terminal
window with the alternate screen active.
render: fix csd border rendering glitch when width > 5px CSD borders are always *at least* 5px. If url.border-width=0, those 5px are all fully transparent (and act as interactive resize handles). As csd.border-width increases, the number of transparent pixels decrease. Once csd.border-width >= 5, the border is fully opaque. When csd.border-width > 5, then width of the border is (obviously) more than 5px. But, when rendering the opaque part of the border, we still used 5px for the invisible part, which caused some pixman rectangles to have negative x/y coordinates. This resulted in rendering glitches due to overflows in pixman when rendering the borders. The fix is to ensure the total border size is always at least, but not *always* 5px. That is, set it to max(5, csd.border-width). This patch also fixes an issue where the CSD borders were not dimmed (like the titlebar) when the window looses input focus. Closes #823
2021-11-29 19:23:58 +01:00
* CSD border not being dimmed when window is not focused.
* Visual corruption with large CSD borders
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#823](https://codeberg.org/dnkl/foot/issues/823)).
input: always update the xcursor shape in pointer enter/motion events Now that term_xcursor_update_for_seat() takes the current surface into account (i.e. doesn’t assume the cursor is over the main grid), there’s no longer any need to call render_xcursor_set() directly. Thus, we can simply call term_xcursor_update_for_seat() on **all** pointer enter and motion events. As long as we take care to update the internal state to reflect the, possibly new, current surface before doing so. Also make sure to **always** reset the seat’s “current” xcursor pointer on pointer leave events. This is done without actually sending anything to the compositor, but is necessary to ensure that we *do* send a request to update the xcursor on the next pointer enter event.
2021-12-01 20:04:01 +01:00
* Mouse cursor shape sometimes not being updated correctly.
osc-4: don’t update the color of cells with RGB fg/bg colors OSC 4/104 changes the 256-color palette. We also run a pass over the visible cells, and update their colors. This was previously done by comparing the actual color of the cell, with the “old” color in the palette. If they matched, the cell was updated. This meant that cells with an RGB color (i.e. not a palette based color) was also updated, _if_ its color matched the palette color. Now that each cell tracks its color *source*, we can ignore all non-palette based cells. Note that this still isn’t perfect: if the palette contains multiple entries with the same color, we’ll end up updating the “wrong” cells. Closes #678
2021-11-30 19:36:28 +01:00
* Color palette changes (via OSC 4/104) no longer affect RGB colors
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#678](https://codeberg.org/dnkl/foot/issues/678)).
input: finalize mouse selection on a pointer-leave event on the GRID surface If a mouse selection was ongoing, and the user switched workspace (probably using the keyboard...), and then back, the selection was still treated as ongoing, while all other mouse state has been reset. This meant the user had to tap at least once to stop the selection.
2021-11-25 15:21:53 +01:00
changelog: add new ‘unreleased’ section
2021-11-22 22:24:13 +01:00
### Contributors
changelog: prepare for 1.10.2
2021-12-02 20:26:42 +01:00
* Jonas Ådahl
changelog: add new ‘unreleased’ section
2021-11-22 22:24:13 +01:00
changelog: prepare for 1.10.1
2021-11-22 21:56:38 +01:00
## 1.10.1
meson: add -Dthemes=false|true This adds a new meson option that controls whether the example theme files should be installed or not. The default is true. Previously, themes were gated by the -Ddocs option.
2021-11-14 23:12:18 +01:00
changelog: add new ‘unreleased’ section
2021-11-14 18:26:24 +01:00
### Added
meson: add -Dthemes=false|true This adds a new meson option that controls whether the example theme files should be installed or not. The default is true. Previously, themes were gated by the -Ddocs option.
2021-11-14 23:12:18 +01:00
* `-Dthemes=false|true` meson command line option. When disabled,
example theme files are **not** installed.
footclient.desktop: new XDG desktop file, for footclient
2021-11-15 12:13:39 +01:00
* XDG desktop file for footclient.
meson: add -Dthemes=false|true This adds a new meson option that controls whether the example theme files should be installed or not. The default is true. Previously, themes were gated by the -Ddocs option.
2021-11-14 23:12:18 +01:00
changelog: add new ‘unreleased’ section
2021-11-14 18:26:24 +01:00
### Fixed
config: letter-spacing: add missing ‘return’ The missing return caused us to fall through to the bottom of the function, where we ended with an error message: [main].letter-spacing: 0: not a valid option: letter-spacing Closes #795
2021-11-15 19:22:06 +01:00
* Regression: `letter-spacing` resulting in a “not a valid option”
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
error ([#795](https://codeberg.org/dnkl/foot/issues/795)).
config: create a copy of the section name The parsing context keeps a pointer to the current section name. This is used when logging errors. However, the pointer was into a buffer allocated by getline(). This buffer are often re-used in the next call to getline(), or free:d. Regardless, the section name pointer is invalid after the next call to getline(), which meant all error messages were logging a correct section name.
2021-11-21 10:55:57 +01:00
* Regression: bad section name in configuration error messages.
changelog: pipe-* key bindings not being parsed correctly
2021-11-21 18:09:10 +01:00
* Regression: `pipe-*` key bindings not being parsed correctly,
resulting in invalid error messages
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#809](https://codeberg.org/dnkl/foot/issues/809)).
changelog: osc-8 data not being cleared when cell is overwritten
2021-11-20 18:10:45 +01:00
* OSC-8 data not being cleared when cell is overwritten
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#804](https://codeberg.org/dnkl/foot/issues/804),
[#801](https://codeberg.org/dnkl/foot/issues/801)).
config: letter-spacing: add missing ‘return’ The missing return caused us to fall through to the bottom of the function, where we ended with an error message: [main].letter-spacing: 0: not a valid option: letter-spacing Closes #795
2021-11-15 19:22:06 +01:00
changelog: add new ‘unreleased’ section
2021-11-14 18:26:24 +01:00
### Contributors
changelog: prepare for 1.10.1
2021-11-22 21:56:38 +01:00
* Arnavion
* Craig Barnes
* Soc Virnyl Silab Estela
* Xiretza
changelog: add new ‘unreleased’ section
2021-11-14 18:26:24 +01:00
changelog: prepare for 1.10.0
2021-11-14 18:10:43 +01:00
## 1.10.0
changelog: add a new ‘unreleased’ section
2021-10-02 14:48:13 +02:00
### Added
notify: add the notify-focus-inhibit config option foot doesn't show desktop notifications (via OSC777) if the current terminal has keyboard focus. This is probably a sane default, but there are use cases where showing a notification regardless of the focus status may be desired. For example, a completion notification of a long running task inside a non-focused tmux window. This PR adds the notify-focus-inhibit option which can be used to disable inhibition of notifications when the window has focus. The default value is `yes`, which retains the old behavior.
2021-10-05 23:07:01 +02:00
changeloge: style fixes
2021-10-22 19:57:11 +02:00
* `notify-focus-inhibit` boolean option, which can be used to control
whether desktop notifications should be inhibited when the terminal
has keyboard focus
config: add [key-bindings].noop action Key combinations assigned to this action will not be sent to the application. Closes #765
2021-10-24 11:49:37 +02:00
* `[colors].scrollback-indicator` color-pair option, which specifies
changeloge: style fixes
2021-10-22 19:57:11 +02:00
foreground and background colors for the scrollback indicator.
config: add [key-bindings].noop action Key combinations assigned to this action will not be sent to the application. Closes #765
2021-10-24 11:49:37 +02:00
* `[key-bindings].noop` action. Key combinations assigned to this
action will not be sent to the application
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#765](https://codeberg.org/dnkl/foot/issues/765)).
meson: install themes to $datadir/foot/themes
2021-10-27 17:31:02 +02:00
* Color schemes are now installed to `${datadir}/foot/themes`.
csd: add support for a visible border When we’re using CSDs, we’ve up until now rendered a 5px invisible border. This border handles interactive resizing. I.e. hovering it changes the mouse cursor, and mouse button events are used to start an interactive resize. This patch makes it possible to color part of (or the entire) border, with a configurable color. To facilitate this, two new options have been added: * csd.border-width * csd.border-color border-width defaults to 0, resulting in the look we’re used to. border-color defaults to the title bar color. If the title bar color hasn’t been set, it defaults to the default foreground color (just like the title bar color does). This means that, setting border-width but not border-color, results in a border that blends with the title bar.
2021-10-27 18:27:08 +02:00
* `[csd].border-width` and `[csd].border-color`, allowing you to
configure the width and color of the CSD border.
input: add support for modifyOtherKeys=2 Similar to modifyOtherKeys=1 (foot’s default, and only, mode), except that: * All modifiers (and not just Ctrl) generate \E[27;m;n~ escapes * Regular keys (with modifiers) also generate \E[27;m;n~ escapes (for example, C-h no longer generates ^H, but \E[27;5;104~) For our keymap based lookups, this is handled by adding MOD_MODIFY_OTHER_KEYS_STATE<N> variants. For “generic” keys, we simply adjust the conditions for when to emit a \E[27;m;n~ escape - the only requirement is that at least one modifier is active.
2021-11-11 17:43:39 +01:00
* Support for `XTMODKEYS` with `Pp=4` and `Pv=2` (_modifyOtherKeys=2_).
config: add [colors].dim0-7 This allows you to configure custom colors to be used when colors are being dimmed (`\E[2m`). It is implemented by color matching (just like bold-text-in-bright=palette-based); the color-to-be-dimmed is matched against the current color palette. If it matches one of the regular colors (colors 0-7), the corresponding “dim” color will be used. If it matches one of the bright colors (colors 8-15), the corresponding “regular” color will be used (but *only* if the “dim” color has been set). Otherwise, the color is dimmed by reducing its luminance. The default behavior, i.e. when dim0-7 hasn’t been configured, is to dim by reducing luminance for *all* colors. I.e. we don’t do any color matching at all. In particular, this means that dimming a bright color will *not* result in the corresponding “regular” color. Closes #776
2021-11-03 14:25:38 +01:00
* `[colors].dim0-7` options, allowing you to configure custom “dim”
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
colors ([#776](https://codeberg.org/dnkl/foot/issues/776)).
changeloge: style fixes
2021-10-22 19:57:11 +02:00
notify: add the notify-focus-inhibit config option foot doesn't show desktop notifications (via OSC777) if the current terminal has keyboard focus. This is probably a sane default, but there are use cases where showing a notification regardless of the focus status may be desired. For example, a completion notification of a long running task inside a non-focused tmux window. This PR adds the notify-focus-inhibit option which can be used to disable inhibition of notifications when the window has focus. The default value is `yes`, which retains the old behavior.
2021-10-05 23:07:01 +02:00
changelog: add a new ‘unreleased’ section
2021-10-02 14:48:13 +02:00
### Changed
config: enable grapheme shaping by default This changes the default value of tweak.grapheme-shaping to “yes”, thus enabling grapheme shaping by default. It also changes the default value of tweak.grapheme-width-method to “wcswidth”, for maximum compatibility with terminal applications.
2021-10-13 17:42:40 +02:00
* `[tweak].grapheme-shaping` is now enabled by default when both foot
itself, and fcft has been compiled with support for it.
* Default value of `[tweak].grapheme-width-method` changed from
`double-width` to `wcswidth`.
pgo: full-inner: add --override tweak.grapheme-shaping=no Grapheme shaping is now enabled by default in foot. However, when generating the profiling data in PGO builds, this results in skewed optimizations. The end result is worse benchmark results regardless of whether grapheme-shaping is enabled or not (when running the benchmarks).
2021-10-16 16:58:59 +02:00
* INSTALL.md: `--override tweak.grapheme-shaping=no` added to PGO
command line.
wayland: error out if there aren’t any seats available If there aren’t any seats available, input is not possible (neither keyboard nor mouse input). Note that this is not the same thing as e.g. no keyboard being plugged in. In this case, there will be a seat, but without the keybaord capability. Input may not be possible _right now_, but may be later, if the user plugs in a keyboard. Closes #779
2021-11-07 11:29:25 +01:00
* Foot now terminates if there are no available seats - for example,
due to the compositor not implementing a recent enough version of
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
the `wl_seat` interface ([#779](https://codeberg.org/dnkl/foot/issues/779)).
changelog: boolean options
2021-11-07 11:35:39 +01:00
* Boolean options in `foot.ini` are now limited to
“yes|true|on|1|no|false|off|0”, Previously, anything that did not
match “yes|true|on”, or a number greater than 0, was treated as
“false”.
input: don’t apply [scrollback].multiplier when alt screen is in use Closes #787
2021-11-08 18:41:42 +01:00
* `[scrollback].multiplier` is no longer applied when the alternate
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
screen is in use ([#787](https://codeberg.org/dnkl/foot/issues/787)).
config: enable grapheme shaping by default This changes the default value of tweak.grapheme-shaping to “yes”, thus enabling grapheme shaping by default. It also changes the default value of tweak.grapheme-width-method to “wcswidth”, for maximum compatibility with terminal applications.
2021-10-13 17:42:40 +02:00
changelog: add a new ‘unreleased’ section
2021-10-02 14:48:13 +02:00
### Removed
PKGBUILD: drop The bundled PKGBUILD has been pretty much identical to the one in the AUR package “foot-git” for a long time now.
2021-11-07 15:58:42 +01:00
* The bundled PKGBUILD.
config: remove options that were deprecated in 1.8.x * [main].bell * [main].jump-label-letters * [main].url-launch * [main].osc8-underline
2021-11-14 14:17:08 +01:00
* Deprecated `bell` option (replaced with `[bell]` section in 1.8.0).
* Deprecated `url-launch`, `jump-label-letters` and `osc8-underline`
options (moved to a dedicated `[url]` section in 1.8.0)
PKGBUILD: drop The bundled PKGBUILD has been pretty much identical to the one in the AUR package “foot-git” for a long time now.
2021-11-07 15:58:42 +01:00
changelog: add a new ‘unreleased’ section
2021-10-02 14:48:13 +02:00
### Fixed
input: check for ‘effective’ modifiers, not ‘depressed’ When reading XKB modifier state, use XKB_STATE_MODS_EFFECTIVE, not XKB_STATE_MODS_DEPRESSED. This fixes handling of ‘sticky’ modifier keys.
2021-10-02 17:33:01 +02:00
* ‘Sticky’ modifiers in input handling; when determining modifier
state, foot was looking at **depressed** modifiers, not
**effective** modifiers, like it should.
changelog: mention csd.size=0 fix
2021-10-08 02:28:01 +00:00
* Fix crashes after enabling CSD at runtime when `csd.size` is 0.
selection: convert \r -> \n when reading clipboard data This fixes an issue where pasting (using e.g. OSC-52) in client applications that doesn’t do this conversion themselves, like tmux, doesn’t work. Closes #752
2021-10-19 21:34:04 +02:00
* Convert `\r` to `\n` when reading clipboard data
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#752](https://codeberg.org/dnkl/foot/issues/752)).
input: update serial on each key press/release and mouse button The serial is used when copying/pasting data from the clipboard. Up until now, we’ve used the serial from the keyboard/mouse enter events. This works in most cases, but breaks in the following example: $ wl-copy WLCOPY /* Ctrl+Shift+v works fine (pastes "WLCOPY") */ $ printf "\033]52;c;eHl6\a" /* Ctrl+Shift+v pastes "WLCOPY" instead of "xyz" */ Shifting focus away and then back to the foot window, and re-executing the printf works, suggesting the “enter” serial is no longer valid after another process(?) has copied something to the clipboard. Updating the serial on key press/release (and the corresponding mouse serial on mouse button events) seems to fix this. I’ve also tested that “normal” copy/paste operations, within the same foot instance, and between foot and other applications, are still working. In at least river (wlroots based), and GNOME/mutter. Closes #753
2021-10-20 18:47:36 +02:00
* Clipboard occasionally ceasing to work, until window has been
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
re-focused ([#753](https://codeberg.org/dnkl/foot/issues/753)).
term: ignore window title updates if title is un-changed
2021-10-22 18:01:53 +02:00
* Don’t propagate window title updates to the Wayland compositor
unless the new title is different from the old title.
input: check for ‘effective’ modifiers, not ‘depressed’ When reading XKB modifier state, use XKB_STATE_MODS_EFFECTIVE, not XKB_STATE_MODS_DEPRESSED. This fixes handling of ‘sticky’ modifier keys.
2021-10-02 17:33:01 +02:00
changelog: add a new ‘unreleased’ section
2021-10-02 14:48:13 +02:00
### Contributors
changelog: prepare for 1.10.0
2021-11-14 18:10:43 +01:00
* armin
* Craig Barnes
* Daniel Martí
* feeptr
* Mitja Horvat
* Ronan Pigott
* Stanislav Ochotnický
changelog: add a new ‘unreleased’ section
2021-10-02 14:48:13 +02:00
changelog: prepare for 1.9.2
2021-10-02 14:46:42 +02:00
## 1.9.2
changelog: add a new ‘unreleased’ section
2021-10-01 21:57:57 +02:00
### Changed
pgo: full-inner: do not set LC_CTYPE=en_US.UTF-8 That locale may not exist. Instead, require the user/build script to explicitly set an UTF-8 locale. Document this in INSTALL.md, and in the bundled PKGBUILD.
2021-10-02 14:43:02 +02:00
* PGO helper scripts no longer set `LC_CTYPE=en_US.UTF-8`. But, note
changelog: fix minor grammatical mistake
2021-11-14 11:33:11 +00:00
that “full” PGO builds still **require** a UTF-8 locale; you need
pgo: full-inner: do not set LC_CTYPE=en_US.UTF-8 That locale may not exist. Instead, require the user/build script to explicitly set an UTF-8 locale. Document this in INSTALL.md, and in the bundled PKGBUILD.
2021-10-02 14:43:02 +02:00
to set one manually in your build script
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#728](https://codeberg.org/dnkl/foot/issues/728)).
pgo: full-inner: do not set LC_CTYPE=en_US.UTF-8 That locale may not exist. Instead, require the user/build script to explicitly set an UTF-8 locale. Document this in INSTALL.md, and in the bundled PKGBUILD.
2021-10-02 14:43:02 +02:00
changelog: prepare for 1.9.1
2021-10-01 20:52:19 +02:00
## 1.9.1
changelog: add new ‘unreleased’ section
2021-08-27 13:44:18 +02:00
### Added
changelog: check if primary font is monospaced
2021-08-31 19:54:31 +02:00
* Warn when it appears the primary font is not monospaced. Can be
disabled by setting `[tweak].font-monospace-warn=no`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#704](https://codeberg.org/dnkl/foot/issues/704)).
changelog: pgo build scripts
2021-09-12 16:59:23 +02:00
* PGO build scripts, in the `pgo` directory. See INSTALL.md -
_Performance optimized, PGO_, for details
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#701](https://codeberg.org/dnkl/foot/issues/701)).
box-drawing: add braille characters Render braille ourselves, instead of using font glyphs. Decoding a braille character is easy enough; there are 256 codepoints, represented by an 8-bit integer (i.e. subtract the Unicode codepoint offset, 0x2800, and you’re left with an integer in the range 0-255). Each bit corresponds to a dot. The first 6 bits represent the upper 6 dots, while the two last bits represent the fourth (and last) row of dots. The hard part is sizing the dots and the spacing between them. The aim is to have the spacing between the dots be the same size as the dots themselves, and to have the margins on each side be half the size of the dots. In a perfectly sized cell, this means two braille characters next to each other will be evenly spaced. This is however almost never the case. The layout logic currently: * Set dot size to either the width / 4, or height / 8, depending on which one is smallest. * Horizontal spacing is initialized to the width / 4 * Vertical spacing is initialized to the height / 8 * Horizontal margins are initialized to the horizontal spacing / 2 * Vertical margins are initialized to the vertical spacing / 2. Next, we calculate the number of “remaining” pixels. That is, if we add the left margin, two dots and the spacing between, how many pixels are left on the horizontal axis? These pixels are distributed in the following order (we “stop” as soon as we run out of pixels): * If the dot size is 0 (happens for very small font sizes), increase it to 1. * If the margins are 0, increase them to 1. * If we have enough pixels (need at 2 horizontal and 4 vertical), increase the dot size. * Increase spacing. * Increase margins. Closes #702
2021-09-02 14:55:26 +02:00
* Braille characters (U+2800 - U+28FF) are now rendered by foot
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
itself ([#702](https://codeberg.org/dnkl/foot/issues/702)).
main/client: add no-op "-e" command-line option
2021-09-18 23:40:40 +01:00
* `-e` command-line option. This option is simply ignored, to appease
program launchers that blindly pass `-e` to any terminal emulator
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#184](https://codeberg.org/dnkl/foot/issues/184)).
changelog: check if primary font is monospaced
2021-08-31 19:54:31 +02:00
changelog: add new ‘unreleased’ section
2021-08-27 13:44:18 +02:00
### Changed
changelog: terminfo changes
2021-08-30 20:31:28 +02:00
* `-Ddefault-terminfo` is now also applied to the generated terminfo
definitions when `-Dterminfo=enabled`.
* `-Dcustom-terminfo-install-location` no longer accepts `no` as a
special value, to disable exporting `TERMINFO`. To achieve the same
result, simply don’t set it at all. If it _is_ set, `TERMINFO` is
still exported, like before.
* The default install location for the terminfo definitions have been
changed back to `${datadir}/terminfo`.
term: only scale using DPI if *all* monitors have a scaling factor or one With dpi-aware=auto (the default), scale fonts using DPI *only* if *all* available monitors have a scaling factor of one. The idea is this: if a user, with multiple monitors, have enabled scaling on *at least* one monitor, he/she has most likely done so to match the size of his/hers other monitors. For example, if the user has one monitor with a scaling factor of one, and another one with a scaling factor of two, he/she expects things to be twice as large on the second monitor. If we (foot) scale using DPI on the first monitor, and using the scaling factor on the second monitor, foot will *not* look twice as big on the second monitor (this was the old behavior of dpi-aware=auto). Part of #714
2021-09-19 11:58:34 +02:00
* `dpi-aware=auto`: fonts are now scaled using the monitor’s DPI only
when **all** monitors have a scaling factor of one
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#714](https://codeberg.org/dnkl/foot/issues/714)).
fcft: adapt to API changes in fcft-3.x Fcft no longer uses wchar_t, but plain uint32_t to represent codepoints. Since we do a fair amount of string operations in foot, it still makes sense to use something that actually _is_ a string (or character), rather than an array of uint32_t. For this reason, we switch out all wchar_t usage in foot to char32_t. We also verify, at compile-time, that char32_t used UTF-32 (which is what fcft expects). Unfortunately, there are no string functions for char32_t. To avoid having to re-implement all wcs*() functions, we add a small wrapper layer of c32*() functions. These wrapper functions take char32_t arguments, but then simply call the corresponding wcs*() function. For this to work, wcs*() must _also_ be UTF-32 compatible. We can check for the presence of the __STDC_ISO_10646__ macro. If set, wchar_t is at least 4 bytes and its internal representation is UTF-32. FreeBSD does *not* define this macro, because its internal wchar_t representation depends on the current locale. It _does_ use UTF-32 _if_ the current locale is UTF-8. Since foot enforces UTF-8, we simply need to check if __FreeBSD__ is defined. Other fcft API changes: * fcft_glyph_rasterize() -> fcft_codepoint_rasterize() * font.space_advance has been removed * ‘tags’ have been removed from fcft_grapheme_rasterize() * ‘fcft_log_init()’ removed * ‘fcft_init()’ and ‘fcft_fini()’ must be explicitly called
2021-08-21 14:50:42 +02:00
* fcft >= 3.0.0 in now required.
changelog: terminfo changes
2021-08-30 20:31:28 +02:00
changelog: add new ‘unreleased’ section
2021-08-27 13:44:18 +02:00
### Fixed
input: workaround GNOME issue with pointer button events Under certain circumstances, GNOME will send multiple pointer button press events, without any release or leave events in between. This trips up our button tracking. Workaround, by replacing the existing state for the pressed button with the new state. Previously, debug builds would assert (and thus crash), while release builds would have multiple states for the same button, causing (probably) issues like the title bar not being usable (as in, cannot be dragged, buttons not working etc). Hopefully closes #709
2021-09-06 18:12:45 +02:00
* Added workaround for GNOME bug where multiple button press events
(for the same button) is sent to the CSDs without any release or
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
leave events in between ([#709](https://codeberg.org/dnkl/foot/issues/709)).
selection: line-wise selection now handles soft line-wrapping Previously, soft-wrapped lines were not selected correctly, as the selection logic was hardcoded to simply select everything between the first and last column on the current terminal row. Now, we scan backward and forward, looking for hard-wrapped lines. This is similar to how word-based selection works. Closes #726
2021-09-30 13:39:23 +02:00
* Line-wise selection not taking soft line-wrapping into account
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#726](https://codeberg.org/dnkl/foot/issues/726)).
input: workaround GNOME issue with pointer button events Under certain circumstances, GNOME will send multiple pointer button press events, without any release or leave events in between. This trips up our button tracking. Workaround, by replacing the existing state for the pressed button with the new state. Previously, debug builds would assert (and thus crash), while release builds would have multiple states for the same button, causing (probably) issues like the title bar not being usable (as in, cannot be dragged, buttons not working etc). Hopefully closes #709
2021-09-06 18:12:45 +02:00
changelog: add new ‘unreleased’ section
2021-08-27 13:44:18 +02:00
### Contributors
main/client: add no-op "-e" command-line option
2021-09-18 23:40:40 +01:00
* [craigbarnes](https://codeberg.org/craigbarnes)
changelog: prepare for 1.9.1
2021-10-01 20:52:19 +02:00
* Arnavion
main/client: add no-op "-e" command-line option
2021-09-18 23:40:40 +01:00
changelog: add new ‘unreleased’ section
2021-08-27 13:44:18 +02:00
changelog: prepare for 1.9.0
2021-08-27 12:45:22 +02:00
## 1.9.0
changelog: add new ‘unreleased’ section
2021-07-18 18:07:26 +02:00
### Added
changelog: window title in CSDs
2021-07-22 21:39:35 +02:00
* Window title in the CSDs
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#638](https://codeberg.org/dnkl/foot/issues/638)).
meson: add -Ddocs=disabled|enabled|auto command line option When enabled (the default, if scdoc is found), we build and install the man pages, example foot.ini, readme, changelog and license files.
2021-07-24 13:09:25 +02:00
* `-Ddocs=disabled|enabled|auto` meson command line option.
config: include: add support for ~-expansion Closes #659
2021-07-30 14:44:16 +02:00
* Support for `~`-expansion in the `include` directive
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#659](https://codeberg.org/dnkl/foot/issues/659)).
box-drawing: add U+1FB3C-U+1FB6F, U+1FB9A and U+1FB9B These are the “wedges” from the Unicode 13 “Legacy Computing” symbols. Closes #474
2021-08-03 18:10:41 +02:00
* Unicode 13 characters U+1FB3C - U+1FB6F, U+1FB9A and U+1FB9B to list
of box drawing characters rendered by foot itself (rather than using
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
font glyphs) ([#474](https://codeberg.org/dnkl/foot/issues/474)).
terminfo: change kmous to \E[<, add XM+xm capabilities ncurses has had a bug where mouse support is completely disabled if the terminfo didn’t have kmous=\E[M, *or*, the terminfo *name* contained ‘xterm’. This appears to have been fixed. Thus, change kmous to \E[<, and set xm/XM accordingly. With this, ncurses application will use the SGR mouse reporting mode, instead of the legacy reporting mode.
2021-08-05 19:21:57 +02:00
* `XM`+`xm` to terminfo.
input: implement support for mouse wheel left/right We now emit button 6/7 events (when the client application grabs the mouse). This buttons map to mouse wheel horizontal scroll events. Or, left/right tilting, if you like. Wayland report these as ‘axis’ events (just like regular scroll wheel events), and thus we need to translate those scroll events to button events. libinput does not define any mouse buttons for wheel tilts, so we add our own defitions. These are added last in the BTN_* range, just before the BTN_JOYSTICK events.
2021-08-05 18:34:09 +02:00
* Mouse buttons 6/7 (mouse wheel left/right).
changelog: url.uri-characters
2021-08-09 19:58:40 +02:00
* `url.uri-characters` option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#654](https://codeberg.org/dnkl/foot/issues/654)).
changelog: window title in CSDs
2021-07-22 21:39:35 +02:00
changelog: add new ‘unreleased’ section
2021-07-18 18:07:26 +02:00
### Changed
Only brighten palette colors with bold-text-in-bright=palette-based
2021-07-22 18:22:39 +02:00
terminfo: install to $datadir/foot/terminfo by default, append to TERMINFO_DIRS As of 2021-07-31, ncurses ships its own version of foot’s terminfo. Since: * It doesn’t have the non-standard Sync,Tc,setrgbf,setrgbb capabilities. * It doesn’t set hs,fsl,dsl (statusbar). * We want to be able to update our termminfo without waiting for an ncurses release. * Foot should be installable and usable on Linux systems that doesn’t have the latest ncurses. we still want to ship our own version. We can however not install it to the default terminfo location (e.g. /usr/share/terminfo), since it will collide with the ncurses provided files. Our options are to either rename our terminfo to something else, or to keep the name, but install our terminfo files somewhere else. The first option would be the easy one. However, I think it makes sense to use the same name. For example, a user that SSH’s into a remote system that does *not* have our own version installed, but *does* have the ncurses one, will gracefully fall back to that one, which is better than manually having to set e.g. TERM=xterm-256color. Now, if we want to use the same name, we need to install it somewhere else. But where? And how do we ensure our version is preferred over the ncurses one? I opted to $datadir/foot/terminfo (e.g. /usr/share/foot/terminfo) by default. It makes it namespaced to foot (i.e. we’re not introducing a new “standard” terminfo location), thus guaranteeing it wont collide with ncurses. To enable applications to find it, we export TERMINFO_DIRS. This is a list of *additional* directories to search for terminfo files. If it’s already defined, we *append* to it. The nice thing with this is, if there’s no terminfo in that location (e.g. when you SSH into a remote), the default terminfo location is *also* searched. But only *after* having searched through TERMINFO_DIRS. In short: our version is preferred, but the ncurses one (or an older version of our terminfo package!) will be used if ours cannot be found. To enable packagers full control over the new behavior, the existing meson command line options have been modified, and a new option added: -Dterminfo=disabled|enabled|auto: *build* and *install* the terminfo files. -Dcustom-terminfo-install-location=<path>: *where* the terminfo files are expected to be found. This *needs* to be set *even* if -Dterminfo=disabled. For example, if the packaging script builds and packages the terminfo files separate from the regular foot build. The path is *relative to $prefix*, and defaults to $datadir/foot/terminfo. This is the value that will be appended to TERMINFO_DIRS. Note that you can set it to ‘no’, in which case foot will *not* set/modify TERMINFO_DIRS. Only do this if you don’t intend to package foot’s terminfo files at all (i.e. you plan on using the ncurses ones only). -Ddefault-terminfo=foot. Allows overriding the default TERM value. This should only be changed if the target platform doesn’t support terminfo files. Closes #671
2021-08-07 16:42:51 +02:00
* Terminfo files can now co-exist with the foot terminfo files from
ncurses. See `INSTALL.md` for more information
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#671](https://codeberg.org/dnkl/foot/issues/671)).
Only brighten palette colors with bold-text-in-bright=palette-based
2021-07-22 18:22:39 +02:00
* `bold-text-in-bright=palette-based` now only brightens colors from palette
changelog: asynchronous client application termination
2021-07-31 20:13:52 +02:00
* Raised grace period between closing the PTY and sending `SIGKILL` (when
terminating the client application) from 4 to 60 seconds.
* When terminating the client application, foot now sends `SIGTERM` immediately
after closing the PTY, instead of waiting 2 seconds.
term: send SIGTERM/SIGKILL to the entire process group
2021-07-31 22:50:19 +02:00
* Foot now sends `SIGTERM`/`SIGKILL` to the client application’s process group,
instead of just to the client application’s process.
terminfo: change kmous to \E[<, add XM+xm capabilities ncurses has had a bug where mouse support is completely disabled if the terminfo didn’t have kmous=\E[M, *or*, the terminfo *name* contained ‘xterm’. This appears to have been fixed. Thus, change kmous to \E[<, and set xm/XM accordingly. With this, ncurses application will use the SGR mouse reporting mode, instead of the legacy reporting mode.
2021-08-05 19:21:57 +02:00
* `kmous` terminfo capability from `\E[M` to `\E[<`.
pt-or-px: heed the dpi-aware setting Before this patch, pt-or-px values, like letter-spacing, were *always* scaled using the current DPI value. This is wrong; if the fonts are scaled using the output’s scaling factor, then so should all other point values. This also fixes an issue where e.g. letter-spacing would use one DPI value at startup, but then when increasing/decreasing or resetting the font size, would be re-calculated using a different DPI value, leading to completely different spacing. This happened when there were multiple monitors, with different DPI values, and foot guessed the initial DPI value wrong. Normally, foot would correct itself as soon as the window was mapped, and the “correct” DPI value known. But if the fonts were scaled using the scaling factor, it was possible that the font reload never happened. This patch also updates the thickness calculation (for LIGHT and HEAVY box drawing characters) to use the scaling factor when appropriate. Closes #680
2021-08-13 17:38:56 +02:00
* pt-or-px values (`letter-spacing`, etc) and the line thickness
(`tweak.box-drawing-base-thickness`) in box drawing characters are
now translated to pixel values using the monitor’s scaling factor
when `dpi-aware=no`, or `dpi-aware=auto` and the scaling factor is
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
larger than 1 ([#680](https://codeberg.org/dnkl/foot/issues/680)).
spawn: don’t error out if we fail to chdir()
2021-08-30 17:55:36 +02:00
* Spawning a new terminal with a working directory that does not exist
is no longer a fatal error.
Only brighten palette colors with bold-text-in-bright=palette-based
2021-07-22 18:22:39 +02:00
changelog: add new ‘unreleased’ section
2021-07-18 18:07:26 +02:00
### Removed
changelog: mention km/smm/rmm being removed
2021-08-14 21:08:32 +02:00
* `km`/`smm`/`rmm` from terminfo; foot prefixes Alt-key combinations
with `ESC`, and not by setting the 8:th “meta” bit, regardless of
`smm`/`rmm`. While this _can_ be disabled by, resetting private mode
1036, the terminfo should reflect the **default** behavior
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#670](https://codeberg.org/dnkl/foot/issues/670)).
changelog: mention keypad application mode keys being removed
2021-08-14 21:10:47 +02:00
* Keypad application mode keys from terminfo; enabling the keypad
application mode is not enough to make foot emit these sequences -
you also need to disable private mode 1035
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#670](https://codeberg.org/dnkl/foot/issues/670)).
changelog: mention km/smm/rmm being removed
2021-08-14 21:08:32 +02:00
changelog: add new ‘unreleased’ section
2021-07-18 18:07:26 +02:00
### Fixed
render: prevent cells from overflowing into margin
2021-07-20 11:12:38 +02:00
* Rendering into the right margin area with `tweak.overflowing-glyphs`
enabled.
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
* PGO builds with clang ([#642](https://codeberg.org/dnkl/foot/issues/642)).
search: reset match state when selection is cancelled While we’re in scrollback search mode, the selection may be cancelled (for example, if the application is scrolling out the selected text). Trying to e.g. extend the search selection after this has happened triggered a crash. This fixes it by simply resetting the search match state when the selection is cancelled. Closes #644
2021-07-22 17:53:29 +02:00
* Crash in scrollback search mode when selection has been canceled due
to terminal content updates
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#644](https://codeberg.org/dnkl/foot/issues/644)).
wayland: prevent hang when terminating due to broken Wayland connection If the call to fdm_wayl() with EPOLLHUP was followed by calls to wayl_roundtrip(), foot would hang. The reason for this is that the EPOLLHUP handler in fdm_wayl() would call wl_display_cancel_read(). wayl_roundtrip() also calls wl_display_cancel_read() (since we normally have called wl_display_prepare_read()), before calling wl_display_roundtrip(). When calling wl_display_cancel_read() two times in a row, without a wl_display_prepare_read() in between, wl_display_roundtrip() hangs. Fix by not calling wl_display_cancel_read() in fdm_wayl(). This ensures our invariant holds: wl_display_prepare_read() is *always* in effect outside of fdm_wayl(). Closes #651
2021-07-24 20:31:14 +02:00
* Foot process not terminating when the Wayland connection is broken
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#651](https://codeberg.org/dnkl/foot/issues/651)).
changelog: initialize output scaling factor to 1
2021-07-26 19:00:56 +02:00
* Output scale being zero on compositors that does not advertise a
scaling factor.
changelog: asynchronous client application termination
2021-07-31 20:13:52 +02:00
* Slow-to-terminate client applications causing other footclient instances to
freeze when closing a footclient window.
render: run the “overflowing glyphs” prepass *before* rendering sixels This fixes an issue where the left-most column of a sixel was “overwritten” by the cell content. This patch also rewrites the prepass logic, to try to reduce the number of loads performed. The new logic loops each row from left to right, looking for dirty cells. When a dirty cell is found, we first scan backwards, until we find a non-overflowing cell. That cell is unaffected by the overflowing cell we’re currently dealing with. We can also stop as soon as we see a dirty cell, since that cell will already have been dealt with. Then, we scan forward, dirtying cells until we see a non-overflowing cell. That first non-overflowing cell is also dirtied, but after that we break. The last loop, that scans forward, advances the same cell pointer used in the outer loop.
2021-08-10 18:33:18 +02:00
* Underlying cell content showing through in the left-most column of
sixels.
changelog: cursor.blink now works in GNOME
2021-08-18 20:18:00 +02:00
* `cursor.blink` not working in GNOME
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#686](https://codeberg.org/dnkl/foot/issues/686)).
term: check visual-focus, not kbd-focus when enabling/disabling cursor blink term_cursor_blink_update() is called when the visual focus changes state (i.e. when our top-level surface is activated de-activated). Checking keyboard focus worked on Sway, but on e.g. GNOME, the order in which keyboard focus and visual focus are updated is different, and we ended up either making the cursor invisible, or visible, but not blinking, when changing focus back to the window. Closes #686
2021-08-17 18:31:42 +02:00
* Blinking cursor stops blinking, or becoming invisible, when
switching focus from, and then back to a terminal window on GNOME
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#686](https://codeberg.org/dnkl/foot/issues/686)).
render: prevent cells from overflowing into margin
2021-07-20 11:12:38 +02:00
changelog: add new ‘unreleased’ section
2021-07-18 18:07:26 +02:00
### Contributors
changelog: initialize output scaling factor to 1
2021-07-26 19:00:56 +02:00
* Nihal Jere
Only brighten palette colors with bold-text-in-bright=palette-based
2021-07-22 18:22:39 +02:00
* [nowrep](https://codeberg.org/nowrep)
changelog: prepare for 1.9.0
2021-08-27 12:45:22 +02:00
* [clktmr](https://codeberg.org/clktmr)
changelog: initialize output scaling factor to 1
2021-07-26 19:00:56 +02:00
changelog: add new ‘unreleased’ section
2021-07-18 18:07:26 +02:00
changelog: prepare for 1.8.2
2021-07-18 17:57:42 +02:00
## 1.8.2
changelog: add new ‘unreleased’ section
2021-07-01 20:19:28 +02:00
### Added
config: add locked-title=no|yes Closes #386
2021-07-04 17:59:40 +02:00
* `locked-title=no|yes` to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#386](https://codeberg.org/dnkl/foot/issues/386)).
render: Allow cells to bleed into their neighbor This patch adds a `confined` flag to each cell to track if the last rendered glyph bled into it's right neighbor. To keep things simple, bleeding into any other neighbor cell than the immediate right one is not allowed. This should cover most use cases. Before rendering a row we now do a prepass and mark all cells unclean that are affected by a bleeding neighbor. If there are consecutive bleeding cells, the whole group must be re-rendered even if only a single cell has changed. The patch also deprecates both old overflowing glyph options *allow-overflowing-double-width-glyphs* and *pua-double-width* in favor of a single new one named *overflowing-glyphs*.
2021-06-15 11:45:27 +02:00
* `tweak.overflowing-glyphs` option, which can be enabled to fix rendering
issues with glyphs of any width that appear cut-off
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#592](https://codeberg.org/dnkl/foot/issues/592)).
config: add locked-title=no|yes Closes #386
2021-07-04 17:59:40 +02:00
changelog: add new ‘unreleased’ section
2021-07-01 20:19:28 +02:00
### Changed
term: rows printed to now defaults to having a hard linebreak That is, instead of requiring a ‘\n’ to be printed, non-empty lines are now treated as having a hard linebreak by default. The linebreak is cleared on an explicit wrap.
2021-07-02 16:31:46 +02:00
* Non-empty lines are now considered to have a hard linebreak,
_unless_ an actual word-wrap is inserted.
csi: invert the meaning of DECSDM There has been some confusion whether enabling DECSDM (private mode 80) enables or disables sixel scrolling. Foot currently enables scrolling when DECSDM is set, and this patch changes this, such that setting DECSDM now *disables* scrolling. The confusion is apparently due to a documentation error in the VT340 manual, as described in https://github.com/dankamongmen/notcurses/issues/1782#issuecomment-863603641. And that makes sense, in a way: the SDM in DECSDM stands for Sixel Display Mode. I.e. it stands to reason that enabling that disables scrolling. Anyway, this lead to https://github.com/hackerb9/lsix/issues/41, where it was eventually proven (by testing on a real VT340), that foot, and a large number of other terminals (including XTerm) has it wrong: https://github.com/hackerb9/lsix/issues/41#issuecomment-873269599.
2021-07-14 19:17:44 +02:00
* Setting `DECSDM` now _disables_ sixel scrolling, while resetting it
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
_enables_ scrolling ([#631](https://codeberg.org/dnkl/foot/issues/631)).
term: rows printed to now defaults to having a hard linebreak That is, instead of requiring a ‘\n’ to be printed, non-empty lines are now treated as having a hard linebreak by default. The linebreak is cleared on an explicit wrap.
2021-07-02 16:31:46 +02:00
changelog: add new ‘unreleased’ section
2021-07-01 20:19:28 +02:00
### Removed
render: Allow cells to bleed into their neighbor This patch adds a `confined` flag to each cell to track if the last rendered glyph bled into it's right neighbor. To keep things simple, bleeding into any other neighbor cell than the immediate right one is not allowed. This should cover most use cases. Before rendering a row we now do a prepass and mark all cells unclean that are affected by a bleeding neighbor. If there are consecutive bleeding cells, the whole group must be re-rendered even if only a single cell has changed. The patch also deprecates both old overflowing glyph options *allow-overflowing-double-width-glyphs* and *pua-double-width* in favor of a single new one named *overflowing-glyphs*.
2021-06-15 11:45:27 +02:00
* The `tweak.allow-overflowing-double-width-glyphs` and
`tweak.pua-double-width` options (which have been superseded by
`tweak.overflowing-glyphs`).
changelog: add new ‘unreleased’ section
2021-07-01 20:19:28 +02:00
### Fixed
allow-overflowing-double-width-glyphs: take glyph offset into account A narrow, but offset:ed glyph should still be considered double width. This patch also fixes a crash, when the maybe-double width glyph is in the last column. This is a regression.
2021-07-02 16:29:08 +02:00
url-mode: purge SHM pixmaps when destroying URLs Unlike other surface types, the SHM cookie depends on the address of each URL instance. This means if we enable, disable, and then enable URL mode again (thus showing exactly the same URLs as the first time), the URLs will have new addresses, and thus the old SHM pixmaps will not get purged automatically. So, manually purge them when destroying the URLs.
2021-07-11 09:54:04 +02:00
* FD exhaustion when repeatedly entering/exiting URL mode with many
URLs.
url-mode: fix crash when removing duplicate and/or overlapping URLs Removing overlaping and duplicated URLs is done by running two nested loops, that both iterate the same URL list. When a duplicate is found, one of the URLs is destroyed and removed from the list. Deleting and removing an item *is* safe, but only as long as _no other_ iterator has references to it. In this case, if we remove an item from e.g. the inner iterator, we’ll crash if the outer iterator’s *next* item is the item being removed. Closes #627
2021-07-11 10:06:12 +02:00
* Double free of URL while removing duplicated and/or overlapping URLs
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
in URL mode ([#627](https://codeberg.org/dnkl/foot/issues/627)).
url-mode: abort when running into un-allocated scrollback memory When tagging URL cells (in preparation for rendering URL mode), we loop the URL’s entire range, setting the `url` attribute of all cells, and dirtying the rows. It is possible to create URLs that are invalid, and wrap around the scrollback, even though the scrollback hasn’t yet been filled. For example, by starting an OSC-8 URL, moving the cursor, and then closing the OSC-8 URL. These URLs are invalid, but are still rendered just fine. “Fine” being relative - they will typically fill the entire screen. But at least that’s a very clear indication for the user that’s something is wrong. The problem is when we hit un-allocated scrollback rows. We didn’t check for NULL rows, and crashed. This has now been fixed.
2021-07-11 11:31:11 +02:00
* Crash when an unclosed OSC-8 URL ran into un-allocated scrollback
rows.
changelog: box-drawing fixes on big-endian
2021-07-14 19:48:13 +02:00
* Some box-drawing characters were rendered incorrectly on big-endian
architectures.
render: search: set clip region Fixes crash when the search box has been reduced in height, due to limited window space.
2021-07-15 18:27:10 +02:00
* Crash when resizing the window to the smallest possible size while
scrollback search is active.
render: scrollback indicator: improve handling of very small window sizes
2021-07-15 18:26:26 +02:00
* Scrollback indicator being incorrectly rendered when window size is
very small.
url-mode: use shm_get_many() If we have lots of URLs, we use up a *lot* of SHM buffers (and thus pools). Each and every one is a single mmap(), of at least 4K. Since all URL labels are created and destroyed at the same time, it makes sense to use a single pool for all buffers. To do this, we must now do two passes; first one to generate the actual string (label content), and to calculate the label sizes. Then we use this information to allocate all SHM buffers at once, from the same pool. Finally, we iterate the URLs again, this time to actually render them.
2021-07-15 18:39:41 +02:00
* Reduced memory usage in URL mode.
changelog: crash when \E[3J was executed with a selection in the scrollback
2021-07-18 15:38:46 +02:00
* Crash when the `E3` escape (`\E[3J`) was executed, and there was a
term: erase_scrollback(): destroy sixels that touch the scrollback
2021-07-18 16:31:33 +02:00
selection, or sixel image, in the scrollback
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#633](https://codeberg.org/dnkl/foot/issues/633)).
allow-overflowing-double-width-glyphs: take glyph offset into account A narrow, but offset:ed glyph should still be considered double width. This patch also fixes a crash, when the maybe-double width glyph is in the last column. This is a regression.
2021-07-02 16:29:08 +02:00
changelog: add new ‘unreleased’ section
2021-07-01 20:19:28 +02:00
### Contributors
render: Allow cells to bleed into their neighbor This patch adds a `confined` flag to each cell to track if the last rendered glyph bled into it's right neighbor. To keep things simple, bleeding into any other neighbor cell than the immediate right one is not allowed. This should cover most use cases. Before rendering a row we now do a prepass and mark all cells unclean that are affected by a bleeding neighbor. If there are consecutive bleeding cells, the whole group must be re-rendered even if only a single cell has changed. The patch also deprecates both old overflowing glyph options *allow-overflowing-double-width-glyphs* and *pua-double-width* in favor of a single new one named *overflowing-glyphs*.
2021-06-15 11:45:27 +02:00
* [clktmr](https://codeberg.org/clktmr)
changelog: add new ‘unreleased’ section
2021-07-01 20:19:28 +02:00
changelog: prepare for 1.8.1
2021-07-01 20:14:20 +02:00
## 1.8.1
log: add LOG_CLASS_NONE and use as initializer for log_level This means that logging will be completely disabled until log_init() has been called, which is useful to prevent log spam when running UNITTEST{} blocks in debug builds. Note that this doesn't change the default log level at runtime, which was already being set to LOG_CLASS_INFO in main.c and client.c. The new log level is also exposed to the command-line interface as `--log-level=none`, which allows disabling logging entirely.
2021-06-26 22:15:09 +01:00
changelog: add new ‘unreleased’ section
2021-06-25 08:44:41 +02:00
### Added
log: add LOG_CLASS_NONE and use as initializer for log_level This means that logging will be completely disabled until log_init() has been called, which is useful to prevent log spam when running UNITTEST{} blocks in debug builds. Note that this doesn't change the default log level at runtime, which was already being set to LOG_CLASS_INFO in main.c and client.c. The new log level is also exposed to the command-line interface as `--log-level=none`, which allows disabling logging entirely.
2021-06-26 22:15:09 +01:00
* `--log-level=none` command-line option.
terminfo: add Tc, setrgbf and setrgbb capabilities These extensions are used by tmux and neovim, in order to make use of 24-bit colors without facing the problems that plague the `RGB` capability. This should allow 24-bit colors to work "out of the box" in tmux, without the usual workaround of adding: set-option -ga terminal-overrides ",foot*:Tc" ...to ~/.tmux.conf. See also: * https://github.com/kovidgoyal/kitty/commit/18fe2e8dfa34038aabd5c3a2fdb3624e2b27932a#commitcomment-31373962 * https://github.com/neovim/neovim/blob/f83c25942dd8b94ad5218ce78b9e6fb86d2f0358/runtime/doc/term.txt#L123-L139 * https://github.com/tmux/tmux/blob/b1a8c0fe022e99cffb0fb4f321740464f35bc6b9/CHANGES#L988-L989 Closes #615
2021-06-29 08:47:46 +01:00
* `Tc`, `setrgbf` and `setrgbb` capabilities in `foot` and `foot-direct`
terminfo entries. This should make 24-bit RGB colors work in tmux and
neovim, without the need for config hacks or detection heuristics
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#615](https://codeberg.org/dnkl/foot/issues/615)).
config: add tweak.grapheme-width-method=wcswidth|at-most-2
2021-06-30 18:00:33 +02:00
log: add LOG_CLASS_NONE and use as initializer for log_level This means that logging will be completely disabled until log_init() has been called, which is useful to prevent log spam when running UNITTEST{} blocks in debug builds. Note that this doesn't change the default log level at runtime, which was already being set to LOG_CLASS_INFO in main.c and client.c. The new log level is also exposed to the command-line interface as `--log-level=none`, which allows disabling logging entirely.
2021-06-26 22:15:09 +01:00
changelog: add new ‘unreleased’ section
2021-06-25 08:44:41 +02:00
### Changed
changelog: move grapheme cluster width entry to ‘changed’, and rewrite it
2021-07-01 20:13:03 +02:00
* Grapheme cluster width is now limited to two cells by default. This
may cause cursor synchronization issues with many applications. You
can set `[tweak].grapheme-width-method=wcswidth` to revert to the
changelog: s/from/in
2021-07-01 20:44:53 +02:00
behavior in foot-1.8.0.
changelog: move grapheme cluster width entry to ‘changed’, and rewrite it
2021-07-01 20:13:03 +02:00
changelog: add new ‘unreleased’ section
2021-06-25 08:44:41 +02:00
### Fixed
vt: don’t reset utf8proc grapheme state when we’re not at a grapheme break
2021-06-25 20:42:23 +02:00
* Grapheme cluster state being reset between codepoints.
config: remove replaced/removed key bindings, instead of marking as ‘unused’ Instead of keeping removed/replaced key bindings in the key binding array (marked as ‘unused’), remove them, by compacting the array. The invariant is thus that there should be *no* entries in the key binding list with the `BIND_ACTION_NONE` for action. Add code to debug builds that verifies this, plus a unit test. Closes #614
2021-06-29 18:08:15 +02:00
* Regression: custom URL key bindings not working
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#614](https://codeberg.org/dnkl/foot/issues/614)).
vt: don’t reset utf8proc grapheme state when we’re not at a grapheme break
2021-06-25 20:42:23 +02:00
changelog: add new ‘unreleased’ section
2021-06-25 08:44:41 +02:00
### Contributors
log: add LOG_CLASS_NONE and use as initializer for log_level This means that logging will be completely disabled until log_init() has been called, which is useful to prevent log spam when running UNITTEST{} blocks in debug builds. Note that this doesn't change the default log level at runtime, which was already being set to LOG_CLASS_INFO in main.c and client.c. The new log level is also exposed to the command-line interface as `--log-level=none`, which allows disabling logging entirely.
2021-06-26 22:15:09 +01:00
* [craigbarnes](https://codeberg.org/craigbarnes)
changelog: add new ‘unreleased’ section
2021-06-25 08:44:41 +02:00
changelog: prepare for 1.8.0
2021-06-25 08:23:36 +02:00
## 1.8.0
csi: add support for DECSET 2026, as an alternative to BSU/ESU sequences See: https://gitlab.freedesktop.org/terminal-wg/specifications/-/merge_requests/2#note_847720
2021-04-25 18:35:46 +01:00
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
### Grapheme shaping
changelog: spelling; add missing ‘l’ in ‘experimental’
2021-06-24 22:55:28 +02:00
This release adds _experimental, opt-in_ support for grapheme cluster
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
segmentation and grapheme shaping.
(note: several of the examples below may not render correctly in your
browser, viewer or editor).
Grapheme cluster segmentation is the art of splitting up text into
grapheme clusters, where a cluster may consist of more than one
Unicode codepoint. For example, 🙂 is a single codepoint, while 👩🏽‍🚀
changelog: updates to “grapheme shaping”
2021-06-24 14:04:08 +02:00
consists of 4 codepoints (_Woman_ + _Medium skin tone_ + _Zero width
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
joiner_ + _Rocket_). The goal is to _cluster_ codepoints belonging to
the same grapheme in the same cell in the terminal.
Previous versions of foot implemented a simple grapheme cluster
segmentation technique that **only** handled zero-width
changelog: composed -> combining
2021-06-24 17:36:52 +02:00
codepoints. This allowed us to cluster combining characters, like q́
changelog: updates to “grapheme shaping”
2021-06-24 14:04:08 +02:00
(_q_ + _COMBINING ACUTE ACCENT_).
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
Once we have a grapheme cluster, we need to _shape_ it.
changelog: composed -> combining
2021-06-24 17:36:52 +02:00
Combining characters are simple: they are typically rendered as
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
multiple glyphs layered on top of each other. This is why previous
versions of foot got away with it without any actual text shaping
support.
Beyond that, support from the font library is needed. Foot now depends
on fcft-2.4, which added support for grapheme and text shaping. When
rendering a cell, we ask the font library: give us the glyph(s) for
this sequence of codepoints.
Fancy emoji sequences aside, using libutf8proc for grapheme cluster
segmentation means **improved correctness**.
For full support, the following is required:
* fcft compiled with HarfBuzz support
* foot compiled with libutf8proc support
* `tweak.grapheme-shaping=yes` in `foot.ini`
changelog: describe what (does not) happens when grapheme-shaping=no
2021-06-24 17:36:57 +02:00
If `tweak.grapheme-shaping` has **not** been enabled, foot will
neither use libutf8proc to do grapheme cluster segmentation, nor will
it use fcft’s grapheme shaping capabilities to shape combining
characters.
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
This feature is _experimental_ mostly due to the “wcwidth” problem;
how many cells should foot allocate for a grapheme cluster? While the
answer may seem simple, the problem is that, whatever the answer is,
changelog: updates to “grapheme shaping”
2021-06-24 14:04:08 +02:00
the client application **must** come up with the **same**
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
answer. Otherwise we get cursor synchronization issues.
In this release, foot simply adds together the `wcwidth()` of all
codepoints in the grapheme cluster. This is equivalent to running
`wcswidth()` on the entire cluster. **This is likely to change in the
future**.
changelog: updates to “grapheme shaping”
2021-06-24 14:04:08 +02:00
Finally, note that grapheme shaping is not the same thing as text (or
text run) shaping. In this version, foot only shapes individual
graphemes, not entire text runs. That means e.g. ligatures are **not**
supported.
changelog: add a “grapheme shaping” section
2021-06-24 10:51:43 +02:00
Merge branch 'releases/1.7'
2021-04-18 20:16:48 +02:00
### Added
csi: add support for DECSET 2026, as an alternative to BSU/ESU sequences See: https://gitlab.freedesktop.org/terminal-wg/specifications/-/merge_requests/2#note_847720
2021-04-25 18:35:46 +01:00
* Support for DECSET/DECRST 2026, as an alternative to the existing
"synchronized updates" DCS sequences
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#459](https://codeberg.org/dnkl/foot/issues/459)).
config: add ‘beam-thickness’ option * Rename cursor.style value ‘bar’ to ‘beam’. ‘bar’ remains recognized, but should eventually be deprecated and then removed. * Add ‘cursor.beam-thickness’ option, a pt-or-px value specifying the thickness of the beam cursor. Defaults to 1.5pt. * Rename (and export) pt_or_px_as_pixels() to term_pt_or_px_as_pixels() * Change term_pt_or_px_as_pixels() to round point values instead of truncating them.
2021-04-30 20:31:47 +02:00
* `cursor.beam-thickness` option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#464](https://codeberg.org/dnkl/foot/issues/464)).
config: add cursor.underline-thickness Works in pretty much the same way as ‘beam-thickness’, except that the default value is “the font’s underline thickness”. This means, that when unset, the cursor underline thickness scales with the font size. But, when explicitly set, either to a point size value, or a pixel size, it remains fixed at that size. Closes #524
2021-05-18 18:52:10 +02:00
* `cursor.underline-thickness` option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#524](https://codeberg.org/dnkl/foot/issues/524)).
box-drawing: add Unicode 13 U+1FB70 - U+1FB8B Part of #471
2021-05-03 17:57:16 +02:00
* Unicode 13 characters U+1FB70 - U+1FB8B to list of box drawing
characters rendered by foot itself (rather than using font glyphs)
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#471](https://codeberg.org/dnkl/foot/issues/471)).
config: move url-mode related options to a dedicated section, ‘url’
2021-05-20 17:56:56 +02:00
* Dedicated `[bell]` section to config, supporting multiple actions
and a new `command` action to run an arbitrary command.
update changelog
2021-05-07 04:49:34 -05:00
(https://codeberg.org/dnkl/foot/pulls/483)
config: move url-mode related options to a dedicated section, ‘url’
2021-05-20 17:56:56 +02:00
* Dedicated `[url]` section to config.
config: add url.protocols This makes the protocols recognized by auto-detected URLs configurable. Closes #531
2021-05-20 17:58:06 +02:00
* `[url].protocols` option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#531](https://codeberg.org/dnkl/foot/issues/531)).
configure full color palette in foot.ini Allow the use of numeric keys in [colors] to configure the full set of 256 colors in the palette. Fixes #489
2021-05-08 02:18:45 -05:00
* Support for setting the full 256 color palette in foot.ini
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#489](https://codeberg.org/dnkl/foot/issues/489))
changeloge: xdg-activation support
2021-05-14 14:22:43 +02:00
* XDG activation support, will be used by `[bell].urgent` when
available (falling back to coloring the window margins red when
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
unavailable) ([#487](https://codeberg.org/dnkl/foot/issues/487)).
config: bind ctrl+c to "cancel" in search/url mode by default Closes #544
2021-05-25 16:51:07 +01:00
* `ctrl`+`c` as a default key binding; to cancel search/url mode.
notify: add ${window-title}
2021-05-27 12:11:47 +02:00
* `${window-title}` to `notify`.
config: add ‘include’ directive This allows you to include sub-configurations. For example, theme files. The ‘include’ directive is a top-level keyword. I.e. it cannot be used inside sections. * The included file must be specified with an absolute path * The included file is parsed in its own scope * Nested includes are allowed * Multiple include directives are allowed Closes #555
2021-05-28 17:44:13 +02:00
* Support for including files in `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#555](https://codeberg.org/dnkl/foot/issues/555)).
changelog: add bug ref to ‘environment section added to foot/footclient’
2021-05-30 10:21:24 +02:00
* `ENVIRONMENT` section in **foot**(1) and **footclient**(1) man pages
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#556](https://codeberg.org/dnkl/foot/issues/556)).
config: add boolean option tweak.pua-double-width When enabled, PUA (Private Usage Area) codepoints are always treated as double-width glyphs, regardless of the actual glyph width. Requires allow-overflowing-double-width-glyphs=yes
2021-05-31 17:10:05 +02:00
* `tweak.pua-double-width` option to `foot.ini`, letting you force
_Private Usage Area_ codepoints to be treated as double-width
characters.
osc: implement iTerm2’s OSC-9 - desktop notifications
2021-06-02 17:50:29 +02:00
* OSC 9 desktop notifications (iTerm2 compatible).
changelog: add issue links for previous 2 entries
2021-06-09 09:30:34 +01:00
* Support for LS2 and LS3 (locking shift) escape sequences
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#581](https://codeberg.org/dnkl/foot/issues/581)).
Override options from command line Allow any configuration option to be overridden with -o/--override 'section.key=value' arguments, as suggested in #554 update completitions for override slight refactoring to ease footclient support
2021-06-11 04:40:08 -05:00
* Support for overriding configuration options on the command line
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#554](https://codeberg.org/dnkl/foot/issues/554),
[#600](https://codeberg.org/dnkl/foot/issues/600)).
config: add underline-offset option This option allows the user to configure a custom underline offset. That is, use the user provided offset instead of the font provided one. Closes #490
2021-06-17 17:52:38 +02:00
* `underline-offset` option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#490](https://codeberg.org/dnkl/foot/issues/490)).
config: add csd.button-color option This option controls the foreground color of the minimize/maximize/close buttons. I.e. the color used to draw the minimize/maximize/close glyphs. It defaults to default background color.
2021-06-20 10:44:50 +02:00
* `csd.button-color` option to `foot.ini`.
changelog: -Dterminfo-install-location meson command line option
2021-06-23 16:58:10 +02:00
* `-Dterminfo-install-location=disabled|<custom-path>` meson command
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
line option ([#569](https://codeberg.org/dnkl/foot/issues/569)).
config: add ‘beam-thickness’ option * Rename cursor.style value ‘bar’ to ‘beam’. ‘bar’ remains recognized, but should eventually be deprecated and then removed. * Add ‘cursor.beam-thickness’ option, a pt-or-px value specifying the thickness of the beam cursor. Defaults to 1.5pt. * Rename (and export) pt_or_px_as_pixels() to term_pt_or_px_as_pixels() * Change term_pt_or_px_as_pixels() to round point values instead of truncating them.
2021-04-30 20:31:47 +02:00
csi: add support for DECSET 2026, as an alternative to BSU/ESU sequences See: https://gitlab.freedesktop.org/terminal-wg/specifications/-/merge_requests/2#note_847720
2021-04-25 18:35:46 +01:00
Merge branch 'releases/1.7'
2021-04-18 20:16:48 +02:00
### Changed
changelog: generate-alt-random-writes.py --sixel fixes
2021-04-22 11:26:59 +02:00
meson: require fcft >= 2.4
2021-05-07 11:31:33 +02:00
* [fcft](https://codeberg.org/dnkl/fcft): required version bumped from
2.3.x to 2.4.x.
changelog: generate-alt-random-writes.py --sixel fixes
2021-04-22 11:26:59 +02:00
* `generate-alt-random-writes.py --sixel`: width and height of emitted
sixels has been adjusted.
render: do render concealed text when it’s highlighted
2021-04-23 21:27:32 +02:00
* _Concealed_ text (`\E[8m`) is now revealed when highlighted.
render: modify background color for highlighted text when fg == bg When rendering a selected/highlighted cell where the foreground and background colors are the same, invert the background color to make the selected text legible. Closes #455
2021-04-23 21:30:47 +02:00
* The background color of highlighted text is now adjusted, when the
foreground and background colors are the same, making the
highlighted text legible
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#455](https://codeberg.org/dnkl/foot/issues/455)).
config: add ‘beam-thickness’ option * Rename cursor.style value ‘bar’ to ‘beam’. ‘bar’ remains recognized, but should eventually be deprecated and then removed. * Add ‘cursor.beam-thickness’ option, a pt-or-px value specifying the thickness of the beam cursor. Defaults to 1.5pt. * Rename (and export) pt_or_px_as_pixels() to term_pt_or_px_as_pixels() * Change term_pt_or_px_as_pixels() to round point values instead of truncating them.
2021-04-30 20:31:47 +02:00
* `cursor.style=bar` to `cursor.style=beam`. `bar` remains a
recognized value, but will eventually be deprecated, and removed.
* Point values in `line-height`, `letter-spacing`,
`horizontal-letter-offset` and `vertical-letter-offset` are now
rounded, not truncated, when translated to pixel values.
main/client: change exit code * foot exits with -26/230 * footclient exits with -36/220 This is to give each application a range of exit codes. Currently unused, but we may want to change this in the future.
2021-05-01 10:46:40 +02:00
* Foot’s exit code is now -26/230 when foot itself failed to launch
foot/footclient: use a custom exit code when foot/footclient fail to run Normally, foot and footclient uses the exit code from the client application (i.e. the shell). However, foot (or footclient) itself may fail to run; if run outside of a Wayland session, or no fonts are installed, or the client application/shell cannot be found (“foot lsdjfldsjf”) etc. Up until now, there has been no way to differentiate these kind of failures from the client application exiting with code 1. This patch changes foot’s failure exit code to -27/229, and footclient’s to -28/228. Note that footclient will exit with foot’s -27/229 if footclient ran successfully, but the foot server failed to instantiate a new window. Closes #466.
2021-04-30 22:47:16 +02:00
(due to invalid command line options, client application/shell not
main/client: change exit code * foot exits with -26/230 * footclient exits with -36/220 This is to give each application a range of exit codes. Currently unused, but we may want to change this in the future.
2021-05-01 10:46:40 +02:00
found etc). Footclient’s exit code is -36/220 when it itself fails
to launch (e.g. bad command line option) and -26/230 when the foot
foot/footclient: use a custom exit code when foot/footclient fail to run Normally, foot and footclient uses the exit code from the client application (i.e. the shell). However, foot (or footclient) itself may fail to run; if run outside of a Wayland session, or no fonts are installed, or the client application/shell cannot be found (“foot lsdjfldsjf”) etc. Up until now, there has been no way to differentiate these kind of failures from the client application exiting with code 1. This patch changes foot’s failure exit code to -27/229, and footclient’s to -28/228. Note that footclient will exit with foot’s -27/229 if footclient ran successfully, but the foot server failed to instantiate a new window. Closes #466.
2021-04-30 22:47:16 +02:00
server failed to instantiate a new window
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#466](https://codeberg.org/dnkl/foot/issues/466)).
render: only apply alpha when we’re using the default bg for background In all other cases, alpha is disabled. This includes: * Palette- or RGB-colors matching the default background color * When any kind of reverse video is enabled (e.g. DECSCNM, or ANSI reverse)
2021-05-01 20:17:54 +02:00
* Background alpha no longer applied to palette or RGB colors that
matches the background color.
changelog: improved performance when double buffering
2021-05-12 20:07:18 +02:00
* Improved performance on compositors that does not release shm
buffers immediately, e.g. KWin
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#478](https://codeberg.org/dnkl/foot/issues/478)).
changelog: ctrl+w can now be used across lines
2021-05-17 18:19:55 +02:00
* `ctrl + w` (_extend-to-word-boundary_) can now be used across lines
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#421](https://codeberg.org/dnkl/foot/issues/421)).
url-mode: remove overlapping URLs, not just duplicates echo -e '\e]8;;https://www.foo.bar\e\\https://www.foo\e]8;;\e\\.bar' will produce an OSC-8 URL (https://www.foo) that is slightly shorter than the auto-detected one (https://www.foo.bar). This produces strange results in URL mode. For example, if url.osc8-underline=always, the OSC8 underline will be removed when url-mode is exited. This patch changes the behavior so that auto-detected URLs that overlap OSC-8 URLs are removed. Note that OSC-8 URLs cannot overlap with each other, and that auto-detected URLs also cannot overlap with each other.
2021-05-22 16:42:43 +02:00
* Ignore auto-detected URLs that overlap with OSC-8 URLs.
config: notify: change default value to use ${app-id} Make the default value of ‘notify’ use ${app-id} for icon and application name.
2021-05-27 11:41:57 +02:00
* Default value for the `notify` option to use `-a ${app-id} -i
${app-id} ...` instead of `-a foot -i foot ...`.
input: pass through scrollback-* key bindings when alt screen is activw Since the alt screen have no scrollback, all scrollback-* actions are effectively no-ops when the alt screen is active. Make them available to the client application instead. Closes #573
2021-06-04 23:25:45 +02:00
* `scrollback-*`+`pipe-scrollback` key bindings are now passed through
to the client application when the alt screen is active
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#573](https://codeberg.org/dnkl/foot/issues/573)).
render: reverse video only swaps *default* fg/bg This matches XTerm behavior, and fixes vttest 11.6.6.2: Test non-VT100 -> Test ISO-6429 colors -> Test of VT102-style features with BCE -> Test of screen features
2021-06-07 21:46:46 +02:00
* Reverse video (`\E[?5h`) now only swaps the default foreground and
background colors. Cells with explicit foreground and/or background
colors remain unchanged.
changelog: tabs are preserved
2021-06-09 09:57:20 +02:00
* Tabs (`\t`) are now preserved when the window is resized, and when
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
copying text ([#508](https://codeberg.org/dnkl/foot/issues/508)).
sixel: add support for overlapping sixels Writing a sixel on top of an already existing sixel currently has the following limitations in foot: * The parts of the first sixel that is covered by the new sixel are removed, completely. Even if the new sixel has transparent areas. I.e. writing a transparent sixel on top of another sixel *replaces* the first sixel with the new sixel, instead of layering them on top of each other. * The second sixel erases the first sixel cell-wise. That is, a sixel whose size isn’t a multiple of the cell dimensions will leave unsightly holes in the first sixel. This patch takes care of both issues. The first one is actually the easiest one: all we need to do is calculate the intersection, and blend the two images. To keep things relatively simple, we use the pixman image from the *new* image, and use the ‘OVER_REVERSE’ operation to blend the new image over the old one. That is, the old image is still split into four tiles (top, left, right, bottom), just like before. But instead of throwing away the fifth middle tile, we blend it with the new image. As an optimization, this is only done if the new image has transparency (P1=1). The second problem is solved by detecting when we’re erasing an area from the second image that is larger than the new image. In this case, we enlarge the new image, and copy the old image into the new one. Finally, when we enlarge the new image, there may be areas in the new image that is *not* covered by the old image. These areas are made transparent. The end result is: * Each cell is covered by at *most* 1 sixel image. I.e. the total numbers of sixels are finite. This is important for the ‘mpv --vo=sixel’ use case - we don’t want to end up with thousands of sixels layered on top of each other. * Writing an opaque sixel on top of another sixel has _almost_ zero performance impact. Especially if the two sixels have the same size, so that we don’t have to resize the new image. Again, important for the ‘mpv --vo=sixel’ use case. Closes #562
2021-06-06 21:38:31 +02:00
* Writing a sixel on top of another sixel no longer erases the first
sixel, but the two are instead blended
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#562](https://codeberg.org/dnkl/foot/issues/562)).
config: demote “no configuration found, using defaults” to a mere warning And don’t notify the user in the terminal window, only log it on stderr.
2021-06-10 20:40:01 +02:00
* Running foot without a configuration file is no longer an error; it
has been demoted to a warning, and is no longer presented as a
notification in the terminal window, but only logged on stderr.
changelog: generate-alt-random-writes.py --sixel fixes
2021-04-22 11:26:59 +02:00
Merge branch 'releases/1.7'
2021-04-18 20:16:48 +02:00
### Deprecated
render: force underlines to be visible In some cases, the underline position (typically provided by the font, mind you), end up below the cell, making it visible. Note that below the cell here means below the line. I.e. the font provided underline position is below the font provided line height... Oh well. Doing this in foot rather than fcft, since other applications typically don’t have to clip the rendered text. Closes #503
2021-05-11 17:40:59 +02:00
config: move url-mode related options to a dedicated section, ‘url’
2021-05-20 17:56:56 +02:00
* `bell` option in `foot.ini`; set actions in the `[bell]` section
instead.
* `url-launch` option in `foot.ini`; use `launch` in the `[url]`
section instead.
* `jump-label-letters` option in `foot.ini`; use `label-letters` in
the `[url]` section instead.
* `osc8-underline` option in `foot.ini`; use `osc8-underline` in the
`[url]` section instead.
update changelog
2021-05-07 04:49:34 -05:00
render: force underlines to be visible In some cases, the underline position (typically provided by the font, mind you), end up below the cell, making it visible. Note that below the cell here means below the line. I.e. the font provided underline position is below the font provided line height... Oh well. Doing this in foot rather than fcft, since other applications typically don’t have to clip the rendered text. Closes #503
2021-05-11 17:40:59 +02:00
Merge branch 'releases/1.7'
2021-04-18 20:16:48 +02:00
### Removed
quirk: remove plasma/kwin quirk Older version of Plasma/KWin had an issue where buffer damage recorded before the buffer was attached were ignored. This appears to have been fixed now.
2021-05-11 17:39:13 +02:00
* Buffer damage quirk for Plasma/KWin.
Merge branch 'releases/1.7'
2021-04-18 20:16:48 +02:00
### Fixed
changelog: generate-alt-random-writes.py --sixel fixes
2021-04-22 11:26:59 +02:00
* `generate-alt-random-writes.py --sixel` sometimes crashing,
resulting in PGO build failures.
config: fix color cube generation Closes #479
2021-05-06 12:37:22 +02:00
* Wrong colors in the 256-color cube
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#479](https://codeberg.org/dnkl/foot/issues/479)).
term: reset: fix reset of the VT struct 1. Free buffers and strings 2. memset() the vt struct 3. re-initialize members that must not be zero We _could_ replace the memset() with explicit zeroing of all the members. It’s just that there’s a lot of arrays, so this is much easier. Closes #495
2021-05-08 15:18:25 +02:00
* Memory leak triggered by “opening” an OSC-8 URI and then resetting
the terminal without closing the URI
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#495](https://codeberg.org/dnkl/foot/issues/495)).
changelog: sixel assertion hit when a sixel fills the scrollback
2021-05-08 20:29:35 +02:00
* Assertion when emitting a sixel occupying the entire scrollback
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
history ([#494](https://codeberg.org/dnkl/foot/issues/494)).
render: force underlines to be visible In some cases, the underline position (typically provided by the font, mind you), end up below the cell, making it visible. Note that below the cell here means below the line. I.e. the font provided underline position is below the font provided line height... Oh well. Doing this in foot rather than fcft, since other applications typically don’t have to clip the rendered text. Closes #503
2021-05-11 17:40:59 +02:00
* Font underlines being positioned below the cell (and thus being
invisible) for certain combinations of fonts and font sizes
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#503](https://codeberg.org/dnkl/foot/issues/503)).
sixel: don’t *ever* shrink image below its SRA size If the image was accompanied with a “Set Raster Attributes” (SRA) command, make sure we *never* shrink the image below the size specified in the SRA. Images are normally shrunk when their bottom rows are fully transparent. This enables sixels that aren’t a multiple of 6 to be emitted, without also emitting an SRA command. But if there *is* an SRA command, obey it. Verified against XTerm-367
2021-05-16 10:57:43 +02:00
* Sixels with transparent bottom border being resized below the size
specified in _”Set Raster Attributes”_.
changelog: fonts sometimes not being reloaded with the correct scaling factor
2021-05-13 00:21:22 +02:00
* Fonts sometimes not being reloaded with the correct scaling factor
when `dpi-aware=no`, or `dpi-aware=auto` with monitor(s) with a
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
scaling factor > 1 ([#509](https://codeberg.org/dnkl/foot/issues/509)).
vt: limit maximum value of params in vt_param_get() So that the value is clamped to the range [0, 0x7fffffff] and retains the same value, regardless of whether it's interpreted as a signed or unsigned integer. Closes #522
2021-05-16 19:38:00 +01:00
* Crash caused by certain CSI sequences with very large parameter
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
values ([#522](https://codeberg.org/dnkl/foot/issues/522)).
fdm: always check for signals after epoll_pwait(), not only on EINTR This fixes an issue where we, at least on FreeBSD, sometimes get stuck in epoll_pwait() after the shell has exited. It turned out to be because the SIGCHLD signal was delivered at the same time FDs were made readable/writeable. I.e. epoll_pwait() returned a non-zero value even though it should have been interrupted by the SIGCHLD. To avoid having to search the entire signal array *every time* epoll_pwait() returns, add a flag that is set in the signal handler. This tells the FDM to scan the signal array after returning from epoll_pwait().
2021-05-21 20:00:45 +02:00
* Rare occurrences where the window did not close when the shell
exited. Only seen on FreeBSD
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#534](https://codeberg.org/dnkl/foot/issues/534))
wayland: roundtrip: log error and abort when wl_display_roundtrip() fails ayl_roundtrip() has the following code: wl_display_roundtrip(wayl->display); while (wl_display_prepare_read(wayl->display) != 0) wl_display_dispatch_pending(wayl->display); wayl_flush(wayl); If the first wl_display_roundtrip() fails, for example because the Wayland socket has been closed, we may get stuck in the while-loop. This happens if the read queue isn’t empty, in which case wl_display_prepare_read() will return -1 and we’ll continue trying to dispatch the pending events forever, never succeeding since the socket is gone. Closes #542
2021-05-24 20:42:55 +02:00
* Foot process(es) sometimes remaining, using 100% CPU, when closing
multiple foot windows at the same time
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#542](https://codeberg.org/dnkl/foot/issues/542)).
changelog: fixed mod+shift+tab regression
2021-05-25 07:57:23 +02:00
* Regression where `<mod>+shift+tab` always produced `\E[Z` instead of
the correct `\E[27;<mod>;9~` sequence
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#547](https://codeberg.org/dnkl/foot/issues/547)).
term: fix crash when an OSC-8 URI wraps around the scrollback Long OSC-8 URIs, that are split up over multiple rows, are handled by emitting one URI range on each row the URL touches. This was done by initializing a row index variable, and then incrementing it each loop iteration. This caused an out-of-bounds array access when the row index reached the maximum number of scrollback lines. The fix is simple: make sure the row index variable wraps around, instead of incrementing without any bounds. Closes #552
2021-05-26 13:59:32 +02:00
* Crash when a line wrapping OSC-8 URI crossed the scrollback wrap
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
around ([#552](https://codeberg.org/dnkl/foot/issues/552)).
selection: pay attention to hard linebreaks when search for word boundaries Double-clicking on a word in the left or right margin, would line-wrap the selection if there was a non-empty cell in the corresponding right/left margin on the prev/next line. Regardless of whether there was a hard linebreak or not. Script to reprouce: !/bin/bash cols=$(tput cols) printf "%*coo\nbar\n" $((${cols} - 2)) f Run, then double click either “foo” or “bar”. Neither should select the other part. Closes #565
2021-05-31 17:12:38 +02:00
* Selection incorrectly wrapping rows ending with an explicit newline
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#565](https://codeberg.org/dnkl/foot/issues/565)).
url-mode: off-by-one error in end-point column of auto-detected URLs When an auto-detected URL ended *on* the right-most column, the URL endpoint was off by one, resulting in the underline in URL mode being one character short.
2021-06-01 18:58:26 +02:00
* Off-by-one error in markup of auto-detected URLs when the URL ends
in the right-most column.
grid: don’t cut multi-column chars in half when resizing the alt screen When we resize the alt screen, we don’t reflow the text, we simply truncate all the lines. When doing this, make sure we don’t truncate in the middle of a multi-column character.
2021-06-02 19:32:05 +02:00
* Multi-column characters being cut in half when resizing the
alternate screen.
slave/spawn: restore SIGHUP handler after fork(), before exec() Foot installs a SIG_IGN handler for SIGHUP. Ignored signals are inherited in sub-processes. Thus, we need to restore it to SIG_DFL before exec:ing.
2021-06-02 17:48:57 +02:00
* Restore `SIGHUP` in spawned processes.
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
* Text reflow performance ([#504](https://codeberg.org/dnkl/foot/issues/504)).
csi: IL+DL: move cursor to column 0 This fixes vttest 11.6.6.3 Test non-VT100 -> Test ISO-6429 colors -> Test of VT102-style features with BCE -> Test Insert/Delete Char/Line
2021-06-07 21:57:11 +02:00
* IL+DL (`CSI Ps L` + `CSI Ps M`) now moves the cursor to column 0.
vt: fix SS2/SS3 escape sequences to act correctly as single shifts These sequences are supposed to affect the next printable ASCII character and then reset to the previous character set, but before this commit they were behaving like locking shifts.
2021-06-08 21:09:40 +01:00
* SS2 and SS3 (single shift) escape sequences behaving like locking
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
shifts ([#580](https://codeberg.org/dnkl/foot/issues/580)).
selection: add support for TEXT/STRING/UTF8_STRING mime-types in incoming offers We were already offering these mime types for our own clipboard data, but ignored them in incoming offers. Fixes paste issues from Geany. Closes #583
2021-06-09 09:51:07 +02:00
* `TEXT`+`STRING`+`UTF8_STRING` mime types not being recognized in
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
clipboard offers ([#583](https://codeberg.org/dnkl/foot/issues/583)).
term: free the data associated with the pixman image when destroying box-drawing glyphs Closes #586
2021-06-09 10:31:24 +02:00
* Memory leak caused by custom box drawing glyphs not being completely
freed when destroying a foot window instance
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#586](https://codeberg.org/dnkl/foot/issues/586)).
search: don’t crash when we don’t have any XKB compose state
2021-06-16 17:44:14 +02:00
* Crash in scrollback search when current XKB layout is missing
_compose_ definitions.
render: use a timer instead of relying on the frame callback for title update throttling Using the frame callback works most of the time, but e.g. Sway doesn’t call it while the window is hidden, and thus prevents us from updating the title in e.g. stacked views. This patch uses a timer FD instead. We store a timestamp from when the title was last updated. When the application wants to update the title, we first check if we already have a timer running, and if so, does nothing. If no timer is running, check the timestamp. If enough time has passed, update the title immediately. If not, instantiate a timer and wait for it to trigger. Set the minimum time between two updates to ~8ms (twice per frame, for a 60Hz output, and ~once per frame on a 120Hz output). Closes #591
2021-06-15 17:27:50 +02:00
* Window title not being updated while window is hidden
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#591](https://codeberg.org/dnkl/foot/issues/591)).
uri: hostname_is_localhost(): don’t crash if hostname == NULL
2021-06-19 15:56:39 +02:00
* Crash on badly formatted URIs in e.g. OSC-8 URLs.
wayland: apply CSD/SSD changes in the surface configure event The configure event asks the client to change its decoration mode. The configured state should not be applied immediately. Clients must send an ack_configure in response to this event. See xdg_surface.configure and xdg_surface.ack_configure for details. In particular, ”the configured state should *not* be applied immediately”. Instead, treat CSD/SSD changes like all other window dimension related changes: store the to-be mode in win->configure, and apply it in the surface configure event. This fixes an issue where foot incorrectly resized the window when the server switched between CSD/SSD at run-time.
2021-06-22 18:58:38 +02:00
* Window being incorrectly resized on CSD/SSD run-time changes.
changelog: generate-alt-random-writes.py --sixel fixes
2021-04-22 11:26:59 +02:00
Merge branch 'releases/1.7'
2021-04-18 20:16:48 +02:00
### Contributors
update changelog
2021-05-07 04:49:34 -05:00
* [r\_c\_f](https://codeberg.org/r_c_f)
doc: add ENVIRONMENT section to foot(1) and footclient(1) man pages Closes #556
2021-05-30 03:29:31 +01:00
* [craigbarnes](https://codeberg.org/craigbarnes)
Merge branch 'releases/1.7'
2021-04-18 20:16:48 +02:00
changelog: prepare for 1.7.2
2021-04-18 20:12:26 +02:00
## 1.7.2
changelog: add new ‘unreleased’ section
2021-03-28 14:29:55 +02:00
### Added
osc: add support for URxvt extension to include alpha in OSC-11 There are two variants, either using a ‘[percent]’ prefix for legacy colors, or using ‘rgba:r/g/b/a’ instead of ‘rgb:r/g/b’. Closes #436
2021-04-05 22:05:50 +02:00
changelog: tweak wording for URxvt’s XParseColor extension
2021-04-07 08:01:55 +02:00
* URxvt OSC-11 extension to set background alpha
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#436](https://codeberg.org/dnkl/foot/issues/436)).
changelog: rewrite entry for OSC 17/117/19/119
2021-04-08 13:50:02 +02:00
* OSC 17/117/19/119 - change/reset selection background/foreground
color.
config: add box-drawings-uses-font-glyphs=no|yes option When disabled, we render box drawing characters ourselves. This is the default. When enabled, we instead use font glyphs. I.e. no special treatment. Closes #430
2021-04-09 23:19:20 +02:00
* `box-drawings-uses-font-glyphs=yes|no` option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#430](https://codeberg.org/dnkl/foot/issues/430)).
osc: add support for URxvt extension to include alpha in OSC-11 There are two variants, either using a ‘[percent]’ prefix for legacy colors, or using ‘rgba:r/g/b/a’ instead of ‘rgb:r/g/b’. Closes #436
2021-04-05 22:05:50 +02:00
changelog: add new ‘unreleased’ section
2021-03-28 14:29:55 +02:00
### Changed
render: draw underline cursor below text underline This ensures the cursor is visible on cells where the text is underlined. Closes #415
2021-04-09 21:47:57 +02:00
* Underline cursor is now rendered below text underline
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#415](https://codeberg.org/dnkl/foot/issues/415)).
render: don’t let URL jump label sub-surfaces extend outside window geometry We have no guarantee that sub-surfaces extending outside the window geometry are rendered correctly (if at all). For example, both Sway and River will render the window border on top of the sub-surface. Future versions of Sway may clip the sub-surface. Since jump-labels are positioned slightly above, and to the left of the URLs first character, having a label on either the top row, or on the first column, will likely position it outside the window. This is handled by simply setting x/y to 0 (or, to -margin, since the label coordinate is later offsetted with the window margins). Second, if the label is very long, it may extend outside the window. This is very unusual for labels only showing the key, and not the URL itself, but could happen in this case too, if e.g. the user has configured double-width key characters. This is handled by calculating its maximum width, and then truncating the label. Although very unlikely, it is possible for a label to also extend outside the window’s vertical size. This could happen for very small font sizes, where the label’s own margins are large, relative to the font size. This case is currently not handled. Closes #443
2021-04-10 13:16:39 +02:00
* Foot now tries much harder to keep URL jump labels inside the window
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
geometry ([#443](https://codeberg.org/dnkl/foot/issues/443)).
config: bold-text-in-bright: add ‘palette-based’ as a special value When ‘bold-text-in-bright’ is set ‘to palette-based’, colors matching one of the 8 regular palette colors are brightened by using the corresponding bright palette color. Other colors, or all colors if ‘bold-text-in-bright’ is set to ‘yes|true’, are brightened by increasing the luminance.
2021-04-17 21:57:08 +02:00
* `bold-text-in-bright` may now be set to `palette-based`, in which
case it will use the corresponding bright palette color when the
color to brighten matches one of the base 8 colors, instead of
increasing the luminance
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#449](https://codeberg.org/dnkl/foot/issues/449)).
render: draw underline cursor below text underline This ensures the cursor is visible on cells where the text is underlined. Closes #415
2021-04-09 21:47:57 +02:00
changelog: add new ‘unreleased’ section
2021-03-28 14:29:55 +02:00
### Fixed
revert: input: do not include consumed modifiers in the set sent to the client There were two issues with it: * Not all applications decode the sequence into a set of modifiers + key, but use a fixed sequence -> combo mapping, that we broke. * There were unforeseen issues with e.g. F1-12, where the modifier were removed from combos like Ctrl+F12, or Alt+F12. The reason is simple; XKB tells us that Ctrl, or Alt, is a consumed modifier. Now, _why_ it thinks that is a different story. This reverts 6cd72bdee6c2b11f7cab15df9afb0ed92a7f8ba0 Closes #425
2021-03-29 20:11:32 +02:00
* Reverted _"Consumed modifiers are no longer sent to the client
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
application"_ ([#425](https://codeberg.org/dnkl/foot/issues/425)).
sixel: fix double free caused by bad free() in sixel_colors_set() sixel_color_set() is called when the number of (sixel) color registers is changed. It frees the current palette, and changes the “palette size” variable. Originally, we only had a single palette. This is the one free:d by sixel_color_set(). Later, we added support for private vs. shared palettes. With this change, we now have one palette that is “never” free:d (the shared one), and a private palette that is always free:d after a sixel has been emitted. ‘sixel.palette’ is a pointer to the palette currently in use, and should only be accessed **while emitting a sixel**. This is the pointer sixel_color_set() free:d. So for example, if ‘sixel.palette’ pointed to the shared palette, we’d free the shared palette. But, we didn’t reset ‘sixel.shared_palette’, causing a double free later on. Closes #427
2021-03-30 11:08:03 +02:00
* Crash caused by a double free originating in `XTSMGRAPHICS` - set
number of color registers
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#427](https://codeberg.org/dnkl/foot/issues/427)).
config: parse_key_binding_section(): use provided action-map Don’t call has_key_binding_collisions() with ‘binding_action_map’ unconditionally; use the provided ‘action_map’ instead. This fixes wrong error messages for key combo collisions in key binding sections other than the regular “key-bindings”.
2021-04-05 14:33:44 +02:00
* Wrong action referenced in error message for key binding collisions
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#432](https://codeberg.org/dnkl/foot/issues/432)).
changelog: don’t use a hyphen between ‘OSC’ and the number
2021-04-07 08:02:21 +02:00
* OSC 4/104 out-of-bounds accesses to the color table. This was the
changelog: move OSC-4/104 fix from 1.7.1 to ‘unreleased’
2021-04-05 22:07:58 +02:00
reason pywal turned foot windows transparent
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#434](https://codeberg.org/dnkl/foot/issues/434)).
terminal: drain PTY when client terminates This is done by: * Not limiting the number of times we try to read from the PTY when we’ve have POLLHUP * Not requiring the entire the previous read to have filled our buffer. * Not erroring out on EIO.
2021-04-07 19:09:31 +02:00
* PTY not being drained when the client application terminates.
changelog: auto_left_margin on cub1 only
2021-04-08 13:11:37 +02:00
* `auto_left_margin` not being limited to `cub1`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#441](https://codeberg.org/dnkl/foot/issues/441)).
search: find_next(): proper check for scrollback wrap around Besides disallowing matches that crosses the scrollback wrap-around, this also fixes a crash when the trying to search beyond the last output, when the scrollback history hasn’t yet been completely filled.
2021-03-28 20:59:35 +02:00
* Crash in scrollback search mode when searching beyond the last output.
revert: input: do not include consumed modifiers in the set sent to the client There were two issues with it: * Not all applications decode the sequence into a set of modifiers + key, but use a fixed sequence -> combo mapping, that we broke. * There were unforeseen issues with e.g. F1-12, where the modifier were removed from combos like Ctrl+F12, or Alt+F12. The reason is simple; XKB tells us that Ctrl, or Alt, is a consumed modifier. Now, _why_ it thinks that is a different story. This reverts 6cd72bdee6c2b11f7cab15df9afb0ed92a7f8ba0 Closes #425
2021-03-29 20:11:32 +02:00
changelog: add new ‘unreleased’ section
2021-03-28 14:29:55 +02:00
### Contributors
changelog: add cglogic to ‘contributors’
2021-04-18 20:11:27 +02:00
* [cglogic](https://codeberg.org/cglogic)
changelog: add new ‘unreleased’ section
2021-03-28 14:29:55 +02:00
changelog: prepare for 1.7.1
2021-03-28 14:25:09 +02:00
## 1.7.1
changelog: add new ‘unreleased’ section
2021-03-20 14:14:58 +01:00
### Changed
changelog: updated PGO build instructions
2021-03-26 21:00:41 +01:00
* Update PGO build instructions in `INSTALL.md`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#418](https://codeberg.org/dnkl/foot/issues/418)).
changelog: spaces matches empty cells in scrollback search mode
2021-03-27 23:02:56 +01:00
* In scrollback search mode, empty cells can now be matched by spaces.
changelog: updated PGO build instructions
2021-03-26 21:00:41 +01:00
changelog: add new ‘unreleased’ section
2021-03-20 14:14:58 +01:00
### Fixed
input: must have all required modifiers to un-shift a symbol When detecting, and repairing, “broken” key bindings (where the key binding itself explicitly lists a modifier that is consumed by the final symbol - e.g “Shift+W”), don’t just look for an intersection between the set of modifiers needed to produce the final symbol, and the modifiers listed in the key combo. Instead, check if the key combo has *all* the required modifiers. Example: Shift+AltGr+w produces Page_Down. I.e. Page_Down is the _shifted_ symbol, ‘w’ is the un-shifted symbol, and Shift+AltGr are the modifiers required to shift ‘w’ to Page_Down. If we have the key combo Shift+Page_Down, foot would, correctly, determine that Page_Down is a shifted symbol. It would find the Shift+AltGr modifier set, and since the intersection of “Shift+AltGr” and “Shift” (from our key combo) is non-empty, foot would (incorrectly) determine that we can, and should, replace Page_Down with its un-shifted symbol ‘w’. This is completely wrong, since Shift+w does _not_ produce Page_Down. Closes #407
2021-03-21 11:55:03 +01:00
* Logic that repairs invalid key bindings ended up breaking valid key
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
bindings instead ([#407](https://codeberg.org/dnkl/foot/issues/407)).
term: increase/decrease custom line-height with font size changes When the user has set a custom line-height, we now adjust it when increasing/decreasing (“zooming”) the font size at run-time. Previously, the line-height was fixed at the size specified in foot.ini.
2021-03-20 15:32:31 +01:00
* Custom `line-height` settings now scale when increasing or
decreasing the font size at run-time.
changelog: newlines incorrectly inserted into copied text
2021-03-23 14:18:04 +01:00
* Newlines sometimes incorrectly inserted into copied text
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#410](https://codeberg.org/dnkl/foot/issues/410)).
changelog: don’t crash upon receiving text-input::enter without keyboard focus
2021-03-23 14:06:10 +01:00
* Crash when compositor send `text-input-v3::enter` events without
first having sent a `keyboard::enter` event
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#411](https://codeberg.org/dnkl/foot/issues/411)).
render: draw sixels before taking the render worker lock This fixes a possible deadlock; render_sixels_images() may call render_cell(), which may need to take the worker lock (when rendering either a blinking cell, or a box drawing glyph that isn’t yet in the glyph cache).
2021-03-24 20:46:51 +01:00
* Deadlock when rendering sixel images.
changelog: sub-surface sizes not a multiple of the scaling factor
2021-03-25 09:42:15 +01:00
* URL labels, scrollback search box or scrollback position indicator
sometimes not showing up, caused by invalidly sized surface buffers
when output scaling was enabled
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#409](https://codeberg.org/dnkl/foot/issues/409)).
changelog: empty sixels resulted in non-empty images
2021-03-28 13:04:15 +02:00
* Empty sixels resulted in non-empty images.
input: must have all required modifiers to un-shift a symbol When detecting, and repairing, “broken” key bindings (where the key binding itself explicitly lists a modifier that is consumed by the final symbol - e.g “Shift+W”), don’t just look for an intersection between the set of modifiers needed to produce the final symbol, and the modifiers listed in the key combo. Instead, check if the key combo has *all* the required modifiers. Example: Shift+AltGr+w produces Page_Down. I.e. Page_Down is the _shifted_ symbol, ‘w’ is the un-shifted symbol, and Shift+AltGr are the modifiers required to shift ‘w’ to Page_Down. If we have the key combo Shift+Page_Down, foot would, correctly, determine that Page_Down is a shifted symbol. It would find the Shift+AltGr modifier set, and since the intersection of “Shift+AltGr” and “Shift” (from our key combo) is non-empty, foot would (incorrectly) determine that we can, and should, replace Page_Down with its un-shifted symbol ‘w’. This is completely wrong, since Shift+w does _not_ produce Page_Down. Closes #407
2021-03-21 11:55:03 +01:00
changelog: 1.7.0
2021-03-20 14:02:12 +01:00
## 1.7.0
changelog: add new ‘unreleased’ section
2020-12-18 15:02:08 +01:00
### Added
config: add optional ‘center’ argument to ‘pad’ When set, the grid contents is centered in the window. I.e. the left/right and top/bottom margins are equal (+- 1px). This causes the content to “jump” while doing an interactive resize, but may still be preferred in e.g. a tiling WM. Closes #273
2021-01-06 11:17:29 +01:00
* The `pad` option now accepts an optional third argument, `center`
(e.g. `pad=5x5 center`), causing the grid to be centered in the
window, with equal amount of padding of the left/right and
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
top/bottom side ([#273](https://codeberg.org/dnkl/foot/issues/273)).
changelog: move line-height entry from ‘changed’ to ‘added’
2021-01-11 09:30:08 +01:00
* `line-height`, `letter-spacing`, `horizontal-letter-offset` and
`vertical-letter-offset` to `foot.ini`. These options let you tweak
cell size and glyph positioning
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#244](https://codeberg.org/dnkl/foot/issues/244)).
config: add ‘select-extend-character-wise’ bind action This forces the (new) selection mode to be character-wise when extending a word- or line-wise selection. Default key binding is ctrl+RMB.
2021-01-06 11:11:46 +01:00
* Key/mouse binding `select-extend-character-wise`, which forces the
selection mode to 'character-wise' when extending a selection.
csi: implement DECSET 47 - use alternate screen buffer
2021-01-16 13:34:40 +01:00
* `DECSET` `47`, `1047` and `1048`.
changelog: OSC-8 support
2021-02-21 20:16:25 +01:00
* URL detection and OSC-8 support. URLs are highlighted and activated
using the keyboard (**no** mouse support). See **foot**(1)::URLs, or
changelog: URL mode
2021-02-07 11:42:41 +01:00
[README.md](README.md#urls) for details
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#14](https://codeberg.org/dnkl/foot/issues/14)).
changelog: -d,--log-level
2021-02-09 21:20:18 +01:00
* `-d,--log-level={info|warning|error}` to both `foot` and
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
`footclient` ([#337](https://codeberg.org/dnkl/foot/issues/337)).
changelog: -D,--working-directory=DIR
2021-02-12 09:48:32 +01:00
* `-D,--working-directory=DIR` to both `foot` and `footclient`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#347](https://codeberg.org/dnkl/foot/issues/347))
sixel: implement private mode 80 - sixel scrolling When enabled (the default), sixels behave much like normal output; the start where the cursor is, and the cursor moves with the sixel. I.e. after emitting a sixel the cursor is left after the image; either to the right, if private mode 8452 is enabled, or otherwise on the next line. Terminal content is scrolled up if the sixel is larger than the screen. When disabled, sixels *always* start at (0,0), the cursor never moves, and the terminal content never scrolls. In other words, the ‘disabled’ mode is a much simpler mode. All we need to do to support both modes is re-write the sixel-emitting loop to: * break early if we’re “out of rows”, i.e. we’ve reached the bottom of the screen. * not linefeed, or move the cursor when scrolling is disabled This patch also fixes a bug in the (new) implementation of private mode 8452. When emitting a sixel, we may break it up into smaller pieces, to ensure a single sixel (as tracked internally) does not cross the scrollback wrap-around. The code that checked if we should do a linefeed or not, would skip the linefeed on the last row of *each* such sixel piece. The correct thing to do is to skip it only on the last row of the *last* piece. I chose not to fix this bug in a separate patch since doing so would have meant re-writing it again when implementing private mode 80.
2021-02-26 09:28:03 +01:00
* `DECSET 80` - sixel scrolling
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#361](https://codeberg.org/dnkl/foot/issues/361)).
sixel: implement private mode 1070 - private color palette When enabled (the default), sixels use private color registers. That is, the color palette from the last sixel is *not* re-used. When disabled, sixels share (i.e. re-use) the same color palette. Closes #362
2021-02-16 19:37:49 +01:00
* `DECSET 1070` - sixel private color palette
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#362](https://codeberg.org/dnkl/foot/issues/362)).
sixel: implement private mode 8452 - cursor positioning after sixel When disabled (the default), the cursor is positioned on a new line after emitting a sixel image. When enabled, the cursor is positioned to the right of the sixel image. Closes #363
2021-02-16 19:11:38 +01:00
* `DECSET 8452` - position cursor to the right of sixels
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#363](https://codeberg.org/dnkl/foot/issues/363)).
changelog: change "control- and escape sequences" to "escape sequences" According to the way ECMA-48 defines these terms, "escape sequences" are a superset of "control sequences", so there's no real reason to mention both.
2021-02-23 19:58:26 +00:00
* Man page **foot-ctlseqs**(7), documenting all supported escape
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
sequences ([#235](https://codeberg.org/dnkl/foot/issues/235)).
changelog: implemented DCS parameter P2
2021-03-11 17:37:56 +01:00
* Support for transparent sixels (DCS parameter `P2=1`)
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#391](https://codeberg.org/dnkl/foot/issues/391)).
add changelog entry, completions and man entry for -N, --no-wait
2021-03-13 07:49:57 -03:00
* `-N,--no-wait` to `footclient`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#395](https://codeberg.org/dnkl/foot/issues/395)).
Add: Bash completion for foot and footclient * use toe for terminfo, thanks Craig. * adds optional dependency on bash-completion for positional arguments Co-authored-by: Craig Barnes <craigbarnes@protonmail.com>
2021-03-13 19:04:33 +01:00
* Completions for Bash shell
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#10](https://codeberg.org/dnkl/foot/issues/10)).
csi: implement XTVERSION (CSI > 0q) This is a fairly new XTerm extension. The reply is on the format: DCS > | text ST XTerm replies with ‘text’ = “XTerm(366)”. Foot replies with ‘text’ = “foot(1.6.4)” Closes #359
2021-02-16 12:00:58 +01:00
* Implement `XTVERSION` (`CSI > 0q`). Foot will reply with
`DCS>|foot(<major>.<minor>.<patch>)ST`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#359](https://codeberg.org/dnkl/foot/issues/359)).
Merge branch 'releases/1.6'
2021-01-29 20:12:32 +01:00
config: add optional ‘center’ argument to ‘pad’ When set, the grid contents is centered in the window. I.e. the left/right and top/bottom margins are equal (+- 1px). This causes the content to “jump” while doing an interactive resize, but may still be preferred in e.g. a tiling WM. Closes #273
2021-01-06 11:17:29 +01:00
changelog: add new ‘unreleased’ section
2020-12-18 15:02:08 +01:00
### Changed
meson: use wrap files for fcft/tllist subprojects See: https://mesonbuild.com/Wrap-dependency-system-manual.html
2020-12-19 22:43:09 +00:00
* The fcft and tllist library subprojects are now handled via Meson
[wrap files](https://mesonbuild.com/Wrap-dependency-system-manual.html)
instead of needing to be manually cloned.
changelog: box drawing characters are rendered by foot
2021-01-01 21:08:57 +01:00
* Box drawing characters are now rendered by foot, instead of using
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
font glyphs ([#198](https://codeberg.org/dnkl/foot/issues/198))
changelog: double- or triple clicking then dragging extends word- or line-wise
2021-01-02 21:28:55 +01:00
* Double- or triple clicking then dragging now extends the selection
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
word- or line-wise ([#267](https://codeberg.org/dnkl/foot/issues/267)).
changelog: box drawing line thickness depend on the font size
2021-01-12 17:38:12 +01:00
* The line thickness of box drawing characters now depend on the font
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
size ([#281](https://codeberg.org/dnkl/foot/issues/281)).
config: add ‘select-extend-character-wise’ bind action This forces the (new) selection mode to be character-wise when extending a word- or line-wise selection. Default key binding is ctrl+RMB.
2021-01-06 11:11:46 +01:00
* Extending a word/line-wise selection now uses the original selection
mode instead of switching to character-wise.
changelog: tiocswinsz is now delayed by 100ms while doing an interactive resize
2021-01-20 18:10:24 +01:00
* While doing an interactive resize of a foot window, foot now
requires 100ms of idle time (where the window size does not change)
before sending the new dimensions to the client application. The
timing can be tweaked, or completely disabled, by setting
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
`resize-delay-ms` ([#301](https://codeberg.org/dnkl/foot/issues/301)).
csi: ‘CSI 13 ; 2 t’ reply is now (0,0) Foot previously responded with window local coordinates. But, XTerm responds with screen *absolute* coordinates. This isn’t possible under Wayland, thus we now report (0,0) instead. Same as we do for ‘CSI 13 ; 0 t’.
2021-02-16 14:31:46 +01:00
* `CSI 13 ; 2 t` now reports (0,0).
changelog: new key binding matching logic
2021-03-04 10:12:39 +01:00
* Key binding matching logic; key combinations like `Control+Shift+C`
**must** now be written as either `Control+C` or `Control+Shift+c`,
the latter being the preferred
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
variant. ([#376](https://codeberg.org/dnkl/foot/issues/376))
input: do not include consumed modifiers in the set sent to the client When sending a key escape sequence to the client application, do not include consumed modifiers. Fixes part of #376
2021-02-26 20:54:42 +01:00
* Consumed modifiers are no longer sent to the client application
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#376](https://codeberg.org/dnkl/foot/issues/376)).
meson: bump minimum xkbcommon version to 1.0.0 This requirement is due to the recently added maybe_repair_key_combo() function, which is making use of xkb_keymap_key_get_mods_for_level(). See also: commit a5b554761a8b376657be2a7e613b37fd5803920c.
2021-03-07 19:28:17 +00:00
* The minimum version requirement for the libxkbcommon dependency is
now 1.0.0.
changelog: empty pixel rows at the bottom of a sixel is now trimmed
2021-03-11 17:32:38 +01:00
* Empty pixel rows at the bottom of a sixel is now trimmed.
changelog: implemented DCS parameter P2
2021-03-11 17:37:56 +01:00
* Sixels with DCS parameter `P2=0|2` now use the _current_ ANSI
background color for empty pixels instead of the default background
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
color ([#391](https://codeberg.org/dnkl/foot/issues/391)).
changelog: sixel decoding performance improvements
2021-03-12 21:43:35 +01:00
* Sixel decoding optimized; up to 100% faster in some cases.
sixel: max geometry should be max geometry, not current window size “current geometry” will report whatever value is the smallest; the max geometry or the current window size. But “max geometry” always returns the configured max geometry. This aligns foot’s behavior with XTerm.
2021-03-14 10:58:13 +01:00
* Reported sixel “max geometry” from current window size, to the
configured maximum size (defaulting to 10000x10000).
csi: ‘CSI 13 ; 2 t’ reply is now (0,0) Foot previously responded with window local coordinates. But, XTerm responds with screen *absolute* coordinates. This isn’t possible under Wayland, thus we now report (0,0) instead. Same as we do for ‘CSI 13 ; 0 t’.
2021-02-16 14:31:46 +01:00
changelog: update ‘contributors’
2020-12-20 15:42:32 +01:00
Merge branch 'releases/1.6'
2020-12-20 15:51:04 +01:00
### Removed
main: remove deprecated "--geometry" option Closes #287
2021-01-13 19:59:54 +00:00
changelog: use standard signals for SIGCHLD
2021-02-11 19:54:55 +01:00
* The `-g,--geometry` command-line option (which had been deprecated
and superseded by `-w,--window-size-pixels` since 1.5.0).
main: remove deprecated "--geometry" option Closes #287
2021-01-13 19:59:54 +00:00
Merge branch 'releases/1.6'
2021-01-29 20:12:32 +01:00
### Fixed
changelog: some mouse events never being sent to the client application
2021-02-02 09:53:24 +01:00
* Some mouse bindings (_primary paste_, for example) did not require
`shift` to be pressed while used in a mouse grabbing
application. This meant the mouse event was never seen by the
application.
spawn/slave: restore signal mask after fork slave: no need to restore signal handlers; they are automatically restored as long as they are not SIG_IGN (which they never are in foot). spawn(): restore signal mask after fork. This fixes an issue where a terminal spawned with ctrl+shift+n did not terminate when its shell exited. Closes #366
2021-02-21 11:57:38 +01:00
* Terminals spawned with `ctrl`+`shift`+`n` not terminating when
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
exiting shell ([#366](https://codeberg.org/dnkl/foot/issues/366)).
changelog: default value of -t,--term in --help when built without terminfo
2021-02-26 15:16:42 +01:00
* Default value of `-t,--term` in `--help` output when foot was built
without terminfo support.
term: don’t close PTY when client application dies Closing it as soon as we detect that the client has died, means we may not have drained it completely. The PTY is either closed _by_ the client application, or by us when we shutdown the terminal. Thus, leaving it open (until we call term_shutdown()) is fine.
2021-03-12 22:06:50 +01:00
* Drain PTY when the client application terminates.
changelog: some mouse events never being sent to the client application
2021-02-02 09:53:24 +01:00
Merge branch 'releases/1.6'
2021-01-29 20:12:32 +01:00
### Contributors
* [craigbarnes](https://codeberg.org/craigbarnes)
changelog: default value of -t,--term in --help when built without terminfo
2021-02-26 15:16:42 +01:00
* toast
Mention fix in Changelog.
2021-03-01 20:26:56 +01:00
* [l3mon4d3](https://codeberg.org/l3mon4d3)
Add: Bash completion for foot and footclient * use toe for terminfo, thanks Craig. * adds optional dependency on bash-completion for positional arguments Co-authored-by: Craig Barnes <craigbarnes@protonmail.com>
2021-03-13 19:04:33 +01:00
* [Simon Schricker](mailto:s.schricker@sillage.at)
Merge branch 'releases/1.6'
2021-02-12 21:41:53 +01:00
changelog: add section for 1.6.4
2021-02-12 10:44:42 +01:00
## 1.6.4
changelog: prepare for 1.6.4
2021-02-12 21:27:15 +01:00
changelog: add section for 1.6.4
2021-02-12 10:44:42 +01:00
### Added
changelog: selection-target=none|primary|clipboard|both
2021-01-16 15:44:51 +01:00
* `selection-target=none|primary|clipboard|both` to `foot.ini`. It can
be used to configure which clipboard(s) selected text should be
copied to. The default is `primary`, which corresponds to the
behavior in older foot releases
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#288](https://codeberg.org/dnkl/foot/issues/288)).
changelog: selection-target=none|primary|clipboard|both
2021-01-16 15:44:51 +01:00
changelog: add section for 1.6.4
2021-02-12 10:44:42 +01:00
### Changed
ime: Reset terminal's IME state on text_input.leave To reproduce issue: - Launch an IME from inside foot - Type in some preedit text - Use Ctrl-C to close the IME - IME text stays in terminal until focus is changed
2021-01-29 12:57:03 -07:00
* The IME state no longer stays stuck in the terminal if the IME goes
away during preedit.
changelog: -Dterminfo changed from boolean to feature option
2021-02-09 19:44:57 +01:00
* `-Dterminfo` changed from a `boolean` to a `feature` option.
changelog: use standard signals for SIGCHLD
2021-02-11 19:54:55 +01:00
* Use standard signals instead of a signalfd to handle
`SIGCHLD`. Fixes an issue on FreeBSD where foot did not detect when
the client application had terminated.
ime: Reset terminal's IME state on text_input.leave To reproduce issue: - Launch an IME from inside foot - Type in some preedit text - Use Ctrl-C to close the IME - IME text stays in terminal until focus is changed
2021-01-29 12:57:03 -07:00
changelog: add section for 1.6.4
2021-02-12 10:44:42 +01:00
### Fixed
selection: don’t strip formatting C0 control characters in bracketed paste mode It’s ok to let the receiving end handle formatting C0 control characters in bracketed paste mode. In fact, we *must* let them through. Otherwise it is impossible to paste e.g. tabs into editors and similar applications.
2021-02-12 10:03:01 +01:00
* `BS`, `HT` and `DEL` from being stripped in bracketed paste mode.
changelog: add section for 1.6.4
2021-02-12 10:44:42 +01:00
### Contributors
ime: Reset terminal's IME state on text_input.leave To reproduce issue: - Launch an IME from inside foot - Type in some preedit text - Use Ctrl-C to close the IME - IME text stays in terminal until focus is changed
2021-01-29 12:57:03 -07:00
* [tdeo](https://codeberg.org/tdeo)
changelog: -Dterminfo changed from boolean to feature option
2021-02-09 19:44:57 +01:00
* jbeich
Merge branch 'releases/1.6'
2021-01-29 20:12:32 +01:00
changelog: add empty 1.6.3 section
2021-01-21 11:43:22 +01:00
## 1.6.3
changelog: prepare for 1.6.3
2021-01-29 19:52:27 +01:00
changelog: add empty 1.6.3 section
2021-01-21 11:43:22 +01:00
### Added
Add fish completion
2021-01-07 22:21:07 +03:00
* Completions for fish shell
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#11](https://codeberg.org/dnkl/foot/issues/11))
* FreeBSD support ([#238](https://codeberg.org/dnkl/foot/issues/238)).
Send text_input_rectangle requests for text-input
2020-12-20 15:01:21 -07:00
* IME popup location support: foot now sends the location of the cursor
so any popup can be displayed near the text that is being typed.
Add fish completion
2021-01-07 22:21:07 +03:00
changelog: add empty 1.6.3 section
2021-01-21 11:43:22 +01:00
### Changed
Require trailing comment to be preceded by a space or tab Fixes `word-delimiters` option to not ignore `#` and subsequent characters. Closes #270
2021-01-03 14:08:25 -05:00
* Trailing comments in `foot.ini` must now be preceded by a space or tab
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#270](https://codeberg.org/dnkl/foot/issues/270))
changelog: search input box no longer accepts non-printables
2021-01-24 11:33:59 +01:00
* The scrollback search box no longer accepts non-printable characters.
selection: strip non-formatting C0, BS, HT and DEL from pasted text
2021-01-23 11:22:22 +01:00
* Non-formatting C0 control characters, `BS`, `HT` and `DEL` are now
stripped from pasted text.
Require trailing comment to be preceded by a space or tab Fixes `word-delimiters` option to not ignore `#` and subsequent characters. Closes #270
2021-01-03 14:08:25 -05:00
Merge branch 'releases/1.6'
2020-12-20 15:51:04 +01:00
### Fixed
terminal: shutdown (or --hold) when the client process terminates 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.
2020-12-26 01:29:40 +01:00
* Exit when the client application terminates, not when the TTY file
descriptor is closed.
ime: don’t call text-input functions when it isn’t available Closes #259
2020-12-25 22:04:19 +01:00
* Crash on compositors not implementing the _text input_ interface
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#259](https://codeberg.org/dnkl/foot/issues/259)).
render: mark cell overflowed into as dirty When tweak.allow-overflowing-double-width-glyphs=yes, then certain glyphs are allowed to overflow into the neighbouring cell. However, if the cell “owning” the double-width glyph is erased (_only_ that cell), then the cell overflowed into is not redrawn, causing part of the double-width glyph to remain on screen. To avoid checking for these glyphs when printing to the terminal (i.e at parse time), simply mark both cells as dirty when we render the overflowing glyph. Yes, this means that the cells will always be re-rendered. We count on them only making up a small portion of the screen.
2021-01-02 22:24:49 +01:00
* Erased, overflowing glyphs (when
`tweak.allow-overflowing-double-width-glyphs=yes` - the default) not
properly erasing the cell overflowed **into**.
Require trailing comment to be preceded by a space or tab Fixes `word-delimiters` option to not ignore `#` and subsequent characters. Closes #270
2021-01-03 14:08:25 -05:00
* `word-delimiters` option ignores `#` and subsequent characters
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#270](https://codeberg.org/dnkl/foot/issues/270))
render: draw combining characters on top of colored bitmap glyphs (emoji)
2021-01-04 18:32:55 +01:00
* Combining characters not being rendered when composed with colored
changelog: glyhps -> glyphs
2021-01-11 09:35:01 +01:00
bitmap glyphs (i.e. colored emojis).
changelog: add hyphen between ‘newline’ and ‘terminated’
2021-01-12 14:55:21 +01:00
* Pasting URIs from the clipboard when the source has not
newline-terminated the last URI
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#291](https://codeberg.org/dnkl/foot/issues/291)).
sixel: current geometry: don’t exceed current window dimensions This is similar to what XTerm does, and fixes an issue with lsix, where the output did not wrap.
2021-01-14 14:41:34 +01:00
* Sixel “current geometry” query response not being bounded by the
current window dimensions (fixes `lsix` output)
input: don’t enable keyboard repeat timer when repeat rate is zero wayland-client-protocol.h: Negative values for either rate or delay are illegal. A rate of zero will disable any repeating (regardless of the value of delay). This fixes a division-by-zero crash.
2021-01-16 12:27:58 +01:00
* Crash on keyboard input when repeat rate was zero (i.e. no repeat).
terminal: fix encoding of mouse buttons 6 and 7 in mouse events 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).
2021-01-22 17:03:43 +01:00
* Wrong button encoding of mouse buttons 6 and 7 in mouse events.
search: fix matching against composed characters
2021-01-24 12:02:20 +01:00
* Scrollback search not matching composed characters.
changelog: high cpu usage while holding down e.g. arrow keys in search mode
2021-01-25 10:05:51 +01:00
* High CPU usage when holding down e.g. arrow keys while in scrollback
search mode.
search: ad-hoc workaround for combining characters with positive x-offsets When rendering the search input box, do the same ad-hoc workaround for combining characters with a positive x-offset as we do when rendering normal grid cells. In this case, we don’t *know* when we’re dealing with combining characters. But we can detect zero-width characters. For these, check their glyph’s x-offset. If positive, adjust it like we do when rendering combining glyphs in the main grid, to ensure the glyph is positioned over the _previous_ character, not the next.
2021-01-25 10:00:43 +01:00
* Rendering of composed characters in the scrollback search box.
ime: fix rendering of pre-edit cursor when positioned after the pre-edit string We failed to convert the byte-indices to cell indices, resulting in a box cursor covering the entire pre-edit string. Note that in addition to fixing the translation from byte index to cell index, the rendered had to be updated to dirty one extra cell from the original grid. Without this, we left trailing cursors behind us when the user deleted text from the pre-edit string.
2021-01-25 21:57:42 +01:00
* IME pre-edit cursor when positioned at the end of the pre-edit
string.
search: fix matching of multi-column characters We were matching the sub-sequence SPACERs as if they were regular characters, which obviously failed.
2021-01-26 20:05:14 +01:00
* Scrollback search not matching multi-column characters.
terminal: shutdown (or --hold) when the client process terminates 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.
2020-12-26 01:29:40 +01:00
Merge branch 'releases/1.6'
2020-12-20 15:51:04 +01:00
### Contributors
Add myself to Contributors
2021-01-03 15:49:24 -05:00
* [pc](https://codeberg.org/pc)
Add fish completion
2021-01-07 22:21:07 +03:00
* [FollieHiyuki](https://codeberg.org/FollieHiyuki)
changelog: freebsd support
2021-01-23 10:12:39 +01:00
* jbeich
Send text_input_rectangle requests for text-input
2020-12-20 15:01:21 -07:00
* [tdeo](https://codeberg.org/tdeo)
Merge branch 'releases/1.6'
2020-12-20 15:51:04 +01:00
meson/pkgbuild: bump version to 1.6.2
2020-12-21 15:58:25 +01:00
## 1.6.2
### Fixed
* Version number in `meson.build`.
Merge branch 'releases/1.6'
2020-12-20 15:51:04 +01:00
## 1.6.1
changelog: add 1.6.1 section
2020-12-20 15:46:05 +01:00
### Added
changelog: mention --seed in in generate-alt-random.pu
2020-12-21 13:47:45 +01:00
* `--seed` to `generate-alt-random.py`, enabling deterministic PGO
builds.
changelog: add 1.6.1 section
2020-12-20 15:46:05 +01:00
### Changed
changelog: use -std=c11 instead of -std=c18
2020-12-21 12:20:08 +01:00
Merge branch 'releases/1.6'
2020-12-21 13:55:19 +01:00
changelog: use -std=c11 instead of -std=c18
2020-12-21 12:20:08 +01:00
* Use `-std=c11` instead of `-std=c18`.
changelog: mention -Wno-profile-instr-unprofiled
2020-12-21 13:50:06 +01:00
* Added `-Wno-profile-instr-unprofiled` to Clang cflags in PGO builds
([INSTALL.md](https://codeberg.org/dnkl/foot/src/branch/releases/1.6/INSTALL.md#user-content-performance-optimized-pgo))
changelog: use -std=c11 instead of -std=c18
2020-12-21 12:20:08 +01:00
changelog: add new ‘unreleased’ section
2020-12-18 15:02:08 +01:00
### Fixed
changelog: mention meson dependency fix
2020-12-20 11:56:18 +01:00
* Missing dependencies in meson, causing heavily parallelized builds
to fail.
render: fix rounding error when calculating background color with alpha We use pre-multiplied alpha color channels, but were having bad rounding errors due to the alpha divider being truncated to an integer. The algorithm for pre-multiplying a color channel is: alpha_divider = 0xffff / alpha pre_mult_color = color / alpha_divider In order to fix the rounding errors, we could turn ‘alpha_divider’ into a double. That however would introduce a performance penalty since now we’d need to do floating point math for each cell. The algorithm can be trivially converted to: pre_mult_color = color * alpha / 0xffff Since both color and alpa values are < 65536, the multiplication is “safe”; it will not overflow an uint32_t. Closes #249
2020-12-20 12:25:12 +01:00
* Background color when alpha < 1.0 being wrong
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#249](https://codeberg.org/dnkl/foot/issues/249)).
generate-alt-random: ioctl(TIOCGWINSZ) may fail in run inside a container This _should_ only happen when we’re doing a partial PGO build, since then the script is run in the parent terminal. In this case, the user is expected to use --rows/--cols anyway.
2020-12-21 13:40:53 +01:00
* `generate-alt-random.py` failing in containers.
changelog: mention meson dependency fix
2020-12-20 11:56:18 +01:00
changelog: add new ‘unreleased’ section
2020-12-18 15:02:08 +01:00
### Contributors
meson: use wrap files for fcft/tllist subprojects See: https://mesonbuild.com/Wrap-dependency-system-manual.html
2020-12-19 22:43:09 +00:00
* [craigbarnes](https://codeberg.org/craigbarnes)
changelog: update ‘contributors’
2020-12-20 15:42:32 +01:00
* [sterni](https://codeberg.org/sterni)
meson: use wrap files for fcft/tllist subprojects See: https://mesonbuild.com/Wrap-dependency-system-manual.html
2020-12-19 22:43:09 +00:00
changelog: add new ‘unreleased’ section
2020-12-18 15:02:08 +01:00
changelog: prepare for 1.6.0
2020-12-18 14:51:34 +01:00
## 1.6.0
changelog: add note about PGO without Wayland
2020-11-22 12:18:22 +01:00
### For packagers
Starting with this release, foot can be PGO:d (compiled using profile
guided optimizations) **without** a running Wayland session. This
means foot can be PGO:d in e.g. sandboxed build scripts. See
changelog: update link to install instructions for PGO
2020-11-22 19:03:41 +01:00
[INSTALL.md](INSTALL.md#user-content-performance-optimized-pgo).
changelog: add note about PGO without Wayland
2020-11-22 12:18:22 +01:00
changelog: add new ‘unreleased’ section
2020-09-18 21:29:39 +02:00
### Added
changelog: reverse auto-wrap
2020-10-02 21:44:03 +02:00
changelog: ime: add link to INSTALL.md
2020-12-05 11:09:05 +01:00
* IME support. This is compile-time optional, see
[INSTALL.md](INSTALL.md#user-content-options)
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#134](https://codeberg.org/dnkl/foot/issues/134)).
changelog: add missing space in escape sequence
2020-12-08 20:31:22 +01:00
* `DECSET` escape to enable/disable IME: `CSI ? 737769 h` enables IME
changelog: don’t repeat ‘IME’
2020-12-08 20:31:48 +01:00
and `CSI ? 737769 l` disables it. This can be used to
changelog: consistently use ‘CSI ? X h/l’ instead of `\E[?Xh/l`
2020-12-08 20:29:44 +01:00
e.g. enable/disable IME when entering/leaving insert mode in vim.
changelog: move entry for dpi-aware up, to make it more visible
2020-12-18 14:46:56 +01:00
* `dpi-aware` option to `foot.ini`. The default, `auto`, sizes fonts
using the monitor’s DPI when output scaling has been
**disabled**. If output scaling has been **enabled**, fonts are
sized using the scaling factor. DPI-only font sizing can be forced
by setting `dpi-aware=yes`. Setting `dpi-aware=no` forces font
sizing to be based on the scaling factor.
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#206](https://codeberg.org/dnkl/foot/issues/206)).
term: enable reverse wrap-around by default Since we’re now doing reverse auto-wrapping by default, we add ‘bw’ (‘auto_left_margin’)to terminfo.
2020-10-06 18:42:26 +02:00
* Implement reverse auto-wrap (_auto\_left\_margin_, _bw_, in
terminfo). This mode can be enabled/disabled with `CSI ? 45 h` and
changelog: fix CSI escape sequence
2020-10-08 19:52:10 +02:00
`CSI ? 45 l`. It is **enabled** by default
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#150](https://codeberg.org/dnkl/foot/issues/150)).
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `bell` option to `foot.ini`. Can be set to `set-urgency` to make
bell: optionally render margins in red when receiving BEL Add anew config option, ‘bell=none|set-urgency’. When set to ‘set-urgency’, the margins will be painted in red (if the window did not have keyboard focus). This is intended as a cheap replacement for the ‘urgency’ hint, that doesn’t (yet) exist on Wayland. Closes #157
2020-10-08 19:55:32 +02:00
foot render the margins in red when receiving `BEL` while **not**
csi: implement ‘CSI ? 1042 h/l’ - enable/disable bell-is-urgent
2020-10-11 17:44:29 +02:00
having keyboard focus. Applications can dynamically enable/disable
this with the `CSI ? 1042 h` and `CSI ? 1042 l` escape
sequences. Note that Wayland does **not** implement an _urgency_
hint like X11, but that there is a
bell: optionally render margins in red when receiving BEL Add anew config option, ‘bell=none|set-urgency’. When set to ‘set-urgency’, the margins will be painted in red (if the window did not have keyboard focus). This is intended as a cheap replacement for the ‘urgency’ hint, that doesn’t (yet) exist on Wayland. Closes #157
2020-10-08 19:55:32 +02:00
[proposal](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/9)
to add support for this. The value `set-urgency` was chosen for
forward-compatibility, in the hopes that this proposal eventualizes
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#157](https://codeberg.org/dnkl/foot/issues/157)).
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `bell` option can also be set to `notify`, in which case a desktop
changelog: group ‘bell’ entries together
2020-12-16 10:32:21 +01:00
notification is emitted when foot receives `BEL` in an unfocused
window.
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `word-delimiters` option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#156](https://codeberg.org/dnkl/foot/issues/156)).
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `csd.preferred` can now be set to `none` to disable window
changelog: move ‘csd.preferred=none’ from ‘changed’ to ‘added’
2020-10-11 19:04:21 +02:00
decorations. Note that some compositors will render SSDs despite
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
this option being used ([#163](https://codeberg.org/dnkl/foot/issues/163)).
changelog: auto-scroll while selecting
2020-10-11 18:19:38 +02:00
* Terminal content is now auto-scrolled when moving the mouse above or
below the window while selecting
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#149](https://codeberg.org/dnkl/foot/issues/149)).
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `font-bold`, `font-italic` `font-bold-italic` options to
config: add font-bold, font-italic and font-bold-italic options These options lets the user configure custom fonts and styles, to use with the bold and italic cell attributes. By default, they are unset, meaning we use the bold/italic variants of the regular font. Closes #169.
2020-10-20 21:04:47 +02:00
`foot.ini`. These options allow custom bold/italic fonts. They are
unset by default, meaning the bold/italic version of the regular
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
font is used ([#169](https://codeberg.org/dnkl/foot/issues/169)).
selection: implement support for drag-and-drop We accept COPY and MOVE actions, for text/plain;charset=utf-8 mime-types. To implement DnD, we need to track the current DnD data offer *and* the terminal instance it is (currently) targeting. To do this, a seat has a new member, ‘dnd_term’. On a DnD enter event, we lookup the corresponding terminal instance and point ‘dnd_term’ to it. On a DnD leave event, ‘dnd_term’ is reset. The DnD data offer is tracked in the terminal’s wayland window instance. It is reset, along with the seat’s ‘dnd_term’ on a DnD leave event. On a drop event, we immediately clear the seat’s ‘dnd_term’, to ensure we don’t reset it, or destroy the offer before the drop has been completed. The drop’s ‘done()’ callback takes care of destroying and resetting the DnD offer in the terminal’s wayland window instance. Closes #175
2020-10-26 21:02:53 +01:00
* Drag & drop support; text, files and URLs can now be dropped in a
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
foot terminal window ([#175](https://codeberg.org/dnkl/foot/issues/175)).
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `clipboard-paste` and `primary-paste` scrollback search bindings. By
default, they are bound to `ctrl+v ctrl+y` and `shift+insert`
respectively, and lets you paste from the clipboard or primary
selection into the search buffer.
* Support for `pipe-*` actions in mouse bindings. It was previously
changelog: move pipe-* actions from ‘fixed’ to ‘added’
2020-11-13 23:26:03 +01:00
not possible to add a command to these actions when used in mouse
bindings, making them useless
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#183](https://codeberg.org/dnkl/foot/issues/183)).
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `bold-text-in-bright` option to `foot.ini`. When enabled, bold text
is rendered in a brighter color
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#199](https://codeberg.org/dnkl/foot/issues/199)).
client: add new "--window-size-*" options to docs and CHANGELOG.md
2020-11-22 18:36:37 +00:00
* `-w,--window-size-pixels` and `-W,--window-size-chars` command line
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
options to `footclient` ([#189](https://codeberg.org/dnkl/foot/issues/189)).
foot/footclient: add short options to all command line options e81388336750a20a2da98a57e9726c8ba1b481e3 added “missing” short command line options to footclient. Except they weren’t missing; they were intentionally missing short options and only supported long options. This commit makes the new/missing short options “official”, by adding documentation, zsh completions and including them in usage().
2020-11-23 19:19:19 +01:00
* Short command line options for `--title`, `--maximized`,
`--fullscreen`, `--login-shell`, `--hold` and `--check-config`.
changelog: DECSET 27127 - modifies Esc to send \E[27127~ instead of \E
2020-12-07 20:43:32 +01:00
* `DECSET` escape to modify the `escape` key to send `\E[27;1;27~`
changelog: consistently use ‘CSI ? X h/l’ instead of `\E[?Xh/l`
2020-12-08 20:29:44 +01:00
instead of `\E`: `CSI ? 27127 h` enables the new behavior, `CSI ?
27127 l` disables it (the default).
osc: implement urxvt’s “OSC 777;notify” OSC 777 is URxvt’s generic escape to send commands to its perl extensions. The first parameter is the name of the extension, followed by its arguments. OSC 777;notify is a, if not well established, at least a fairly well known escape sequence to request a (desktop) notification. The syntax is: \e]777;notify;<title>;<body>\e\\ Neither title nor body is escaped in any way, meaning they should not contain a ‘;’. Foot will split title from body at the *first* ‘;’. Any remaining ‘;’ characters are treated as part of ‘body’. Instead of adding built-in support for the freedesktop notification specification (which would require us to link against at least dbus), add a new config option to foot.ini: ‘notify’. This option specifies the command to execute when a notification is received. ‘${title}’ and ‘${body}’ can be used anywhere, in any combination, and as many times as you want, in any of the command arguments. The default value is ‘notify-send -a foot -i foot ${title} ${body}’
2020-12-08 19:19:55 +01:00
* OSC 777;notify: desktop notifications. Use in combination with the
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
new `notify` option in `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#224](https://codeberg.org/dnkl/foot/issues/224)).
terminfo: add status line capabilities: hs, dsl, fsl and tsl * hs - boolean, signals status line availability * tsl - to_status_line: begin an OSC 2 sequence (set window title) * fsl - from_status_line: OSC terminator * dsl - disable status line: \E]2;\E\\ - clears the window title Closes #242
2020-12-18 13:46:57 +01:00
* Status line terminfo capabilities `hs`, `tsl`, `fsl` and `dsl`. This
enables e.g. vim to set the window title
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#242](https://codeberg.org/dnkl/foot/issues/242)).
changelog: reverse auto-wrap
2020-10-02 21:44:03 +02:00
Merge branch 'releases/1.5' into master
2020-10-11 19:36:00 +02:00
### Changed
render: blink switches between foreground and dimmed foreground
2020-10-22 18:41:47 +02:00
* Blinking text now uses the foreground color, but dimmed down in its
off state, instead of the background color.
sixel: change default max size to 10000x10000 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.
2020-11-23 20:10:55 +01:00
* Sixel default maximum size is now 10000x10000 instead of the current
window size.
resize: don’t reflow text on alt screen Alt screen applications normally reflow/readjust themselves on a window resize. When we do it too, the result is graphical glitches/flashes since our re-flowed text is rendered in one frame, and the application re-flowed text soon thereafter. We can’t avoid rendering some kind of re-flowed frame, since we don’t know when, or even if, the application will update itself. To avoid glitches, we need to render, as closely as possible, what the application itself will render shortly. This is actually pretty simple; we just need to copy the visible content over from the old grid to the new grid. We don’t bother with text re-flow, but simply truncate long lines. To simplify things, we simply cancel any active selection (since often times, it will be corrupted anyway when the application redraws itself). Since we’re not reflowing text, there’s no need to translate e.g. the cursor position - we just keep the current position (but bounded to the new dimensions). Fun thing: ‘less’ gets corrupted if we don’t leave the cursor at the (new) bottom row. To handle this, we check if the cursor (before resize) is at the bottom row, and if so, we move it to the new bottom row. Closes #221
2020-11-24 19:00:57 +01:00
* Graphical glitches/flashes when resizing the window while running a
fullscreen application, i.e. the 'alt' screen
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#221](https://codeberg.org/dnkl/foot/issues/221)).
term: split cursor blink state into two There are two different escape sequences that can be used to set the cursor blink state: ‘CSI ? 12 h/l’ and ‘CSI Ps SP q’. Up until now, they both modified the same internal state in foot. This meant you could enable a blinking cursor with e.g. ‘CSI ? 12 h’ and then disable it with ‘CSI 2 SP q’. Since the ‘CSI ? 12’ escapes are used in the civis/cnorm/cvvis terminfo entries, applications often ended up disabling the blink state on exit (typically be emitting ‘cnorm’), requiring users to manually re-enable blinking. By splitting the internal state into two separate states, we can improve the situation. The cursor will blink if at least one of the two have been enabled. The setting in foot.ini sets the default state of the ‘CSI Ps SP q’ escape. This means if the user has enabled blinking in the configuration, the cursor will blink regardless of civis/cnorm/cvvis. Which probably is what the user wants. If the user has NOT enabled blinking, civis/cnorm/cvvis act as intended: cvvis blink, civis and cnorm do not. If an application overrides the cursor blink/style with ‘CSI Ps SP q’, that will override the user’s setting in foot.ini. But most likely that too is intended (for example, the user may have configured the application to use a different cursor style). And, a well written application will emit the ‘Se’ terminfo sequence on exit, which in foot is defined to ‘CSI SP q’, which will reset both the style and blink state to the user configured style/state. Closes #218
2020-11-26 18:09:32 +01:00
* Cursor will now blink if **either** `CSI ? 12 h` or `CSI Ps SP q`
has been used to enable blinking. **cursor.blink** in `foot.ini`
controls the default state of `CSI Ps SP q`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#218](https://codeberg.org/dnkl/foot/issues/218)).
csi: fix sub-parameter versions of 38/48 SGR escapes Well this is embarrassing; the sub-parameter versions of the 38/48 SGR escapes all required an extra ‘:2’ that wasn’t supposed to be there, causing all the other sub-parameters to be shifted one step to the right. That is, foot expected e.g. 38:2:2:r:g:b, or 38:2:5:idx when the correct sequences are 38:2:cs:r:g:b and 38:5:idx. I.e. I mixed up the color-space ID (cs) of 38:2 with *type* of color: RGB or indexed. In addition to fixing this, this patch also adds support for a “bastard” version of the sub-parameter based RGB escapes, where the color-space identifier has been left out: e.g. 38:2:r:g:b. This sequence is invalid, but applications tend to “forget” the color-space ID...
2020-12-12 20:50:43 +01:00
* The sub-parameter versions of the SGR RGB color escapes (e.g
`\E[38:2...m`) can now be used _without_ the color space ID
parameter.
changelog: ECMA-4*8*
2020-12-16 10:33:04 +01:00
* SGR 21 no longer disables **bold**. According to ECMA-48, SGR 21 is
csi: SGR 21 is “double underline”, not “disable bold” (according to ECMA-48)
2020-12-14 19:10:30 +01:00
_”double underline_”. Foot does not (yet) implement that, but that’s
no reason to implement a non-standard behavior.
csi: implement DECRQM (DEC modes), for real Previously, we always returned ‘2 - reset’, instead of the actual state of the requested mode.
2020-12-16 13:57:40 +01:00
* `DECRQM` now returns actual state of the requested mode, instead of
always returning `2`.
csi: fix sub-parameter versions of 38/48 SGR escapes Well this is embarrassing; the sub-parameter versions of the 38/48 SGR escapes all required an extra ‘:2’ that wasn’t supposed to be there, causing all the other sub-parameters to be shifted one step to the right. That is, foot expected e.g. 38:2:2:r:g:b, or 38:2:5:idx when the correct sequences are 38:2:cs:r:g:b and 38:5:idx. I.e. I mixed up the color-space ID (cs) of 38:2 with *type* of color: RGB or indexed. In addition to fixing this, this patch also adds support for a “bastard” version of the sub-parameter based RGB escapes, where the color-space identifier has been left out: e.g. 38:2:r:g:b. This sequence is invalid, but applications tend to “forget” the color-space ID...
2020-12-12 20:50:43 +01:00
render: blink switches between foreground and dimmed foreground
2020-10-22 18:41:47 +02:00
Merge branch 'releases/1.5' into master
2020-10-11 19:36:00 +02:00
### Removed
config: remove support for loading configuration from footrc
2020-12-08 19:49:43 +01:00
* Support for loading configuration from `$XDG_CONFIG_HOME/footrc`.
changelog: use code/monospace highlighting for foot.ini config options
2020-12-18 14:46:16 +01:00
* `scrollback` option from `foot.ini`.
* `geometry` from `foot.ini`.
* Key binding action `scrollback-up` and `scrollback-down`.
config: remove support for loading configuration from footrc
2020-12-08 19:49:43 +01:00
Merge branch 'releases/1.5' into master
2020-10-11 19:36:00 +02:00
### Fixed
config: ignore “self” when detecting key binding collisions Previously, foot would not accept the following: [key-bindings] minimize=Escape minimize=Escape Now it does. I.e. key combos in the action being updated are ignored when detecting collisions. The example above is contrived; a real world example could be to remove certain combos from an action with multiple combos; perhaps to free up a combo for another action. Example: [search-bindings] cancel=Escape This would previously cause an error since `cancel=Control+g Escape` by default. Closes #233
2020-12-05 11:21:17 +01:00
* Error when re-assigning a default key binding
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#233](https://codeberg.org/dnkl/foot/issues/233)).
csi: ‘CSI s’ and ‘CSI u’ now saves/restores attributes and charsets
2020-12-11 20:01:19 +01:00
* `\E[s`+`\E[u` (save/restore cursor) now saves and restores
attributes and charset configuration, just like `\E7`+`\E8`.
input: report mouse drag events also when the pointer is outside the grid As long as the mouse button was *pressed* while the pointer was inside the grid, we want to keep reporting motion events until the button is released. Even when the pointer moves outside the grid (but in this case, the reported coordinates are bounded by the grid size). This patch also tries to improve multi-button handling (i.e. multiple buttons pressed at the same time), and the events we report to the client for these, in the following ways: * Motion events now report the *initial* button. That is, if you start a drag operation with the LEFT button, then press RIGHT (before releasing LEFT), keep reporting LEFT in the motion events. * Mouse release events are reported for *any* button, as long as the pointer is *inside* the grid, *or*, the button released was the button used to start a drag operation. The last point is important; if we have reported a button press followed by motion events (i.e. a drag operation), we need to report the button release, *even* if the pointer is outside the grid. Note that the client may receive unbalanced button press/release events in the following ways if the user pressed one, and then a second button *inside* the grid, then releases the *first* button (possibly outside the grid), and finally releases the *second* button *outside* the grid. In this case, both buttons will report press events. The first button will report a release event since it is the initial button in the drag operation. However, we don’t track the fact that the second button is being pressed, and thus if it is released outside the grid, it wont generate a release event.
2020-12-11 20:48:43 +01:00
* Report mouse motion events to the client application also while
dragging the cursor outside the grid.
csi: fix sub-parameter versions of 38/48 SGR escapes Well this is embarrassing; the sub-parameter versions of the 38/48 SGR escapes all required an extra ‘:2’ that wasn’t supposed to be there, causing all the other sub-parameters to be shifted one step to the right. That is, foot expected e.g. 38:2:2:r:g:b, or 38:2:5:idx when the correct sequences are 38:2:cs:r:g:b and 38:5:idx. I.e. I mixed up the color-space ID (cs) of 38:2 with *type* of color: RGB or indexed. In addition to fixing this, this patch also adds support for a “bastard” version of the sub-parameter based RGB escapes, where the color-space identifier has been left out: e.g. 38:2:r:g:b. This sequence is invalid, but applications tend to “forget” the color-space ID...
2020-12-12 20:50:43 +01:00
* Parsing of the sub-parameter versions of indexed SGR color escapes
(e.g. `\E[38:5...m`)
term: enabling application synchronized updates clear pending grid refresh 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.
2020-12-14 19:05:03 +01:00
* Frames occasionally being rendered while application synchronized
updates is in effect.
config_font_parse(): return fail/success
2020-12-15 18:55:27 +01:00
* Handling of failures to parse the font specification string.
vt: don’t ignore extra private/intermediate characters Take ‘\E(#0’ for example - this is *not* the same as ‘\E(0’. Up until now, foot has however treated them as the same escape, because the handler for ‘\E(0’ didn’t verify there weren’t any _other_ private characters present. Fix this by turning the ‘private’ array into a single 4-byte integer. This allows us to match *all* privates with a single comparison. Private characters are added to the LSB first, and MSB last. This means we can check for single privates in pretty much the same way as before: switch (term->vt.private) { case ‘?’: ... break; } Checking for two (or more) is much uglier, but foot only supports a *single* escape with two privates, and no escapes with three or more: switch (term->vt.private) { case 0x243f: /* ‘?$’ */ ... break; } The ‘clear’ action remains simple (and fast), with a single write operation. Collecting privates is potentially _slightly_ more complex than before; we now need mask and compare, instead of simply comparing, when checking how many privates we already have. We _could_ add a counter, which would make collecting privates easier, but this would add an additional write to the ‘clean’ action which is really bad since it’s in the hot path.
2020-12-16 14:30:49 +01:00
* Extra private/intermediate characters in escape sequences not being
ignored.
config: ignore “self” when detecting key binding collisions Previously, foot would not accept the following: [key-bindings] minimize=Escape minimize=Escape Now it does. I.e. key combos in the action being updated are ignored when detecting collisions. The example above is contrived; a real world example could be to remove certain combos from an action with multiple combos; perhaps to free up a combo for another action. Example: [search-bindings] cancel=Escape This would previously cause an error since `cancel=Control+g Escape` by default. Closes #233
2020-12-05 11:21:17 +01:00
Merge branch 'releases/1.5'
2020-12-01 20:02:58 +01:00
### Contributors
* [kennylevinsen](https://codeberg.org/kennylevinsen)
* [craigbarnes](https://codeberg.org/craigbarnes)
changelog: add entry for 1.5.4
2020-12-01 19:33:22 +01:00
## 1.5.4
readme/doc:foot.1: document the (new) keypad behavior
2020-11-11 18:37:28 +01:00
### Changed
Merge branch 'releases/1.5'
2020-12-01 20:02:58 +01:00
readme/doc:foot.1: document the (new) keypad behavior
2020-11-11 18:37:28 +01:00
* Num Lock by default overrides the keypad mode. See
changelog: fix link to readme#keypad
2020-11-12 18:20:54 +01:00
**foot.ini**(5)::KEYPAD, or
[README.md](README.md#user-content-keypad) for details
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#194](https://codeberg.org/dnkl/foot/issues/194)).
config: enable allow-overflowing-double-width-glyphs by default
2020-11-13 17:49:23 +01:00
* Single-width characters with double-width glyphs are now allowed to
overflow into neighboring cells by default. Set
**tweak.allow-overflowing-double-width-glyphs** to ‘no’ to disable
this.
readme/doc:foot.1: document the (new) keypad behavior
2020-11-11 18:37:28 +01:00
changelog: add entry for 1.5.4
2020-12-01 19:33:22 +01:00
### Fixed
wayland: preempt render scheduling in ‘configure’ events A configure event must be “committed”. In case of resizing, that means rendering a new frame and committing that surface. render_resize() will resize the grid and *schedule* a render refresh. However, if one is already pending, the refresh will take a very (relatively) long time - until the next frame callback is received. This poses a problem when the window is hidden, since in this case, the frame callback *never* comes. This in turn means we fail to commit a new surface in response to the ‘configure’ event. And that means the compositor needs to wait for a transaction timeout before continuing. The end effect is very slow and jerky window resizing when a hidden foot window is being resized. This can happen in tiled compositors, like Sway, where a window can be tabbed (and thus invisible), but still resized when its container is resized. Closes #190
2020-11-10 19:20:35 +01:00
* Resize very slow when window is hidden
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#190](https://codeberg.org/dnkl/foot/issues/190)).
keymap: use same lookup table for Tab and ISO_Left_Tab With XKB, Shift+Tab maps to XKB_KEY_ISO_Left_Tab, not XKB_Key_Tab. Previously, we had two different lookup tables for the two. The tab table was correctly populated, while the ISO-left tab wasn’t. As a result, all Shift+Tab combos (except Shift+Tab itself) was wrong, and resulted in the same escape sequence as Shift+Tab. Fix by using the same table for both tab and ISO-left tab. Closes #210
2020-11-19 19:15:13 +01:00
* Key mappings for key combinations with `shift`+`tab`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#210](https://codeberg.org/dnkl/foot/issues/210)).
keymap: fix alt+return combos All alt+return combos mapped to the same escape sequence as alt+return itself. With this patch, alt+<mod(s)>+return map to a standard ‘CSI 27;x;13~’ sequence.
2020-11-19 19:20:15 +01:00
* Key mappings for key combinations with `alt`+`return`.
client: fix handling of "-m" command-line flag
2020-11-22 16:40:15 +00:00
* `footclient` `-m` (`--maximized`) flag being ignored.
sixel: fix crash when an explicit sixel size had a height less than 6 pixels
2020-11-23 19:22:40 +01:00
* Crash with explicitly sized sixels with a height less than 6 pixels.
keymap: add ‘CSI 27;<mod>;27~’ escapes for Esc with modifiers
2020-11-28 11:50:32 +01:00
* Key mappings for `esc` with modifiers.
Merge branch 'releases/1.5'
2020-11-06 20:21:33 +01:00
### Contributors
changelog: update contributors
2020-11-21 22:05:24 +01:00
* [craigbarnes](https://codeberg.org/craigbarnes)
Merge branch 'releases/1.5'
2020-11-06 20:21:33 +01:00
changelog: prepare for 1.5.3
2020-11-06 20:06:31 +01:00
## 1.5.3
### Fixed
input: don’t crash if xkbcommon cannot find a compose file Handle xkb_compose_table_new_from_locale() returning NULL. When this happens, log a warning that “dead keys” will be disabled, and make sure to never de-reference the compose table pointer. Closes #170
2020-10-19 18:30:19 +02:00
* Crash when libxkbcommon cannot find a suitable libX11 _compose_
file. Note that foot will run, but without support for dead keys.
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#170](https://codeberg.org/dnkl/foot/issues/170)).
wayland: properly restore window size when being un-tiled Bind to xdg-shell version 2 if available, as this enables us to track our window’s ‘tiled’ state in the ‘configure’ events. This in turn allows us to stash the ‘old’ window size when being tiled, to be used again when restoring the window size when un-tiled.
2020-10-20 20:58:03 +02:00
* Restored window size when window is un-tiled.
input: don’t allow diagonal resize when tiled
2020-10-20 21:00:19 +02:00
* XCursor shape in CSD corners when window is tiled.
input: handle XKB errors * Don’t de-reference the xkb context/keymap/state if we failed to instantiate them. * Don’t try to send a translated utf8 key sequence if the translation failed. * Handle xkb_compose_state_get_utf8() and xkb_state_key_get_utf8() returning more than 64 bytes. This _may_ fix #171.
2020-10-20 21:01:33 +02:00
* Error handling when processing keyboard input (maybe
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
[#171](https://codeberg.org/dnkl/foot/issues/171)).
tiocswinsz: fix compilation error on e.g. ppc64 On some platforms, TIOCSWINSZ has a very large value, > 0x80000000. On some platforms, the `request` argument to `ioctl(3)` is an `int`. For platforms where both of the above is true, gcc will warn (and error out if compiled with `-Werror`) on: ioctl(fd, TIOCSWINSZ, ...) To silence this warning, we need to cast `TIOCSWINSZ` to an integer. However, doing this on platforms where `request` is an `unsigned long` will result in `TIOCSWINSZ` being sign-extended (and thus we end up with an invalid value). It seems that casting to `unsigned int` works in both cases; it silences the long -> int conversion warning, while also preserving the correct value in all cases.
2020-10-29 18:06:04 +01:00
* Compilation error _"overflow in conversion from long 'unsigned int'
to 'int' changes value... "_ seen on platforms where the `request`
argument in `ioctl(3)` is an `int` (for example: linux/ppc64).
input: don’t use seat->kbd_focus as terminal when processing a key press When converting mouse scroll events to keyboard input (in alternate scroll mode), we need to use seat->mouse_focus, not seat->kbd_focus. To enable this, break out key press/release handling code to a separate function that takes an explicit term argument. Call this function from keyboard_key(), input_repeat() and in alternate scroll mode. Closes #179
2020-11-03 19:44:51 +01:00
* Crash when using the mouse in alternate scroll mode in an unfocused
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
window ([#179](https://codeberg.org/dnkl/foot/issues/179)).
selection: explicitly set direction when right-click extending Fixes an issue where right-click-and-dragging to extend a selection caused one cell being removed from the selection. Closes #180
2020-11-04 19:01:59 +01:00
* Character dropped from selection when "right-click-hold"-extending a
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
selection ([#180](https://codeberg.org/dnkl/foot/issues/180)).
Merge branch 'releases/1.5' into master
2020-10-11 19:36:00 +02:00
input: regression: don’t pass on mouse click to application if we consumed it When we ‘consume’ a mouse button event (i.e. when we have a shortcut mapped to it), the event should *not* be passed on to the client application. In 5f64c5c33590a41afd3f621870c6abd89b859073, button handling was refactored and unfortunately introduced a regression where we once again started passing consumed button presses to the client application. Fixes #168
2020-10-13 08:02:09 +02:00
## 1.5.2
### Fixed
* Regression: middle clicking double pastes in e.g. vim
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#168](https://codeberg.org/dnkl/foot/issues/168))
input: regression: don’t pass on mouse click to application if we consumed it When we ‘consume’ a mouse button event (i.e. when we have a shortcut mapped to it), the event should *not* be passed on to the client application. In 5f64c5c33590a41afd3f621870c6abd89b859073, button handling was refactored and unfortunately introduced a regression where we once again started passing consumed button presses to the client application. Fixes #168
2020-10-13 08:02:09 +02:00
changelog: prepare for 1.5.1
2020-10-11 19:31:01 +02:00
## 1.5.1
changelog: reverse auto-wrap
2020-10-02 21:44:03 +02:00
changelog: add new ‘unreleased’ section
2020-09-18 21:29:39 +02:00
### Changed
changelog: multiplier default value changed from 1.0 -> 3.0
2020-09-29 19:41:53 +02:00
changelog: multiplier: the option belongs to the ‘scrollback’ section
2020-09-29 19:43:39 +02:00
* Default value of the **scrollback.multiplier** option in `foot.ini`
from `1.0` to `3.0`.
config: bind shift+insert to primary-paste by default
2020-10-10 10:27:42 +02:00
* `shift`+`insert` now pastes from the primary selection by
default. This is in addition to middle-clicking with the mouse.
changelog: multiplier default value changed from 1.0 -> 3.0
2020-09-29 19:41:53 +02:00
changelog: add new ‘unreleased’ section
2020-09-18 21:29:39 +02:00
### Fixed
input: mouse: match binding if binding’s click count is *less* Allow a mouse binding to match even if its click count is less than the actual click count. If there are multiple bindings that match, use the one with the highest click count (that less than, or equal to the actual click count). Closes #146
2020-09-27 14:31:39 +02:00
* Mouse bindings now match even if the actual click count is larger
than specified in the binding. This allows you to, for example,
quickly press the middle-button to paste multiple times
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#146](https://codeberg.org/dnkl/foot/issues/146)).
changelog: fixed color flashes with OSC 4,10,11
2020-09-29 10:11:03 +02:00
* Color flashes when changing the color palette with OSC 4,10,11
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#141](https://codeberg.org/dnkl/foot/issues/141)).
grid: reflow: retain scrollback position Closes #142
2020-09-24 18:35:40 +02:00
* Scrollback position is now retained when resizing the window
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#142](https://codeberg.org/dnkl/foot/issues/142)).
changelog: reword trackpad scrolling speed entry
2020-09-29 09:49:21 +02:00
* Trackpad scrolling speed to better match the mouse scrolling speed,
and to be consistent with other (Wayland) terminal emulators. Note
that it is (much) slower compared to previous foot versions. Use the
changelog: trackpad scrolling: ‘multiplier’ is in the ‘scrollback’ section
2020-09-29 19:47:29 +02:00
**scrollback.multiplier** option in `foot.ini` if you find the new
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
speed too slow ([#144](https://codeberg.org/dnkl/foot/issues/144)).
config: ignore key/value pairs following an invalid section name When we detected an invalid section name, we correctly logged this and warned the user. However, the internal state machine now had an invalid section enum value. This caused a crash when the next key/value pair was to be parsed and we tried to lookup which parser function to call. Closes #159.
2020-10-07 18:34:48 +02:00
* Crash when `foot.ini` contains an invalid section name
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#159](https://codeberg.org/dnkl/foot/issues/159)).
render: apply opacity correctly when in reverse video mode
2020-10-08 19:53:11 +02:00
* Background opacity when in _reverse video_ mode.
sixel: overwrite-by-rectangle expects ‘width’ to not exceed screen This fixes a crash when the emitted sixel extends beyond the right margin. The crash only happens when there are other sixel images already emitted. Fixes part of #151
2020-10-02 20:55:10 +02:00
* Crash when writing a sixel image that extends outside the terminal's
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
right margin ([#151](https://codeberg.org/dnkl/foot/issues/151)).
sixel: fix sheared image when image crosses scrollback wrap-around When a sixel image crosses the scrollback wrap-around, it is split up into (at least) two pieces. We use cursor->point.col for all pieces’ x-coordinate. This caused the final image to appear sheared, since we do a carriage-return (after a number of linefeeds) after each piece - this causes the cursor’s position to be reset to the left margin. The solution is simple; remember the cursor’s initial x-coordinate, and use that to position all image pieces. Closes #151.
2020-10-02 20:56:44 +02:00
* Sixel image at non-zero column positions getting sheared at
seemingly random occasions
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#151](https://codeberg.org/dnkl/foot/issues/151)).
changelog: we’ve fixed several sixel+reflow related bugs
2020-10-07 18:46:11 +02:00
* Crash after either resizing a window or changing the font size if
there were sixels present in the scrollback while doing so.
csi: only respond to Primary DA when Ps == 0
2020-10-09 18:53:00 +02:00
* _Send Device Attributes_ to only send a response if `Ps == 0`.
selection: use appropriate check for PRIMARY paste Assume it could be a copy-paste typo. We should check PRIMARY, not CLIPBOARD. Without this fix, we can't use PRIMARY until we copy anything to CLIPBOARD.
2020-10-10 21:13:08 +03:00
* Paste from primary when clipboard is empty.
input: mouse: match binding if binding’s click count is *less* Allow a mouse binding to match even if its click count is less than the actual click count. If there are multiple bindings that match, use the one with the highest click count (that less than, or equal to the actual click count). Closes #146
2020-09-27 14:31:39 +02:00
changelog: add new ‘unreleased’ section
2020-09-18 21:29:39 +02:00
### Contributors
changelog: add contributor
2020-10-09 19:19:40 +02:00
* [craigbarnes](https://codeberg.org/craigbarnes)
changelog: update ‘contributors’ list
2020-10-10 23:34:21 +02:00
* [zar](https://codeberg.org/zar)
changelog: add contributor
2020-10-09 19:19:40 +02:00
changelog: add new ‘unreleased’ section
2020-09-18 21:29:39 +02:00
changelog: prepare for 1.5.0
2020-09-18 21:22:59 +02:00
## 1.5.0
changelog: scrollback indicator is a *new* feataure
2020-07-29 07:08:14 +02:00
changelog: move deprecation section up first, change most ‘footrc’ -> ‘foot.ini’ The deprecation sections mentions ‘footrc’ being deprecated, and replaced by ‘foot.ini’. Since a lot of the changelog entries refer to foot.ini, make sure the user sees this first. Also, use foot.ini (and not footrc) consistently in all changelog entries.
2020-09-08 19:37:59 +02:00
### Deprecated
* `$XDG_CONFIG_HOME/footrc`/`~/.config/footrc`. Use
`$XDG_CONFIG_HOME/foot/foot.ini`/`~/.config/foot/foot.ini` instead.
key-binding: deprecate scrollback-up/down, add scrollback-up/down-line This deprecates/renames scrollback-up/down to scrollback-up/down-page. It also renames scrollback-up/down-half to scrollback-up/down-half-page, and adds the new bindings scrollback-up/down-line.
2020-09-10 18:17:47 +02:00
* **scrollback** option in `foot.ini`. Use **scrollback.lines**
instead.
* **scrollback-up** key binding. Use **scrollback-up-page** instead.
* **scrollback-down** key binding. Use **scrollback-down-page**
instead.
changelog: move deprecation section up first, change most ‘footrc’ -> ‘foot.ini’ The deprecation sections mentions ‘footrc’ being deprecated, and replaced by ‘foot.ini’. Since a lot of the changelog entries refer to foot.ini, make sure the user sees this first. Also, use foot.ini (and not footrc) consistently in all changelog entries.
2020-09-08 19:37:59 +02:00
changelog: add new 'unreleased' section
2020-07-23 18:56:47 +02:00
### Added
changelog: move scrollback indicator entries from 1.4.3 to 'unreleased'
2020-07-27 19:08:28 +02:00
* Scrollback position indicator. This feature is optional and
changelog: update scrollback indicator entry to reflect moved options
2020-07-29 17:50:19 +02:00
controlled by the **scrollback.indicator-position** and
changelog: move deprecation section up first, change most ‘footrc’ -> ‘foot.ini’ The deprecation sections mentions ‘footrc’ being deprecated, and replaced by ‘foot.ini’. Since a lot of the changelog entries refer to foot.ini, make sure the user sees this first. Also, use foot.ini (and not footrc) consistently in all changelog entries.
2020-09-08 19:37:59 +02:00
**scrollback.indicator-format** options in `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#42](https://codeberg.org/dnkl/foot/issues/42)).
Fix typos
2020-08-15 23:29:38 +02:00
* Key bindings in _scrollback search_ mode are now configurable.
main: add --check-config command line option
2020-07-29 17:48:22 +02:00
* `--check-config` command line option.
config: add 'pipe-selected' key binding This works just like pipe-visible and pipe-scrollback, but pipes the user-selected text, if any, to the external tool. Closes #51
2020-07-31 17:02:53 +02:00
* **pipe-selected** key binding. Works like **pipe-visible** and
**pipe-scrollback**, but only pipes the currently selected text, if
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
any ([#51](https://codeberg.org/dnkl/foot/issues/51)).
changelog: move deprecation section up first, change most ‘footrc’ -> ‘foot.ini’ The deprecation sections mentions ‘footrc’ being deprecated, and replaced by ‘foot.ini’. Since a lot of the changelog entries refer to foot.ini, make sure the user sees this first. Also, use foot.ini (and not footrc) consistently in all changelog entries.
2020-09-08 19:37:59 +02:00
* **mouse.hide-when-typing** option to `foot.ini`.
* **scrollback.multiplier** option to `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#54](https://codeberg.org/dnkl/foot/issues/54)).
config: make selection foreground/background colors configurable The default is still to inverse the regular foreground/background colors. If the user sets *both* of the new options, selection-foreground and selection-background, those colors will *always* be used for selected cells, instead of inverting the regular foreground/background colors.
2020-08-12 18:53:32 +02:00
* **colors.selection-foreground** and **colors.selection-background**
changelog: move deprecation section up first, change most ‘footrc’ -> ‘foot.ini’ The deprecation sections mentions ‘footrc’ being deprecated, and replaced by ‘foot.ini’. Since a lot of the changelog entries refer to foot.ini, make sure the user sees this first. Also, use foot.ini (and not footrc) consistently in all changelog entries.
2020-09-08 19:37:59 +02:00
options to `foot.ini`.
* **tweak.render-timer** option to `foot.ini`.
changelog: modifier support in mouse bindings
2020-08-10 19:16:26 +02:00
* Modifier support in mouse bindings
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#77](https://codeberg.org/dnkl/foot/issues/77)).
changelog: click count in mouse bindings
2020-08-10 20:59:05 +02:00
* Click count support in mouse bindings, i.e double- and triple-click
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#78](https://codeberg.org/dnkl/foot/issues/78)).
changelog: new mouse actions
2020-08-11 10:26:31 +02:00
* All mouse actions (begin selection, select word, select row etc) are
now configurable, via the new **select-begin**,
**select-begin-block**, **select-extend**, **select-word**,
**select-word-whitespace** and **select-row** options in the
changelog: move deprecation section up first, change most ‘footrc’ -> ‘foot.ini’ The deprecation sections mentions ‘footrc’ being deprecated, and replaced by ‘foot.ini’. Since a lot of the changelog entries refer to foot.ini, make sure the user sees this first. Also, use foot.ini (and not footrc) consistently in all changelog entries.
2020-09-08 19:37:59 +02:00
**mouse-bindings** section in `foot.ini`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#79](https://codeberg.org/dnkl/foot/issues/79)).
changelog: xtsave/xtrestore
2020-08-16 17:03:58 +02:00
* Implement XTSAVE/XTRESTORE escape sequences, `CSI ? Ps s` and `CSI ?
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
Ps r` ([#91](https://codeberg.org/dnkl/foot/issues/91)).
slave: set $COLORTERM environment variable to "truecolor" This is also done by libvte, alacritty, kitty and several other terminal emulators as a way to indicate support for 24-bit RGB colors. It generally also implies support for the xterm 256-color palette and basic ECMA-48 colors.
2020-08-23 05:31:34 +01:00
* `$COLORTERM` is now set to `truecolor` at startup, to indicate
support for 24-bit RGB colors.
render: optionally enable heuristics that deal with private usage area chars Try to detect double-width *glyphs* for single-width *characters*, and allow them to overflow into the next cell. This is only done for single-width chars with a glyph width that is at least 1.5 cells wide, but at most 3 cells. The feature is gated by the new ‘tweak.allow-overflowing-double-width-glyphs’, and is disabled by default. Closes #116
2020-09-03 17:37:44 +02:00
* Experimental support for rendering double-width glyphs with a
character width of 1. Must be explicitly enabled with
`tweak.allow-overflowing-double-width-glyphs`
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#116](https://codeberg.org/dnkl/foot/issues/116)).
Add -W,--window-size-chars, and foot.ini:initial-window-size-chars * Add -W,--window-size-chars command line option * Add initial-window-size-chars foot.ini option * Add -w,--window-size-pixels command line option * Add initial-window-size-pixels foot.ini option * Deprecate -g,--geometry command line option in favor of -w,--window-size-pixels * Deprecate geometry option in foot.ini in favor of initial-window-size-pixels
2020-09-08 19:17:29 +02:00
* **initial-window-size-pixels** options to `foot.ini` and
`-w,--window-size-pixels` command line option to `foot`. This option
replaces the now deprecated **geometry** and `-g,--geometry`
options.
* **initial-window-size-chars** option to `foot.ini` and
`-W,--window-size-chars` command line option to `foot`. This option
configures the initial window size in **characters**, and is an
alternative to **initial-window-size-pixels**.
key-binding: deprecate scrollback-up/down, add scrollback-up/down-line This deprecates/renames scrollback-up/down to scrollback-up/down-page. It also renames scrollback-up/down-half to scrollback-up/down-half-page, and adds the new bindings scrollback-up/down-line.
2020-09-10 18:17:47 +02:00
* **scrollback-up-half-page** and **scrollback-down-half-page** key
config: add scrollback-{up,down}-half key bindings These new bindings scroll up/down half a page in the scrollback (instead of the full page scrolled by ‘scrollback-{up,down}’). Closes #128.
2020-09-09 19:40:48 +02:00
bindings. They scroll up/down half of a page in the scrollback
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#128](https://codeberg.org/dnkl/foot/issues/128)).
key-binding: deprecate scrollback-up/down, add scrollback-up/down-line This deprecates/renames scrollback-up/down to scrollback-up/down-page. It also renames scrollback-up/down-half to scrollback-up/down-half-page, and adds the new bindings scrollback-up/down-line.
2020-09-10 18:17:47 +02:00
* **scrollback-up-line** and **scrollback-down-line** key
bindings. They scroll up/down a single line in the scrollback.
config: add mouse.alternate-scroll-mode option This option controls the initial state of the Alternate Scroll Mode, and defaults to ‘enabled’.
2020-09-15 19:09:00 +02:00
* **mouse.alternate-scroll-mode** option to `foot.ini`. This option
controls the initial state of the _Alternate Scroll Mode_, and
changelog: mouse events -> mouse scroll events
2020-09-15 19:29:38 +02:00
defaults to `yes`. When enabled, mouse scroll events are translated
to up/down key events in the alternate screen, letting you scroll in
config: add mouse.alternate-scroll-mode option This option controls the initial state of the Alternate Scroll Mode, and defaults to ‘enabled’.
2020-09-15 19:09:00 +02:00
e.g. `less` and other applications without enabling native mouse
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
support in them ([#135](https://codeberg.org/dnkl/foot/issues/135)).
changelog: move scrollback indicator entries from 1.4.3 to 'unreleased'
2020-07-27 19:08:28 +02:00
config: add scrollback section * Move 'scrollback' to 'scrollback.lines' * Move (the new) 'scrollback-indicator-*' options to 'scrollback.indicator-*' Log a deprecation warning when the old 'scrollback' option is used, but don't remove it, yet.
2020-07-29 17:41:24 +02:00
changelog: scrollback indicator is a *new* feataure
2020-07-29 07:08:14 +02:00
### Changed
changelog: move deprecation section up first, change most ‘footrc’ -> ‘foot.ini’ The deprecation sections mentions ‘footrc’ being deprecated, and replaced by ‘foot.ini’. Since a lot of the changelog entries refer to foot.ini, make sure the user sees this first. Also, use foot.ini (and not footrc) consistently in all changelog entries.
2020-09-08 19:37:59 +02:00
* Renamed man page for `foot.ini` from **foot**(5) to **foot.ini**(5).
config: configuration errors are no longer fatal Instead of refusing to start foot on configuration errors, we start and print a user-notification.
2020-07-31 17:07:14 +02:00
* Configuration errors are no longer fatal; foot will start and print
an error inside the terminal (and of course still log errors on
stderr).
server/client: use $WAYLAND_DISPLAY instead of $XDG_SESSION_ID in default socket path Foot is a Wayland client and cannot be run outside of a Wayland session. As such, it makes more sense to use $WAYLAND_SESSION instead of $XDG_SESSION_ID in the default socket path since this makes it clearer which Wayland session we belong to. Closes #55.
2020-08-02 13:10:31 +02:00
* Default `--server` socket path to use `$WAYLAND_DISPLAY` instead of
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
`$XDG_SESSION_ID` ([#55](https://codeberg.org/dnkl/foot/issues/55)).
changelog: trailing empty cells are not highlighted in mouse selections
2020-08-18 18:03:41 +02:00
* Trailing empty cells are no longer highlighted in mouse selections.
changelog: new configuration file location
2020-08-27 20:02:43 +02:00
* Foot now searches for its configuration in
`$XDG_DATA_DIRS/foot/foot.ini`, if no configuration is found in
`$XDG_CONFIG_HOME/foot/foot.ini` or in `$XDG_CONFIG_HOME/footrc`.
render: change minimum window size from 4x20 -> 1x2 (rows/cols)
2020-09-07 19:34:06 +02:00
* Minimum window size changed from four rows and 20 columns, to 1 row
and 2 columns.
key-binding: deprecate scrollback-up/down, add scrollback-up/down-line This deprecates/renames scrollback-up/down to scrollback-up/down-page. It also renames scrollback-up/down-half to scrollback-up/down-half-page, and adds the new bindings scrollback-up/down-line.
2020-09-10 18:17:47 +02:00
* **scrollback-up/down** renamed to **scrollback-up/down-page**.
config: add tweak.scaling-filter Use the new fcft_set_scaling_filter() API to use a non-default scaling filter. By default, we use lanczo3, the ‘best’ filter. This overrides the default in fcft, which is ‘cubic’ filtering.
2020-09-13 17:59:56 +02:00
* fcft >= 2.3.0 is now required.
changelog: scrollback indicator is a *new* feataure
2020-07-29 07:08:14 +02:00
config: tokenize key bindings' pipe command when loading the configuration This allows us to detect syntax errors early on, and is also more efficient since we don't have to re-tokenize the command line every time the binding is executed.
2020-07-30 18:53:51 +02:00
### Fixed
* Command lines for **pipe-visible** and **pipe-scrollback** are now
tokenized (i.e. syntax checked) when the configuration is loaded,
instead of every time the key binding is executed.
grid: reflow: don't insert <width> spacer cells for *every* empty cell Only do it for the last, non-empty cell.
2020-08-04 18:07:54 +02:00
* Incorrect multi-column character spacer insertion when reflowing
text.
fix printf-format errors in 32-bit builds
2020-08-06 23:20:46 +02:00
* Compilation errors in 32-bit builds.
changelog: 'of' -> 'in'
2020-08-07 20:08:30 +02:00
* Mouse cursor style in top and left margins.
input: motion: do selection update even if cursor is outside the grid Previously, the selection was only updated when the mouse cursor was inside the grid. This makes it difficult to e.g. do large selections fast, since you often end up moving the cursor outside the grid, or outside the terminal window even. Now, we update the selection regardless of *where* the cursor is. This is done by bounding the row/col we pass to 'selection_update()' to the grid, while still setting the seat's row/col to -1 when the cursor is outside the grid, to ensure the xcursor etc are set correctly. Care must also be taken to *not* pass any motion events to a mouse grabbing client, when the cursor is outside the grid. Closes #70.
2020-08-07 19:55:02 +02:00
* Selection is now **updated** when the cursor moves outside the grid
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#70](https://codeberg.org/dnkl/foot/issues/70)).
search: fix viewport not moving if we tried to move it past the scrollback start If the match was somewhere near the scrollback beginning, and if the entire scrollback hadn't yet been filled, we ended up trying to move the viewport past the beginning of the scrollback, which we then adjusted in the wrong direction, causing the viewport to not move at all. Besides being a bad user experience, since the new match wasn't visible, foot would also crash if you manually scrolled up to the match.
2020-08-12 18:45:35 +02:00
* Viewport sometimes not moving when doing a scrollback search.
changelog: cancelling -> canceling
2020-08-13 06:33:10 +02:00
* Crash when canceling a scrollback search and the window had been
search: fix viewport not moving if we tried to move it past the scrollback start If the match was somewhere near the scrollback beginning, and if the entire scrollback hadn't yet been filled, we ended up trying to move the viewport past the beginning of the scrollback, which we then adjusted in the wrong direction, causing the viewport to not move at all. Besides being a bad user experience, since the new match wasn't visible, foot would also crash if you manually scrolled up to the match.
2020-08-12 18:45:35 +02:00
resized while searching.
selection: adjust start point when the selection changes direction Without this, the initial cell will always be selected, regardless of how the selection is moved to the left or right. With this patch, the initial cell will only be selected while the selection is being made in the original direction. Changing direction of the selection moves the start point to next/previous character.
2020-08-12 18:50:49 +02:00
* Selection start point not moving when the selection changes
direction.
osc: dirty grids on *all* color modifying sequences We only updated the grid for OSC 4 - Set color <idx>. But we did *not* do it for 104 (reset color <idx>), 10 - set default foreground, 11 - set default background, 110 - reset default foreground, or 111 - reset default background.
2020-08-18 07:20:57 +02:00
* OSC 10/11/104/110/111 (modify colors) did not update existing screen
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
content ([#94](https://codeberg.org/dnkl/foot/issues/94)).
extract: only emit newlines if followed by non-empty cells Closes #97
2020-08-20 19:21:25 +02:00
* Extra newlines when copying empty cells
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#97](https://codeberg.org/dnkl/foot/issues/97)).
input: inhibit mouse events to client when a binding has consumed it This introduces a new state to a seat's mouse struct, 'consumed'. It is set on a mouse *press* event that is claimed by a mouse binding. It is cleared after a mouse *release* event. While set, *no* mouse motion or button events are sent to the client application.
2020-08-22 13:35:36 +02:00
* Mouse events from being sent to client application when a mouse
binding has consumed it.
changelog: fixed input events from getting mixed with paste data
2020-08-22 09:16:51 +02:00
* Input events from getting mixed with paste data
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#101](https://codeberg.org/dnkl/foot/issues/101)).
changelog: output objects received before XDG output manager
2020-09-04 18:08:37 +02:00
* Missing DPI values for “some” monitors on Gnome
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#118](https://codeberg.org/dnkl/foot/issues/118)).
grid: reflow: calculate width of composed characters correctly Before this patch, reflow called `wcwidth()` on our magic values for composed characters.
2020-09-06 19:14:46 +02:00
* Handling of multi-column composed characters while reflowing.
keymap: emit \E[27;2;13~ for all key combinations involving Shift+Return This is what XTerm emits with `modifyOtherKeys=1`, which is foot’s only mode.
2020-09-07 22:03:58 +02:00
* Escape sequences sent for key combinations with `Return`, that did
**not** include `Alt`.
osc52: unset (clear) selection when an invalid payload is received
2020-09-09 18:46:39 +02:00
* Clipboard (or primary selection) is now cleared when receiving an
OSC-52 command with an invalid base64 encoded payload.
grid: reflow: make sure cursor is within the visible screen area Even though we translate the cursor position from the old grid coordinates to the new, the cursor may _still_ end up outside the visible area. Make sure it doesn’t.
2020-09-09 18:40:06 +02:00
* Cursor position being set outside the grid when reflowing text.
render: csd: hide buttons when title bar gets too small to fit them
2020-09-09 18:43:23 +02:00
* CSD buttons to be hidden when window size becomes so small that they
no longer fit.
config: tokenize key bindings' pipe command when loading the configuration This allows us to detect syntax errors early on, and is also more efficient since we don't have to re-tokenize the command line every time the binding is executed.
2020-07-30 18:53:51 +02:00
Merge branch 'releases/1.4' into master
2020-07-29 07:07:46 +02:00
### Contributors
changelog: add craigbarnes to 'contributors' for the upcoming release
2020-08-03 08:17:26 +02:00
* [craigbarnes](https://codeberg.org/craigbarnes)
changelog: add birger to 'contributers' for the upcoming release
2020-08-08 10:23:26 +02:00
* [birger](https://codeberg.org/birger)
changelog: add ordoviz to contributors
2020-08-16 09:14:15 +02:00
* [Ordoviz](https://codeberg.org/Ordoviz)
changelog: add cherti to contributors
2020-09-18 21:22:27 +02:00
* [cherti](https://codeberg.org/cherti)
changelog: add craigbarnes to 'contributors' for the upcoming release
2020-08-03 08:17:26 +02:00
changelog: add extra newline between index and first release
2020-07-29 07:01:44 +02:00
changelog: add 1.4.4 section
2020-07-29 06:55:23 +02:00
## 1.4.4
input: margins are not selectable * Fix col/row calculation in pointer-enter event; we did not take the margins into account. * seat->mouse.col,row are now set to -1 if the cursor is inside the margins. That is, col/row are only ever valid when the mouse is actually over the grid, and not in the margins. * Use regular 'left-ptr' mouse cursor when mouse is inside the margins, to not make the user think he/she can start a selection. Besides making things clearer, this also fixes a crash that occurred if you started a selection in e.g. the right margin.
2020-07-26 12:31:13 +02:00
### Changed
* Mouse cursor is now always a `left_ptr` when inside the margins, to
indicate it is not possible to start a selection.
changelog: add new 'unreleased' section
2020-07-27 19:00:25 +02:00
### Fixed
changelog: move scrollback indicator entries from 1.4.3 to 'unreleased'
2020-07-27 19:08:28 +02:00
* Crash when starting a selection inside the margins.
changelog: move #47 to the correct release
2020-07-28 20:07:53 +02:00
* Improved font size consistency across multiple monitors with
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
different DPI ([#47](https://codeberg.org/dnkl/foot/issues/47)).
config: handle trailing comments and empty values
2020-07-28 19:55:09 +02:00
* Handle trailing comments in `footrc`
changelog: add new 'unreleased' section
2020-07-27 19:00:25 +02:00
changelog: prepare for 1.4.3
2020-07-27 18:55:12 +02:00
## 1.4.3
changelog: add new 'unreleased' section
2020-07-23 18:56:47 +02:00
### Added
readme: add section describing how to identify foot
2020-07-24 17:50:48 +02:00
* Section to [README.md](README.md) describing how to programmatically
identify foot.
meson: install LICENSE, README.md and CHANGELOG.md
2020-07-25 09:05:11 +02:00
* [LICENSE](LICENSE), [README.md](README.md) and
[CHANGELOG.md](CHANGELOG.md) are now installed to
`${datadir}/doc/foot`.
tokenize: handle escaped quotes We only support escaping quotes inside a quote, and only of the same type as the enclosing quote. I.e. "double quote \"escaped double quote\"" But not "double quote \'invalid escaped single quote\'"
2020-07-27 16:43:41 +02:00
* Support for escaping quotes in **pipe-visible** and
**pipe-scrollback** commands.
readme: add section describing how to identify foot
2020-07-24 17:50:48 +02:00
changelog: add new 'unreleased' section
2020-07-23 18:56:47 +02:00
### Changed
csi: primary DA: remove features we do not support We do not implement * Selective Erase * Technical Character Set * Terminal state interrogation
2020-07-24 17:46:18 +02:00
* Primary DA to no longer indicate support for _Selective Erase_,
_Technical Characters_ and _Terminal State Interrogation_.
csi: secondary DA: do not pretend we're xterm Previously, our secondary DA response indicated a) VT420, b) an XTerm version number. Now, we indicate VT220 (which corresponds to the primary DA response), and we report foot's version number as MMmmpp. I.e major, minor and patch versions, using two digits. E.g. 1.4.2 is encoded as 010402
2020-07-24 17:47:47 +02:00
* Secondary DA to report foot as a VT220 instead of a VT420.
* Secondary DA to report foot's version number in parameter 2, the
_Firmware Version_. The string is made up of foot's major, minor and
patch version numbers, always using two digits for each version
number and without any other separating characters. Thus, _1.4.2_
would be reported as `010402` (i.e. the full response would be
`\E[>1;010402;0c`).
search: improve viewport movements * Don't move the viewport if the new match is already fully visible * When we do have to move the viewport, position it such that the new match ends up roughly in the middle.
2020-07-24 17:49:50 +02:00
* Scrollback search to only move the viewport if the match lies
outside it.
* Scrollback search to focus match, that requires a viewport change,
roughly in the center of the screen.
selection: extending a selection is now interactive That is, a selection extension can be resized just like an ordinary extension.
2020-07-27 16:44:41 +02:00
* Extending a selection with the right mouse button now works while
dragging the mouse.
search: improve viewport movements * Don't move the viewport if the new match is already fully visible * When we do have to move the viewport, position it such that the new match ends up roughly in the middle.
2020-07-24 17:49:50 +02:00
changelog: add new 'unreleased' section
2020-07-23 18:56:47 +02:00
### Fixed
search: fix crash when searching the scrollback history search_update_selection() was changed in 1.4.x to *first* update the selection, *then* move the viewport. This leads to a crash if the new match (selection) is outside the current viewport; the selection code assumes the updated selection endpoint is in the visible viewport. Changing back to *first* move the viewport, *then* update the selection solves this.
2020-07-25 11:23:54 +02:00
selection: extending a selection is now interactive That is, a selection extension can be resized just like an ordinary extension.
2020-07-27 16:44:41 +02:00
* Crash in scrollback search.
changelog: mention fix for crash on unclosed quote in tokenizer
2020-07-27 16:41:35 +02:00
* Crash when a **pipe-visible** or **pipe-scrollback** command
contained an unclosed quote
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#49](https://codeberg.org/dnkl/foot/issues/49)).
search: fix crash when searching the scrollback history search_update_selection() was changed in 1.4.x to *first* update the selection, *then* move the viewport. This leads to a crash if the new match (selection) is outside the current viewport; the selection code assumes the updated selection endpoint is in the visible viewport. Changing back to *first* move the viewport, *then* update the selection solves this.
2020-07-25 11:23:54 +02:00
changelog: add 'contributors' section
2020-07-25 13:55:05 +02:00
### Contributors
* [birger](https://codeberg.org/birger)
* [cherti](https://codeberg.org/cherti)
changelog: add new 'unreleased' section
2020-07-23 18:56:47 +02:00
changelog: add index
2020-03-15 11:39:11 +01:00
changelog: prepare for 1.4.2
2020-07-23 18:51:33 +02:00
## 1.4.2
render: bump maximum window title length from 100 to 2048 (bytes) Apparently, the max is ~8K, but lets stay on the safe side.
2020-07-22 21:07:57 +02:00
### Changed
* Maximum window title length from 100 to 2048.
changelog: add new 'unreleased' section
2020-07-22 20:06:07 +02:00
### Fixed
sixel: overwrite: use target sixel's height, not cell height When copying the image data for the left and right parts of the splitted images, use the sixel's height, not the cell height. This fixes a crash when the sixel didn't cover the entire cell height.
2020-07-23 18:13:54 +02:00
* Crash when overwriting a sixel and the row being overwritten did not
cover an entire cell.
sixel: remove sixel-to-be-splitted *before* splitting it This fixes an assertion in debug builds, due to the pre-splitted and splitted sixels overlapping.
2020-07-23 18:15:29 +02:00
* Assertion failure in debug builds when overwriting a sixel image.
sixel: overwrite: use target sixel's height, not cell height When copying the image data for the left and right parts of the splitted images, use the sixel's height, not the cell height. This fixes a crash when the sixel didn't cover the entire cell height.
2020-07-23 18:13:54 +02:00
changelog: prepare or 1.4.1
2020-07-22 20:03:28 +02:00
## 1.4.1
changelog: add a new 'unreleased' section
2020-07-22 19:11:57 +02:00
### Fixed
changelog: prepare or 1.4.1
2020-07-22 20:03:28 +02:00
* Compilation errors in release builds with some combinations of
compilers and compiler flags.
changelog: add a new 'unreleased' section
2020-07-22 19:11:57 +02:00
changelog: prepare for 1.4.0
2020-07-22 18:59:19 +02:00
## 1.4.0
changelog: prepare for the next, unreleased version
2020-05-13 13:22:19 +02:00
### Added
terminfo: add tmux extension 'Sync' - indicates 'Synchronized Updates' support
2020-05-16 14:13:45 +02:00
* `Sync` to terminfo. This is a tmux extension that indicates
_"Synchronized Updates"_ are supported.
changelog: mention addition of '--hold' to footclient
2020-05-26 20:12:53 +02:00
* `--hold` command line option to `footclient`.
input: add key mapping for XKB_KEY_KP_Decimal
2020-06-27 20:03:41 +02:00
* Key mapping for `KP_Decimal`.
terminfo: add remaining keypad keys
2020-06-27 20:05:50 +02:00
* Terminfo entries for keypad keys: `ka1`, `ka2`, `ka3`, `kb1`, `kb3`,
`kc1`, `kc2`, `kc3`, `kp5`, `kpADD`, `kpCMA`, `kpDIV`, `kpDOT`,
`kpMUL`, `kpSUB` and `kpZRO`.
config: add 'blink' option to cursor section in footrc This option controls whether the default cursor should blink or not. The default is to *not* blink.
2020-06-30 17:45:34 +02:00
* **blink** option to `footrc`; a boolean that lets you control
whether the cursor should blink or not by default. Note that
applications can override this.
changelog: add multi-seat support
2020-07-09 09:17:42 +02:00
* Multi-seat support
vt: implement C0::FF - processed in the same way as C0::LF
2020-07-14 09:18:52 +02:00
* Implemented `C0::FF` (form feed)
changelog: document pipe-visible and pipe-scrollback bindings
2020-07-15 17:53:36 +02:00
* **pipe-visible** and **pipe-scrollback** key bindings. These let you
pipe either the currently visible text, or the entire scrollback to
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
external tools ([#29](https://codeberg.org/dnkl/foot/issues/29)). Example:
changelog: use bemenu instead of fuzzel in pipe-visible example
2020-07-15 18:22:40 +02:00
`pipe-visible=[sh -c "xurls | bemenu | xargs -r firefox] Control+Print`
terminfo: add tmux extension 'Sync' - indicates 'Synchronized Updates' support
2020-05-16 14:13:45 +02:00
render: only apply transparency to the default background color
2020-05-16 16:26:52 +02:00
changelog: prepare for the next, unreleased version
2020-05-13 13:22:19 +02:00
### Changed
render: only apply transparency to the default background color
2020-05-16 16:26:52 +02:00
* Background transparency to only be used with the default background
color.
changelog: make it easier to read
2020-06-29 21:52:32 +02:00
* Copy-to-clipboard/primary-selection to insert a line break if either
selection: copy: insert line break if either cell is empty
2020-05-16 22:29:53 +02:00
the last cell on the previous line or the first cell on the next
line is empty.
term: scrolling: clamp number of rows to number of rows in scrolling region
2020-05-16 23:44:54 +02:00
* Number of lines to scroll is now always clamped to the number of
lines in the scrolling region..
changelog: is -> are
2020-05-21 20:28:26 +02:00
* New terminal windows spawned with `ctrl`+`shift`+`n` are no longer
term: don't double fork new terminal windows Instead, register their PIDs with the new reaper module and let it handle them.
2020-05-21 20:17:29 +02:00
double forked.
changelog: language
2020-06-14 09:14:04 +02:00
* Unicode combining character overflow errors are only logged when
unicode combining: don't log overflow errors unless LOG_ENABLE_DBG == 1
2020-06-09 17:31:58 +02:00
debug logging has been enabled.
osc: set color: update both grids, but exclude scrollback
2020-06-14 09:34:46 +02:00
* OSC 4 (_Set Color_) now updates already rendered cells, excluding
scrollback.
term: use 'left_ptr' instead of 'hand2' as cursor when client is mouse grabbing
2020-06-29 21:51:53 +02:00
* Mouse cursor from `hand2` to `left_ptr` when client is capturing the
mouse.
sixel: destroy all sixels when font size is decreased If changing the font size causes the cell size to decrease, either horizontally or vertically (or both), then delete all sixels since the grid space they allocated no longer is enough to hold the images.
2020-06-29 21:53:29 +02:00
* Sixel images are now removed when the font size is **decreased**.
csi: '\E[0 q' resets the cursor style to the default, not '\E[2 q' Also update 'Se' capability in the terminfo, to reflect this.
2020-06-30 17:43:43 +02:00
* `DECSCUSR` (_Set Cursor Style_, `CSI Ps SP q`) now uses `Ps=0`
instead of `Ps=2` to reset the style to the user configured default
style. `Ps=2` now always configures a _Steady Block_ cursor.
* `Se` terminfo capability from `\E[2 q` to `\E[ q`.
changelog: hollow cursor is now based on keyboard focus, not visual focus
2020-07-11 18:43:50 +02:00
* Hollow cursor to be drawn when window has lost _keyboard_ focus
rather than _visual_ focus.
render: only apply transparency to the default background color
2020-05-16 16:26:52 +02:00
scrolling: fix crash when offset was exactly at the wrap-around When making sure we don't scroll past the scrollback history, and the current offset was exactly at the wrap around, the new view port was set to offset+1, which in this particular case meant outside the valid row numbers.
2020-05-19 18:51:56 +02:00
changelog: prepare for the next, unreleased version
2020-05-13 13:22:19 +02:00
### Fixed
selection: don't automatically no-op operations if selection isn't enabled When the client is capturing the mouse, selection can only be done by holding done shift. This is why a lot of selection functions are no-ops if selection isn't currently enabled. However, there are many cases where we actually need to modify the selection. In particular, selection_cancel(). Thus, only check for enabled selection when we're dealing with user input. Bonus: this also fixes a bug where an ongoing selection were finalized as soon as the user released shift, even if he was still holding down the mouse button.
2020-05-16 21:09:59 +02:00
* Do not stop an ongoing selection when `shift` is released. When the
changelog: 'capturing mouse events' -> 'capturing the mouse'
2020-06-29 21:52:50 +02:00
client application is capturing the mouse, one must hold down
selection: don't automatically no-op operations if selection isn't enabled When the client is capturing the mouse, selection can only be done by holding done shift. This is why a lot of selection functions are no-ops if selection isn't currently enabled. However, there are many cases where we actually need to modify the selection. In particular, selection_cancel(). Thus, only check for enabled selection when we're dealing with user input. Bonus: this also fixes a bug where an ongoing selection were finalized as soon as the user released shift, even if he was still holding down the mouse button.
2020-05-16 21:09:59 +02:00
`shift` to start a selection. This selection is now finalized only
when the mouse button is released - not as soon as `shift` is
released.
changelog: language
2020-06-14 09:14:04 +02:00
* Selected cells did not appear selected if programmatically modified.
scrolling: fix crash when offset was exactly at the wrap-around When making sure we don't scroll past the scrollback history, and the current offset was exactly at the wrap around, the new view port was set to offset+1, which in this particular case meant outside the valid row numbers.
2020-05-19 18:51:56 +02:00
* Rare crash when scrolling and the new viewport ended up **exactly**
on the wrap around.
selection: handle viewport wrap around correctly When the viewport wraps around, the selection points may be "incorrect".
2020-05-19 18:49:42 +02:00
* Selection handling when viewport wrapped around.
changelog: slave -> client
2020-06-29 21:53:07 +02:00
* Restore signal mask in the client process.
slave: set IUTF8
2020-05-26 18:18:11 +02:00
* Set `IUTF8`.
selection: don't allow only half of double-width characters to be selected
2020-06-02 18:21:39 +02:00
* Selection of double-width characters. It is no longer possible to
select half of a double-width character.
render: draw hollow block cursor on top of the character, not the opposite
2020-06-02 18:22:55 +02:00
* Draw hollow block cursor on top of character.
changelog: slave -> client
2020-06-29 21:53:07 +02:00
* Set an initial `TIOCSWINSZ`. This ensures clients never read a
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
`0x0` terminal size ([#20](https://codeberg.org/dnkl/foot/issues/20)).
changelog: mention fix for glyphs overflowing into surrounding cells
2020-06-03 17:40:55 +02:00
* Glyphs overflowing into surrounding cells
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#21](https://codeberg.org/dnkl/foot/issues/21)).
csi: \E[3J: reset render.last_cursor.row if necessary This fixes a crash that occurred when the last rendered cursor cell had scrolled off screen, and \E[3J (clear scrollback) was executed.
2020-06-09 17:32:34 +02:00
* Crash when last rendered cursor cell had scrolled off screen and
`\E[J3` was executed.
osc: don't assert on \E]4 being followed by a ';' This fixes a crash (in debug builds) that could be triggered by e.g. cat:ing /dev/urandom.
2020-06-09 17:33:26 +02:00
* Assert (debug builds) when an `\e]4` OSC escape was not followed by
a `;`.
changelog: group sixel related changes toghether
2020-06-29 21:57:01 +02:00
* Window title always being set to "foot" on reset.
* Terminfo entry `kb2` (center keypad key); it is now set to `\EOu`
(which is what foot emits) instead of the incorrect value `\EOE`.
Codespell fixes
2023-10-03 14:11:55 +02:00
* Palette reuse in sixel images. Previously, the palette was reset
sixel: do not reset palette after each image A client can re-use the palette between images. Resetting the palette breaks this. Now we initialize the palette on demand, and resets it when the palette size is changed (by the client).
2020-06-10 18:36:54 +02:00
after each image.
Fix typos
2020-08-15 23:29:38 +02:00
* Do not auto-resize a sixel image for which the client has specified
sixel: if the client has specified a size, do not change that We used to auto-resize images to always be a multiple of 6. This is incorrect. The client may, for example, have specified a size to align the image to a cell boundary, which may not be a multiple of 6. Furthermore, in e.g. Jexer, which splits up an image into stripes, that the next image would "overwrite" the previous one. Since the next image was started on a cell row that the previous image had overflowed into.
2020-06-11 18:40:52 +02:00
a size. This fixes an issue where an image would incorrectly
overflow into the cell row beneath.
changelog: sixel images can now be printed on
2020-06-27 14:27:49 +02:00
* Text printed, or other sixel images drawn, on top of a sixel image
no longer erases the entire image, only the part(s) covered by the
new text or image.
changelog: group sixel related changes toghether
2020-06-29 21:57:01 +02:00
* Sixel images being erased when printing text next to them.
reflow: ensure sixels are correctly sorted when re-inserted And make sure to remove re-inserted sixels that has wrapped around the scrollback (this may happen when the window size decreases).
2020-06-29 21:59:40 +02:00
* Sixel handling when resizing window.
scroll: destroy scrolled out sixels before scroll is applied The logic that breaks out of sixel loops does not work for rows that has already wrapped around. Thus, we need to destroy sixels that are about to be scrolled out *before* we actually scroll. Since this is the *only* time we destroy sixels (instead of overwriting it), rename the sixel functions. And, since they now do a very specific thing, they can be greatly simplified (and thus faster).
2020-06-29 22:01:02 +02:00
* Sixel handling when scrollback wraps around.
changelog: mention fix for 'too many wl_surface_damage_buffer()' calls
2020-07-13 15:10:03 +02:00
* Foot now issues much fewer `wl_surface_damage_buffer()` calls
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#35](https://codeberg.org/dnkl/foot/issues/35)).
vt: process C0::VT the same way we process C0::LF Previously, C0::VT was implemented as a simple 'cursor down'. I.e. it would behave as LF **until** it reached the bottom of the screen, where instead of scrolling, it became a no-op. See https://vt100.net/docs/vt102-ug/chapter5.html
2020-07-14 09:15:15 +02:00
* `C0::VT` to be processed as `C0::LF`. Previously, `C0::VT` would
only move the cursor down, but never scroll.
changelog: prefix all C0 names with 'C0::'
2020-07-14 11:33:30 +02:00
* `C0::HT` (_Horizontal Tab_, or `\t`) no longer clears `LCF` (_Last
term: linefeed: explicitly clear LCF LF should always clear LCF. Previously, it was done implicitly in term_cursor_down(). I.e it was cleared as long as the cursor wasn't at the bottom of the scrolling region
2020-07-14 10:49:44 +02:00
Column Flag_).
changelog: prefix all C0 names with 'C0::'
2020-07-14 11:33:30 +02:00
* `C0::LF` now always clears `LCF`. Previously, it only cleared it
when the cursor was **not** at the bottom of the scrolling region.
csi: IND+RI now clears LCF
2020-07-14 10:52:15 +02:00
* `IND` and `RI` now clears `LCF`.
changelog: 'not' -> 'now'
2020-07-14 12:48:16 +02:00
* `DECAWM` now clears `LCF`.
term: print: force line-wrap if a multi-column character does not fit on current line
2020-07-14 10:58:57 +02:00
* A multi-column character that does not fit on the current line is
now printed on the next line, instead of only printing half the
character.
added font-size limitting to changelog
2020-07-15 11:05:22 +02:00
* Font size can no longer be reduced to negative values
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#38](https://codeberg.org/dnkl/foot/issues/38)).
changelog: sixel images can now be printed on
2020-06-27 14:27:49 +02:00
changelog: language
2020-06-14 09:14:04 +02:00
changelog 1.3.0
2020-05-13 13:09:12 +02:00
## 1.3.0
meson/PKGBUILD/changelog: prepare for 1.2.0
2020-03-06 20:11:50 +01:00
### Added
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: user configurable key- and mouse bindings
2020-03-12 10:23:59 +01:00
* User configurable key- and mouse bindings. See `man 5 foot` and the
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
example `footrc` ([#1](https://codeberg.org/dnkl/foot/issues/1))
conf: rename 'startup-mode' to 'initial-window-mode'
2020-03-28 12:04:00 +01:00
* **initial-window-mode** option to `footrc`, that lets you control
the initial mode for each newly spawned window: _windowed_,
_maximized_ or _fullscreen_.
changelog: one entry for conf-option + command line option changes
2020-04-24 20:40:33 +02:00
* **app-id** option to `footrc` and `--app-id` command line option,
that sets the _app-id_ property on the Wayland window.
* **title** option to `footrc` and `--title` command line option, that
sets the initial window title.
changelog: right mouse button extends current selection
2020-04-04 12:08:46 +02:00
* Right mouse button extends the current selection.
changelog: use backticks for full escape sequence too, and shorten entry
2020-04-25 23:07:47 +02:00
* `CSI Ps ; Ps ; Ps t` escape sequences for the following parameters:
changelog: CSI 13;2t and CSI 14t have also been implemented
2020-04-25 23:09:10 +02:00
`11t`, `13t`, `13;2t`, `14t`, `14;2t`, `15t`, `19t`.
unicode-combine: simplify - remove -Dunicode-precompose option Since the pre-composing functionality is now part of fcft, it makes little sense to have a compile time option - there's no size benefit to be had. Furthermore, virtually all terminal emulators do pre-composing (alacritty being an exception), this really isn't that controversial.
2020-05-10 17:10:33 +02:00
* Unicode combining characters.
changelog: spaces
2020-03-14 23:28:21 +01:00
config: add 'blink' option to cursor section in footrc This option controls whether the default cursor should blink or not. The default is to *not* blink.
2020-06-30 17:45:34 +02:00
Merge branch 'releases/1.2'
2020-03-14 23:21:56 +01:00
### Changed
completions: zsh: don't strip spaces from font name completions
2020-03-15 12:31:42 +01:00
* Spaces no longer removed from zsh font name completions.
changelog: mention change of default key binding for spaw-terminal
2020-03-17 21:12:37 +01:00
* Default key binding for _spawn-terminal_ to ctrl+shift+n.
changelog: mention renderer performance improvements with scrolling
2020-03-29 11:32:38 +02:00
* Renderer is now much faster with interactive scrolling
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#4](https://codeberg.org/dnkl/foot/issues/4))
changelog: mention memfd sealing failures not being fatal errors fix
2020-04-03 20:17:47 +02:00
* memfd sealing failures are no longer fatal errors.
changelog: selection is no longer cleared on resize
2020-04-17 22:43:28 +02:00
* Selection to no longer be cleared on resize.
changelog: current output's subpixel order is preferred over FontConfig
2020-04-22 19:52:28 +02:00
* The current monitor's subpixel order (RGB/BGR/V-RGB/V-BGR) is
preferred over FontConfig's `rgba` property. Only if the monitor's
subpixel order is `unknown` is FontConfig's `rgba` property used. If
the subpixel order is `none`, then grayscale antialiasing is
used. The subpixel order is ignored if antialiasing has been
disabled.
term: load primary fonts in parallel Use four threads to load the four primary font variants - normal, bold, italic and bold italic. This speeds up initial startup, and reloading of fonts on a DPI change.
2020-04-28 22:07:02 +02:00
* The four primary font variants (normal, bold, italic, bold italic)
are now loaded in parallel. This speeds up both the initial startup
changelog: grammar
2020-06-30 17:46:25 +02:00
time, as well as DPI changes.
main/client: be POSIXLY_CORRECT when parsing command line This means command line parsing stops when it encounters the first nonoption argument. The result is that one no longer need to use '--' to ensure arguments are passed to the shell/command, instead of parsed by foot. That is, instead of foot -- sh -c true one can now do foot sh -c true Arguments to foot *must* go before the command: foot --fullscreen sh -c true
2020-05-08 18:43:03 +02:00
* Command line parsing no longer tries to parse arguments following
the command-to-execute. This means one can now write `foot sh -c
true` instead of `foot -- sh -c true`.
completions: zsh: don't strip spaces from font name completions
2020-03-15 12:31:42 +01:00
Merge branch 'releases/1.2'
2020-03-14 23:21:56 +01:00
### Removed
changelog: spaces
2020-03-14 23:28:21 +01:00
Merge branch 'releases/1.2'
2020-03-14 23:21:56 +01:00
* Keyboard/pointer handler workarounds for Sway 1.2.
changelog: spaces
2020-03-14 23:28:21 +01:00
Merge branch 'releases/1.2'
2020-03-14 23:21:56 +01:00
### Fixed
changelog: spaces
2020-03-14 23:28:21 +01:00
Merge branch 'releases/1.2'
2020-03-14 23:21:56 +01:00
* Sixel images moved or deleted on window resize.
alt-screen: use a custom 'saved' cursor when switching to alt screen This fixes an issue where we failed to restore the cursor correctly when exiting from the alternate screen, if the client had sent escapes to save the cursor position while inside the alternate screen. This was because we used the *same* storage for saving the cursor position through escapes, as for saving it when entering the alternate screen. Fix by using a custom variable dedicated to normal <--> alt screen switching.
2020-03-16 12:00:25 +01:00
* Cursor sometimes incorrectly restored on exit from alternate screen.
render: render non-block cursors after rendering the glyph + decorations This fixes an issue where an 'underline' cursor wasn't visible on underlined text - the cursor was rendered first, and then shadowed by the text underline.
2020-03-17 11:47:47 +01:00
* 'Underline' cursor being invisible on underlined text.
render: resize: update saved 'normal' cursor if we're in alt screen When resizing in alt mode, we never updated the saved 'normal' cursor. This meant that when we exited alt mode, the cursor would be positioned where it was in the old pre-resize/reflow grid. Now, we update the saved cursor in the same way we update visible cursor. The result is that when we exit the alt screen, the cursor is restored to the same coordinates it would have been updated to had the resize been done in the 'normal' screen.
2020-03-22 11:14:56 +01:00
* Restored cursor position in 'normal' screen when window was resized
while in 'alt' screen.
changelog: mention OSC 7 hostname validation fix
2020-04-03 20:16:56 +02:00
* Hostname in OSC 7 URI not being validated.
changelog: osc 4 multiple 'c;spec' pairs
2020-04-04 14:31:46 +02:00
* OSC 4 with multiple `c;spec` pairs.
changelog: alt+return now emits ESC \r
2020-04-08 17:39:54 +02:00
* Alt+Return to emit "ESC \r".
input: slow trackpad scrolling now eventually scroll a line Before, we converted each axis event's scroll amount to an integer and scrolled that many lines. However, axis events are speed sensitive - very slow scrolling will result in events with a scroll amount that is < 1.0. For us, this meant we never scrolled a single line. You could slow scroll all day if you wanted, and still we would never scroll a single line. Fix this by aggregating the scroll amount from axis events until the scroll amount is > 1.0, and then scroll.
2020-04-10 18:43:29 +02:00
* Trackpad sloooow scrolling to eventually scroll a line.
term: reset: plug memory leak In reset, we allocated new rows for all the currently visible lines. We did **not** however, free the 'old' rows. Fix by not explicitly allocating new rows, but instead allocating uninitialized rows when needed, and then explicitly erasing the row. If there already was a row allocated, it is simply erased. If there wasn't, the a new line is malloc:ed, and then erased.
2020-04-13 11:42:10 +02:00
* Memory leak in terminal reset.
changelog: cursor coordinates are now translated on resize
2020-04-17 20:49:09 +02:00
* Translation of cursor coordinates on resize
osc: fix scaling of RGB formatted color specifiers
2020-05-02 23:07:26 +02:00
* Scaling color specifiers in OSC sequences.
osc: fix 'OSC 12 ?' to return the cursor color, not the cursor text color
2020-05-02 22:58:30 +02:00
* `OSC 12 ?` to return the cursor color, not the cursor's text color.
osc: OSC 12: mimic xterm - a color value of 0 means use inverted fg/bg
2020-05-02 22:58:50 +02:00
* `OSC 12;#000000` to configure the cursor to use inverted
foreground/background colors.
slave: configure pts to be the controlling terminal of the forked process
2020-05-13 13:04:52 +02:00
* Call `ioctl(TIOCSCTTY)` on the pts fd in the slave process.
Revert "term: print: line-wrap multi-column characters instead of cutting them in half" This reverts commit 8448296bb3c0fa96f5af5cb7ec563bb0c7e99093. Applications need to be multi-column character aware anyway, and they should deal with this.
2020-05-09 12:04:55 +02:00
changelog: spaces
2020-03-14 23:28:21 +01:00
meson/PKGBUILD: bump version to 1.2.3
2020-03-15 11:28:01 +01:00
## 1.2.3
### Fixed
* Forgot to version bump 1.2.2
changelog: update
2020-03-09 21:11:41 +01:00
## 1.2.2
meson/PKGBUILD/changelog: prepare for 1.2.0
2020-03-06 20:11:50 +01:00
### Changed
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: update
2020-03-09 21:11:41 +01:00
* Changed icon name in `foot.desktop` and `foot-server.desktop` from
_terminal_ to _utilities-terminal_.
* `XDG_SESSION_ID` is now included in the server/daemon default socket
path.
changelog: spaces
2020-03-14 23:28:21 +01:00
meson/PKGBUILD/changelog: prepare for 1.2.0
2020-03-06 20:11:50 +01:00
### Fixed
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: updated to mention fix for #3 I really need to learn to update the changelog **with** the fix...
2020-03-10 18:17:14 +01:00
* Window size doubling when moving window between outputs with
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
different scaling factors ([#3](https://codeberg.org/dnkl/foot/issues/3)).
changelog: mention fix for #5
2020-03-11 20:18:47 +01:00
* Font being too small on monitors with fractional scaling
Revert "changelog: convert all issue links to reference links in the 1.12.0 release" This reverts commit 6652a836adb26ef55789bbd23113b158090451fd. We only added the actual links to the 1.12.0 release, meaning all other issue hyperlinks broke.
2022-04-22 20:02:15 +02:00
([#5](https://codeberg.org/dnkl/foot/issues/5)).
changelog: updated to mention fix for #3 I really need to learn to update the changelog **with** the fix...
2020-03-10 18:17:14 +01:00
meson/PKGBUILD/changelog: prepare for 1.2.0
2020-03-06 20:11:50 +01:00
meson/PKGBUILD/changelog: bump to 1.2.1
2020-03-06 21:21:34 +01:00
## 1.2.1
### Fixed
changelog: spaces
2020-03-14 23:28:21 +01:00
meson/PKGBUILD/changelog: bump to 1.2.1
2020-03-06 21:21:34 +01:00
* Building AUR package
meson/PKGBUILD/changelog: prepare for 1.2.0
2020-03-06 20:11:50 +01:00
## 1.2.0
changelog: add all major changes for 1.2.0
2020-03-06 20:10:27 +01:00
changelog: template
2020-03-06 19:45:04 +01:00
### Added
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: add all major changes for 1.2.0
2020-03-06 20:10:27 +01:00
* Run-time text resize using ctrl-+, ctrl+- and ctrl+0
* Font size adjusts dynamically to outputs' DPI
* Reflow text when resizing window
* **pad** option to `footrc`
* **login-shell** option to `footrc` and `--login-shell` command line
option
* Client side decorations (CSDs). This finally makes foot usable on
GNOME.
* Sixel graphics support
* OSC 12 and 112 escape sequences (set/reset text cursor color)
* REP CSI escape sequence
* `oc` to terminfo
* foot-server.desktop file
* Window and cell size reporting escape sequences
* `--hold` command line option
* `--print-pid=FILE|FD` command line option
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: template
2020-03-06 19:45:04 +01:00
### Changed
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: add all major changes for 1.2.0
2020-03-06 20:10:27 +01:00
* Subpixel antialiasing is only enabled when background is opaque
* Meta/alt ESC prefix can now be disabled with `\E[?1036l`. In this
mode, the 8:th bit is set and the result is UTF-8 encoded. This can
also be disabled with `\E[1024l` (in which case the Alt key is
effectively being ignored).
* terminfo now uses ST instead of BEL as OSC terminator
* Logging to print to stderr, not stdout
* Backspace now emits DEL (^?), and ctrl+backspace emits BS (^H)
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: template
2020-03-06 19:45:04 +01:00
### Removed
changelog: spaces
2020-03-14 23:28:21 +01:00
changelog: add all major changes for 1.2.0
2020-03-06 20:10:27 +01:00
* '28' from DA response
Reference in a new issue Copy permalink