From 2da6730e5a67709e56e3342cdab42a9435e7c9e0 Mon Sep 17 00:00:00 2001 From: Benedikt Heine Date: Wed, 2 Aug 2017 15:56:10 +0200 Subject: [PATCH] Add docs for transient rules --- CHANGELOG.md | 2 ++ docs/dunst.pod | 12 +++++++----- 2 files changed, 9 insertions(+), 5 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 737f387..2264f8d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -7,6 +7,8 @@ ## Changed - transient hints are now handled + An additional rule option (`match_transient` and `set_transient`) is added + to optionally reset the transient setting ## 1.2.0 - 2017-07-12 diff --git a/docs/dunst.pod b/docs/dunst.pod index b91df5e..d334ea0 100644 --- a/docs/dunst.pod +++ b/docs/dunst.pod @@ -235,6 +235,7 @@ Don't timeout notifications if user is idle longer than this value (in seconds). Set to 0 to disable. Transient notifications will ignore this setting and timeout anyway. +Use a rule overwriting with 'set_transient = no' to disable this behavior. =item B (default: "Monospace 8") @@ -558,9 +559,10 @@ matched. =item B Notifications can be matched for any of the following attributes: appname, -summary, body, icon, category and msg_urgency where each is the respective -notification attribute to be matched and 'msg_urgency' is the urgency of the -notification, it is named so to not conflict with trying to modify the urgency. +summary, body, icon, category, match_transient and msg_urgency where each is +the respective notification attribute to be matched and 'msg_urgency' is the +urgency of the notification, it is named so to not conflict with trying to +modify the urgency. To define a matching rule simply assign the specified value to the value that should be matched, for example: @@ -576,8 +578,8 @@ Shell-like globing is supported. =item B The following attributes can be overridden: timeout, urgency, foreground, -background, new_icon, format where, as with the filtering attributes, each one -corresponds to the respective notification attribute to be modified. +background, new_icon, set_transient, format where, as with the filtering attributes, +each one corresponds to the respective notification attribute to be modified. As with filtering, to make a rule modify an attribute simply assign it in the rule definition.