From 9cf99ea4bffd667ae59e4328a28b86dcefacb3f4 Mon Sep 17 00:00:00 2001 From: Daniel Eklöf Date: Fri, 26 Jul 2024 16:23:17 +0200 Subject: notify: close notification by sending SIGINT to helper 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. --- doc/foot.ini.5.scd | 5 +++++ 1 file changed, 5 insertions(+) (limited to 'doc') diff --git a/doc/foot.ini.5.scd b/doc/foot.ini.5.scd index 195baafe..df219e7b 100644 --- a/doc/foot.ini.5.scd +++ b/doc/foot.ini.5.scd @@ -524,6 +524,11 @@ xdgtoken=95ebdfe56e4f47ddb5bba9d7dc3a2c35 Closing a notification is only supported by the Kitty Desktop Notification protocol, OSC-99. + If set to the empty string (the default), foot will instead try to + close the notification by sending SIGINT to the notification + helper process. For example, *notify-send --wait* (libnotify >= + 0.8.0) responds to SIGINT by closing the notification. + Default: _not set_ *inhibit-when-focused* -- cgit v1.3