--startup_notification option as an alternative to -startup_notification (#1208)$HOME in path in your dunstrc. See man 3 wordexp for the details (#1215)monitor (eDP-1, HDMI-1, etc). This is more relyable than the order of monitors. (#1250)show_age_treshold = -1 (#1164)history-clear command to delete all notifications from history (#1131)history-rm command to remove a single notification from history (#1128)progress_bar_corner_radius option for adding rounded corners to the progress bar (off by default) (#1119)icon_corner_radius option for adding rounded corners to notification icons (#1139)idle_threshold turned on (#1140)override_dbus_timeout setting to override the notification timeout set via
dbus. (#1035)min_icon_size and max_icon_size a rule for even more flexibility
(#1069)scale as well. This way
notification stay visually in the same place on higher DPI screens. (#1039)action_name setting that was accidentally dropped. (#1051)dunstctl history. (#1060)progress_bar_min_width. Before it was an unused setting. (#1006)progress_bar_horizontal_alignment for changing the alignment of the progress
@@ -154,7 +186,7 @@ [global]
section. Please move your settings there.open_url was used without URL’s. (#1000)follow is now none again by default. This was the case before v1.7.0 as well. (#990).dunstctl action is now working again.icon_position = off not being respected (#996).enable_recursive_icon_lookup=true. Setting icon sizes
@@ -207,8 +239,8 @@ default_icon setting for setting the icon when no icons are given (#984)DUNST_DESKTOP_ENTRY. (#874)set_category for change a notifications category with rules. (1b72b2a)context and context_all mouse actions for opening the context menu (#848)open_url mouse action for opening url’s in a notification (#848)left_ptr when hovering over dunst (Wayland)
(#903)startup_notification and verbosity are now only available as a command
line arguments. (#803)idle_timeout=0 (#814)follow=none not working on Wayland (#814)config.h. (#803)text_icon_padding for adding padding between the notification icon and text
(#810)/etc/dunst/dunstrc (#798)history_ignore flag broken when using multiple rules (#747)DUNST_COMMAND_{PAUSE,RESUME,TOGGLE} (#830)min_icon_size option to automatically scale up icons to a desired value (#674)vertical_alignment option to control the text/icon alignment within the notification (#684)ignore_dbusclose setting (#732)dunstify notification client is now installed by default (#701)max_icon_size not working with dynamic width (#614)frame_color via rules (#498)skip_display rule option to skip initial notification display, and
include the notification in the history. (#590)ellipsize option to control how long lines should be ellipsized when word_wrap is set to false (#374)new_icon rule being ignored on notifications that had a raw icon (#423)match_transient and set_transient) is added
@@ -458,7 +490,7 @@ SERVICEDIR_(DBUS|SYSTEMD) params to overwrite them. (#463)always_run_script option to run script even if a notification is suppressed%n format flag for getting progress value without any extra charactersallow_markup is deprecated with markup as its replacementdunst - configuration file
The configuration is divided into sections in an ini-like format. Every section starts with the section's name in square brackets. After that is a list of key-value pairs that specify the settings. Whitespace is purely cosmetic and doesn't change the result.
-The 'global' section contains the general settings applying to all of dunst. The rest of the settings can be specified via rules and can be located in any section. These rules can change a notification based on it's properties. There are filtering rules and modifying rules. The filtering rules specify on what notifications the rule is applied and the modifying rules specify what is changed about the matching notifications. Some special sections have implied filters that cannot be changed. The "global" section, for example has no filters, thus applies to all notifications.
+The 'global' section contains the general settings applying to all of dunst. The rest of the settings can be specified via rules and can be located in any section. These rules can change a notification based on its properties. There are filtering rules and modifying rules. Filtering rules specify what notifications the rule applies to. Modifying rules specify changes to the matching notifications. Some special sections have implied filters that cannot be changed. For example, the "global" section has no filters: it applies to all notifications.
See RULES for more details.
All experimental settings are marked with Experimental
Specifies on which monitor the notifications should be displayed in, count starts at 0. See the follow setting.
+Specifies on which monitor the notifications should be displayed in, either by name or by number, starting from 0. See the follow setting.
Defines where the notifications should be placed in a multi-monitor setup. All values except none override the monitor setting.
-On Wayland there is no difference between mouse and keyboard focus. When either of the is used, the compositor will choose an output. This will generally be the output last interacted with.
+On Wayland there is no difference between mouse and keyboard focus. When either of them is used, the compositor will choose an output. This will generally be the output last interacted with.
The maximum height of a single notification.
The number of notifications that can appear at one time. When this limit is reached any additional notifications will be queued and displayed when the currently displayed ones either time out or are manually dismissed. The value 0 means no limit. If indicate_hidden is true, then the specified limit is reduced by 1 and the last notification is a message informing how many hidden notifications are waiting to be displayed. See the indicate_hidden entry for more information.
If set to true, display notifications with higher urgency above the others.
-If set to true or urgency_descending, display notifications with higher urgency above the others. critical first, then normal, then low.
+If set to false or id, sort notifications by id.
+If set to urgency_ascending, notifications are sorted by urgency, low first, then normal, then critical.
+If set to update, notifications are sorted by their update_time. So the most recent is always at the top. This means that if you set sort to update, and stack_duplicates to true, the duplicate will always be at the top.
+When the notification window is at the bottom of the screen, this order is automatically reversed. =item idle_threshold (default: 0)
Don't timeout notifications if user is idle longer than this time. See TIME FORMAT for valid times.
Set to 0 to disable.
A client can mark a notification as transient to bypass this setting and timeout anyway. Use a rule with 'set_transient = no' to disable this behavior.
@@ -386,7 +387,7 @@This setting enables the new icon lookup method. This new system will eventually be the old icon lookup.
-Currently icons are looked up in the icon_path. Since the icon_path wasn't recursive, one had to add a ton of paths to this list. This has been drastically simplified by the new lookup method. Now you only have to set icon_theme to the name of the theme you want. To enable this new behaviour, set enable_recursive_icon_lookup to true in the [experimental] section. See the respective settings for more details.
+Currently icons are looked up in the icon_path. Since the icon_path wasn't recursive, one had to add a ton of paths to this list. This has been drastically simplified by the new lookup method. Now you only have to set icon_theme to the name of the theme you want. To enable this new behaviour, set enable_recursive_icon_lookup to true in the [global] section. See the respective settings for more details.
Ignore the dbus closeNotification message. This is useful to enforce the timeout set by dunst configuration. Without this parameter, an application may close the notification sent before the user defined timeout.
A Notification will appear whenever notification's override_pause_level >= dunst's paused level. Setting this to values other than 0 allows you to create partial pause modes, where more urgent notifications get through, but less urgent stay paused. For example, when you can set a low battery noficiation's override_pause_level to 60 and then set dunst's pause level to 60. This will cause dunst to only show battery level notification (and other notifications with override_pause_level >= 60), while suspending others.
+Keyboard shortcuts are defined in the following format: "Modifier+key" where the modifier is one of ctrl,mod1,mod2,mod3,mod4 and key is any keyboard key.
@@ -655,7 +660,7 @@new_iconUpdates the icon of the notification, it should be a path or a name for a valid image. This overrides the icon that was sent with dunstify or another notification tool.
+Updates the icon of the notification, it should be a path or a name for a valid image. This overrides the icon that was sent with dunstify or another notification tool. Expansion of the argument is carried out using wordexp(3) with command substitution disabled.
icon_position (values: [left/right/top/off], default: left)default_iconSets the default icon of the notification, it should be a path or a name for a valid image. This does not override the icon that was sent with dunstify or another notification tool.
+Sets the default icon of the notification, it should be a path or a name for a valid image. This does not override the icon that was sent with dunstify or another notification tool. Expansion of the argument is carried out using wordexp(3) with command substitution disabled.
set_stack_tagAnother, less recommended way to get notifcations details from a script is via command line parameters. These are passed to the script in the following order: appname, summary, body, icon_path, urgency.
Where DUNST_ICON_PATH or icon_path is the absolute path to the icon file if there is one. DUNST_URGENCY or urgency is one of "LOW", "NORMAL" or "CRITICAL". DUNST_URLS is a newline-separated list of urls associated with the notification.
Note that some variables may be empty.
-If the notification is suppressed, the script will not be run unless always_run_scripts is set to true.
-If '~/' occurs at the beginning of the script parameter, it will get replaced by the users' home directory. If the value is not an absolute path, the directories in the PATH variable will be searched for an executable of the same name.
+If the notification is suppressed, the script will not be run unless always_run_script is set to true.
+The script parameter is expanded according to wordexp(3) with command substitution disabled. If the expanded value is not an absolute path, the directories in the PATH variable will be searched for an executable of the same name.
Colors are interpreted as X11 color values. This includes both verbatim color names such as "Yellow", "Blue", "White", etc as well as #RGB and #RRGGBB values.
You may also specify a transparency component in #RGBA or #RRGGBBAA format.
@@ -771,16 +776,16 @@All hints
See RULES for more detailed explanations for some options.
The current stable version of Dunst is 1.9.1 released on March 8 2023.
+The current stable version of Dunst is 1.10.0 released on Februari 19 2024.
Lots of exciting and useful features are being added to dunst, all while making -dunst even more configurable and reliable.
-For users:
-This release re-adds the keyboard shortcuts for those who have been missing -them. Also, support for drop-in files has been implemented. Files placed in -dunstrc.d/*.conf will be read after the main dunstrc. This may be useful for -theming (with pywal or otherwise). In the future we will add example drop-in -files for different default themes and special configuration.
-For maintainers:
-Not much has been changed for maintainers. Maybe you’ll find the drop-in files -useful for distro-specific fixes. Note that only the files in the directory of -the used dunstrc will be read (see dunst(1) for documentation).
+It’s been a while since the last release. That does not mean that the +development has been stagnent. There are some long requested features have been +implemented, like a do not disturb mode in the form of multiple pause levels. +You can specify the priority of notification and selectively pause them. The +progress bar rendering for low progress values has been fixed, with preparation +work being done for more progress bar customization.
+Since dunst gained Wayland support, Wayland received a lot of development. +Dunst needed to do some catchup for that. A new Wayland idle protocol is +implemented and support for Wayland touch screens and multi-seat has been +added. It’s now also possible to specify displays by their port name, instead +of number.
+Take a look at the changelog for all the bug fixes and improvements.
diff --git a/index.html b/index.html index 6f327f7..9f24b1b 100644 --- a/index.html +++ b/index.html @@ -1,7 +1,7 @@ - + diff --git a/index.xml b/index.xml index f0a0602..dcb486f 100644 --- a/index.xml +++ b/index.xml @@ -12,8 +12,7 @@