aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
| * config: remove debug loggingDaniel Eklöf2025-02-05-2/+0
| |
| * tests: config: handle regex key bindingsDaniel Eklöf2025-02-05-8/+28
| |
| * doc: foot.ini: document custom regular expressionsDaniel Eklöf2025-02-05-1/+57
| |
| * foot.ini: improve documentation of custom regexDaniel Eklöf2025-02-05-0/+8
| |
| * config+url: add support for user-defined regex patternsDaniel Eklöf2025-02-05-48/+310
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Users can now define their own regex patterns, and use them via key bindings: [regex:foo] regex=foo(bar)? launch=path-to-script-or-application {match} [key-bindings] regex-launch=[foo] Control+Shift+q regex-copy=[foo] Control+Mod1+Shift+q That is, add a section called 'regex:', followed by an identifier. Define a regex and a launcher command line. Add a key-binding, regex-launch and/or regex-copy (similar to show-urls-launch and show-urls-copy), and connect them to the regex with the "[regex-name]" syntax (similar to how the pipe-* bindings work).
| * xmalloc: calling xrealloc() or xreallocarray() with a 0-size is UB in C23Daniel Eklöf2025-02-05-2/+4
| | | | | | | | And likely to in future POSIX too.
| * url-mode: regex: make sure there's always room for the NULL terminatorDaniel Eklöf2025-02-05-1/+2
| |
| * foot.ini+doc: add default value of url.regexDaniel Eklöf2025-02-05-2/+4
| |
| * url-mode+config: wip: add url.regex optionDaniel Eklöf2025-02-05-54/+76
| |
| * config: remove url.{uri-characters,protocols}Daniel Eklöf2025-02-05-178/+7
| |
| * url-mode: wip: regex: tweak debug log messageDaniel Eklöf2025-02-05-2/+2
| |
| * url-mode: wip: regex: mention changes from original regexDaniel Eklöf2025-02-05-1/+5
| |
| * url-mode: wip: regex: don't allow {}, do allow matched []Daniel Eklöf2025-02-05-3/+7
| |
| * url-mode: wip: more work on regex matchingDaniel Eklöf2025-02-05-286/+75
| | | | | | | | Remove the old auto-detection and instead use the regex matches.
| * url-mode: wip: convert to regex matching for auto-detectionDaniel Eklöf2025-02-05-0/+145
| |
| * grid: typoDaniel Eklöf2025-02-05-1/+2
| |
| * xmalloc: add xreallocarray()Daniel Eklöf2025-02-05-0/+8
|/
* box-drawings: handle architecture with soft-floatThomas Bonnefille2025-02-05-3/+1
| | | | | | | | | | | | Currently, architecture using soft-floats doesn't support instructions FE_INVALID, FE_DIVBYZERO, FE_OVERFLOW and FE_UNDERFLOW and so building on those architectures results with a build error. As the sqrt math function should set errno to EDOM if an error occurs, fetestexcept shouldn't be mandatory. This commit removes the float environment error handling. Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
* server: don't instantiate a client without a monitorsewn2025-02-05-0/+6
|
* term: ptmx pause/resume: don't modify the FDM if ptmx has been closedDaniel Eklöf2025-02-05-0/+4
| | | | | This fixes error message spam when resizing a terminal window executed with --hold, and where the client application has terminated.
* Revert "forgejo: server/standalone: what happens when we set required=true?"Daniel Eklöf2025-02-04-2/+0
| | | | This reverts commit 70aa033d7912b978264d035b095b25090ff00f07.
* forgejo: server/standalone: what happens when we set required=true?Daniel Eklöf2025-02-04-0/+2
|
* forgejo: remind user to sanitize pasted configDaniel Eklöf2025-02-04-1/+1
|
* forgejo: server/standalone: tweak wordingDaniel Eklöf2025-02-04-3/+3
|
* forgejo: issue happens in foot --server, standalone, or both?Daniel Eklöf2025-02-04-0/+8
|
* forgejo: ask user to provide distro *version*, when applicableDaniel Eklöf2025-02-04-2/+2
|
* input: match unshifted key-bindings before shiftedDaniel Eklöf2025-01-31-42/+42
| | | | | | | | | | | | | | | | | | | | That is, try to match e.g. Control+shift+a, before trying to match Control+A. In most cases, order doesn't matter. There are however a couple of symbols where the layout consumes the shift-modifier, and the generated symbol is the same in both the shifted and unshifted form. One such example is backspace. Before this patch, key-bindings with shift-backspace would be ignored, if there were another key-binding with backspace. So, for example, if we had one key-binding with Control+Backspace, and another with Control+Shift+Backspace, the latter would never trigger, as we would always match the first one. By checking for unshifted matches first, we ensure Control+Shift+Backspace does match.
* input: ignore key-bindings without modifiers when matching untranslated/rawDaniel Eklöf2025-01-31-6/+6
| | | | | | | | | When matching the unshifted symbol, or the raw key code, ignore all key bindings that don't have any modifiers. This fixes an issue where it was impossible to enter (some of the) numbers on the keypad, **if** there was a key-binding for e.g. KP_Page_Up, or KP_Page_Down.
* key-bindings: add keypad variants to existing default key-bindingsDaniel Eklöf2025-01-31-10/+18
|
* input: close fd on no/unrecognized keymap formatAttila Fidan2025-01-30-0/+4
|
* forgejo: config: render as .ini, instead of the default markdownDaniel Eklöf2025-01-27-0/+1
|
* forgejo: remove "e.g." from placeholder textDaniel Eklöf2025-01-27-1/+1
|
* forgejo: add optional field for terminal multiplexersDaniel Eklöf2025-01-27-3/+9
|
* doc: foot.ini: describe key binding match logicDaniel Eklöf2025-01-27-2/+31
|
* key-bindings: try all bindings in translated mode before matching untranslated, and then finally rawDaniel Eklöf2025-01-27-9/+52
| | | | | | | | | | | | | | | | | | | When trying to match key bindings, we do three types of matching: * Match the _translated_ symbol (e.g. Control+C) * Match the _untranslated_ symbol (e.g. Control+Shift+c) * Match raw keyboard codes This was done for *each* key binding. This meant we sometimes matched a keybinding in raw mode, even though there was a translated/untranslated binding that would match it too. All depending on the internal order of the key binding list. This patch changes it, so that we first try all bindings in translated mode, then all bindings in untranslated mode, and finally all bindings in raw mode. Closes #1929
* forgejo: application -> application(s)Daniel Eklöf2025-01-27-1/+1
|
* forgejo: add optional field for shell/TUIDaniel Eklöf2025-01-27-0/+6
|
* config: fix memory leak on e.g. "not a valid XKB key name" errorsDaniel Eklöf2025-01-27-5/+4
|
* render: resize: configure with only one dimension being zeroDaniel Eklöf2025-01-26-15/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The protocol states: If the width or height arguments are zero, it means the client should decide its own window dimension. This may happen when the compositor needs to configure the state of the surface but doesn't have any information about any previous or expected dimension. The wording is a bit ambiguous; does it mean we should set *both* width and height to values we choose, even if only one dimension is zero in the configure event? Or does it mean that we should choose the value for the dimension that is zero in the configure event? Regardless, it's pretty clear that it does *not* mean we should *only* choose width and height if *both* dimensions are zero in the configure event. This is foot's behavior before this patch, meaning if only one of them is zero, foot assumed the compositor wanted us to set the width (or height) to zero... Change this, so that we now choose value for the "missing" dimension, but do use the compositor provided value for the other dimension. Closes #1925 Relevant issues: * https://gitlab.freedesktop.org/wayland/wayland-protocols/-/issues/155 * https://github.com/YaLTeR/niri/issues/1050
* grid: reflow: regression: remove (truncate) SPACER cells at the end of lineDaniel Eklöf2025-01-25-1/+6
| | | | | | | | | | | | | | | | | | | | When printing a double-width glyph at the end of the line, it will get pushed to the next line if there's only one cell left on the current line. That last cell on the current line is filled with a SPACER value. When reflowing the text, the SPACER cell should be "removed", so that the double-width glyph continues directly after the text on the previous line. 9567694bab7149afbb4e4fcc4c754272a8d25aba fixed an issue where reflowing e.g. neofetch output incorrectly removed spaces between the logo, and the system info. But also introduced a regression where SPACER values no longer are removed. This patch tries to fix it, by adding back empty cells, but NOT SPACER cells.
* changelog: cwd > 1024 charsDaniel Eklöf2025-01-24-0/+3
|
* client: port bfabc5450b3a01c7d701809b3cf6158220ea289e to footclientDaniel Eklöf2025-01-24-1/+1
|
* fix infinite loop/oom when cwd longer then 1024camel-cdr2025-01-24-1/+1
| | | | | | The code reads cwd into a buffer, which is expanded while errno is ERANGE, with the intent of growing the buffer until the path fits. While getcwd will set errno on error, it will not reset it once the path fits into the buffer. So to not get an infinite loop once errno is ERANGE, we need to make sure to reset errno, such that the loop behaves as expected.
* config: check for FcNameUnparse() failureDaniel Eklöf2025-01-24-0/+5
|
* input: kitty: refactor, try to simplify and be less confusingDaniel Eklöf2025-01-22-47/+60
| | | | | | | | | | Use better named variables while juggling the shifted vs. unshifted key codes. Switch to variable names appropriate for the kitty keyboard protocol once we have all the unshifted, shifted and base key codes done. It's not until then we can decide which key code to use as the main key, and whether or not to report the alternate key code.
* input: kitty: add more test casesDaniel Eklöf2025-01-22-0/+46
|
* input: kitty: only set 'alternate' if the "unshifted" code is printableDaniel Eklöf2025-01-22-19/+26
| | | | | Fixes a regression where alt+backspace was reported as ^[[8:127;3u instead of ^[[127;3u.
* input: codespell: indiciates -> indicatesDaniel Eklöf2025-01-22-2/+2
|
* shm: codespell: re-using -> reusingDaniel Eklöf2025-01-22-1/+1
|
* input: kitty: add initial unit testDaniel Eklöf2025-01-22-0/+229
| | | | | | | | Test a couple of key combos from the se and de(neo) layouts. This unit test isn't intended to test _all_ key combinations, for all kitty flag combinations, but to be more of a regression test - whenever we discover a buggy, weird combo, add it here.
* input: kitty: improve handling of alternate+base keys even moreDaniel Eklöf2025-01-20-33/+41
| | | | | | | | | | | | | | | | * Always do a base key lookup. Before this, we didn't do that if we matched the XKB sym to a lookup table entry (i.e. keypads, cursor keys etc.) * Try to retrieve the unshifted symbol also when we matched the symbol to a lookup table entry. When successful, we now report an alternate key for keypad and cursor keys; before this patch, we only did that for keys that didn't have an entry in the lookup table (i.e. ASCII chars etc). This improves compatibility with kitty (and the kitty keyboard protocol) in more corner cases. One particular example is the neo keyboard layout, where part of the regular keys act as keypad keys when num-lock is active.
* input: kitty: fix alternate codepoint sometimes not being reportedDaniel Eklöf2025-01-20-23/+9
| | | | | | | | | | | | | | | | | | | | | When alternate key reporting is enabled (i.e. when we're supposed to report the shifted key along with the unshifted key), we try to figure out whether the key really is shifted or not (and thus which xkb keysym to use for the unshifted and shifted keys in the escape). This was done by getting the layout's *all* modifier combinations that produce the shifted keysym, and if any of of them contained a modifier that isn't supported by the kitty protocol, the shifted and unshifted keys are derived from the same keysym. This is to ensure we handle things like AltGr-combos correctly. The issue is, since there may be more than one modifier combination generating the shifted keysym, we may end up using the wrong keysym just because _another_ combination set contains modifiers not supported by the kitty protocol. What we're interrested in is whether the *pressed* set of modifiers contains such modifiers. Closes #1918
* vt: combining chars: ensure 'key' is within rangeDaniel Eklöf2025-01-18-0/+2
| | | | | | When there's a key collision, we increment the key and check again. When doing this, we need to ensure the key is withing range, and wrap around to 0 if the key value is too large.
* Merge branch 'releases/1.20'Daniel Eklöf2025-01-18-7/+20
|\
| * changelog: move utf8proc entry to correct release1.20.2releases/1.20Daniel Eklöf2025-01-18-3/+3
| |
| * changelog: add back entry to 1.20.1, removed in de3becef96f30b96f0fceddf73805c3951ccb59fDaniel Eklöf2025-01-18-0/+3
| |
| * meson: bump version to 1.20.2Daniel Eklöf2025-01-18-1/+1
| |
| * changelog: prepare for 1.20.2Daniel Eklöf2025-01-18-6/+5
| |
| * forgejo: bugs: short explanation of what an IME isDaniel Eklöf2025-01-18-2/+2
| |
| * forgejo: bugs: config: uppercase description's first letterDaniel Eklöf2025-01-18-1/+1
| |
| * forgejo: bugs: add required field 'config'Daniel Eklöf2025-01-18-0/+7
| | | | | | | | Require all bug submitters to include their foot configs.
| * forgejo: bugs: add required field 'distro'Daniel Eklöf2025-01-18-0/+8
| |
| * term: cursor_refresh(): don't try to dirty the grid if we don't have oneDaniel Eklöf2025-01-18-0/+7
| | | | | | | | | | | | | | | | | | | | | | If the compositor sends a keyboard enter event before our window has been mapped, foot crashes; the enter event triggers a cursor refresh (hollow -> non-hollow block cursor), which crashes since we haven't yet allocated a grid. Fix by no-op:ing the refresh if the window hasn't been configured yet. Closes #1910
| * changelog: colors.flash-alpha=1.0Daniel Eklöf2025-01-18-0/+6
| |
| * Revert "config: don't allow colors.flash-alpha to be 1.0"Alexander Orzechowski2025-01-18-26/+2
| | | | | | | | This reverts commit 56d2c3e990509d18de31e6009e0d0c6254f99b67.
| * terminal: Refresh only overlay when flash expiresAlexander Orzechowski2025-01-18-1/+6
| | | | | | | | | | | | | | If we call render_refresh, that will wait for a callback to the main surface. In the case of a flash, the main surface might not get callbacks if the compositor implements fancy culling optimizations like wlroots wlr_scene compositors such as sway version >=1.10.
| * render: Expose render_overlayAlexander Orzechowski2025-01-18-1/+5
| | | | | | | | | | This function updates the overlay that foot uses. It will be used to update the overlay when the flash effect ends.
| * changelog: 'CSI 21 t' and 'OSC 176 ?' disabledDaniel Eklöf2025-01-18-0/+7
| |
| * doc: ctlseqs: remove 'CSI 21 t'Daniel Eklöf2025-01-18-3/+0
| |
| * osc: ignore 'OSC 176 ?' - report app IDDaniel Eklöf2025-01-18-0/+4
| | | | | | | | | | It's not widely used (don't know _any_ application that uses it), and can be used to trick users to run unwanted commands.
| * csi: ignore 'CSI 21 t' - report window titleDaniel Eklöf2025-01-18-0/+4
| | | | | | | | | | It's not widely used (don't know _any_ application that uses it), and can be used to trick users to run unwanted commands.
| * ci: "meson [options]" is deprecated (do "meson setup [options]" instead)Daniel Eklöf2025-01-18-9/+9
| |
| * changelog: utf8proc.h not foundDaniel Eklöf2025-01-18-0/+3
| |
| * meson: fix dependencies (utf8proc missing in lots of places)Daniel Eklöf2025-01-18-3/+7
| |
| * ci: sr.ht: try to bring up to date, and pull from codebergDaniel Eklöf2025-01-18-1/+2
| |
| * ci: sr.ht: disable x64 (rely on codeberg only)Daniel Eklöf2025-01-18-0/+0
| |
| * changelog: add missing issue refDaniel Eklöf2025-01-18-1/+1
| |
| * changelog: add new 'unreleased' sectionDaniel Eklöf2025-01-18-0/+11
| |
* | features: add +/-system-bell to version outputDaniel Eklöf2025-01-17-3/+15
| |
* | Add support for the new Wayland protocol xdg-system-bellDaniel Eklöf2025-01-17-11/+91
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From the release notes: system bell - allowing e.g. terminal emulators to hand off system bell alerts to the compositor for among other things accessibility purposes The new protocol is used when the new config option bell.system=yes (and the compositor implements the protocol, obviously). The system bell is rung independent of whether the foot window has keyboard focus or not (thus relying on compositor configuration to determine whether anything should be done or not in response to the bell). The new option is enabled by default.
* | forgejo: bugs: short explanation of what an IME isDaniel Eklöf2025-01-10-2/+2
| |
* | forgejo: bugs: config: uppercase description's first letterDaniel Eklöf2025-01-10-1/+1
| |
* | forgejo: bugs: add required field 'config'Daniel Eklöf2025-01-10-0/+7
| | | | | | | | Require all bug submitters to include their foot configs.
* | forgejo: bugs: add required field 'distro'Daniel Eklöf2025-01-10-0/+8
| |
* | term: cursor_refresh(): don't try to dirty the grid if we don't have oneDaniel Eklöf2025-01-09-0/+7
| | | | | | | | | | | | | | | | | | | | | | If the compositor sends a keyboard enter event before our window has been mapped, foot crashes; the enter event triggers a cursor refresh (hollow -> non-hollow block cursor), which crashes since we haven't yet allocated a grid. Fix by no-op:ing the refresh if the window hasn't been configured yet. Closes #1910
* | changelog: colors.flash-alpha=1.0Daniel Eklöf2025-01-09-0/+6
| |
* | Merge branch 'opaque-flash'Daniel Eklöf2025-01-09-28/+13
|\ \
| * | Revert "config: don't allow colors.flash-alpha to be 1.0"Alexander Orzechowski2025-01-09-26/+2
| | | | | | | | | | | | This reverts commit 56d2c3e990509d18de31e6009e0d0c6254f99b67.
| * | terminal: Refresh only overlay when flash expiresAlexander Orzechowski2025-01-09-1/+6
| | | | | | | | | | | | | | | | | | | | | If we call render_refresh, that will wait for a callback to the main surface. In the case of a flash, the main surface might not get callbacks if the compositor implements fancy culling optimizations like wlroots wlr_scene compositors such as sway version >=1.10.
| * | render: Expose render_overlayAlexander Orzechowski2025-01-09-1/+5
|/ / | | | | | | | | This function updates the overlay that foot uses. It will be used to update the overlay when the flash effect ends.
* | Merge branch 'ignore-title-and-app-id-report-queries'Daniel Eklöf2025-01-07-3/+15
|\ \ | | | | | | | | | Related to #1894
| * | changelog: 'CSI 21 t' and 'OSC 176 ?' disabledDaniel Eklöf2025-01-07-0/+7
| | |
| * | doc: ctlseqs: remove 'CSI 21 t'Daniel Eklöf2025-01-07-3/+0
| | |
| * | osc: ignore 'OSC 176 ?' - report app IDDaniel Eklöf2025-01-07-0/+4
| | | | | | | | | | | | | | | It's not widely used (don't know _any_ application that uses it), and can be used to trick users to run unwanted commands.
| * | csi: ignore 'CSI 21 t' - report window titleDaniel Eklöf2025-01-07-0/+4
|/ / | | | | | | | | It's not widely used (don't know _any_ application that uses it), and can be used to trick users to run unwanted commands.
* | ci: "meson [options]" is deprecated (do "meson setup [options]" instead)Daniel Eklöf2025-01-04-9/+9
| |
* | changelog: utf8proc.h not foundDaniel Eklöf2025-01-04-0/+3
| |
* | meson: fix dependencies (utf8proc missing in lots of places)Daniel Eklöf2025-01-04-3/+7
| |
* | ci: sr.ht: try to bring up to date, and pull from codebergDaniel Eklöf2025-01-04-1/+2
| |
* | ci: sr.ht: disable x64 (rely on codeberg only)Daniel Eklöf2025-01-04-0/+0
| |