aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
* meson: bump version to 1.25.01.25.0releases/1.25Daniel Eklöf2025-10-16-1/+1
|
* changelog: prepare for 1.25.0Daniel Eklöf2025-10-16-5/+6
|
* render: don't warn about immediate buffer release if pre-apply-damage has been activatedDaniel Eklöf2025-10-16-1/+1
|
* wayland: always render a new frame after a fullscreen changeDaniel Eklöf2025-10-15-8/+23
| | | | | | | | | | | This is needed, since we disable alpha in fullscreen, and since we use different image buffer formats (XRGB vs. ARGB) when we have alpha vs. when we don't (and fullscreen always disables alpha). Normally, this happens anyway, as the window is resized when going in or out from fullscreen. But, it's technically possible for a compositor to change an application's fullscreen state without resizing the window.
* extract: number of spaces after the tab shouldn't include the tab cell itselfDaniel Eklöf2025-10-11-2/+5
| | | | | | | | This fixes an off by one, where we sometimes "ate" an extra space when extracting contents with tabs. This happened if the tab (and its subsequent spaces) were followed by an additional space. Closes #2194
* config: add colors.dim-blend-towards=black|whiteDaniel Eklöf2025-10-10-4/+51
| | | | | | | | | | | | Before this patch, we always blended towards black when dimming text. However, with light color themes, it usually looks better if we dim towards white instead. This option allows you to choose which color to blend towards. The default is 'black' in '[colors]', and 'white' in '[colors2]'. Closes #2187
* changelog: updated jump label colors in modus-operandiDaniel Eklöf2025-10-10-0/+2
|
* fix: jump labels are more readableMatthias Heyman2025-10-10-0/+2
|
* wayland: restore opacity after exiting fullscreenCharalampos Mitrodimas2025-10-10-1/+12
| | | | | | | | | | | | | | | | | | | | When exiting fullscreen mode, the window's transparency was not being restored, leaving it opaque until another window was fullscreened. This occurred because the Wayland opaque region was set based only on the configured alpha value, without considering the fullscreen state. Since commit 899b768b74 ("render: disable transparency when we're fullscreened") transparency is disabled during fullscreen to avoid compositor-mandated black backgrounds affecting the intended colors. However, the opaque region was not being updated when the fullscreen state changed. Fixes: https://codeberg.org/dnkl/foot/issues/2180 Signed-off-by: Charalampos Mitrodimas <charmitro@posteo.net>
* render: when double-buffering, pre-apply previous frame's damage earlyDaniel Eklöf2025-10-10-26/+287
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Foot likes it when compositor releases buffer immediately, as that means we only have to re-render the cells that have changed since the last frame. For various reasons, not all compositors do this. In this case, foot is typically forced to switch between two buffers, i.e. double-buffer. In this case, each frame starts with copying over the damage from the previous frame, to the new frame. Then we start rendering the updated cells. Bringing over the previous frame's damage can be slow, if the changed area was large (e.g. when scrolling one or a few lines, or on full screen updates). It's also done single-threaded. Thus it not only slows down frame rendering, but pauses everything else (i.e. input processing). All in all, it reduces performance and increases input latency. But we don't have to wait until it's time to render a frame to copy over the previous frame's damage. We can do that as soon as the compositor has released the buffer (for the frame _before_ the previous frame). And we can do this in a thread. This frees up foot to continue processing input, and reduces frame rendering time since we can now start rendering the modified cells immediately, without first doing a large memcpy(3). In worst case scenarios (or perhaps we should consider them best case scenarios...), I've seen up to a 10x performance increase in frame rendering times (this obviously does *not* include the time it takes to copy over the previous frame's damage, since that doesn't affect neither input processing nor frame rendering). Implemented by adding a callback mechanism to the shm abstraction layer. Use it for the grid buffers, and kick off a thread that copies the previous frame's damage, and resets the buffers age to 0 (so that foot understands it can start render to it immediately when it later needs to render a frame). Since we have certain way of knowing if a compositor releases buffers immediately or not, use a bit of heuristics; if we see 10 consecutive non-immediate releases (that is, we reset the counter as soon as we do see an immediate release), this new "pre-apply damage" logic is enabled. It can be force-disabled with tweak.pre-apply-damage=no. We also need to take care to wait for the thread before resetting the render's "last_buf" pointer (or we'll SEGFAULT in the thread...). We must also ensure we wait for the thread to finish before we start rendering a new frame. Under normal circumstances, the wait time is always 0, the thread has almost always finished long before we need to render the next frame. But it _can_ happen. Closes #2188
* changelog: shm buffer stride alignmentDaniel Eklöf2025-10-05-0/+10
|
* doc: foot.ini: document tweak.min-stride-alignmentDaniel Eklöf2025-10-05-0/+26
|
* shm: page-align the memfd size (also needed for GPU direct import)Daniel Eklöf2025-10-05-4/+8
|
* config: add tweak.min-stride-alignmentDaniel Eklöf2025-10-05-1/+29
| | | | | | | | | | | | This allows the user to configure the value by which a surface buffer's stride must be an even multiple of. This can be used to ensure the stride meets the GPU driver's requirements for direct import. Defaults to 256. Set to 0 to disable. Closes #2182
* term: osc8: tag *all* cells in a multi-column character as an URIDaniel Eklöf2025-10-04-3/+12
| | | | | | | | | | | | | When we print a character to the grid, we must also update its OSC-8 state if an OSC-8 URI is currently active. For double-width characters, this was only being done for the first cell. This causes the labels in URL mode to be off, as the link was effectively chopped up into multiple pieces. Closes #2179
* Revert "term: erase: use erase_line() whenever a range corresponds to a full line"Daniel Eklöf2025-10-04-8/+2
| | | | | | This reverts commit 44a674edb86f2f8db3304d76faf567346dcd7d94. It caused a regression with prompt markers, in at least fish+starship.
* term: erase: use erase_line() whenever a range corresponds to a full lineDaniel Eklöf2025-09-25-2/+8
|
* changelog: add new 'unreleased' sectionDaniel Eklöf2025-09-12-0/+11
|
* Merge branch 'releases/1.24'Daniel Eklöf2025-09-12-6/+7
|\
| * meson: bump version to 1.24.01.24.0releases/1.24Daniel Eklöf2025-09-12-1/+1
| |
| * changelog: prepare for 1.24.0Daniel Eklöf2025-09-12-5/+6
|/
* term: no need to pass ptmx as stdout to utempterDaniel Eklöf2025-09-09-2/+2
|
* meson: utempter del has no argumentDaniel Eklöf2025-09-09-2/+3
| | | | | This fixes an issue where we didn't record a logout record when using the libutempter backend.
* doc: foot.ini: typo: upppercase -> uppercaseDaniel Eklöf2025-08-31-1/+1
|
* config: add 'uppercase-regex-insert'Ryan Roden-Corrent2025-08-31-1/+24
| | | | | | | | | | This makes the "uppercase hint character inserts selected text" behavior added in #1975 configurable, as it can have unexpected behavior for some users. It defaults to "on", preserving the new behavior of `foot`, after Fixes #2159.
* input: unit test: check pipe2() return valueDaniel Eklöf2025-08-30-1/+1
| | | | Fixes compilation failures with clang, in release mode.
* config: value_to_*(): don't overwrite result variable on errorDaniel Eklöf2025-08-25-7/+20
| | | | | | | | | | | 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: fix compilation error: return value ignoredDaniel Eklöf2025-08-01-1/+1
|
* server/client: add support for sending SIGUSR to footclientDaniel Eklöf2025-08-01-12/+151
| | | | | | | | | | | 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
|
* doc: foot.ini: mention SIGUSR1/SIGUSR2 and reference foot(1)Daniel Eklöf2025-07-30-1/+5
|
* doc: foot: document SIGUSR1/SIGUSR2Daniel Eklöf2025-07-30-0/+15
|
* server: sigusr1/2: update conf object with the "new" themeDaniel Eklöf2025-07-30-16/+49
| | | | | | | | When sending SIGUSR1/SIGUSR2 to a server process, all currently running client instances change their theme. But before this patch, all future instances used the original theme. With this patch, the server owned config object is updated with the selected theme, thus making new instances use the same theme as well.
* slave: remove more environment variables set by other terminalsDaniel Eklöf2025-07-30-2/+48
| | | | | | This ensures applications don't mistake foot for another terminal emulator. Not that applications _should_ rely on environment variables, but some do anyway...
* url-mode: for some reason we sorted the label letters before assigning themDaniel Eklöf2025-07-29-12/+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)
* Add tinted variant of modus-vivendi themeTobias Mock2025-07-24-0/+25
|
* changelog: add new 'unreleased' sectionDaniel Eklöf2025-07-23-0/+11
|
* Merge branch 'releases/1.23'Daniel Eklöf2025-07-23-10/+4
|\
| * meson: bump version to 1.23.11.23.1releases/1.23Daniel Eklöf2025-07-23-1/+1
| |
| * changelog: prepare for 1.23.1Daniel Eklöf2025-07-23-9/+3
| |
| * Merge branch 'master' into releases/1.23Daniel Eklöf2025-07-23-32/+134
| |\ | |/ |/|
* | osc: color reset: read default color from currently active themeDaniel Eklöf2025-07-22-14/+53
| |
* | term: make sure the color table is populated *before* the slave process is spawnedDaniel Eklöf2025-07-22-2/+1
| |
* | fdm: when logging signal related errors, include the signal nameDaniel Eklöf2025-07-21-6/+30
| | | | | | | | | | | | Since sigabbrev_np() is GNU only, provide a fallback function that returns "SIG<signo>" when sigabbrev_np() doesn't exist (for example, on FreeBSD).
* | shm: don't set pixman_fmt_without_alpha twiceDaniel Eklöf2025-07-21-1/+5
| | | | | | | | | | | | | | | | 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: unregister SIGUSR2 on exitDaniel Eklöf2025-07-18-0/+1
| |
* | main: SIGUSR1 selects the first color theme, SIGUSR2 the secondDaniel Eklöf2025-07-18-5/+21
| | | | | | | | | | | | | | | | | | | | 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-4/+12
| | | | | | | | | | | | | | 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
| |
* | Merge branch 'releases/1.23'Daniel Eklöf2025-07-16-4/+9
|\|
| * meson: bump to 1.23.01.23.0Daniel Eklöf2025-07-16-1/+1
| |
| * changelog: prepare for 1.23.0Daniel Eklöf2025-07-16-3/+8
|/
* config: silence valgrind-detected leak in config_font_parse()Daniel Eklöf2025-07-11-1/+3
|
* issue template: compositor version -> compositor name and versionDaniel Eklöf2025-07-11-1/+1
| | | | | The existing hints and descriptions are apparently not enough; some people still only mention the version, which is rather useless.
* csi: add '52' to the DA reply, to indicate PSC-52 supportDaniel Eklöf2025-06-10-7/+13
| | | | | | 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-5/+9
|
* main: do a theme toggle upon receiving SIGUSR1Daniel Eklöf2025-06-10-0/+19
| | | | Caveat: in server mode, *all* instances toggle their themes.
* term+input: refactor: move theme switching into term_theme_* functionsDaniel Eklöf2025-06-10-58/+80
|
* quirks: remove subsurface unmap quirk for SwayDaniel Eklöf2025-06-09-26/+8
| | | | | | | | 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.
* wayland: fix global listener for xdg_toplevel_icon_manager_v1tokyo4j2025-05-24-2/+2
|
* conf: pad: add center-when-fullscreen and center-when-maximized-and-fullscreenDaniel Eklöf2025-05-24-20/+60
| | | | | | | | | | | | | | | | | | | | 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: map "dnd-move" to WP_CURSOR_SHAPE_DEVICE_V1_SHAPE_MOVEDaniel Eklöf2025-05-23-1/+1
|
* cursor-shape: add 'dnd-ask' and 'all-resize'Daniel Eklöf2025-05-22-6/+39
| | | | | | | | | | | | | | | | | | | | 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-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | 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
* render: improve CSD button positioningKirill Primak2025-05-21-11/+16
| | | | | This commit fixes titlebar button positioning when maximization isn't available but minimization is.
* libxkbcommon: don't require 1.8.0Daniel Eklöf2025-05-18-0/+24
| | | | | | | | | | 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
* Revert "xkbcommon: require libxkbcommon >= 1.8.0"Daniel Eklöf2025-05-18-1/+1
| | | | This reverts commit 34d3f4664b93d42ec3e1eef9a11e78756465d25a.
* csi: when REP:ing a "combining" character, use correct widthDaniel Eklöf2025-05-16-1/+15
| | | | | | | | | | 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
* term: unittest: auto-scroll timer FD is created on-demand nowadaysDaniel Eklöf2025-05-08-4/+2
|
* render: refactor to allow setting only selection bg or fgDaniel Eklöf2025-05-05-54/+62
| | | | | | | | | | | | 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
* doc: foot.ini: fix description of dark/light themesDaniel Eklöf2025-05-05-2/+2
|
* Update catppuccin themesChen Mulong2025-05-05-0/+20
| | | | | | From https://github.com/catppuccin/foot Without the 'cursor.color', those themes have problems with cursor display problems in the zsh vi normal mode.
* config: tweak.surface-bit-depth: add support for 16-bit surfacesDaniel Eklöf2025-05-03-25/+101
| | | | | | | | | 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-7/+15
| | | | | | 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.
* wayland: attempt to log protocol errors on failure to flushDaniel Eklöf2025-05-02-1/+8
| | | | | When failing to flush, and the error is EPIPE, attempt to read and dispatch events. This ensures protocol errors are logged.
* wayland: always call wl_display_dispatch_pending() at least once, after readingDaniel Eklöf2025-05-02-0/+2
| | | | | | | | | | | This fixes an issue where protocol errors aren't reported. I'm guessing the read succeeds, but that prepare_read() _also_ succeeds immediately, since there aren't any events to dispatch (only log the protocol error). By calling dispatch unconditionally, we ensure any error messages are printed. Then we proceed to loop prepare_read() + dispatch_pending() until the queue is empty.
* Paste URL/regex selection to prompt if key is uppercase.Ryan Roden-Corrent2025-05-01-5/+21
| | | | | | | | | | | | | | | | 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-10/+22
|\
| * meson: bump version to 1.22.31.22.3releases/1.22Daniel Eklöf2025-05-01-1/+1
| |
| * 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-71/+108
| | | | | | | | | | | | | | | | | | | | | | 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-21/+14
| |
| * 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-71/+105
| | | | | | | | | | | | | | | | | | | | | | 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-21/+11
| |
* | readme: add liberapay donation buttonDaniel Eklöf2025-04-30-0/+2
| |
* | Merge branch 'releases/1.22'Daniel Eklöf2025-04-30-8/+16
|\|
| * meson: bump version to 1.22.21.22.2Daniel Eklöf2025-04-30-1/+1
| |
| * changelog: prepare 1.22.2Daniel Eklöf2025-04-30-9/+3
| |
| * doc: foot.ini: gamma-correct: tweak wording of 8- vs. 10-bit surfacesDaniel Eklöf2025-04-30-4/+5
| |
| * scripts: srgb: use 2.2 gamma TF instead of piece-wise sRGB TFDaniel Eklöf2025-04-30-24/+20
| |
| * changelog: add new 'unreleased' sectionDaniel Eklöf2025-04-30-0/+11
| |
* | readme: donations: add liberapayDaniel Eklöf2025-04-30-0/+1
| |
* | doc: foot.ini: gamma-correct: tweak wording of 8- vs. 10-bit surfacesDaniel Eklöf2025-04-28-4/+5
| |
* | scripts: srgb: use 2.2 gamma TF instead of piece-wise sRGB TFDaniel Eklöf2025-04-28-24/+17
| |
* | config: parse_color_theme(): make NOINLINEDaniel Eklöf2025-04-27-1/+1
| |
* | changelog: mention the new combined dark/light theme filesDaniel Eklöf2025-04-26-0/+7
| |
* | themes: paper-color: add dark/light combined theme fileDaniel Eklöf2025-04-26-0/+49
| |
* | themes: nvim: add dark/light combined theme fileDaniel Eklöf2025-04-26-0/+56
| |
* | themes: gruvbox: add dark/light combined theme fileDaniel Eklöf2025-04-26-0/+42
| |