aboutsummaryrefslogtreecommitdiff
path: root/CHANGELOG.md (follow)
Commit message (Collapse)AuthorAgeLines
* config: value_to_*(): don't overwrite result variable on errorDaniel Eklöf2025-08-25-1/+6
| | | | | | | | | | | Some of the value_to_*() functions wrote directly to the output variable, even when the value was invalid. This often resulted in the an actual configuration option (i.e. a member in the config struct) to be overwritten by an invalid value. For example, -o initial-color-theme=0 would set conf->initial_color_theme to -1, resulting in a crash later, when initializing a terminal instance.
* server/client: add support for sending SIGUSR to footclientDaniel Eklöf2025-08-01-0/+4
| | | | | | | | | | | This patch adds the IPC infrastructure necessary to propagate SIGUSR1/SIGUSR2 from a footclient process to the server process. By targeting a particular footclient instance, only that particular instance changes theme. This is different from when targeting the server process, where all instances change theme. Closes #2156
* changelog: SIGUSR changes in the serverDaniel Eklöf2025-07-30-0/+3
|
* url-mode: for some reason we sorted the label letters before assigning themDaniel Eklöf2025-07-29-0/+5
| | | | | | | Don't do this. Now that we **don't** sort them, the first letter chosen by the user is always assigned to the bottom most URL. Closes #2140 (again)
* changelog: add new 'unreleased' sectionDaniel Eklöf2025-07-23-0/+11
|
* changelog: prepare for 1.23.1Daniel Eklöf2025-07-23-9/+3
|
* osc: color reset: read default color from currently active themeDaniel Eklöf2025-07-22-0/+2
|
* shm: don't set pixman_fmt_without_alpha twiceDaniel Eklöf2025-07-21-0/+4
| | | | | | | | When selecting 16-bit surfaces, we set pixman_fmt_without_alpha twice, and never set pixman_fmt_with_alpha. This caused 10-bit surfaces to be used instead, since it checks if pixman_fmt_with_alpha has been overridden or not.
* main: SIGUSR1 selects the first color theme, SIGUSR2 the secondDaniel Eklöf2025-07-18-0/+4
| | | | | | | | | | Before this patch, SIGUSR1 toggled between [colors] and [colors2]. Now, SIGUSR1 changes to [colors], regardless of what the current color theme is, and SIGUSR2 changes to [colors2]. Closes #2144
* url-mode: assign label keys in reverse orderDaniel Eklöf2025-07-17-0/+8
| | | | | | | The _last_ URL is often the one you are interested in, and with this change, it is always assigned the first (and thus the same) key. Closes #2140
* changelog: add new 'unreleased' sectionDaniel Eklöf2025-07-16-0/+11
|
* changelog: prepare for 1.23.0Daniel Eklöf2025-07-16-3/+8
|
* csi: add '52' to the DA reply, to indicate PSC-52 supportDaniel Eklöf2025-06-10-0/+3
| | | | | | Note: only *copy* is required to be enabled in security.osc52; paste is optional, see https://github.com/contour-terminal/contour/issues/1761#issuecomment-2944492097
* osc: 52: clear selection if the payload is the empty stringDaniel Eklöf2025-06-10-0/+1
|
* main: do a theme toggle upon receiving SIGUSR1Daniel Eklöf2025-06-10-0/+2
| | | | Caveat: in server mode, *all* instances toggle their themes.
* quirks: remove subsurface unmap quirk for SwayDaniel Eklöf2025-06-09-0/+5
| | | | | | | | Sway used to have an issue where unmapping a subsurface did not damage the surface below (https://github.com/swaywm/sway/issues/6960). This has been fixed for quite some time now, so let's remove the quirk.
* conf: pad: add center-when-fullscreen and center-when-maximized-and-fullscreenDaniel Eklöf2025-05-24-0/+4
| | | | | | | | | | | | | | | | | | | | Before this patch, the grid content was *always* centered when the window was maximized or fullscreened, regardless of how the user had configured padding. Now, the behavior is controlled by the 'pad' option. Before this patch, the syntax was pad MxN [center] Now it is pad MxN [center|center-when-fullscreen|center-when-maximized-and-fullscreen] The default is "pad 0x0 center-when-maximized-and-fullscreen", to match current behavior. Closes #2111
* cursor-shape: add 'dnd-ask' and 'all-resize'Daniel Eklöf2025-05-22-0/+1
| | | | | | | | | | | | | | | | | | | | These (non-css) cursor shapes were added to the cursor-shape-v1 protocol in wayland-protocols 1.42. We don't need (or use them at all) internally, but add them to the list we use to translate from shape names to shape enums. This allows users to set a custom shape (via OSC-22), while still using server side cursors (i.e. no need to fallback to client-side cursors). If we try to set a shape not implemented by the server, we get a protocol error and foot exits. This is bad. So, make sure we don't do that: 1. First, we need to explicitly bind v2 if implemented by the server 2. Track the bound version number in the wayland struct 3. When matching shape enum, skip shapes not supported in the currently bound version of the cursor-shape protocol
* wayland: configure: don't commit if we have a pending refreshDaniel Eklöf2025-05-21-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | Currently, if the following occurs: 1. foot has AxB size 2. Compositor sends CxD size 3. foot detects a resize, acks and saves CxD, but doesn't redraw immediately 4. Compositor sends CxD size again (due to a toplevel state array change, for example) Then foot will detect no resize occurred, and will do an "empty" commit immediately. In this particular case that's wrong, since we're effectively acking+committing the initial AxB size. Fix by only doing the immediate commit if there's no size change **and** there's no pending refresh. Note: normally, we'd resize and refresh+commit immediately, but if we're waiting for a frame callback, then the refresh+commit will be delayed (i.e. scheduled). This is what we're checking here. Closes #2105
* libxkbcommon: don't require 1.8.0Daniel Eklöf2025-05-18-0/+3
| | | | | | | | | | The version bump was done since we now use XKB_VMOD_NAME_*; macros added in libxkbcommon 1.8.0. Not all distros have updated libxkbcommon yet (read: Debian). Since it's fairly easy to work around, let's do that. Closes #2103
* csi: when REP:ing a "combining" character, use correct widthDaniel Eklöf2025-05-16-0/+4
| | | | | | | | | | Before this patch, we just called c32width(), which only works on actual codepoints. If the last printed character is a "combining" character, i.e. a key into our lookup table for multi-codepoint graphemes, we need to lookup the grapheme and pick the width from there. See https://gitlab.com/AutumnMeowMeow/jexer/-/issues/119#note_2499712901
* render: refactor to allow setting only selection bg or fgDaniel Eklöf2025-05-05-0/+4
| | | | | | | | | | | | Before this, we only applied custom selection colors, if *both* the selection bg and fg had been set. Since the options are already split up into two separate options, and since it makes sense to at least be able to keep the foreground colors unchanged (i.e. only setting the selection background), let's allow only having one of the selection colors set. Closes #1846
* config: tweak.surface-bit-depth: add support for 16-bit surfacesDaniel Eklöf2025-05-03-0/+5
| | | | | | | | | This adds supports for 16-bit surfaces, using the new PIXMAN_a16b16g16r16 buffer format. This maps to WL_SHM_FORMAT_ABGR16161616 (little-endian). Use the new 16-bit surfaces by default, when gamma-correct-blending=yes.
* osc: restore configured alpha if OSC-11 has no alpha valueDaniel Eklöf2025-05-02-0/+3
| | | | | | When parsing an OSC-11 without an alpha value (i.e. standard OSC-11, not rxvt's extended variant), restore the alpha value from the configuration, rather than keeping whatever the current alpha is.
* Paste URL/regex selection to prompt if key is uppercase.Ryan Roden-Corrent2025-05-01-0/+3
| | | | | | | | | | | | | | | | In copy-regex/show-urls-copy mode, if the last input character was uppercase, copy the selection to the clipboard _and_ paste it. This is useful for taking a file path from a command output:(log, git, test failure, etc.) and using it in another command. This is inspired by the behavior of copy mode in wezterm: https://wezterm.org/quickselect.html I could have made it check every character in the hint, but it seemed fine to assume that if the last character was uppercase, the user wanted this behavior. Closes #1975.
* Merge branch 'releases/1.22'Daniel Eklöf2025-05-01-9/+21
|\
| * changelog: prepare for 1.22.3Daniel Eklöf2025-05-01-8/+3
| |
| * config: tweak.surface-bit-depth now defaults to 'auto'Daniel Eklöf2025-05-01-0/+13
| | | | | | | | | | | | | | | | | | | | | | When set to 'auto', use 10-bit surfaces if gamma-correct blending is enabled, and 8-bit surfaces otherwise. Note that we may still fallback to 8-bit surfaces (without disabling gamma-correct blending) if the compositor does not support 10-bit surfaces. Closes #2082
| * config: gamma-correct-blending: disable by defaultDaniel Eklöf2025-05-01-0/+4
| |
| * changelog: add new 'unreleased' sectionDaniel Eklöf2025-05-01-0/+11
| |
* | config: tweak.surface-bit-depth now defaults to 'auto'Daniel Eklöf2025-05-01-0/+10
| | | | | | | | | | | | | | | | | | | | | | When set to 'auto', use 10-bit surfaces if gamma-correct blending is enabled, and 8-bit surfaces otherwise. Note that we may still fallback to 8-bit surfaces (without disabling gamma-correct blending) if the compositor does not support 10-bit surfaces. Closes #2082
* | config: gamma-correct-blending: disable by defaultDaniel Eklöf2025-05-01-0/+1
| |
* | Merge branch 'releases/1.22'Daniel Eklöf2025-04-30-7/+15
|\|
| * changelog: prepare 1.22.2Daniel Eklöf2025-04-30-9/+3
| |
| * scripts: srgb: use 2.2 gamma TF instead of piece-wise sRGB TFDaniel Eklöf2025-04-30-0/+15
| |
| * changelog: add new 'unreleased' sectionDaniel Eklöf2025-04-30-0/+11
| |
* | scripts: srgb: use 2.2 gamma TF instead of piece-wise sRGB TFDaniel Eklöf2025-04-28-0/+12
| |
* | changelog: mention the new combined dark/light theme filesDaniel Eklöf2025-04-26-0/+7
| |
* | config: add initial-color-theme=1|2Daniel Eklöf2025-04-26-0/+2
| | | | | | | | | | | | | | | | This option selects which color theme to use by default. I.e. at startup, and after a reset. This is useful with combined theme files, where a single file defines e.g. both a dark and light version of the theme.
* | csi: implement private mode 2031 (dark/light mode detection)Daniel Eklöf2025-04-26-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Recognize 'CSI ? 996 n', and respond with - 'CSI ? 997 ; 1 n' if the primary theme is active - 'CSI ? 997 ; 2 n' if the alternative theme is actice * Implement private mode 2031, where changing the color theme (currently only possible via key bindings) causes the terminal to send the same CSI sequences as above. In this context, foot's primary theme is considered dark, and the alternative theme light (since the default theme is dark). Closes #2025
* | key-bindings: add bindings to switch between color themesDaniel Eklöf2025-04-26-0/+10
| | | | | | | | | | | | * color-theme-switch-1: select the primary color theme * color-theme-switch-2: select the alternative color theme * color-theme-toggle: toggle between the primary and alternative color themes
* | config: move cursor.color to colors.cursorDaniel Eklöf2025-04-26-0/+8
| |
* | changelog: add new 'unreleased' sectionDaniel Eklöf2025-04-26-0/+11
|/
* changelog: prepare for 1.22.1Daniel Eklöf2025-04-26-7/+6
|
* changelog: add missing bug refDaniel Eklöf2025-04-26-0/+1
|
* render: regression: alpha applied to inversed text/selectionsDaniel Eklöf2025-04-25-0/+2
| | | | | | Introduced by 5f83278afd0530c323d4192e1095b3d1dea644c9 Closes #2073
* changelog: zero-width grapheme breaking codepoints causing fallback font to be usedDaniel Eklöf2025-04-24-0/+4
|
* Revert "term: append zero-width grapheme breaking characters to previous cell"Daniel Eklöf2025-04-24-2/+2
| | | | This reverts commit 76503fb86a8b8a6b5c3ce1be87c15a55af38508d.
* Revert "term: ignore LTR+RTL markers (U+200E + U+200F)"Daniel Eklöf2025-04-24-9/+0
| | | | This reverts commit 70b324b24c86473a99528feb6f1f91ca70e11a02.
* term: ignore LTR+RTL markers (U+200E + U+200F)Daniel Eklöf2025-04-24-0/+9
| | | | | | | | | Foot doesn't implement RTL, and explicit LTR markers is neither needed, nor used in anyway. In fact, they cause issues with font lookup, as fcft often fails to find the marker codepoint in the primary font, causing a fallback font to be used instead. Closes #2049
* input: reset modifiers in keyboard_leave()Daniel Eklöf2025-04-19-0/+3
| | | | Closes #2034
* csi: don't allow client app to enable grapheme-shaping when disabled at compile-timeDaniel Eklöf2025-04-19-0/+5
| | | | Closes #2039
* render: fix colors.alpha-mode=matchingDaniel Eklöf2025-04-19-0/+4
| | | | | | Before this patch, it only matched RGB color sources. It did not match the default bg color, or indexed colors. That is, e.g. CSI 43m didn't apply alpha, even if the color3 matched the default background color.
* changelog: add new 'unreleased' sectionDaniel Eklöf2025-04-17-0/+11
|
* changelog: prepare for 1.22.0Daniel Eklöf2025-04-17-5/+11
|
* changelog: move 'alpha-mode' to next-releaseDaniel Eklöf2025-04-14-3/+5
|
* config: add alpha_mode optionFazzi2025-04-14-0/+3
|
* url-mode: fix double-width characters not being handled correctlyDaniel Eklöf2025-04-13-0/+3
| | | | | | | | | When a regex matches a string containing double-width characters, the CELL_SPACER values were included in the URL string. This meant the final URL (either launched, or copied) weren't handled correctly, as invalid UTF-8 sequences were inserted in the middle of the string. Closes #2027
* changelog: move vmod support in config from "changed" to "added"Daniel Eklöf2025-04-10-4/+4
|
* wayland+input: add support for toplevel edge constraintsDaniel Eklöf2025-04-07-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Edge constraints are new (not yet available in a wayland-protocols release) toplevel states, acting as a complement to the existing tiled states. Tiled tells us we shouldn't draw shadows etc *outside our window geometry*. Constrained tells us the window cannot be resized in the constrained direction. This patch does a couple of things: * Recognize the new states when debug logging * Change is_top_left() etc to look at the new constrained state instead of the tiled state. These functions are used when both choosing cursor shape, and when determining if/how to resize a window on a CSD edge click-and-drag. * Update cursor shape selection to use the default (left_ptr) shape when on a constrained edge (or corner). * Update CSD resize triggering, to not trigger a resize when attempted on a constrained edge (or corner). See https://gitlab.freedesktop.org/wayland/wayland-protocols/-/commit/86750c99ed062c306e837f11bb9492df572ad677: An edge constraint is an complementery state to the tiled state, meaning that it's not only tiled, but constrained in a way that it can't resize in that direction. This typically means that the constrained edge is tiled against a monitor edge. An example configuration is two windows tiled next to each other on a single monitor. Together they cover the whole work area. The left window would have the following tiled and edge constraint state: [ tiled_top, tiled_right, tiled_bottom, tiled_left, constrained_top, constrained_bottom, constrained_left ] while the right window would have the following: [ tiled_top, tiled_right, tiled_bottom, tiled_left, constrained_top, constrained_bottom, constrained_right ] This aims to replace and deprecate the `gtk_surface1.configure_edges` event and the `gtk_surface1.edge_constraint` enum.
* config: update default URL regexDaniel Eklöf2025-04-07-0/+5
| | | | | | | | | | | | | | | | | | | The old one is in some cases too liberal. The new one is stricter in two ways: 1. The protocol list is now explicit, rather than matching anything:// 2. Allowed characters are now limited to the "safe character set", the "reserved character set", and some from the "unsafe character set" Furthermore, some of the characters are restricted in how/when they are allowed: 1. Periods, commas, question marks etc are allowed inside an URL, but not at the end. 2. [ ], ( ), " " and ' ' are allowed but only when balanced. This allows us to match e.g. [http://foo.bar/foo[bar]] correctly. Closes #2016
* changelog: reword, and remove section that no longer appliesDaniel Eklöf2025-03-31-7/+2
|
* key-binding: recognize virtual modifiers, and translate to the corresponding real modifier.Daniel Eklöf2025-03-31-2/+7
|
* input: xkb: ignore virtual modifiersDaniel Eklöf2025-03-31-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | Some compositors (mutter/GNOME is one) adds _virtual_ modifiers to the set of active modifiers when e.g. Alt, Meta, Super or Hyper is pressed. For example, pressing Alt+b would result in *both* the Alt *and* the Mod1 modifier being set. Since foot makes close to zero assumptions on how the modifiers should be interpreted, this causes various breakages. For example, a foot shortcut defined as Mod1+b will not match, since the Alt modifiers is also set. This has forced users to redefine/override some of the default key bindings to include the additional modifiers. It also causes issues with the kitty keyboard protocol, for some key combinations. Mainly whether or not to use unshifted key or not, resulting in incorrect escape sequences. Since all the "real" modifiers are always set as well, we can safely ignore the virtual modifiers. Closes #2009
* grid: reflow: fix empty line coalescingDaniel Eklöf2025-03-29-0/+3
| | | | | | | If a range of empty lines ended with a non-empty line at the very bottom of the to-be-resized grid, all those empty lines were removed. Closes #2011
* meson: add foot (render.c) -> srgb.h depAlex Xu (Hello71)2025-03-26-0/+1
| | | | | | | otherwise, depending on ninja dependency resolution order and parallel build, srgb.h may not be built in time Fixes: ccf625b991 ("render: gamma-correct blending")
* render: dim and brighten using linear rgb interpolationSam McCall2025-03-23-0/+6
| | | | | | Adds setting tweak.dim-amount, similar to bold-text-in-bright-amount. Closes #2006
* changelog: url-mode: show-urls-persistent regression fixDaniel Eklöf2025-03-20-0/+7
|
* vt: utf8: don't discard current byte when an invalid UTF-8 sequence is detectedDaniel Eklöf2025-03-18-0/+4
| | | | | | | | | | | | | | | | Example: printf "pok\xe9mon\n" would result in 'pokon' - the 'm' has been discarded along with E9. While correct, in some sense, it's perhaps not intuitive. This patch changes the VT parser to instead discard everything up to the invalid byte, but then try the invalid byte from the ground state. This way, invalid UTF-8 sequences followed by both plain ASCII, or longer (and valid) UTF-8 sequences are printed as expected instead of being discarded.
* changelog: add new 'unreleased' sectionDaniel Eklöf2025-03-17-0/+11
|
* changelog: prepare for 1.21.0Daniel Eklöf2025-03-17-4/+13
|
* config: remove deprecated options 'notify' and 'notify-focus-inhibit'Daniel Eklöf2025-03-17-0/+2
| | | | They've been deprecated since 1.18.0
* ime: fix initial cursor rectangle being reported as 0,0,0,0Daniel Eklöf2025-03-17-0/+3
| | | | Closes #1994
* meson: require wayland-protocols >= 1.41Daniel Eklöf2025-03-13-0/+1
|
* meson: require fcft-3.3.1Daniel Eklöf2025-03-13-1/+1
| | | | fcft-3.3.0 is not binary compatible with 3.2.x, and earlier.
* changelog: mention some of the side-effects the new fcft requirement bringsDaniel Eklöf2025-03-12-0/+3
|
* fcft: require fcft >= 3.3.0, add support for new scaling-filtersDaniel Eklöf2025-03-12-1/+1
| | | | | | | | Update tweak.scaling-filter to recognize the new scaling filters added in fcft-3.3.0. Since fcft_set_scaling_filter() is deprecated in 3.3.0, don't use it anymore, and set the scaling filter via fcft_font_options instead.
* changelog: kitty: release events for composed keysDaniel Eklöf2025-03-11-0/+2
|
* term: tweak linebreakingDaniel Eklöf2025-03-05-0/+6
| | | | | | | | | Don't set linebreak on linefeed. Instead, rely on the default value of true, and that it is only cleared when a character is printed while LCF=1. Note that printing to a row that has linebreak cleared, will set the linebreak flag again.
* render: gamma-correct blendingDaniel Eklöf2025-03-05-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This implements gamma-correct blending, which mainly affects font rendering. The implementation requires compile-time availability of the new color-management protocol (available in wayland-protocols >= 1.41), and run-time support for the same in the compositor (specifically, the EXT_LINEAR TF function and sRGB primaries). How it works: all colors are decoded from sRGB to linear (using a lookup table, generated in the exact same way pixman generates it's internal conversion tables) before being used by pixman. The resulting image buffer is thus in decoded/linear format. We use the color-management protocol to inform the compositor of this, by tagging the wayland surfaces with the 'ext_linear' image attribute. Sixes: all colors are sRGB internally, and decoded to linear before being used in any sixels. Thus, the image buffers will contain linear colors. This is important, since otherwise there would be a decode/encode penalty every time a sixel is blended to the grid. Emojis: we require fcft >= 3.2, which adds support for sRGB decoding color glyphs. Meaning, the emoji pixman surfaces can be blended directly to the grid, just like sixels. Gamma-correct blending is enabled by default *when the compositor supports it*. There's a new option to explicitly enable/disable it: gamma-correct-blending=no|yes. If set to 'yes', and the compositor does not implement the required color-management features, warning logs are emitted. There's a loss of precision when storing linear pixels in 8-bit channels. For this reason, this patch also adds supports for 10-bit surfaces. For now, this is disabled by default since such surfaces only have 2 bits for alpha. It can be enabled with tweak.surface-bit-depth=10-bit. Perhaps, in the future, we can enable it by default if: * gamma-correct blending is enabled * the user has not enabled a transparent background
* config: add search-bindings.delete-to-{start,end} key bindingsAdrian fxj9a2025-03-05-0/+4
| | | | | | Defaults to ctrl+u and ctrl+k respectively. Closes #1972
* term: reset the grapheme clustering state on cursor movementsDaniel Eklöf2025-03-04-0/+1
|
* config+render: allow cursor.style=hollowDaniel Eklöf2025-02-19-0/+2
| | | | Closes #1965
* term: set_app_id(): app_id may be NULL, in which case we can't do strlen()Daniel Eklöf2025-02-18-0/+3
| | | | Closes #1963
* changelog: --server=FD failing on FreeBSDDaniel Eklöf2025-02-16-0/+2
|
* term: append zero-width grapheme breaking characters to previous cellDaniel Eklöf2025-02-16-0/+4
| | | | | | | | | | | | | | | | | | When compiled with grapheme clustering support, zero-width characters that also are grapheme breaks, were ignored (not stored in the grid). When utf8proc says the character is a grapheme break, we try to print the character to the current cell. But this is only done when width > 0. As a result, zero width grapheme breaks were simply discarded. This only happens when grapheme clustering is enabled; when disabled, all zero width characters are appended. Fix this by also requiring the width to be non-zero when if we should append the character or not. Closes #1960
* grid: reflow: fix cursor reflow when LCF is setDaniel Eklöf2025-02-13-0/+3
| | | | | | | | | | When the cursor is at the end of the line, with a pending wrap (LCF set), the lcf flag should be cleared *and* the cursor moved one cell to the right. Before this patch, we cleared LCF, but didn't move the cursor. Closes #1954
* themes: update Tokyo Night LightLudovico Gerardi2025-02-13-0/+1
|
* changelog: text-sizing protocolDaniel Eklöf2025-02-06-1/+2
|
* term: insert-mode: handle combining characters correctlyDaniel Eklöf2025-02-06-0/+4
| | | | | | | | | | | | | | | | | When the client application emits combining characters, for example multi-codepoint emojis, in insert-mode, we ended up pushing partial graphemes to the right, for each codepoint, resulting in too many cells (and with the wrong content) being inserted. The fix is fairly simple; don't "insert" when appending characters to an existing grapheme cluster. This isn't something we can detect easily in print_insert() (it would require us to do grapheme clustering again). Fortunately, we do have the required information in action_utf8_print(). So, pass this information as a boolean to term_print(). Closes #1947
* changelog: custom regex'sDaniel Eklöf2025-02-05-0/+5
|
* config: remove url.{uri-characters,protocols}Daniel Eklöf2025-02-05-0/+7
|
* input: close fd on no/unrecognized keymap formatAttila Fidan2025-01-30-0/+2
|
* key-bindings: try all bindings in translated mode before matching untranslated, and then finally rawDaniel Eklöf2025-01-27-0/+3
| | | | | | | | | | | | | | | | | | | 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
* render: resize: configure with only one dimension being zeroDaniel Eklöf2025-01-26-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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-0/+4
| | | | | | | | | | | | | | | | | | | | 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
|
* input: kitty: fix alternate codepoint sometimes not being reportedDaniel Eklöf2025-01-20-0/+7
| | | | | | | | | | | | | | | | | | | | | 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
* Merge branch 'releases/1.20'Daniel Eklöf2025-01-18-6/+19
|\
| * changelog: move utf8proc entry to correct release1.20.2releases/1.20Daniel Eklöf2025-01-18-3/+3
| |