aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
* meson: bump version to 1.16.21.16.2releases/1.16Daniel Eklöf2023-10-17-1/+1
|
* changelog: prepare for 1.16.2Daniel Eklöf2023-10-17-10/+3
|
* Merge branch 'master' into releases/1.16Daniel Eklöf2023-10-17-1/+18
|\
| * render: sixel: regression: wrong cell color behind opaque sixelsDaniel Eklöf2023-10-13-1/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | An opaque sixel that isn't a multiple of the cell size will have some cells partially visible (either the entire last row, the entire last column, or both). These must be rendered before blitting the sixel. f5f2f5a954ee6cf3532a6aba023860ada183d486 introduced a regression, where all such cells were rendered as if the cursor was there, giving them the wrong appearance. Closes #1520
| * changelog: add new 'unreleased' sectionDaniel Eklöf2023-10-12-0/+10
| |
| * Merge branch 'releases/1.16'Daniel Eklöf2023-10-12-11/+4
| |\ | |/ |/|
* | meson: bump version to 1.16.11.16.1Daniel Eklöf2023-10-12-1/+1
| |
* | changelog: prepare for 1.16.1Daniel Eklöf2023-10-12-10/+3
| |
* | Merge branch 'master' into releases/1.16Daniel Eklöf2023-10-12-16/+47
|\|
| * render: fix surface damage when rendering sixels.Daniel Eklöf2023-10-12-9/+13
| | | | | | | | | | | | | | | | | | | | Pass a damage region to render_row()/render_cell() when rendering partially visible cells underneath a sixel. This ensures the affected regions are later reported as 'damaged' to the Wayland compositor. Closes #1515
| * sixel: erase: fix clearing of cell->attrs.cleanDaniel Eklöf2023-10-12-1/+1
| | | | | | | | | | | | | | | | | | When erasing a sixel, the cells underneath it must be marked as 'dirty', in order to be re-rendered. This was not being done correctly; the for loop loops *from* the start col, meaning the *end* col is *not* sixel->pos.col, as that's the *number* of columns, not the *end* column.
| * shm: memfd_create: fallback to not using MFD_NOEXEC_SEALDaniel Eklöf2023-10-12-5/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
| * changelog: fix link to issue 1077Daniel Eklöf2023-10-11-1/+1
| |
| * changelog: add new 'unreleased' sectionDaniel Eklöf2023-10-11-0/+11
| |
| * Merge branch 'releases/1.16'Daniel Eklöf2023-10-11-6/+12
| |\ | |/ |/|
* | meson: bump version to 1.16.01.16.0Daniel Eklöf2023-10-11-1/+1
| |
* | changelog: prepare for 1.16.0Daniel Eklöf2023-10-11-5/+11
|/
* changelog: emphasize the new key bindings are for search modeDaniel Eklöf2023-10-11-1/+1
|
* Merge branch 'fix-font-baseline-calculation'Daniel Eklöf2023-10-11-12/+25
|\ | | | | | | | | Closes #1511 Closes #1463
| * term: cache font baselineDaniel Eklöf2023-10-10-9/+12
| | | | | | | | | | No need to redo the calculation for every single cell we render, every frame...
| * term_font_baseline(): only center glyph when a custom line-height is being usedDaniel Eklöf2023-10-10-2/+10
| | | | | | | | | | | | | | | | When using the font's own line-height, simply set the baseline 'descent' pixels above the bottom of the cell. This fixes an issue where some fonts appeared "glued" to the top of the cell, and sometimes getting partially clipped.
| * changelog: fixed font baseline calculationDaniel Eklöf2023-10-10-0/+2
| |
| * Revert "font baseline: use max(font->height, font->ascent + font->descent) when calculating font ↵Daniel Eklöf2023-10-10-1/+1
|/ | | | | | | | | | | | | height" This reverts commit fd813d0e6cfff57cf8a8f55e9a249ddb6fbdb6d6. The intent of the reverted commit was to align font height calculation with cell height calculation. However, it turns out this breaks some fonts. Typically those with large:ish differences in their 'height' attribute, and their ascent+descent value. Closes #1511
* render: better description of why we disable transparency in fullscreenDaniel Eklöf2023-10-10-13/+23
|
* Merge branch 'visual-bell-remastered'Daniel Eklöf2023-10-10-2/+49
|\ | | | | | | Closes #1337
| * changelog: fix issue number for visual bellDaniel Eklöf2023-10-10-2/+2
| | | | | | | | 1508 refers to the pull request, not the feature request.
| * doc: foot.ini.5: move flash{,-alpha} to the bottom of the 'colors' sectionDaniel Eklöf2023-10-10-7/+7
| |
| * doc: foot.ini.5: flash_alpha -> flash-alphaDaniel Eklöf2023-10-10-1/+1
| |
| * foot.ini: flash_alpha -> flash-alphaDaniel Eklöf2023-10-10-1/+1
| |
| * term: remove unneeded (and mostly unused) term->flash{,_alpha}Daniel Eklöf2023-10-10-6/+0
| |
| * doc: foot.ini: flash: tweak grammar, use consistent formattingDaniel Eklöf2023-10-10-10/+5
| |
| * Enable the use of flash as visual bellRaimund Sacherer2023-10-10-2/+60
|/ | | | | | 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.
* render: more fine-grained wayland surface damage trackingDaniel Eklöf2023-10-10-50/+75
| | | | | | | | | 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.
* config: log_contextual_errno(): sync with log_contextual()Daniel Eklöf2023-10-08-3/+12
| | | | ... in terms of whether to print section/value separators
* shm: move definition of FOOT_MFD_FLAGS to the topDaniel Eklöf2023-10-08-5/+6
|
* Merge branch 'search-extend-selection'Daniel Eklöf2023-10-08-112/+615
|\
| * changelog: add the remaining scrollback-up/down bindingsDaniel Eklöf2023-10-08-1/+5
| |
| * config: add remaining search.scrollback key bindingsDaniel Eklöf2023-10-08-3/+91
| | | | | | | | All scrollback up/down key bindings are now available in search mode.
| * search: fix mixup in search_extend_find_line()Daniel Eklöf2023-10-08-59/+69
| | | | | | | | | | | | | | | | | | The has_wrapped_around_{right,left} functions were mixed up, causing false positives and false negatives, resulting in bad search matches. Also make all search_extend_find* functions return a boolean; false means no change in the selection. In this case, we can skip trying to extend the selection, and updating the UI.
| * foot.ini: document all the new search.extend* bindingsDaniel Eklöf2023-10-08-5/+33
| |
| * config: map ctrl+shift+right to extend-to-word-boundaryDaniel Eklöf2023-10-08-1/+1
| |
| * selection: find_word_boundary: ensure row number is boundedDaniel Eklöf2023-10-08-6/+8
| |
| * search: don't try to extend a search match when there is noneDaniel Eklöf2023-10-08-1/+16
| |
| * selection: selection_update() uses view-local coordinatesDaniel Eklöf2023-10-08-7/+12
| |
| * search: add more key bindings to extend the current matchDaniel Eklöf2023-10-08-102/+453
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* render: disable transparency in margins when in fullscreenDaniel Eklöf2023-10-07-2/+14
| | | | | | | This amends 899b768b744c74e88e54e6d8eb32f53accea79d8, where we started disabling transparency in fullscreen Closes #1503
* shm: if defined, set MFD_NOEXEC_SEAL flag for memfd_create6t8k2023-10-05-1/+6
| | | | | | | | | | Effective from Linux 6.3.0 onward, this creates the memfd without execute permissions and prevents that setting from ever being changed. This is a defense-in-depth security measure and prevents a respective kernel warning from being emitted. See https://lwn.net/Articles/918106/ for more information.
* term_reset: log hard vs. soft resetDaniel Eklöf2023-10-04-0/+2
|
* Codespell fixesDaniel Eklöf2023-10-03-1/+1
|
* Codespell fixesDaniel Eklöf2023-10-03-14/+14
|
* wayland: debug: log wm-capabilities as human-readable stringsDaniel Eklöf2023-10-02-4/+39
|
* term: get_font_dpi(): don't crash when there aren't any available monitorsDaniel Eklöf2023-10-01-2/+6
| | | | | | | | | | | | | 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
* config: apply overrides even if there's no fileAlyssa Ross2023-09-25-22/+21
| | | | | | | | | 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.
* csi: decrqm: 2027: permanently disabled when grapheme-width-method != double-widthDaniel Eklöf2023-09-25-1/+3
|
* csi: implement DECSET/DECRST/DECRQM 2027 - grapheme cluster processingDaniel Eklöf2023-09-25-1/+21
| | | | | | | | | | | 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
* dcs: xtgettcap: ignore queries with invalid hex encodingsDaniel Eklöf2023-09-25-7/+6
| | | | | | | | 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.
* url-mode: don't strip the file:// prefix from localhost URIsDaniel Eklöf2023-09-21-31/+5
| | | | | | | | | | | | | | | | | 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
* changelog: crash when xdg token is set, but compositor does not support activationDaniel Eklöf2023-09-21-1/+4
|
* wayland: check activation supported before activatingAlyssa Ross2023-09-21-1/+1
| | | | | | | | It's possible for token to be set when the compositor doesn't support activation, and this caused a segfault. For example, this can happen when overriding WAYLAND_DISPLAY to point to a compositor that doesn't support activation, in a terminal running under one that does, and so has set XDG_ACTIVATION_TOKEN.
* doc: keybings default noneSertonix2023-09-20-11/+11
|
* selection: add support for selecting the contents of a quoteDaniel Eklöf2023-09-19-17/+199
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* input: make wheel events mappableDaniel Eklöf2023-09-18-105/+162
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* input: improve touch handling on pointer presenseCismonX2023-08-23-32/+73
| | | | | | | | | | | No longer inhibits touch event handling when terminal window has pointer focus. Instead, inhibit touch event when at least one pointer button is held down. This change improves user experience when using foot with both a mouse and a touchscreen. Closes #1428.
* url-mode: handle wide chars and grapheme clusters when auto-detecting URLsDaniel Eklöf2023-08-21-90/+118
| | | | | | | | | | * 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
* add panda themeraggedmyth2023-08-19-0/+27
|
* term: improve fallback logic when selecting scaling factor while unmappedDaniel Eklöf2023-08-18-7/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | 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
* ci: replace 'pipeline' with 'steps'Daniel Eklöf2023-08-18-1/+1
| | | | | | Hopefully fixes: failed to parse pipeline: "pipeline:" got removed, use "steps:" instead
* Merge branch 'systemd-service-ordering'Daniel Eklöf2023-08-11-0/+14
|\ | | | | | | Closes #1436
| * changelog: systemd units in GNOMEMax Gautier2023-08-10-0/+11
| |
| * systemd: skip foot-server.service when not in a Wayland contextMax Gautier2023-08-10-0/+1
| |
| * Order the systemd services after graphical-session.targetMax Gautier2023-08-10-0/+2
|/ | | | | | This fixes services in Wayland session where WAYLAND_DISPLAY is only imported into the systemd user instance environment after graphical-session.target is reached (such as GNOME).
* meson: allow building with wayland-protocols as a subprojectDaniel Eklöf2023-08-08-12/+21
|
* Merge branch 'wayland-protocols-1.32'Daniel Eklöf2023-08-07-184/+33
|\ | | | | | | Closes #1391
| * wayland: cursor-shape-v1 is now always availableDaniel Eklöf2023-08-07-66/+7
| | | | | | | | Since we're requiring wayland-protocols >= 1.32
| * wayland: fractional-scale-v1 is now always availableDaniel Eklöf2023-08-07-78/+17
| | | | | | | | Since we're requiring wayland-protocols >= 1.32
| * wayland: xdg-activation is now always availableDaniel Eklöf2023-08-07-43/+5
| | | | | | | | Since we're requiring wayland-protocols >= 1.32
| * meson: require wayland-protocols >= 1.32Daniel Eklöf2023-08-07-1/+8
|/
* Merge branch 'releases/1.15'Daniel Eklöf2023-08-07-5/+9
|\
| * meson: bump version to 1.15.31.15.3releases/1.15Daniel Eklöf2023-08-07-1/+1
| |
| * changelog: prepare for 1.15.3Daniel Eklöf2023-08-07-10/+3
| |
| * main: “title%s” -> “title=%s”Daniel Eklöf2023-08-07-1/+1
| | | | | | | | | | | | | | | | Fix regression of --title,-T option. This broken when command line parsing was switched to using overrides, in 0b4f1b4af20cea0afae39a2c1c4e42c22962dcde. Closes #1457
| * vt: fix ASAN UB warningDaniel Eklöf2023-08-07-1/+1
| | | | | | | | | | | | | | ../vt.c:648:13: runtime error: signed integer overflow: 3924432811 * 2654435761 cannot be represented in type 'long' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../vt.c:648:13 in Closes #1456
| * render: OSD: center text verticallyDaniel Eklöf2023-08-07-9/+20
| | | | | | | | | | | | | | | | | | | | | | | | 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
| * main: translate command line options to overridesDaniel Eklöf2023-08-07-89/+22
| | | | | | | | | | | | | | | | | | 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.
| * changelog: add new ‘unreleased section’Daniel Eklöf2023-08-07-0/+11
| |
* | changelog: “config” -> “config option”Daniel Eklöf2023-08-05-1/+1
| |
* | main: “title%s” -> “title=%s”Daniel Eklöf2023-08-05-1/+1
| | | | | | | | | | | | | | | | Fix regression of --title,-T option. This broken when command line parsing was switched to using overrides, in 0b4f1b4af20cea0afae39a2c1c4e42c22962dcde. Closes #1457
* | vt: fix ASAN UB warningDaniel Eklöf2023-08-05-1/+1
| | | | | | | | | | | | | | ../vt.c:648:13: runtime error: signed integer overflow: 3924432811 * 2654435761 cannot be represented in type 'long' SUMMARY: UndefinedBehaviorSanitizer: undefined-behavior ../vt.c:648:13 in Closes #1456
* | render: OSD: center text verticallyDaniel Eklöf2023-07-31-9/+20
| | | | | | | | | | | | | | | | | | | | | | | | 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
* | config: remove deprecated option 'utempter'Daniel Eklöf2023-07-31-18/+5
| |
* | main: translate command line options to overridesDaniel Eklöf2023-07-31-89/+22
| | | | | | | | | | | | | | | | | | 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.
* | changelog: add new ‘unreleased section’Daniel Eklöf2023-07-30-0/+11
| |
* | Merge branch 'releases/1.15'Daniel Eklöf2023-07-30-10/+4
|\|
| * meson: bump version to 1.15.21.15.2Daniel Eklöf2023-07-30-1/+1
| |
| * changelog: prepare for 1.15.2Daniel Eklöf2023-07-30-9/+3
| |
| * Merge branch 'master' into releases/1.15Daniel Eklöf2023-07-30-178/+344
| |\ | |/ |/|
* | --window-size-chars: ensure width/height are valid for current scaling factorDaniel Eklöf2023-07-30-16/+7
| | | | | | | | | | | | | | | | | | | | 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
* | Merge branch 'csd-fractional-scaling'Daniel Eklöf2023-07-29-82/+128
|\ \ | | | | | | | | | Closes #1441
| * | changelog: CSDs with fractional scalingDaniel Eklöf2023-07-29-0/+2
| | |
| * | wayl_surface_scale_explicit_width_height(): don’t assert width/height are valid for scaleDaniel Eklöf2023-07-29-7/+28
| | | | | | | | | | | | | | | | | | This function is only called directly when scaling the mouse pointer. The mouse pointer is never guaranteed to have a valid width and height, so skip the width/height assertions for it.