1dunst(5) Dunst Reference dunst(5)
2
6 dunst - configuration file
7
9 An example configuration file is included (usually /etc/dunst/dunstrc).
10 Note: this was previously /usr/share/dunst/dunstrc. To change the
11 configuration, copy this file to ~/.config/dunst/dunstrc and edit it
12 accordingly.
13 The configuration is divided into sections in an ini-like format. The
15 'global' section contains most general settings while the setions
16 'urgency_low', 'urgency_normal' and 'urgency_critical' are for low,
17 normal and critical urgency notifications respectively. The 'shortcuts'
18 section (deprecated) contains all keyboard configuration and the
19 'experimental' section all the features that have not yet been tested
20 thoroughly.
21 Any section that is not one of the above is assumed to be a rule, see
23 RULES for more details.
24 For backwards compatibility reasons the section name 'frame' is
26 considered bound and can't be used as a rule.
27 Global section
29 monitor (default: 0)
30 Specifies on which monitor the notifications should be displayed
31 in, count starts at 0. See the follow setting.
32 follow (values: [none/mouse/keyboard] default: none)
34 Defines where the notifications should be placed in a multi-monitor
35 setup. All values except none override the monitor setting.
36 On Wayland there is no difference between mouse and keyboard focus.
38 When either of the is used, the compositor will choose an output.
39 This will generally be the output last interacted with.
40 none
42 The notifications will be placed on the monitor specified by
43 the monitor setting.
44 mouse
46 The notifications will be placed on the monitor that the mouse
47 is currently in.
48 keyboard
50 The notifications will be placed on the monitor that contains
51 the window with keyboard focus.
52 geometry (format: [{width}][x{height}][+/-{x}[+/-{y}]], default:
54 "0x0+0-0")
55 The geometry of the window the notifications will be displayed in.
56 width
58 The width of the notification window in pixels. A negative
59 value sets the width to the screen width minus the absolute
60 value of the width. If the width is omitted then the window
61 expands to cover the whole screen. If it's 0 the window expands
62 to the width of the longest message being displayed.
63 height
65 The number of notifications that can appear at one time. When
66 this limit is reached any additional notifications will be
67 queued and displayed when the currently displayed ones either
68 time out or are manually dismissed. If indicate_hidden is true,
69 then the specified limit is reduced by 1 and the last
70 notification is a message informing how many hidden
71 notifications are waiting to be displayed. See the
72 indicate_hidden entry for more information.
73 The physical(pixel) height of the notifications vary depending
75 on the number of lines that need to be displayed.
76 See notification_height for changing the physical height.
78 x/y Respectively the horizontal and vertical offset in pixels from
80 the corner of the screen that the notification should be drawn
81 at. For the horizontal(x) offset, a positive value is measured
82 from the left of the screen while a negative one from the
83 right. For the vertical(y) offset, a positive value is measured
84 from the top while a negative from the bottom.
85 It's important to note that the positive and negative sign DOES
87 affect the position even if the offset is 0. For example, a
88 horizontal offset of +0 puts the notification on the left
89 border of the screen while a horizontal offset of -0 at the
90 right border. The same goes for the vertical offset.
91 progress_bar (values: [true/false], default: true)
93 When an integer value is passed to dunst as a hint (see NOTIFY-
94 SEND), a progress bar will be drawn at the bottom of the
95 notification. This behavior can be turned off by setting this
96 setting to false.
97 progress_bar_height (default: 10)
99 The height of the progress bar in pixel. This includes the frame.
100 Make sure this value is bigger than twice the frame width.
101 progress_bar_min_width (default: 150)
103 The minimum width of the progress bar in pixels. The notification
104 is rescaled to fit the bar.
105 progress_bar_max_width (default: 300)
107 The maximum width of the progress bar in pixels. The notification
108 is resized to fit the progress bar.
109 progress_bar_frame_width (default: 1)
111 The frame width of the progress bar in pixels. This value should be
112 smaller than half of the progress bar height.
113 indicate_hidden (values: [true/false], default: true)
115 If this is set to true, a notification indicating how many
116 notifications are not being displayed due to the notification limit
117 (see geometry) will be shown in place of the last notification
118 slot.
119 Meaning that if this is enabled the number of visible notifications
121 will be 1 less than what is specified in geometry, the last slot
122 will be taken by the hidden count.
123 shrink (values: [true/false], default: false)
125 Shrink window if it's smaller than the width. Will be ignored if
126 width is 0.
127 This is used mainly in order to have the shrinking benefit of
129 dynamic width (see geometry) while also having an upper bound on
130 how long a notification can get before wrapping.
131 transparency (default: 0)
133 A 0-100 range on how transparent the notification window should be,
134 with 0 being fully opaque and 100 invisible.
135 This setting will only work if a compositor is running.
137 notification_height (default: 0)
139 The minimum height of the notification window in pixels. If the
140 text and padding cannot fit in within the height specified by this
141 value, the height will be increased as needed.
142 separator_height (default: 2)
144 The height in pixels of the separator between notifications, if set
145 to 0 there will be no separating line between notifications.
146 padding (default: 0)
148 The distance in pixels from the content to the separator/border of
149 the window in the vertical axis
150 horizontal_padding (default: 0)
152 The distance in pixels from the content to the border of the window
153 in the horizontal axis
154 text_icon_padding (default: 0)
156 The distance in pixels from the text to the icon (or vice versa) in
157 the horizontal axis.
158 Setting this to a non-zero value overwrites any padding that
160 horizontal_padding was adding between the notification text and
161 icon.
162 So for example setting
164 text_icon_padding=10
166 horizontal_padding=10
167 is equivalent to
169 text_icon_padding=0
171 horizontal_padding=10
172 frame_width (default: 0)
174 Defines width in pixels of frame around the notification window.
175 Set to 0 to disable.
176 frame_color color (default: #888888)
178 Defines color of the frame around the notification window. See
179 COLORS.
180 separator_color (values: [auto/foreground/frame/#RRGGBB] default: auto)
182 Sets the color of the separator line between two notifications.
183 auto
185 Dunst tries to find a color that fits the rest of the
186 notification color scheme automatically.
187 foreground
189 The color will be set to the same as the foreground color of
190 the topmost notification that's being separated.
191 frame
193 The color will be set to the frame color of the notification
194 with the highest urgency between the 2 notifications that are
195 being separated.
196 anything else
198 Any other value is interpreted as a color, see COLORS
199 sort (values: [true/false], default: true)
201 If set to true, display notifications with higher urgency above the
202 others.
203 idle_threshold (default: 0)
205 Don't timeout notifications if user is idle longer than this time.
206 See TIME FORMAT for valid times.
207 Set to 0 to disable.
209 A client can mark a notification as transient to bypass this
211 setting and timeout anyway. Use a rule with 'set_transient = no' to
212 disable this behavior.
213 Note: this doesn't work on xwayland.
215 layer (Wayland only)
217 One of bottom, top or overlay.
218 Place dunst notifications on the selected layer. Using overlay will
220 cause notifications to be displayed above fullscreen windows,
221 though this may also occur at top depending on your compositor.
222 In Wayland, Notifications won't be delayed when in fullscreen (like
224 when setting fullscreen to pushback in X11). This is a Wayland
225 limitation.
226 The bottom layer is below all windows and above the background.
228 Default: overlay
230 force_xwayland (values: [true/false], default: false) (Wayland only)
232 Force the use of X11 output, even on a wayland compositor. This
233 setting has no effect when not using a Wayland compositor.
234 font (default: "Monospace 8")
236 Defines the font or font set used. Optionally set the size as a
237 decimal number after the font name and space. Multiple font
238 options can be separated with commas.
239 This options is parsed as a Pango font description.
241 line_height (default: 0)
243 The amount of extra spacing between text lines in pixels. Set to 0
244 to disable.
245 markup (values: [full/strip/no], default: no)
247 Defines how markup in notifications is handled.
248 It's important to note that markup in the format option will be
250 parsed regardless of what this is set to.
251 Possible values:
253 full
255 Allow a small subset of html markup in notifications
256 <b>bold</b>
258 <i>italic</i>
259 <s>strikethrough</s>
260 <u>underline</u>
261 For a complete reference see
263 <https://developer.gnome.org/pango/stable/pango-Markup.html>
264 strip
266 This setting is provided for compatibility with some broken
267 clients that send markup even though it's not enabled on the
268 server.
269 Dunst will try to strip the markup but the parsing is
271 simplistic so using this option outside of matching rules for
272 specific applications IS GREATLY DISCOURAGED.
273 See RULES
275 no Disable markup parsing, incoming notifications will be treated
277 as plain text. Dunst will not advertise that it can parse
278 markup if this is set as a global setting.
279 format (default: "%s %b")
281 Specifies how the various attributes of the notification should be
282 formatted on the notification window.
283 Regardless of the status of the markup setting, any markup tags
285 that are present in the format will be parsed. Note that because of
286 that, if a literal ampersand (&) is needed it needs to be escaped
287 as '&'
288 If '\n' is present anywhere in the format, it will be replaced with
290 a literal newline.
291 If any of the following strings are present, they will be replaced
293 with the equivalent notification attribute.
294 %a appname
296 %s summary
297 %b body
298 %i iconname (including its path)
299 %I iconname (without its path)
300 %p progress value ([ 0%] to [100%])
301 %n progress value without any extra characters
302 %% Literal %
303 If any of these exists in the format but hasn't been specified in
305 the notification (e.g. no icon has been set), the placeholders will
306 simply be removed from the format.
307 alignment (values: [left/center/right], default: left)
309 Defines how the text should be aligned within the notification.
310 vertical_alignment (values: [top/center/bottom], default: center)
312 Defines how the text and icon should be aligned vertically within
313 the notification. If icons are disabled, this option has no effect.
314 show_age_threshold (default: -1)
316 Show age of message if message is older than this time. See TIME
317 FORMAT for valid times.
318 Set to -1 to disable.
320 word_wrap (values: [true/false], default: false)
322 Specifies how very long lines should be handled
323 If it's set to false, long lines will be truncated and ellipsized.
325 If it's set to true, long lines will be broken into multiple lines
327 expanding the notification window height as necessary for them to
328 fit.
329 ellipsize (values: [start/middle/end], default: middle)
331 If word_wrap is set to false, specifies where truncated lines
332 should be ellipsized.
333 ignore_newline (values: [true/false], default: false)
335 If set to true, replace newline characters in notifications with
336 whitespace.
337 stack_duplicates (values: [true/false], default: true)
339 If set to true, duplicate notifications will be stacked together
340 instead of being displayed separately.
341 Two notifications are considered duplicate if the name of the
343 program that sent it, summary, body, icon and urgency are all
344 identical.
345 hide_duplicate_count (values: [true/false], default: false)
347 Hide the count of stacked duplicate notifications.
348 show_indicators (values: [true/false], default: true)
350 Show an indicator if a notification contains actions and/or open-
351 able URLs. See ACTIONS below for further details.
352 icon_position (values: [left/right/off], default: off)
354 Defines the position of the icon in the notification window.
355 Setting it to off disables icons.
356 min_icon_size (default: 0)
358 Defines the minimum size in pixels for the icons. If the icon is
359 larger than or equal to the specified value it won't be affected.
360 If it's smaller then it will be scaled up so that the smaller axis
361 is equivalent to the specified size.
362 Set to 0 to disable icon upscaling. (default)
364 If icon_position is set to off, this setting is ignored.
366 max_icon_size (default: 0)
368 Defines the maximum size in pixels for the icons. If the icon is
369 smaller than or equal to the specified value it won't be affected.
370 If it's larger then it will be scaled down so that the larger axis
371 is equivalent to the specified size.
372 Set to 0 to disable icon downscaling. (default)
374 If both min_icon_size and max_icon_size are enabled, the latter
376 gets the last say.
377 If icon_position is set to off, this setting is ignored.
379 icon_path (default:
381 "/usr/share/icons/gnome/16x16/status/:/usr/share/icons/gnome/16x16/devices/")
382 Can be set to a colon-separated list of paths to search for icons
383 to use with notifications.
384 Dunst doesn't currently do any type of icon lookup outside of these
386 directories.
387 sticky_history (values: [true/false], default: true)
389 If set to true, notifications that have been recalled from history
390 will not time out automatically.
391 history_length (default: 20)
393 Maximum number of notifications that will be kept in history. After
394 that limit is reached, older notifications will be deleted once a
395 new one arrives. See HISTORY.
396 dmenu (default: "/usr/bin/dmenu")
398 The command that will be run when opening the context menu. Should
399 be either a dmenu command or a dmenu-compatible menu.
400 browser (default: "/usr/bin/firefox")
402 The command that will be run when opening a URL. The URL to be
403 opened will be appended to the end of the value of this setting.
404 always_run_script (values: [true/false] default: true]
406 Always run rule-defined scripts, even if the notification is
407 suppressed with format = "". See SCRIPTING.
408 title (default: "Dunst")
410 Defines the title of notification windows spawned by dunst.
411 (_NET_WM_NAME property). There should be no need to modify this
412 setting for regular use.
413 class (default: "Dunst")
415 Defines the class of notification windows spawned by dunst. (First
416 part of WM_CLASS). There should be no need to modify this setting
417 for regular use.
418 startup_notification (values: [true/false], default: false)
420 Display a notification on startup. This is usually used for
421 debugging and there shouldn't be any need to use this option.
422 verbosity (values: 'crit', 'warn', 'mesg', 'info', 'debug' default
424 'mesg')
425 Do not display log messages, which have lower precedence than
426 specified verbosity. This won't affect printing notifications on
427 the terminal. Use the '-print' option for this.
428 force_xinerama (values: [true/false], default: false) (X11 only)
430 Use the Xinerama extension instead of RandR for multi-monitor
431 support. This setting is provided for compatibility with older
432 nVidia drivers that do not support RandR and using it on systems
433 that support RandR is highly discouraged.
434 By enabling this setting dunst will not be able to detect when a
436 monitor is connected or disconnected which might break follow mode
437 if the screen layout changes.
438 corner_radius (default: 0)
440 Define the corner radius in pixels. A corner radius of 0 will
441 result in rectangular shaped notifications.
442 By enabling this setting the outer border and the frame will be
444 shaped. If you have multiple notifications, the whole window is
445 shaped, not every single notification.
446 To avoid the corners clipping the icon or text the corner radius
448 will be automatically lowered to half of the notification height if
449 it exceeds it.
450 mouse_left/middle/right_click (values:
452 [none/do_action/close_current/close_all])
453 Defines action of mouse click.
454 none
456 Don't do anything.
457 do_action (default for mouse_middle_click)
459 If the notification has exactly one action, or one is marked as
460 default, invoke it. If there are multiple and no default, open
461 the context menu.
462 close_current (default for mouse_left_click)
464 Close current notification.
465 close_all (default for mouse_right_click)
467 Close all notifications.
468 ignore_dbusclose (default: false)
470 Ignore the dbus closeNotification message. This is useful to
471 enforce the timeout set by dunst configuration. Without this
472 parameter, an application may close the notification sent before
473 the user defined timeout.
474 Shortcut section DEPRECATED SEE DUNSTCTL (X11 only)
476 Keyboard shortcuts are defined in the following format: "Modifier+key"
477 where the modifier is one of ctrl,mod1,mod2,mod3,mod4 and key is any
478 keyboard key.
479 close
481 command line flag: -key <key>
482 Specifies the keyboard shortcut for closing a notification.
484 close_all
486 command line flag: -all_key <key>
487 Specifies the keyboard shortcut for closing all currently displayed
489 notifications.
490 history
492 command line flag: -history_key <key>
493 Specifies the keyboard shortcut for recalling a single notification
495 from history.
496 context
498 command line flag: -context_key <key>
499 Specifies the keyboard shortcut that opens the context menu.
501 Urgency sections
503 The urgency sections work in a similar way to rules and can be used to
504 specify attributes for the different urgency levels of notifications
505 (low, normal, critical). Currently only the background, foreground,
506 hightlight, timeout, frame_color and icon attributes can be modified.
507 The urgency sections are urgency_low, urgency_normal, urgency_critical
509 for low, normal and critical urgency respectively.
510 See the example configuration file for examples.
512 Additionally, you can override these settings via the following command
514 line flags:
515 Please note these flags may be removed in the future. See issue #328 in
517 the bug tracker for discussions (See REPORTING BUGS).
518 -li/ni/ci icon
520 Defines the icon for low, normal and critical notifications
521 respectively.
522 Where icon is a path to an image file containing the icon.
524 -lf/nf/cf color
526 Defines the foreground color for low, normal and critical
527 notifications respectively.
528 See COLORS for the value format.
530 -lb/nb/cb color
532 Defines the background color for low, normal and critical
533 notifications respectively.
534 See COLORS for the value format.
536 -lh/nh/ch color
538 Defines the highlight color for low, normal and critical
539 notifications respectively.
540 See COLORS for the value format.
542 -lfr/nfr/cfr color
544 Defines the frame color for low, normal and critical notifications
545 respectively.
546 See COLORS for more information
548 -lto/nto/cto secs
550 Defines the timeout time for low, normal and critical notifications
551 respectively. See TIME FORMAT for valid times.
552
554 Dunst now contains a command line control command that can be used to
555 interact with it. It supports all functions previously done only via
556 keyboard shortcuts but also has a lot of extra functionality. So see
557 more see dunstctl(1).
558
560 Dunst saves a number of notifications (specified by history_length) in
561 memory. These notifications can be recalled (i.e. redisplayed) by
562 calling dunstctl history (see dunstctl(1)). Whether these notifications
563 will time out like if they have been just send depends on the value of
564 the sticky_history setting.
565 Past notifications are redisplayed in a first-in-last-out order,
567 meaning that pressing the history key once will bring up the most
568 recent notification that had been closed/timed out.
569
571 Dunst has Wayland support since version 1.6.0. Because the Wayland
572 protocol is more focused on security, some things that are possible in
573 X11 are not possible in Wayland. Those differences are reflected in the
574 configuration. The main things that change are that dunst on Wayland
575 cannot use global hotkeys (they are deprecated anyways, use dunstctl)
576 and it cannot detect if an application is fullscreen. If you want to
577 see notifications when in fullscreen, set layer = overlay in the global
578 options.
579 Note that the same limitations exist when using xwayland. If something
581 doesn't quite work in Wayland, please file a bug report. In the mean
582 time, you can try if the X11 output does work on wayland. Use
583 force_xwayland = true for that.
584 If you have your dunst notifications on the same side of your display
586 as your status bar, you might notice that your notifications appear a
587 bit higher or lower than on X11. This is because the notification
588 cannot be placed on top of your status bar. The notifications are
589 placed relative to your status bar, making them appear higher or lower
590 by the height of your status bar. We cannot do anything about that
591 behavior, so you will need to change your geometry variable
592 accordingly.
593
595 Rules allow the conditional modification of notifications. They are
596 defined by creating a section in the configuration file that has any
597 name that is not already used internally (i.e. any name other than
598 'global', 'experimental', 'frame', 'shortcuts', 'urgency_low',
599 'urgency_normal' and 'urgency_critical').
600 There are 2 parts in configuring a rule: Defining the filters that
602 control when a rule should apply and then the actions that should be
603 taken when the rule is matched.
604 filtering
606 Notifications can be matched for any of the following attributes:
607 "appname" (discouraged, see desktop_entry)
609 The name of the application as reported by the client. Be aware
610 that the name can often differ depending on the locale used.
611 "body"
613 The body of the notification
614 "category"
616 The category of the notification as defined by the notification
617 spec. See
618 https://developer.gnome.org/notification-spec/#categories
619 "desktop_entry"
621 GLib based applications export their desktop-entry name. In
622 comparison to the appname, the desktop-entry won't get
623 localized.
624 "icon"
626 The icon of the notification in the form of a file path. Can be
627 empty if no icon is available or a raw icon is used instead.
628 "match_transient"
630 Match if the notification has been declared as transient by the
631 client or by some other rule.
632 See "set_transient" for more details about this attribute.
634 "msg_urgency"
636 Matches the urgency of the notification as set by the client or
637 by some other rule.
638 "stack_tag"
640 Matches the stack tag of the notification as set by the client
641 or by some other rule.
642 See set_stack_tag for more information about stack tags.
644 "summary"
646 Matches the summary, 'title', of the notification.
647 "msg_urgency" is the urgency of the notification, it is named so to
649 not conflict with trying to modify the urgency.
650 Instead of the appname filter, it's recommended to use the
652 desktop_entry filter.
653 To define a matching rule simply assign the specified value to the
655 value that should be matched, for example:
656 appname="notify-send"
658 Matches only messages that were send via notify-send. If multiple
660 filter expressions are present, all of them have to match for the
661 rule to be applied (logical AND).
662 Shell-like globing is supported.
664 modifying
666 The following attributes can be overridden:
667 "background"
669 The background color of the notification. See COLORS for
670 possible values.
671 "foreground"
673 The foreground color of the notification. See COLORS for
674 possible values.
675 "highlight"
677 The highlight color of the notification. This color is used for
678 coloring the progress bar. See COLORS for possible values.
679 "format"
681 Equivalent to the "format" setting.
682 "frame_color"
684 The frame color color of the notification. See COLORS for
685 possible values.
686 "fullscreen" (X11 only)
688 One of show, delay, or pushback.
689 This attribute specifies how notifications are handled if a
691 fullscreen window is focused. By default it's set to show so
692 notifications are being shown.
693 Other possible values are delay: Already shown notifications
695 are continued to be displayed until they are dismissed or time
696 out but new notifications will be held back and displayed when
697 the focus to the fullscreen window is lost.
698 Or pushback which is equivalent to delay with the difference
700 that already existing notifications are paused and hidden until
701 the focus to the fullscreen window is lost.
702 See layer to change fullscreen behavior in Wayland
704 Default: show
706 "new_icon"
708 Updates the icon of the notification, it should be a path to a
709 valid image.
710 "set_stack_tag"
712 Sets the stack tag for the notification, notifications with the
713 same (non-empty) stack tag will replace each-other so only the
714 newest one is visible. This can be useful for example in volume
715 or brightness notifications where you only want one of the same
716 type visible.
717 The stack tag can be set by the client with the 'synchronous',
719 'private-synchronous' 'x-canonical-private-synchronous' or the
720 'x-dunst-stack-tag' hints.
721 "set_transient"
723 Sets whether the notification is considered transient.
724 Transient notifications will bypass the idle_threshold setting.
725 By default notifications are _not_ considered transient but
727 clients can set the value of this by specifying the 'transient'
728 hint when sending notifications.
729 "timeout"
731 Equivalent to the "timeout" setting in the urgency sections.
732 "urgency"
734 This sets the notification urgency.
735 IMPORTANT NOTE: This currently DOES NOT re-apply the attributes
737 from the urgency_* sections. The changed urgency will only be
738 visible in rules defined later. Use "msg_urgency" to match it.
739 "skip_display"
741 Setting this to true will prevent the notification from being
742 displayed initially but will be saved in history for later
743 viewing.
744 As with the filtering attributes, each one corresponds to the
746 respective notification attribute to be modified.
747 As with filtering, to make a rule modify an attribute simply assign
749 it in the rule definition.
750 If the format is set to an empty string, the notification will not
752 be suppressed.
753 SCRIPTING
755 Within rules you can specify a script to be run every time the rule is
756 matched by assigning the 'script' option to the name of the script to
757 be run.
758 When the script is called details of the notification that triggered it
760 will be passed via environment variables. The following variables are
761 available: DUNST_APP_NAME, DUNST_SUMMARY, DUNST_BODY, DUNST_ICON_PATH,
762 DUNST_URGENCY, DUNST_ID, DUNST_PROGRESS, DUNST_CATEGORY,
763 DUNST_STACK_TAG, DUNST_URLS, DUNST_TIMEOUT, DUNST_TIMESTAMP and
764 DUNST_STACK_TAG.
765 Another, less recommended way to get notifcations details from a script
767 is via command line parameters. These are passed to the script in the
768 following order: appname, summary, body, icon_path, urgency.
769 Where DUNST_ICON_PATH or icon_path is the absolute path to the icon
771 file if there is one. DUNST_URGENCY or urgency is one of "LOW",
772 "NORMAL" or "CRITICAL". DUNST_URLS is a newline-separated list of urls
773 associated with the notification.
774 Note that some variables may be empty.
776 If the notification is suppressed, the script will not be run unless
778 always_run_scripts is set to true.
779 If '~/' occurs at the beginning of the script parameter, it will get
781 replaced by the users' home directory. If the value is not an absolute
782 path, the directories in the PATH variable will be searched for an
783 executable of the same name.
784
786 Colors are interpreted as X11 color values. This includes both verbatim
787 color names such as "Yellow", "Blue", "White", etc as well as #RGB and
788 #RRGGBB values.
789 You may also specify a transparency component in #RGBA or #RRGGBBAA
791 format.
792 NOTE: '#' is interpreted as a comment, to use it the entire value needs
794 to be in quotes like so: separator_color="#123456"
795 NOTIFY-SEND
797 dunst is able to get different colors for a message via notify-send.
798 In order to do that you have to add a hint via the -h option. The
799 progress value can be set with a hint, too.
800 notify-send -h string:fgcolor:#ff4444
802 notify-send -h string:bgcolor:#4444ff -h string:fgcolor:#ff4444 -h
803 string:frcolor:#44ff44
804 notify-send -h int:value:42 "Working ..."
805
807 Dunst allows notifiers (i.e.: programs that send the notifications) to
808 specify actions. Dunst has support for both displaying indicators for
809 these, and interacting with these actions.
810 If "show_indicators" is true and a notification has an action, an "(A)"
812 will be prepended to the notification format. Likewise, an "(U)" is
813 prepended to notifications with URLs. It is possible to interact with
814 notifications that have actions regardless of this setting, though it
815 may not be obvious which notifications HAVE actions.
816 The "context" keybinding is used to interact with these actions, by
818 showing a menu of possible actions. This feature requires "dmenu" or a
819 dmenu drop-in replacement present.
820 Alternatively, you can invoke an action with a middle click on the
822 notification. If there is exactly one associated action, or one is
823 marked as default, that one is invoked. If there are multiple, the
824 context menu is shown. The same applies to URLs when there are no
825 actions.
826
828 A time can be any decimal integer value suffixed with a time unit. If
829 no unit given, seconds ("s") is taken as default.
830 Time units understood by dunst are "ms", "s", "m", "h" and "d".
832 Example time: "1000ms" "10m"
834
836 Dunst can be paused via the `dunstctl set-paused true` command. To
837 unpause dunst use `dunstctl set-paused false`. Alternatively you can
838 send SIGUSR1 and SIGUSR2 to pause and unpause respectively. For
839 Example:
840 killall -SIGUSR1 dunst # pause
842 killall -SIGUSR2 dunst # resume
843 When paused dunst will not display any notifications but keep all
845 notifications in a queue. This can for example be wrapped around a
846 screen locker (i3lock, slock) to prevent flickering of notifications
847 through the lock and to read all missed notifications after returning
848 to the computer.
849
851 These are the places where dunst will look for a configuration file.
852 They are listed here in order and if dunst finds one of them, it will
853 stop looking for more.
854 $XDG_CONFIG_HOME/dunst/dunstrc
856 $HOME/.config/dunst/dunstrc
858 -or-
860 $XDG_CONFIG_HOME/dunst/dunstrc
862 /etc/xdg/dunst/dunstrc
864 /etc/dunst/dunstrc
866 This is where the default config file is located
867
869 Written by Sascha Kruse <knopwob@googlemail.com>
870
872 Bugs and suggestions should be reported on GitHub at
873 https://github.com/dunst-project/dunst/issues
874
876 Copyright 2013 Sascha Kruse and contributors (see LICENSE for licensing
877 information)
878 If you feel that copyrights are violated, please send me an email.
880
882 dunstctl(1), dwm(1), dmenu(1), twmn(1), notify-send(1)
8831.6.1 2021-02-27 dunst(5)