aboutsummaryrefslogtreecommitdiff
path: root/meson.build (follow)
Commit message (Collapse)AuthorAgeLines
* meson: bump version to 1.28.01.28.0releases/1.28Daniel Eklöf2026-09-02-1/+1
|
* Add support for file:// URLs for initial working directoryairkoala2026-08-29-1/+1
| | | | | | | | | | | This will allow for foot to be registered as a MIME type handler for directories, allowing a "open with foot" action via xdg-open. Some applications pass a simple directory path (eg. qbittorrent) but others pass it as a "file://" URL (lutris), which is also sometimes percent-encoded (calibre) but sometimes not. This patch should be able to handle all 3 of these variants.
* meson: require xkbcommon >= 1.6.0Daniel Eklöf2026-06-12-1/+1
| | | | | | | | We use XKB_KEYSYM_MAX, which was added in 1.6.0. In other words, this requirement isn't really new, but now we've formalized it in meson.build. Closes #2379
* meson: bump version to 1.27.01.27.0releases/1.27Daniel Eklöf2026-05-15-1/+1
|
* meson: add -Dfanalyzer=false|trueDaniel Eklöf2026-05-11-1/+4
| | | | When enabled, compile with -fanalyzer
* meson: bump version to 1.26.11.26.1releases/1.26Daniel Eklöf2026-03-14-1/+1
|
* meson: clang: add -Wno-wc2y-extensionsDaniel Eklöf2026-03-10-0/+5
| | | | | | | | Recent clang versions warn on __COUNTER__, unless compiling with -std=c2y (which breaks other things). "Fixes" '__COUNTER__' is a C2y extension (__COUNTER__ is used by our UNITTEST macro).
* meson: bump version to 1.26.01.26.0Daniel Eklöf2026-03-03-1/+1
|
* Add support for background blurDaniel Eklöf2026-03-02-0/+4
| | | | | | | | | This patch adds a new config option: colors{,2}.blur=no|yes. When enabled, transparent background are also blurred. Note that this requires the brand new ext-background-effect-v1 protocol, and specifically, that the compositor implements the blur effect.
* config: add toplevel-tag=TAGDaniel Eklöf2025-11-12-1/+6
| | | | | | | | | | | Add support for the new xdg-toplevel-tag-v1 Wayland protocol, by exposing a new config option, `toplevel-tag`, and a corresponding command option, `--toplevel-tag` (in both `foot` and `footclient`). This can help the compositor with session management, or custom window rules. Closes #2212
* meson: bump version to 1.25.01.25.0releases/1.25Daniel Eklöf2025-10-16-1/+1
|
* meson: bump version to 1.24.01.24.0releases/1.24Daniel Eklöf2025-09-12-1/+1
|
* meson: utempter del has no argumentDaniel Eklöf2025-09-09-1/+1
| | | | | This fixes an issue where we didn't record a logout record when using the libutempter backend.
* meson: bump version to 1.23.11.23.1releases/1.23Daniel Eklöf2025-07-23-1/+1
|
* fdm: when logging signal related errors, include the signal nameDaniel Eklöf2025-07-21-0/+6
| | | | | | Since sigabbrev_np() is GNU only, provide a fallback function that returns "SIG<signo>" when sigabbrev_np() doesn't exist (for example, on FreeBSD).
* meson: bump to 1.23.01.23.0Daniel Eklöf2025-07-16-1/+1
|
* libxkbcommon: don't require 1.8.0Daniel Eklöf2025-05-18-0/+1
| | | | | | | | | | 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.
* config: tweak.surface-bit-depth: add support for 16-bit surfacesDaniel Eklöf2025-05-03-0/+4
| | | | | | | | | 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.
* meson: bump version to 1.22.31.22.3releases/1.22Daniel Eklöf2025-05-01-1/+1
|
* meson: bump version to 1.22.21.22.2Daniel Eklöf2025-04-30-1/+1
|
* meson: bump version to 1.22.11.22.1Daniel Eklöf2025-04-26-1/+1
|
* build: fix race when generating emoji-variation-sequences.hJan Palus2025-04-23-1/+2
| | | | | | | d3f692990ef6 moved emoji-variation-sequences.h header inclusion from vt.c to terminal.c. these two files are part of different libraries hence target for generating emoji-variation-sequences.h needs to be moved too.
* meson: bump version to 1.22.01.22.0Daniel Eklöf2025-04-17-1/+1
|
* xkbcommon: require libxkbcommon >= 1.8.0Dominique Martinet2025-04-07-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Trying to build with an older libxkbcommon fails as follow: ``` ../input.c: In function ‘keyboard_keymap’: ../input.c:648:82: error: ‘XKB_VMOD_NAME_ALT’ undeclared (first use in this function); did you mean ‘XKB_MOD_NAME_ALT’? 648 | xkb_mod_index_t alt = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_ALT); | ^~~~~~~~~~~~~~~~~ | XKB_MOD_NAME_ALT ../input.c:648:82: note: each undeclared identifier is reported only once for each function it appears in ../input.c:649:83: error: ‘XKB_VMOD_NAME_META’ undeclared (first use in this function); did you mean XKB_MOD_NAME_ALT’? 649 | xkb_mod_index_t meta = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_META); | ^~~~~~~~~~~~~~~~~~ | XKB_MOD_NAME_ALT ../input.c:650:84: error: ‘XKB_VMOD_NAME_SUPER’ undeclared (first use in this function); did you mean ‘XKB_MOD_NAME_NUM’? 650 | xkb_mod_index_t super = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_SUPER); | ^~~~~~~~~~~~~~~~~~~ | XKB_MOD_NAME_NUM ../input.c:651:84: error: ‘XKB_VMOD_NAME_HYPER’ undeclared (first use in this function); did you mean ‘XKB_MOD_NAME_CAPS’? 651 | xkb_mod_index_t hyper = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_HYPER); | ^~~~~~~~~~~~~~~~~~~ | XKB_MOD_NAME_CAPS ../input.c:652:87: error: ‘XKB_VMOD_NAME_NUM’ undeclared (first use in this function); did you mean ‘XKB_MOD_NAME_NUM’? 652 | xkb_mod_index_t num_lock = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_NUM); | ^~~~~~~~~~~~~~~~~ | XKB_MOD_NAME_NUM ../input.c:653:90: error: ‘XKB_VMOD_NAME_SCROLL’ undeclared (first use in this function); did you mean ‘XKB_LED_NAME_SCROLL’? 653 | xkb_mod_index_t scroll_lock = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_SCROLL); | ^~~~~~~~~~~~~~~~~~~~ | XKB_LED_NAME_SCROLL ../input.c:654:90: error: ‘XKB_VMOD_NAME_LEVEL3’ undeclared (first use in this function); did you mean ‘XKB_MOD_NAME_CTRL’? 654 | xkb_mod_index_t level_three = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_LEVEL3); | ^~~~~~~~~~~~~~~~~~~~ | XKB_MOD_NAME_CTRL ../input.c:655:89: error: ‘XKB_VMOD_NAME_LEVEL5’ undeclared (first use in this function); did you mean ‘XKB_MOD_NAME_CTRL’? 655 | xkb_mod_index_t level_five = xkb_keymap_mod_get_index(seat->kbd.xkb_keymap, XKB_VMOD_NAME_LEVEL5); | ^~~~~~~~~~~~~~~~~~~~ | XKB_MOD_NAME_CTRL ```
* meson: add foot (render.c) -> srgb.h depAlex Xu (Hello71)2025-03-26-1/+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")
* meson: bump version to 1.21.0Daniel Eklöf2025-03-17-1/+1
|
* main/client: simplify code for printing --version stringCraig Barnes2025-03-14-2/+2
|
* meson: require wayland-protocols >= 1.41Daniel Eklöf2025-03-13-28/+4
|
* 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.
* 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.
* render: gamma-correct blendingDaniel Eklöf2025-03-05-2/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* Merge branch 'releases/1.20'Daniel Eklöf2025-01-18-1/+1
|\
| * meson: bump version to 1.20.2Daniel Eklöf2025-01-18-1/+1
| |
| * meson: fix dependencies (utf8proc missing in lots of places)Daniel Eklöf2025-01-18-3/+7
| |
* | Add support for the new Wayland protocol xdg-system-bellDaniel Eklöf2025-01-17-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | meson: fix dependencies (utf8proc missing in lots of places)Daniel Eklöf2025-01-04-3/+7
|/
* meson: bump version to 1.20.11.20.1Daniel Eklöf2025-01-03-1/+1
|
* meson: bump version to 1.20.01.20.0Daniel Eklöf2025-01-01-1/+1
|
* meson: bump version to 1.19.01.19.0releases/1.19Daniel Eklöf2024-10-23-1/+1
|
* meson: detect wayland-protocols >= 1.37, and conditionally enable xdg-toplevel-icon-v1Daniel Eklöf2024-09-13-0/+9
|
* xsnprintf: various improvements related to xvsnprintf() and xsnprintf()Craig Barnes2024-09-13-0/+1
| | | | | | | | | | | | | | | | | | | | | | Summary of changes: * Make xvsnprintf() static * restrict-qualify pointer arguments (as done by the libc equivalents) * Make comments and spec references more thorough * Remove pointless `n <= INT_MAX` assertion (see comment) * Use FATAL_ERROR() instead of xassert() (since the assertion is inside a shared util function but the caller is responsible for ensuring the condition holds true) * Change some callers to use size_t instead of int for the return value (negative returns are impossible and all subsequent uses are size_t) The updated comments and code were taken (and adapted) from: https://gitlab.com/craigbarnes/dte/-/blob/49260bb154bca0434462a41c061e512540ec2e49/src/util/xsnprintf.c#L6-50 This work was entirely authored by me and I hereby license this contribution under the MIT license (stated explicitly, so that there's no ambiguity w.r.t. the original license).
* desktop: rename to foot{,client,-server}.desktopDaniel Eklöf2024-09-08-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | That is, skip the reverse DNS naming scheme suggested by the .desktop specification, and directly match our app-ids ("foot", and "footclient"). This simplifies .desktop -> window instance mapping, allowing DEs to match the filenames directly, without having to look at the StartupWMClass key in the .desktop files. These are the original names of the .desktop files. There were renamed (to use the reverse DNS syntax) to please the flathub people, who *required* this scheme to accept the foot package. But, since: * We don't package foot ourselves * We don't go out of our way to support non-distro packaging schemes * Flathub still hasn't merged the foot PR (it's now 2 years old) * There are no know issues in any known DE that prevents a non-reverse DNS .desktop filename from working * There are plenty of other applications that doesn't use reverse DNS names (a very clear majority, in my case) Let's just revert back to the simpler naming scheme. Closes #1607
* meson: bump version to 1.18.11.18.1releases/1.18Daniel Eklöf2024-08-14-1/+1
|
* meson: add "prefix: '#include <unistd.h>" to cc.has_function()Daniel Eklöf2024-08-09-2/+5
| | | | When checking for execvpe, include <unistd.h>
* meson: fix false positive detection of `memfd_create`Shogo Yamazaki2024-08-09-1/+2
| | | | | Add the arguments to `has_function` to properly detect availability of the function on SDK environments.
* meson: bump version to 1.18.01.18.0Daniel Eklöf2024-08-02-1/+1
|
* meson/pgo: fix PGO build errors with recent meson(?) versionsDaniel Eklöf2024-07-18-0/+6
| | | | | | The back-reference to 'tokenize.c' in the parent directory causes PGO build failures, where gcc can't find the PGO data. Likely due to path/naming issues caused by meson's generated build directories.
* vt: only apply VS-15/16 to valid sequencesDaniel Eklöf2024-06-25-1/+10
| | | | | | | | | | At compile time, build a lookup table from the Unicode data file 'emoji-variation-sequences.txt'. At run-time, when we detect a VS-15/16 sequence, do a lookup in this table, and enforce the variation selector iff the sequence is valid. Closes #1742
* meson: auto-detect execvpe on FreeBSDJan Beich2024-06-07-0/+5
| | | | https://github.com/freebsd/freebsd-src/commit/0667d0e0e365
* render: use single-pixel buffers for overlays, when possibleDaniel Eklöf2024-05-22-0/+1
| | | | | | | | | | | | | | | | | | | The unicode-mode, and flash overlays are single color buffers. This means we can use the single-pixel buffer protocol. It's undefined whether the compositor will release the buffer or not; to make things easier, simply destroy the buffer as soon as we've committed it. Note that since compositors don't necessarily release single-pixel buffers, we can't plug them into our own buffer interface. This means we can't use buffer pointers to check if we can re-use the previous buffer (i.e. we can skip comitting a new buffer), or if we have to create a new one. It's _almost_ enough to just check if the last overlay style is the same as the current one. Except that that doesn't take window resizes into account...
* meson: bump version to 1.17.21.17.2releases/1.17Daniel Eklöf2024-04-17-1/+1
|
* meson: bump version to 1.17.11.17.1Daniel Eklöf2024-04-11-1/+1
|
* meson: bump version to 1.17.01.17.0Daniel Eklöf2024-04-02-1/+1
|
* meson: bump version to 1.16.21.16.2releases/1.16Daniel Eklöf2023-10-17-1/+1
|
* meson: bump version to 1.16.11.16.1Daniel Eklöf2023-10-12-1/+1
|
* meson: bump version to 1.16.01.16.0Daniel Eklöf2023-10-11-1/+1
|
* meson: allow building with wayland-protocols as a subprojectDaniel Eklöf2023-08-08-12/+14
|
* wayland: cursor-shape-v1 is now always availableDaniel Eklöf2023-08-07-12/+2
| | | | Since we're requiring wayland-protocols >= 1.32
* wayland: fractional-scale-v1 is now always availableDaniel Eklöf2023-08-07-9/+2
| | | | Since we're requiring wayland-protocols >= 1.32
* wayland: xdg-activation is now always availableDaniel Eklöf2023-08-07-8/+1
| | | | Since we're requiring wayland-protocols >= 1.32
* meson: require wayland-protocols >= 1.32Daniel Eklöf2023-08-07-1/+1
|
* meson: bump version to 1.15.31.15.3releases/1.15Daniel Eklöf2023-08-07-1/+1
|
* meson: bump version to 1.15.21.15.2Daniel Eklöf2023-07-30-1/+1
|
* meson: add -Dterminfo-base-name optionDaniel Eklöf2023-07-28-3/+9
| | | | | | | | | | | | | | | | This defines the base name of the generated terminfo files. It defaults to the value of -Ddefault-terminfo (i.e. 'foot') Example: meson -Ddefault-terminfo=foot-bananas -Dterminfo-base-name=foot-apples The generated terminfo files will be * terminfo/f/foot-apples * terminfo/f/foot-apples-direct The default value of $TERM will be 'foot-bananas'
* meson: bump version to 1.15.11.15.1Daniel Eklöf2023-07-21-1/+1
|
* Ties systemd units to graphical-session.targetMax Gautier2023-07-21-2/+2
| | | | | | | - wayland-instance template target was a mistake. Systemd does not support simultaneous same user session, so stop trying to go against that. - Only start systemd units in Wayland environments.
* meson: bump version to 1.15.01.15.0Daniel Eklöf2023-07-14-1/+1
|
* meson: move cursor-shape.{c,h} from ‘foot’ binary to vtlibDaniel Eklöf2023-07-03-1/+1
| | | | | This should fix a build issue when doing partial PGO builds, when cursor-shape-v1 is *available*.
* meson: log availability of cursor-shape-v1Daniel Eklöf2023-07-03-0/+4
|
* meson: bump wayland-protocols version required for cursor-shape to 1.32Daniel Eklöf2023-07-03-2/+1
|
* meson: cursor-shape: use .xml from wayland-protocolsDaniel Eklöf2023-07-03-5/+7
| | | | | | | | This patch assumes a git snapshot of wayland-protocols are installed. We need to bump the version number as soon as the next version of wayland-protocols have been released.
* cursor-shape: add support for server side cursor shapesDaniel Eklöf2023-07-03-0/+6
| | | | | | | | | | | | | This implements support for the new cursor-shape-v1 protocol. When available, we use it, instead of client-side cursor surfaces, to select the xcursor shape. Note that we still need to keep client side pointers, for: * backward compatibility * to be able to "hide" the cursor Closes #1379
* refactor: track current xcursor using an enum, instead of a char pointerDaniel Eklöf2023-07-03-0/+1
|
* meson: log availability of optional wayland protocolsDaniel Eklöf2023-06-30-0/+8
|
* meson: generate bindings for wp-fractional-scale + wp-viewportDaniel Eklöf2023-06-29-0/+5
|
* meson: use meson feed feature for scdoc inputsewn2023-06-14-1/+1
| | | | Removes the need for a shell dependency.
* utmp: rewrite utmp loggingDaniel Eklöf2023-05-22-19/+44
| | | | | | | | | | | | | | | | | | | | | | | This patch generalizes the utmp support, to not only support libutempter, but also ulog (and in the future, even more interfaces). * Rename config option main.utempter to main.utmp-helper * Add meson option -Dutmp-backend=none|libutempter|ulog|auto * Rename meson option -Ddefault-utempter-path to -Dutmp-default-helper-path * utmp is no longer detected at compile time, but at runtime instead. Meson will configure the following pre-processor macros, based on the selected utmp backend: * UTMP_ADD - argument to pass to utmp helper when adding a record (starting foot) * UTMP_DEL - argument to pass to utmp helper when removing a record (exiting foot) * UTMP_DEL_HAVE_ARGUMENT - if defined, UTMP_DEL expects an extra argument ($WAYLAND_DISPLAY) * UTMP_DEFAULT_HELPER_PATH - path to the default utmp helper binary The documentation has been updated to mention which arguments are passed to the helper binary. Closes #1314
* meson: bump tllist dependency version to 1.1.0Vivian Szczepanski2023-04-09-1/+1
| | | | | The tll_sort() macro was added to tllist in version 1.1.0, and so building with a previous version causes a linking error.
* meson: bump version to 1.14.01.14.0releases/1.14Daniel Eklöf2023-04-03-1/+1
|
* utils: xtgettcap: new utility, to send XTGETTCAP queriesDaniel Eklöf2022-10-07-0/+1
|
* Add support for creating utmp recordsDaniel Eklöf2022-09-23-1/+23
| | | | | | | | | | | | | | | | | This patch adds support for creating utmp records using the ‘utempter’ helper binary from the ‘libutempter’ package. * New config option ‘main.utempter’ * New meson command line option, -Ddefault-utempter-path. Defaults to auto-detecting the path. The default value of the new ‘main.utempter’ config option depends on the meson command line option ‘-Ddefault-utempter-path’. If ‘main.utempter’ is *not* set to ‘none’, foot will try to execute the utempter helper binary to create utmp records when a new terminal is instantiated. The record is removed when the terminal instance is destroyed.
* chore: rename desktop filesVladimír Magyar2022-09-18-1/+1
|
* meson: bump version to 1.13.11.13.1releases/1.13Daniel Eklöf2022-08-31-1/+1
|
* meson: bump version to 1.13.01.13.0Daniel Eklöf2022-08-07-1/+1
|
* input: add new Unicode input modeDaniel Eklöf2022-07-29-0/+1
| | | | | | | | | | | | | | This mode is activated through the new key-bindings.unicode-input and search-bindings.unicode-input key bindings. When active, the user can “build” a Unicode codepoint by typing its hexadecimal value. Note that there’s no visual feedback in this mode. This is intentional. This mode is intended to be a fallback for users that don’t use an IME. Closes #1116
* wayland: log human readable SHM format names in debug buildsDaniel Eklöf2022-06-20-1/+1
|
* meson: -Dsystemd-units-dir installs even if systemd is not foundDaniel Eklöf2022-05-12-4/+4
| | | | | If -Dsystemd-units-dir is explicitly set, then install the systemd service files regardless of whether systemd is available or not.
* meson: add -Dsystemd-units-dir=<path> meson command line optionDaniel Eklöf2022-05-12-1/+7
| | | | | | | | | This allows package maintainers to override the location to which our systemd service files are installed. It’s value is an *absolute* path, and *not* relative ${prefix}. The default is ${systemduserunitdir}.
* meson: bump version to 1.12.11.12.1releases/1.12Daniel Eklöf2022-04-27-1/+1
|
* meson: bump version to 1.12.01.12.0Daniel Eklöf2022-04-22-1/+1
|
* meson: add -Dtests=false|true optionDaniel Eklöf2022-04-22-1/+5
| | | | | | | When set to false, no test binaries are neither built, nor executed (with “ninja test”). Closes #919
* doc + meson.build: update information about foot.ini, small cleanupMerlin Büge2022-04-22-1/+1
| | | | | | | | | | | | | | | | | | | - foot.ini.5: mention location of example config file - foot.1: replace outdated (or incomplete) information about the location of the config file with references to foot.ini.5 - foot.1 and foot.ini.5: conform to scdoc specification, thus surround each header with (at least) one blank line. additionally consistently use exactly one line before/after each header (was sometimes two before) - foot.1: some parts of the keybindings had their own section, move into KEYBOARD SHORTCUTS section - foot.1: move EXIT STATUS section to the end where it is commonly found - foot.1: copy information about config file handling from the beginning of foot.ini.5 into the CONFIGURATION section of foot.1 - INSTALL.md: foot.ini is no longer included in the documentation - meson.build: do not bundle foot.ini with documentation anymore, see also https://codeberg.org/dnkl/foot/pulls/1015 Closes #1002
* key-binding: new API, for handling sets of key bindingsDaniel Eklöf2022-04-17-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Up until now, our Wayland seats have been tracking key bindings. This makes sense, since the seat’s keymap determines how the key bindings are resolved. However, tying bindings to the seat/keymap alone isn’t enough, since we also depend on the current configuration (i.e. user settings) when resolving a key binding. This means configurations that doesn’t match the wayland object’s configuration, currently don’t resolve key bindings correctly. This applies to footclients where the user has overridden key bindings on the command line (e.g. --override key-bindings.foo=bar). Thus, to correctly resolve key bindings, each set of key bindings must be tied *both* to a seat/keymap, *and* a configuration. This patch introduces a key-binding manager, with an API to add/remove/lookup, and load/unload keymaps from sets of key bindings. In the API, sets are tied to a seat and terminal instance, since this makes the most sense (we need to instantiate, or incref a set whenever a new terminal instance is created). Internally, the set is tied to a seat and the terminal’s configuration. Sets are *added* when a new seat is added, and when a new terminal instance is created. Since there can only be one instance of each seat, sets are always removed when a seat is removed. Terminals on the other hand can re-use the same configuration (and typically do). Thus, sets ref-count the configuration. In other words, when instantiating a new terminal, we may not have to instantiate a new set of key bindings, but can often be incref:ed instead. Whenever the keymap changes on a seat, all key bindings sets associated with that seat reloads (re-resolves) their key bindings. Closes #931
* meson: install foot.ini to /etc/xdg/foot/foot.iniDaniel Eklöf2022-04-17-1/+1
| | | | Closes #1001
* meson: stop using deprecated functions, require meson >= 0.58Daniel Eklöf2022-02-27-5/+5
| | | | | | * get_pkgconfig_variable() -> get_variable() * prog.path() -> prog.full_path() * meson.build_root() -> meson.global_build_root()
* Adding systemd unit files for socket activationMax Gautier2022-02-26-0/+19
| | | | | | | | | | - Support for multiples concurrent instances, templated on WAYLAND_DISPLAY - Use standard input for the socket file descriptor (inetd style) - Always use the socket provided by systemd with the systemd user service - wayland-instance@.target is intended to be a special target a bit like graphical-session.target.
* meson: fcft-3.0.0 is buggy, require 3.0.1Daniel Eklöf2022-02-09-1/+1
| | | | | | | Fcft-3.0.0 is known to cause crashes. We don’t want anyone ever compiling foot against it. Closes #935
* meson: bump version to 1.11.0Daniel Eklöf2022-02-05-1/+1
|
* fcft: adapt to API changes in fcft-3.xDaniel Eklöf2022-02-05-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fcft no longer uses wchar_t, but plain uint32_t to represent codepoints. Since we do a fair amount of string operations in foot, it still makes sense to use something that actually _is_ a string (or character), rather than an array of uint32_t. For this reason, we switch out all wchar_t usage in foot to char32_t. We also verify, at compile-time, that char32_t used UTF-32 (which is what fcft expects). Unfortunately, there are no string functions for char32_t. To avoid having to re-implement all wcs*() functions, we add a small wrapper layer of c32*() functions. These wrapper functions take char32_t arguments, but then simply call the corresponding wcs*() function. For this to work, wcs*() must _also_ be UTF-32 compatible. We can check for the presence of the __STDC_ISO_10646__ macro. If set, wchar_t is at least 4 bytes and its internal representation is UTF-32. FreeBSD does *not* define this macro, because its internal wchar_t representation depends on the current locale. It _does_ use UTF-32 _if_ the current locale is UTF-8. Since foot enforces UTF-8, we simply need to check if __FreeBSD__ is defined. Other fcft API changes: * fcft_glyph_rasterize() -> fcft_codepoint_rasterize() * font.space_advance has been removed * ‘tags’ have been removed from fcft_grapheme_rasterize() * ‘fcft_log_init()’ removed * ‘fcft_init()’ and ‘fcft_fini()’ must be explicitly called