aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeLines
...
* readme: update mastodon linkDaniel Eklöf2024-09-08-1/+1
|
* desktop: rename to foot{,client,-server}.desktopDaniel Eklöf2024-09-08-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* .desktop: remove StartupWMClass cludgeDaniel Eklöf2024-09-08-2/+0
|
* metainfo: add recent releases, update feature listDaniel Eklöf2024-09-08-0/+6
|
* sixel: default bg color is now taken from the sixel palette, not the ANSI bg colorDaniel Eklöf2024-09-05-33/+7
| | | | | | | | | | | | | | | | The wording in the original VT340 documentation is vague: Pixel positions specified as 0 are set to the current background color. What does that mean? We _thought_ it meant the current ANSI background color, as set with e.g. CSI 4x m. It's still all a bit vague, but seeing that we have separate palettes for text and graphic (should we?), it doesn't make sense to use the ANSI background color as the default sixel background color. So, use entry 0 from the sixel palette instead.
* notifications: BEL and OSC-777 now focuses the window on notification activationDaniel Eklöf2024-09-05-4/+14
| | | | | | | | | | | Or put more propertly; if the notification daemon, and the notification helper used by foot has been configured properly (i.e. they both support XDG activation tokens), notifications generated by BEL and OSC-777 will now raise/focus the window when the default action of the notification is activated - typically by clicking the notification. Closes #1822
* changelog: strikeout-thicknessDaniel Eklöf2024-08-26-0/+1
|
* add setting for strikeout thicknessOleh Hushchenkov2024-08-26-2/+32
|
* changelog: mbsntoc32() failure checksDaniel Eklöf2024-08-20-0/+6
|
* term_set_window_title(): fix bad check for invalid UTF-8Daniel Eklöf2024-08-20-1/+1
| | | | mbsntoc32() returns (size_t)-1 on failure, not (char32_t)-1.
* osc: notify: fix bad check for invalid UTF-8Daniel Eklöf2024-08-20-2/+2
| | | | mbsntoc32() returns (size_t)-1 on failure, not (char32_t)-1.
* changelog: resize-keep-gridDaniel Eklöf2024-08-20-0/+8
|
* changelog: add missing reference to #1787Daniel Eklöf2024-08-20-0/+2
|
* feature: add resize-keep-grid to allow text reflow on font changesAndrew J. Hesford2024-08-20-1/+23
|
* render: follow cursor.unfocused-style regardless of cursor.styletokyo4j2024-08-20-12/+17
| | | | | Before this commit, cursor.unfocused-style was effective only with cursor.style=block
* term: thrd_join() returns thrd_success on success, not 0Daniel Eklöf2024-08-15-1/+1
| | | | Closes #1812
* changelog: add new 'unreleased' sectionDaniel Eklöf2024-08-14-0/+11
|
* Merge branch 'releases/1.18'Daniel Eklöf2024-08-14-6/+7
|\
| * meson: bump version to 1.18.11.18.1releases/1.18Daniel Eklöf2024-08-14-1/+1
| |
| * changelog: prepare for 1.18.1Daniel Eklöf2024-08-14-5/+6
| |
| * Merge branch 'master' into releases/1.18Daniel Eklöf2024-08-14-84/+369
| |\ | |/ |/|
* | osc: regression: fix OSC-111 handling of alpha changesDaniel Eklöf2024-08-14-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | When the background alpha changes from fully opaque, to transparent, or vice versa, we need to do more than just repaint the affected cells. For example, we need to create new surfaces with the correct pixel format. OSC-11 (set background color) already does this, but the same alpha checking logic was missing in OSC-111 (reset background color). Fixes #1801
* | utils/xtgettcap: fix possible NULL deref, found by -fanalyzerDaniel Eklöf2024-08-14-0/+3
| |
* | main: spell out the most common reason for setlocale() to failDaniel Eklöf2024-08-13-1/+2
| |
* | main: invalid locale != non-UTF-8 localeDaniel Eklöf2024-08-13-18/+35
| | | | | | | | | | | | | | | | When doing locale fallback, and printing user notifications and log warnings, better separate the case "locale is invalid" from "locale is valid but not UTF-8". Closes #1798
* | slave: prefix user notifications with 'foot'Daniel Eklöf2024-08-09-1/+3
| | | | | | | | To make it clearer _who_ is emitting the warning/errors
* | osc: kitty: update 's' to the latest specDaniel Eklöf2024-08-09-1/+17
| | | | | | | | | | | | | | * The spec now defines a couple of "standard" names. Translate these to the freedesktop compliant names. * The query response no longer contains 'xdg-names', but instead list the supported standard names.
* | doc: foot.ini: document the Unicode ranges covered by the builtin glyphsDaniel Eklöf2024-08-09-3/+11
| |
* | csd: track pointer when rendering and handling CSD button clicksDaniel Eklöf2024-08-09-12/+98
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Render button as highlighted only when pointer is above them * Releasing the mouse button while *not* on the button does *not* activate the button When pressing, and holding, a mouse button, the compositor keeps sending motion events for the surface where the button was pressed, even if the mouse has moved outside it. We also don't get any surface leave/enter events. This meant that the button was rendered as highlighted, and a click registered, if the user pressed the mouse button while on the button, and then moved the cursor away from the button before releasing the button. This patch fixes it, by checking if the current cursor coordinates fall within the button surface.
* | input: CSD buttons are now triggered when releasing the mouse buttonDaniel Eklöf2024-08-09-3/+19
| | | | | | | | | | | | | | | | | | | | | | | | This is how most UIs work. Note that we (at least on River) don't get any surface enter/leave events while a button is held. This means we can't detect if the user pressed the mouse button while on a CSD button, but then moves the mouse outside. Releasing the mouse button will still activate the CSD button. Closes #1787
* | 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.
* | readme: remove CI badges for gitlab and sr.htDaniel Eklöf2024-08-07-2/+0
| |
* | readme: repology: use four columns instead of threeDaniel Eklöf2024-08-07-1/+1
| |
* | readme: repology: use three columns instead of oneDaniel Eklöf2024-08-07-1/+1
| |
* | changelog: osc-99: sound supportDaniel Eklöf2024-08-04-0/+8
| |
* | osc: kitty notifications: add support for XDG sound namesDaniel Eklöf2024-08-04-9/+31
| |
* | osc: kitty notifications: implement s=silentDaniel Eklöf2024-08-04-11/+43
| | | | | | | | | | | | | | | | 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}
* | term: reload_fonts(): don't ignore return value of thrd_join()Daniel Eklöf2024-08-04-2/+4
| | | | | | | | | | | | | | | | | | | | This should fix the ‘ret’ may be used uninitialized warning Closes #1789
* | Merge branch 'xstrjoin3'Craig Barnes2024-08-03-29/+42
|\ \
| * | xmalloc: remove delim param from xstrjoin() and add separate xstrjoin3()Craig Barnes2024-08-03-29/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This avoids the need for an unused third argument for most xstrjoin() calls and replaces the cases where it's needed with a more flexible function. Code generation is the same in both cases, when there are 2 string params and a compile-time known delimiter. This commit also converts 4 uses of xasprintf() to use xstrjoin*(). See also: https://godbolt.org/z/xsjrhv9b6
* | | osc: kitty notifications: ignore invalid IDsDaniel Eklöf2024-08-03-3/+33
|/ / | | | | | | | | | | | | | | | | | | | | | | | | Notification IDs must only use characters from [a-zA-Z0-9_-+.] Terminals **must** sanitize ids received from client programs before sending them back in responses, to mitigate input injection based attacks. That is, they must either reject ids containing characters not from the above set, or remove bad characters when reading ids sent to them. Foot implements the first: reject IDs containing characters not from the above set.
* | changelog: add new 'unreleased' sectionDaniel Eklöf2024-08-02-0/+11
| |
* | Merge branch 'releases/1.18'Daniel Eklöf2024-08-02-5/+11
|\|
| * meson: bump version to 1.18.01.18.0Daniel Eklöf2024-08-02-1/+1
| |
| * changelog: prepare for 1.18.0Daniel Eklöf2024-08-02-4/+10
|/
* readme: typo: foot -> foot'sDaniel Eklöf2024-08-02-1/+1
|
* readme: xtgettcap: mention tigetstr() compabilityDaniel Eklöf2024-08-02-0/+4
|
* changelog: more template parameters we've added to desktop-notificationsDaniel Eklöf2024-08-02-2/+3
|
* Remove a number of unused includesDaniel Eklöf2024-08-02-8/+0
|
* notify: codespell: programatically -> programmaticallyDaniel Eklöf2024-08-02-1/+1
|
* notify: codespell: notificaton -> notificationDaniel Eklöf2024-08-02-1/+1
|
* 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-244/+293
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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.
* notify: don't forget terminating NULL when patching notify helper's argvDaniel Eklöf2024-07-31-6/+10
|
* osc: kitty notifications: buttons, icons, app-name, categories etcDaniel Eklöf2024-07-31-78/+580
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: disable debug loggingDaniel Eklöf2024-07-30-1/+1
|
* notify: remove debug assertionDaniel Eklöf2024-07-30-3/+1
| | | | (FD 0 _is_ valid, after all)
* notify: ${icon}: don't fallback to app-idDaniel Eklöf2024-07-30-8/+5
| | | | | | * 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: don't close FD 0Daniel Eklöf2024-07-30-4/+11
| | | | | | | | | | | | | | | This fixes a regression where closing a terminal instance, or hard- or soft-resetting a terminal caused FD 0 to be closed. This meant it became re-usable. Usually, by memfd_create() when allocating a new surface buffer. So far nothing _really_ bad has happened. But what if FD 0 is now used by a memfd, and we close _another_ terminal instance? This causes our memfd to be closed. And then, when e.g. trying to scroll the terminal content: fallocate() fails with bad FD.
* readme: IRC: update link to point to the web interfaceDaniel Eklöf2024-07-27-2/+3
|
* readme: update mastodon linkDaniel Eklöf2024-07-27-1/+1
|
* notify: close notification by sending SIGINT to helperDaniel Eklöf2024-07-26-29/+65
| | | | | | | | | | | | | 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.
* pgo: add notify_close() stubDaniel Eklöf2024-07-25-0/+5
|
* osc: kitty notifications: implement the 'close' requestDaniel Eklöf2024-07-25-9/+92
| | | | | | | | | | | | | | | | 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\\'
* osc: kitty notification: implement 'close' eventsDaniel Eklöf2024-07-25-6/+30
| | | | | | Application can now request to receive a 'close' event when the notification is closed (but not necessarily activated), by adding 'c=1' to the notification request.
* notify: rename 'report' -> 'report_activated'Daniel Eklöf2024-07-25-5/+5
|
* notify: kitty notifications: fix ID string in activation eventDaniel Eklöf2024-07-25-2/+2
| | | | We forgot to prefix the notification ID with 'i='
* Merge branch 'kitty-notifications'Daniel Eklöf2024-07-25-99/+1087
|\
| * osc+notify: strcmp() -> streq()Daniel Eklöf2024-07-24-13/+13
| |
| * notify: try to read the daemon assigned notification ID from stdoutDaniel Eklöf2024-07-24-2/+55
| | | | | | | | | | 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-3/+3
| |
| * notify: don't create icon file on disk when we're not going to use itDaniel Eklöf2024-07-24-13/+27
| | | | | | | | | | | | | | We always prefer the symbolic name. Thus, there's no need to write raw PNG data to disk if we have a symbolic name. Furthermore, keep the file open until the cache entry is evicted.
| * osc: kitty notifications: don't include '?' in the query replyDaniel Eklöf2024-07-24-1/+1
| | | | | | | | No need to say we support queries, in the query reply...
| * notify: split up the ${action} template parameterDaniel Eklöf2024-07-23-18/+14
| | | | | | | | | | | | | | | | | | 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
| * notify: bug: always adjust amount of data left in stdout bufferDaniel Eklöf2024-07-23-3/+3
| |
| * osc: kitty notifications: implement queryDaniel Eklöf2024-07-23-6/+27
| |
| * doc: foot.ini: desktop-notification: remove 'notification dismissal'Daniel Eklöf2024-07-23-16/+3
| |
| * notify: name the activation action 'default'Daniel Eklöf2024-07-23-2/+2
| | | | | | | | | | This is less unique, but also works better with notification daemons that trigger the 'default' action when e.g. clicked.
| * notify: don't focus/report on notification dismissalDaniel Eklöf2024-07-23-19/+46
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: if there's a symbolic icon name, use itDaniel Eklöf2024-07-23-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | even if there's no graphical ID set. In other words, if there *is* a graphical ID, use the icon cache. Only if there is no graphical ID in the notification request do we fallback to the symbolic name. This means no icon will be displayed if there's no matching icon in the cache. Some examples. You can either pre-load the cache (with inline PNG data, a symbolic name, or both): printf '\e]99;g=123:n=firefox:p=icon:e=1;<PNG data>\e\\' printf '\e]99;g=123;this is a notification\e\\' or printf '\e]99;n=firefox;this is a notification\e\\'
| * notify: consume_stdout(): fix ASAN warningDaniel Eklöf2024-07-23-2/+4
| | | | | | | | | | | | | | | | This is an ASAN false positive; size is always 0 when we're passing a NULL pointer. Still, the warning is easy to avoid, so let's do that to reduce the noise level.
| * osc: remove unused includesDaniel Eklöf2024-07-23-3/+0
| |
| * pgo: updated stubs for notification functionsDaniel Eklöf2024-07-23-1/+17
| |
| * notify: add_icon(): check return value of write()Daniel Eklöf2024-07-23-4/+7
| |
| * notify: clean up logging messagesDaniel Eklöf2024-07-23-2/+4
| |
| * osc: cleanupDaniel Eklöf2024-07-23-16/+3
| |
| * notify: separate active notifications from unfinished kitty notificationsDaniel Eklöf2024-07-23-30/+57
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This fixes an issue where it wasn't possible to trigger multiple notifications with the same kitty notification ID. This is something that works in kitty, and there's no reason why it shouldn't work. The issue was that we track stdout, and the notification helper's PID in the notification struct. Thus, when a notification is being displayed, we can't re-use the same notification struct instance for another notification. This patch fixes this by adding a new notification list, 'active_notifications'. Whenever we detect that we need to track the helper (notification want's to either focus the window on activation, or send an event to the application), we add a copy of the notification to the 'active' list. The notification can then be removed from the 'kitty' list, allowing kitty notifications to re-use the same ID over and over again, even if old notifications are still being displayed.
| * osc: kitty notifications: updated support for iconsDaniel Eklöf2024-07-23-49/+245
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This implements the suggested protocol discussed in https://github.com/kovidgoyal/kitty/issues/7657. Icons are handled by loading a cache. Both in-band PNG data, and symbolic names are allowed. Applications use a graphical ID to reference the icon both when loading the cache, and when showing a notification. * 'g' is the graphical ID * 'n' is optional, and assigns a symbolic name to the icon * 'p=icon' - the payload is icon PNG data. It needs to be base64 encoded, but this is *not* implied. I.e. the application *must* use e=1 explicitly. To load an icon (in-band PNG data): printf '\e]99;g=123:p=icon;<base64-encoded-png-data>\e\\' or (symbolic name) printf '\e]99;g=123:n=firefox:p=icon;\e\\' Of course, we can combine the two, assigning *both* a symbolic name, *and* PNG data: printf '\e]99;g=123:n=firefox:p=icon;<base64-encoded-png>\e\\' Then, to use the icon in a notification: printf '\e]99;g=123;this is a notification\e\\' Foot also allows a *symbolic* icon to be defined and used at the same time: printf '\e]99;g=123:n=firefox;this is a notification\e\\' This obviously won't work with PNG data, since it uses the payload portion of the escape sequence.
| * notify: stdout is a bad nameDaniel Eklöf2024-07-23-9/+9
| |
| * notify: XDG token is now expected to be prefixed with xdgtoken=Daniel Eklöf2024-07-23-30/+74
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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: use xstrjoin() instead of xasprintf()Daniel Eklöf2024-07-23-8/+6
| |
| * pgo: update notify_notify() prototype, add notify_free()Daniel Eklöf2024-07-23-3/+8
| |
| * pgo: update spawn() prototypeDaniel Eklöf2024-07-23-3/+3
| |
| * changelog: new desktop-notifications config sectionDaniel Eklöf2024-07-23-0/+11
| |
| * osc: kitty notifications: implement focus|reportDaniel Eklöf2024-07-23-137/+410
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
| * unicode-mode: disable debug loggingDaniel Eklöf2024-07-23-1/+1
| |
| * wayland: add wayl_activate()Daniel Eklöf2024-07-23-2/+15
| | | | | | | | | | wayl_activate() takes an XDG activation token and does an XDG activation request.
| * spawn: add optional reaper callback, return pid_tDaniel Eklöf2024-07-23-19/+26
| | | | | | | | | | This will allow spawn() callers to do things when the spawned process has terminated.
| * osc: kitty notifications: use body as title, if no title is setDaniel Eklöf2024-07-23-2/+2
| | | | | | | | | | This mirrors kitty's behavior; if the user didn't set a title, but did set the body/text, use the body as title instead.