aboutsummaryrefslogtreecommitdiff
path: root/doc/foot.ini.5.scd (follow)
Commit message (Collapse)AuthorAgeLines
* doc: foot.ini: mention SIGUSR1/SIGUSR2 and reference foot(1)Daniel Eklöf2025-07-30-1/+5
|
* conf: pad: add center-when-fullscreen and center-when-maximized-and-fullscreenDaniel Eklöf2025-05-24-8/+19
| | | | | | | | | | | | | | | | | | | | 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
* render: refactor to allow setting only selection bg or fgDaniel Eklöf2025-05-05-2/+1
| | | | | | | | | | | | 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
|
* config: tweak.surface-bit-depth: add support for 16-bit surfacesDaniel Eklöf2025-05-03-13/+16
| | | | | | | | | 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.
* Paste URL/regex selection to prompt if key is uppercase.Ryan Roden-Corrent2025-05-01-3/+6
| | | | | | | | | | | | | | | | 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.
* config: tweak.surface-bit-depth now defaults to 'auto'Daniel Eklöf2025-05-01-19/+22
| | | | | | | | | | | 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-1/+1
|
* doc: foot.ini: gamma-correct: tweak wording of 8- vs. 10-bit surfacesDaniel Eklöf2025-04-28-4/+5
|
* config: add initial-color-theme=1|2Daniel Eklöf2025-04-26-0/+12
| | | | | | | | 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/+8
| | | | | | | | | | | | | | * 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/+16
| | | | | | * 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: add new section 'colors2'Daniel Eklöf2025-04-26-0/+9
| | | | | | | | This section defines an alternative color theme. The keys are the same as in the 'colors' section, as are the default values. Values are *not* inherited from 'colors'. That is, if you set a value in 'colors', but not in 'colors2', it is *not* inherited by 'colors2'.
* config: move cursor.color to colors.cursorDaniel Eklöf2025-04-26-9/+9
|
* doc: foot.ini: add newish Unicode range to 'box-drawings-uses-font-glyphs'Daniel Eklöf2025-04-19-0/+1
|
* doc: foot.ini: spaces -> tab (for indentation)Daniel Eklöf2025-04-19-1/+1
|
* doc: foot.ini: gamma-correct-blending: mention colors being offDaniel Eklöf2025-04-19-7/+8
|
* doc: foot.ini: key-bindings: untranslated symbols are tried before translatedDaniel Eklöf2025-04-18-8/+9
|
* doc: foot.ini: add colors.alpha-modeDaniel Eklöf2025-04-14-0/+15
|
* doc: foot.ini: workers: "if you have a ridiculous number of cores"Daniel Eklöf2025-04-14-0/+4
|
* config: update default URL regexDaniel Eklöf2025-04-07-1/+1
| | | | | | | | | | | | | | | | | | | 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
* doc: foot.ini: mention virtual modifiers are allowedDaniel Eklöf2025-03-31-1/+2
|
* doc: foot.ini: gamma-correct: move sectionDaniel Eklöf2025-03-23-5/+5
|
* render: dim and brighten using linear rgb interpolationSam McCall2025-03-23-4/+7
| | | | | | Adds setting tweak.dim-amount, similar to bold-text-in-bright-amount. Closes #2006
* doc: foot.ini: codespell: shouuld -> shouldDaniel Eklöf2025-03-17-1/+1
|
* doc: foot.init: surface-bit-depth: mention 10-bit surfaces are slowDaniel Eklöf2025-03-17-0/+3
|
* fcft: require fcft >= 3.3.0, add support for new scaling-filtersDaniel Eklöf2025-03-12-3/+2
| | | | | | | | 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-0/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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/+6
| | | | | | Defaults to ctrl+u and ctrl+k respectively. Closes #1972
* config+render: allow cursor.style=hollowDaniel Eklöf2025-02-19-2/+2
| | | | Closes #1965
* doc: foot.ini: font: add one more fontfeatures exampleDaniel Eklöf2025-02-16-0/+7
| | | | | | | | Add a fontfeatures example where we: * set multiple features * assign a value to the features (as opposed to just enabling a boolean feature)
* doc: foot.ini: fix 'hashes' regex exampleDaniel Eklöf2025-02-10-2/+2
| | | | It's A-F, not A-f
* doc: regex: custom regex's aren't URLsDaniel Eklöf2025-02-05-4/+4
|
* doc: improve regex exampleDaniel Eklöf2025-02-05-9/+10
|
* spawn template variables are on the form ${}, not {}Daniel Eklöf2025-02-05-2/+2
|
* url-mode: use the first *sub* expression as URLDaniel Eklöf2025-02-05-4/+11
| | | | | | | | When auto-matching URLs (or custom regular expressions), use the first *subexpression* as URL, rather than the while regex match. This allows us to write custom regular expressions with prefix/suffix strings that should not be included in the presented match.
* doc: foot.ini: document custom regular expressionsDaniel Eklöf2025-02-05-1/+57
|
* foot.ini+doc: add default value of url.regexDaniel Eklöf2025-02-05-1/+1
|
* url-mode+config: wip: add url.regex optionDaniel Eklöf2025-02-05-0/+5
|
* config: remove url.{uri-characters,protocols}Daniel Eklöf2025-02-05-13/+0
|
* key-bindings: add keypad variants to existing default key-bindingsDaniel Eklöf2025-01-31-5/+8
|
* doc: foot.ini: describe key binding match logicDaniel Eklöf2025-01-27-2/+31
|
* Add support for the new Wayland protocol xdg-system-bellDaniel Eklöf2025-01-17-11/+18
| | | | | | | | | | | | | | | | | | | 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.
* osc: add option to disable OSC-52, partially or fullyDaniel Eklöf2024-12-22-0/+27
| | | | Closes #1867
* docs: document more default bindings in search scrollback mode.Mark Stosberg2024-10-25-1/+1
| | | | These were introduced by #1496 but not fully documented then.
* config: add color.sixelN optionsDaniel Eklöf2024-10-23-0/+6
| | | | These options allows you to configure the default sixel color palette.
* add setting for strikeout thicknessOleh Hushchenkov2024-08-26-0/+12
|
* feature: add resize-keep-grid to allow text reflow on font changesAndrew J. Hesford2024-08-20-0/+12
|
* doc: foot.ini: document the Unicode ranges covered by the builtin glyphsDaniel Eklöf2024-08-09-3/+11
|
* osc: kitty notifications: add support for XDG sound namesDaniel Eklöf2024-08-04-0/+7
|
* osc: kitty notifications: implement s=silentDaniel Eklöf2024-08-04-0/+6
| | | | | | | | This implements part of the new 's' (sound) parameter; the 'silent' value. When s=silent, we set the ${muted} template argument to "true". It is intended to set the 'suppress-sound' hint: notify-send --hint BOOLEAN:suppress-sound:${muted}
* doc: foot.ini: codespell: furhermore -> furthermoreDaniel Eklöf2024-08-02-1/+1
|
* osc: kitty notifications: cleanup and update to latest version of specDaniel Eklöf2024-08-02-25/+49
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Don't store a list of unfinished notifications. Use a single one. If the notification ID of the 'current' notification doesn't match the previous, unfinished one, the 'current' notification replaces the previous one, instead of updating it. * Update xstrjoin() to take an optional delimiter (for example ','), and use that when joining categories and 'alive IDs'. * Rename ${action-arg} to ${action-argument} * Update handling of the 'n' parameter (symbolic icon name); the spec allows it to be used multiple times, and the terminal is supposed to pick the first one it can resolve. Foot can't resolve icons at all, neither can 'notify-send' or 'fyi' (which is what foot typically executes to display a notification); it's the notification daemon that resolves icons. The spec _could_ be interpreted to mean the terminal should lookup .desktop files, and use the value of the 'Icon' key from the first matching .desktop files. But foot doesn't read .desktop files, and I don't intend to implement XDG directory scanning and parsing of .desktop files just to figure out which icon to use. Instead, use a simple heuristics; use the *shortest* symbolic names. The idea is pretty simple: plain icon names are typically shorter than .desktop file IDs.
* osc: kitty notifications: buttons, icons, app-name, categories etcDaniel Eklöf2024-07-31-16/+104
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | First, icons have been finalized in the specification. There were only three things we needed to adjust: * symbolic names are base64 encoded * there are a couple of OSC-99 defined symbolic names that need to be translated to the corresponding XDG icon name. * allow in-band icons without a cache ID (that is, allow applications to use p=icon without having to cache the icon first). Second, add support for the following new additions to the protocol: * 'f': custom app-name, overrides the terminal's app-id * 't': categories * 'p=alive': lets applications poll for currently active notifications * 'id' is now 'unset' by default, rather than "0" * 'w': expire time (i.e. notification timeout) * "buttons": aka actions. This lets applications add additional (to the terminal defined "default" action) actions. The 'activated' event has been updated to report which button/action was used to activate the notification. To support button/actions, desktop-notifications.command had to be reworked a bit. There's now a new config option: desktop-notifications.command-action-arg. It has two template arguments ${action-name} and ${action-label}. command-action-arg gets expanded for *each* action. ${action-name} and ${action-label} has been replaced by ${action-arg} in command. This is a somewhat special template, in that it gets replaced by *all* instances of the expanded actions.
* notify: ${icon}: don't fallback to app-idDaniel Eklöf2024-07-30-1/+1
| | | | | | * Revert --icon to ${app-id} * Use --hint STRING:image-path:${icon} instead * ${icon} no longer expands to ${app-id} if notification has no icon
* notify: close notification by sending SIGINT to helperDaniel Eklöf2024-07-26-0/+5
| | | | | | | | | | | | | If the user hasn't configured a custom 'desktop-notifications.close' command, try to close the notification by sending SIGINT to the notification helper. This is best-effort: * If there's no helper running, we do nothing (except warn) * We don't verify, in any way, the notification is actually closed * We don't send any other signals, under any circumstances. That is, no SIGTERM, no SIGKILL. Ever.
* osc: kitty notifications: implement the 'close' requestDaniel Eklöf2024-07-25-0/+12
| | | | | | | | | | | | | | | | Add a new config option, desktop-notifications.close, defining what to execute to close a notification. It has a single template parameter, ${id}, that is expanded to the external notification ID foot may have picked up from the notification helper. notify-send does not support closing notifications, and it appears impossible to pass an *unsigned* integer as argument to gdbus. Hence no default value for the new 'close' option. Example: printf '\e]99;i=123;this is a notification\e\\' printf '\e]99;i=123:p=close;\e\\'
* notify: try to read the daemon assigned notification ID from stdoutDaniel Eklöf2024-07-24-0/+15
| | | | | And document the things we recognize in the notification helper's stdout.
* config: notify-send: it's "action=label", not "action,label"Daniel Eklöf2024-07-24-1/+1
|
* notify: split up the ${action} template parameterDaniel Eklöf2024-07-23-8/+6
| | | | | | | | | Split it up into two, ${action-name} and ${action-label}. Dunstify, for example, has a different syntax compared to notify-send: notify-send: default=foobar dunstify: default,foobar
* doc: foot.ini: desktop-notification: remove 'notification dismissal'Daniel Eklöf2024-07-23-16/+3
|
* notify: don't focus/report on notification dismissalDaniel Eklöf2024-07-23-5/+26
| | | | | | | | | | | | | | | | Only do it when the notification was activated. Here, activated means the 'click to activate' notification action was triggered. How do we tie everything together? First, we add a new template parameter, ${action}. It's intended to be used with e.g. notify-send's --action option. When the action is triggered, notify-send prints its name on stdout, on a separate line. Look for this in stdout. Only if we've seen it do we focus/report the notification.
* notify: XDG token is now expected to be prefixed with xdgtoken=Daniel Eklöf2024-07-23-5/+8
| | | | | | | | | | | | | | | | This patch modifies our stdout reader to consume input as we go, instead of all at once when stdout is closed. This will make it easier to add support for reading e.g. the daemon assigned notification ID in the future, and also ensures we see the XDG activation token "as soon as possible". Furthermore, to be more future proof, require the XDG activation token to be prefixed with 'xdgtoken=', and ignore other lines. Thus, instead of treating *all* of stdout as the XDG activation token, parse stdout line-by-line, and ignore everything that does not begin with 'xdgtoken='. Everything (on that line) following 'xdgtoken=' is treated as the activation token.
* osc: kitty notifications: implement focus|reportDaniel Eklöf2024-07-23-29/+80
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for window focusing, and sending events back to the client application when a notification is closed. * Refactor notification related configuration options: - add desktop-notifications sub-section - deprecate 'notify' in favor of 'desktop-notifications.command' - deprecate 'notify-focus-inhibit' in favor of 'desktop-notifications.inhibit-when-focused' * Refactor: rename 'struct kitty_notification' to 'struct notification' * Pass a 'struct notification' to notify_notify(), instead of many arguments. * notify_notify() now registers a reaper callback. When the notifier process has terminated, the notification is considered closed, and we either try to focus (activate) the window, or send an event to the client application, depending on the notification setting. * For the window activation, we need an XDG activation token. For now, assume *everything* written on stdout is part of the token. * Refactor: remove much of the warnings from OSC-99; we don't typically log anything when an OSC/CSI has invalid values. * Add icon support to OSC-99. This isn't part of the upstream spec. Foot's implementation: - uses the 'I' parameter - the value is expected to be a symbolic icon name - a quick check for absolute paths is done, and such icon requests are ignored. * Added ${icon} to the 'desktop-notifications.command' template. Uses the icon specified in the notification, or ${app-id} if not set.
* osc/notify: add support for OSC-99, kitty desktop notificationsDaniel Eklöf2024-07-23-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | This adds limited support for OSC-99, kitty desktop notifications[^1]. We support everything defined by the "protocol", except: * 'a': action to perform on notification activation. Since we don't trigger the notification ourselves (over D-Bus), we don't know a) which ID the notification got, or b) when it is clicked. * ... and that's it. Everything else is supported To be explicit, we *do* support: * Chunked notifications (d=0|1), allowing the application to append data to a notification in chunks, before it's finally displayed. * Plain UTF-8, or base64-encoded UTF-8 payload (e=0|1). * Notification identifier (i=xyz). * Payload type (p=title|body). * When to honor the notification (o=always|unfocused|invisible), with the following quirks: - we don't know when the window is invisible, thus it's treated as 'unfocused'. - the foot option 'notify-focus-inhibit' overrides 'always' * Urgency (u=0|1|2) [^1]: https://sw.kovidgoyal.net/kitty/desktop-notifications/
* input: don't map wheel events to BTN_{BACK,FORWARD}Daniel Eklöf2024-07-13-10/+13
| | | | | | | | | | | | | | | | | | | | BTN_BACK and BTN_FORWARD are separate buttons. The scroll wheel don't have any button mappings in libinput/wayland, so make up our own defines. This allows us to map them in mouse bindings. Also expose BTN_WHEEL_{LEFT,RIGHT}. These were already defined, and used, internally, to handle wheel tilt events. With this, they can also be used in mouse bindings. Finally, fix encoding used for BTN_{BACK,FORWARD} when sending mouse button events to the client application. Before this, they were mapped to buttons 4/5. But, button 4/5 are for the scroll wheel, and as mentioned above, BTN_{BACK,FORWARD} are not the same as scroll wheel "buttons". Closes #1763
* doc: foot.ini: line-height: add warning about runtime font size changesDaniel Eklöf2024-07-07-0/+6
|
* doc: foot.ini: fix typosDaniel Eklöf2024-06-25-3/+3
|
* doc: foot.ini: document issues with fractional scaling and initial-window-size-*Daniel Eklöf2024-06-25-1/+12
| | | | | | Since most compositors don't report the correct scaling factor until *after* the window has been mapped, these options often do not work.
* doc: foot.ini: document pixelsizeDaniel Eklöf2024-06-07-3/+9
| | | | | People are apparently too lazy to read fontconfig's documentation, and don't understand how to configure font sizes in foot.
* config: add cursor.blink-rate optionDaniel Eklöf2024-05-20-1/+6
| | | | | | The default is 500ms, which corresponds to the old, hardcoded default. Closes #1707
* config: add new key-binding 'quit', unbound by defaultDaniel Eklöf2024-04-11-0/+3
| | | | Closes #1475
* config: add cursor.unfocused-styleDaniel Eklöf2024-04-10-0/+9
| | | | | | | | | | | | | | | This option controls how we render the cursor when the terminal window is unfocused. Possible values are: * hollow: the default, and how we rendered the cursor before this patch. * unchanged: render the cursor exactly the same way as when the window is focused. * none: do not render any cursor at all Closes #1582
* config: map Control+wheel to font increase/decreaseDaniel Eklöf2024-02-15-2/+11
| | | | | | This is in addition to the already existing keyboard shortcuts. Also add missing default keyboard/mouse bindings to readme + foot(1).
* doc: better examples for pipe-* commandsDaniel Eklöf2024-02-07-6/+4
|
* doc: foot.ini: document pipe-command-outputDaniel Eklöf2024-02-06-7/+15
|
* feature: add resize-by-cells option to constrain window sizes...Andrew J. Hesford2024-02-05-0/+15
| | | | | ...to multiples of the cell size, and preserve grid size when changing fonts or display scales in floating windows.
* man foo.ini.5: Add 'Comma separated list of fonts' examplexnuk2023-10-27-0/+1
|
* 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
|
* 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-0/+16
| | | | | | 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.
* config: add remaining search.scrollback key bindingsDaniel Eklöf2023-10-08-0/+25
| | | | All scrollback up/down key bindings are now available in search mode.
* foot.ini: document all the new search.extend* bindingsDaniel Eklöf2023-10-08-4/+26
|
* csi: implement DECSET/DECRST/DECRQM 2027 - grapheme cluster processingDaniel Eklöf2023-09-25-0/+2
| | | | | | | | | | | 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
* doc: keybings default noneSertonix2023-09-20-11/+11
|
* selection: add support for selecting the contents of a quoteDaniel Eklöf2023-09-19-1/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | 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-3/+24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* config: add tweak.bold-text-in-bright-amountDaniel Eklöf2023-07-28-1/+7
| | | | | | | | By how much to increase the luminance when brightening bold fonts. This was previously hard-coded to a factor of 1.3, which is now the default value of the new config option. Closes #1434
* themes: starlight: update to V4Daniel Eklöf2023-07-18-6/+6
| | | | | | | This also updates the default theme in foot, as well as the documentation. Closes #1409
* config: add csd.double-click-to-maximize=no|yes optionDaniel Eklöf2023-07-14-0/+4
| | | | | | | | | When enabled, double-clicking the CSD titlebar will (un)maximize the window. Defaults to ‘yes’ (since this is the old hard-coded behavior). Closes #1293
* config: make ‘starlight’ the default color themeDaniel Eklöf2023-07-14-6/+6
| | | | Closes #1321
* bind control-shift-u to unicode-input, move urls to oAntoine Beaupré2023-07-10-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Having a keybinding to invoke arbitrary unicode characters is very useful. It's often used as a method of last resort to communicate with people outside of your main language. For example, if you want to type the last letter of my real name, you can invoke the latin-1 character 0xe9 or unicode 0x00e9. You can also use this to type special characters, for example, unicode U+1F4A9 is of course, the infamous PILE OF POO, which is sure to produce million laughs everywhere you go. In foot, there's no keybinding by default to invoke the very useful unicode-input command. There is no "standard" (as in "ISO") keybinding this either. But there *is* a de-facto standard currently deployed by *both* GTK and Qt (a rare feat) *and* Chrome OS (an even rarer feat) and it's control-shift-u. Alternatives include Control-x 8 (emacs), Control V u (vim), Alt (Windows, LibreOffice), or Option (Mac). I doubt we want to adopt any of those. So let's use control-shift-u for this. Unfortunately, it's currently assigned to show-urls-launch, which is unfortunate, but insurmountable. We can reassign this keybinding elsewhere. I have picked control-shift-o in my configuration, because "o" is a good mnemonic for "open URLs". Others have suggested "m" instead. Closes: #1183
* input: add basic support for touchscreen inputCismonX2023-07-05-0/+8
| | | | Closes #517
* config: dpi-aware: remove ‘auto’ value, and default to ‘no’Daniel Eklöf2023-06-29-8/+2
| | | | | | | | | | We now default to scaling fonts using the scaling factor, not monitor DPI. The ‘auto’ value for dpi-aware has been removed. Documentation (man pages and README) have been updated to reflect the new default.
* Fixed a type for the pixel fontsize changewout2023-06-23-1/+1
| | | | xp -> px
* .desktop: remove StartupWMClass from server, use distinct StartupWMClass for foot and footclientjdevdevdev2023-05-22-2/+4
| | | | | | | | | | | | | | | For this to work, the default app-id of footclient has been changed from ‘foot’ to ‘footclient’. By using distinct StartupWMClasses, the compositor can connect a running foot/footclient instance to the correct .desktop-file. This ensures the correct icon is being used in e.g. docks, and that actions like “open another window” works correctly. Note that the user can override the app-id, either by setting app-id in foot.ini, or with the -a,--app-id command line option. Closes #1355
* utmp: rewrite utmp loggingDaniel Eklöf2023-05-22-3/+18
| | | | | | | | | | | | | | | | | | | | | | | 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
* fix typosHarri Nieminen2023-03-28-1/+1
|
* doc: foot.ini: fix spelling mistake in [bell].urgent descriptionCraig Barnes2023-02-16-1/+1
|