1dunst(5) Dunst Reference dunst(5)
2
6 dunst - configuration file
7
9 The configuration is divided into sections in an ini-like format. Every
10 section start with the section's name in square brackets. After that is
11 a list of key-value pairs that specify the settings. Whitespace is
12 purely cosmetic and doesn't matter for the result.
13 The 'global' section contains the general settings applying to all of
15 dunst. The rest of the settings can be specified via rules and can be
16 located in any section. These rules can change a notification based on
17 it's properties. There are filtering rules and modifying rules. The
18 filtering rules specify on what notifications the rule is applied and
19 the modifying rules specify what is changed about the matching
20 notifications. Some special sections have implied filters that cannot
21 be changed. The "global" section, for example has no filters, thus
22 applies to all notifications.
23 See RULES for more details.
25 The 'experimental' section contains all the features that have not yet
27 been tested thoroughly and may be changed at any time.
28 Global section
30 monitor (default: 0)
31 Specifies on which monitor the notifications should be displayed
32 in, count starts at 0. See the follow setting.
33 follow (values: [none/mouse/keyboard] default: none)
35 Defines where the notifications should be placed in a multi-monitor
36 setup. All values except none override the monitor setting.
37 On Wayland there is no difference between mouse and keyboard focus.
39 When either of the is used, the compositor will choose an output.
40 This will generally be the output last interacted with.
41 none
43 The notifications will be placed on the monitor specified by
44 the monitor setting.
45 mouse
47 The notifications will be placed on the monitor that the mouse
48 is currently in.
49 keyboard
51 The notifications will be placed on the monitor that contains
52 the window with keyboard focus.
53 geometry DEPRECATED
55 This setting is deprecated. It's split up into width, height,
56 origin, notification_limit and offset.
57 width
59 The width of the notification window in pixels. This can be a
60 single number to specify a constant width or two numbers for the
61 minimum and maximum width. The notification will expand from the
62 minimum width as neccesary.
63 Examples:
65 width = 300 # constant width of 300
66 width = (0, 300) # width between 0 and 300
67 height
69 The maximum height of a single notification.
70 notification_limit (default: 0)
72 The number of notifications that can appear at one time. When this
73 limit is reached any additional notifications will be queued and
74 displayed when the currently displayed ones either time out or are
75 manually dismissed. The value 0 means no limit. If indicate_hidden
76 is true, then the specified limit is reduced by 1 and the last
77 notification is a message informing how many hidden notifications
78 are waiting to be displayed. See the indicate_hidden entry for more
79 information.
80 origin (default: top-right)
82 The origin of the notification window on the screen. It can then be
83 moved with offset. Origin can be one of:
84 top-left
85 top-center
86 top-right
87 bottom-left
88 bottom-center
89 bottom-right
90 left-center
91 center
92 right-center
93 offset format: (horizontal, vertical)
95 Respectively the horizontal and vertical offset in pixels from the
96 corner of the screen specified by origin. Both values should always
97 be positive or zero.
98 Examples:
100 origin = top-right
101 offset = 10x300 # a margin of 10 pixels from the right and
102 300 pixels from the top
103 scale (default: 0, X11 only)
105 Specifies a scale factor for dimensions to adapt notifications to
106 HiDPI screens. This scales the notification geometry and it's
107 contents. It is not recommended to use a fractional scaling factor,
108 as this may result in things being one pixel off. Try to use a
109 whole number scaling factor and adjust the font size and other
110 sizes as needed. If 0 is specified, the scale factor is auto-
111 detected.
112 progress_bar (values: [true/false], default: true)
114 When an integer value is passed to dunst as a hint (see NOTIFY-
115 SEND), a progress bar will be drawn at the bottom of the
116 notification. This behavior can be turned off by setting this
117 setting to false.
118 progress_bar_height (default: 10)
120 The height of the progress bar in pixel. This includes the frame.
121 Make sure this value is bigger than twice the frame width.
122 progress_bar_min_width (default: 150)
124 The minimum width of the progress bar in pixels. The notification
125 is rescaled to fit the bar.
126 progress_bar_max_width (default: 300)
128 The maximum width of the progress bar in pixels. The notification
129 is resized to fit the progress bar.
130 progress_bar_frame_width (default: 1)
132 The frame width of the progress bar in pixels. This value should be
133 smaller than half of the progress bar height.
134 indicate_hidden (values: [true/false], default: true)
136 If this is set to true, a notification indicating how many
137 notifications are not being displayed due to the notification limit
138 (see notification_limit) will be shown in place of the last
139 notification slot.
140 Meaning that if this is enabled the number of visible notifications
142 will be 1 less than what is specified by notification_limit, the
143 last slot will be taken by the hidden count.
144 transparency (default: 0) (X11 only)
146 A 0-100 range on how transparent the notification window should be,
147 with 0 being fully opaque and 100 invisible.
148 To make windows transparent on wayland, set the transparency part
150 of a color, see COLORS.
151 This setting will only work if a compositor is running.
153 separator_height (default: 2)
155 The height in pixels of the separator between notifications, if set
156 to 0 there will be no separating line between notifications.
157 padding (default: 0)
159 The distance in pixels from the content to the separator/border of
160 the window in the vertical axis
161 horizontal_padding (default: 0)
163 The distance in pixels from the content to the border of the window
164 in the horizontal axis
165 text_icon_padding (default: 0)
167 The distance in pixels from the text to the icon (or vice versa) in
168 the horizontal axis.
169 Setting this to a non-zero value overwrites any padding that
171 horizontal_padding was adding between the notification text and
172 icon.
173 So for example setting
175 text_icon_padding=10
177 horizontal_padding=10
178 is equivalent to
180 text_icon_padding=0
182 horizontal_padding=10
183 frame_width (default: 0)
185 Defines width in pixels of frame around the notification window.
186 Set to 0 to disable.
187 frame_color color (default: #888888)
189 Defines color of the frame around the notification window. See
190 COLORS.
191 separator_color (values: [auto/foreground/frame/#RRGGBB] default: auto)
193 Sets the color of the separator line between two notifications.
194 auto
196 Dunst tries to find a color that fits the rest of the
197 notification color scheme automatically.
198 foreground
200 The color will be set to the same as the foreground color of
201 the topmost notification that's being separated.
202 frame
204 The color will be set to the frame color of the notification
205 with the highest urgency between the 2 notifications that are
206 being separated.
207 anything else
209 Any other value is interpreted as a color, see COLORS
210 sort (values: [true/false], default: true)
212 If set to true, display notifications with higher urgency above the
213 others.
214 idle_threshold (default: 0)
216 Don't timeout notifications if user is idle longer than this time.
217 See TIME FORMAT for valid times.
218 Set to 0 to disable.
220 A client can mark a notification as transient to bypass this
222 setting and timeout anyway. Use a rule with 'set_transient = no' to
223 disable this behavior.
224 Note: this doesn't work on xwayland.
226 layer (Wayland only)
228 One of bottom, top or overlay.
229 Place dunst notifications on the selected layer. Using overlay will
231 cause notifications to be displayed above fullscreen windows,
232 though this may also occur at top depending on your compositor.
233 The bottom layer is below all windows and above the background.
235 Default: overlay
237 force_xwayland (values: [true/false], default: false) (Wayland only)
239 Force the use of X11 output, even on a wayland compositor. This
240 setting has no effect when not using a Wayland compositor.
241 font (default: "Monospace 8")
243 Defines the font or font set used. Optionally set the size as a
244 decimal number after the font name and space. Multiple font
245 options can be separated with commas.
246 This options is parsed as a Pango font description.
248 line_height (default: 0)
250 The amount of extra spacing between text lines in pixels. Set to 0
251 to disable.
252 format (default: "%s %b")
254 Specifies how the various attributes of the notification should be
255 formatted on the notification window.
256 Regardless of the status of the markup setting, any markup tags
258 that are present in the format will be parsed. Note that because of
259 that, if a literal ampersand (&) is needed it needs to be escaped
260 as '&'
261 If '\n' is present anywhere in the format, it will be replaced with
263 a literal newline.
264 If any of the following strings are present, they will be replaced
266 with the equivalent notification attribute.
267 %a appname
269 %s summary
270 %b body
271 %i iconname (including its path)
272 %I iconname (without its path)
273 %p progress value ([ 0%] to [100%])
274 %n progress value without any extra characters
275 %% Literal %
276 If any of these exists in the format but hasn't been specified in
278 the notification (e.g. no icon has been set), the placeholders will
279 simply be removed from the format.
280 vertical_alignment (values: [top/center/bottom], default: center)
282 Defines how the text and icon should be aligned vertically within
283 the notification. If icons are disabled, this option has no effect.
284 show_age_threshold (default: -1)
286 Show age of message if message is older than this time. See TIME
287 FORMAT for valid times.
288 Set to -1 to disable.
290 ignore_newline (values: [true/false], default: false)
292 If set to true, replace newline characters in notifications with
293 whitespace.
294 stack_duplicates (values: [true/false], default: true)
296 If set to true, duplicate notifications will be stacked together
297 instead of being displayed separately.
298 Two notifications are considered duplicate if the name of the
300 program that sent it, summary, body, icon and urgency are all
301 identical.
302 hide_duplicate_count (values: [true/false], default: false)
304 Hide the count of stacked duplicate notifications.
305 show_indicators (values: [true/false], default: true)
307 Show an indicator if a notification contains actions and/or open-
308 able URLs. See ACTIONS below for further details.
309 icon_position (values: [left/right/off], default: off)
311 Defines the position of the icon in the notification window.
312 Setting it to off disables icons.
313 min_icon_size (default: 0)
315 Defines the minimum size in pixels for the icons. If the icon is
316 larger than or equal to the specified value it won't be affected.
317 If it's smaller then it will be scaled up so that the smaller axis
318 is equivalent to the specified size.
319 Set to 0 to disable icon upscaling. (default)
321 If icon_position is set to off, this setting is ignored.
323 max_icon_size (default: 0)
325 Defines the maximum size in pixels for the icons. If the icon is
326 smaller than or equal to the specified value it won't be affected.
327 If it's larger then it will be scaled down so that the larger axis
328 is equivalent to the specified size.
329 Set to 0 to disable icon downscaling. (default)
331 If both min_icon_size and max_icon_size are enabled, the latter
333 gets the last say.
334 If icon_position is set to off, this setting is ignored.
336 icon_path (default:
338 "/usr/share/icons/gnome/16x16/status/:/usr/share/icons/gnome/16x16/devices/")
339 Can be set to a colon-separated list of paths to search for icons
340 to use with notifications.
341 Dunst doesn't currently do any type of icon lookup outside of these
343 directories.
344 sticky_history (values: [true/false], default: true)
346 If set to true, notifications that have been recalled from history
347 will not time out automatically.
348 history_length (default: 20)
350 Maximum number of notifications that will be kept in history. After
351 that limit is reached, older notifications will be deleted once a
352 new one arrives. See HISTORY.
353 dmenu (default: "/usr/bin/dmenu")
355 The command that will be run when opening the context menu. Should
356 be either a dmenu command or a dmenu-compatible menu.
357 browser (default: "/usr/bin/xdg-open")
359 The command that will be run when opening a URL. The URL to be
360 opened will be appended to the end of the value of this setting.
361 always_run_script (values: [true/false] default: true]
363 Always run rule-defined scripts, even if the notification is
364 suppressed with format = "". See SCRIPTING.
365 title (default: "Dunst")
367 Defines the title of notification windows spawned by dunst.
368 (_NET_WM_NAME property). There should be no need to modify this
369 setting for regular use.
370 class (default: "Dunst")
372 Defines the class of notification windows spawned by dunst. (First
373 part of WM_CLASS). There should be no need to modify this setting
374 for regular use.
375 force_xinerama (values: [true/false], default: false) (X11 only)
377 Use the Xinerama extension instead of RandR for multi-monitor
378 support. This setting is provided for compatibility with older
379 nVidia drivers that do not support RandR and using it on systems
380 that support RandR is highly discouraged.
381 By enabling this setting dunst will not be able to detect when a
383 monitor is connected or disconnected which might break follow mode
384 if the screen layout changes.
385 corner_radius (default: 0)
387 Define the corner radius in pixels. A corner radius of 0 will
388 result in rectangular shaped notifications.
389 By enabling this setting the outer border and the frame will be
391 shaped. If you have multiple notifications, the whole window is
392 shaped, not every single notification.
393 To avoid the corners clipping the icon or text the corner radius
395 will be automatically lowered to half of the notification height if
396 it exceeds it.
397 mouse_left/middle/right_click (values:
399 [none/do_action/close_current/close_all/context/context_all])
400 Defines action of mouse click. A touch input in Wayland acts as a
401 mouse left click.
402 none
404 Don't do anything.
405 do_action (default for mouse_middle_click)
407 Invoke the action determined by the action_name rule. If there
408 is no such action, open the context menu.
409 open_url
411 If the notification has exactly one url, open it. If there are
412 multiple ones, open the context menu.
413 close_current (default for mouse_left_click)
415 Close current notification.
416 close_all (default for mouse_right_click)
418 Close all notifications.
419 context
421 Open context menu for the notification.
422 context_all
424 Open context menu for all notifications.
425 ignore_dbusclose (default: false)
427 Ignore the dbus closeNotification message. This is useful to
428 enforce the timeout set by dunst configuration. Without this
429 parameter, an application may close the notification sent before
430 the user defined timeout.
431 Urgency sections
433 The urgency sections work in a similar way to rules and can be used to
434 specify attributes for the different urgency levels of notifications
435 (low, normal, critical). Currently only the background, foreground,
436 hightlight, timeout, frame_color and icon attributes can be modified.
437 The urgency sections are urgency_low, urgency_normal, urgency_critical
439 for low, normal and critical urgency respectively.
440 See the example configuration file for examples.
442 Additionally, you can override these settings via the following command
444 line flags:
445 Please note these flags may be removed in the future. See issue #328 in
447 the bug tracker for discussions (See REPORTING BUGS).
448 -li/ni/ci icon
450 Defines the icon for low, normal and critical notifications
451 respectively.
452 Where icon is a path to an image file containing the icon.
454 -lf/nf/cf color
456 Defines the foreground color for low, normal and critical
457 notifications respectively.
458 See COLORS for the value format.
460 -lb/nb/cb color
462 Defines the background color for low, normal and critical
463 notifications respectively.
464 See COLORS for the value format.
466 -lh/nh/ch color
468 Defines the highlight color for low, normal and critical
469 notifications respectively.
470 See COLORS for the value format.
472 -lfr/nfr/cfr color
474 Defines the frame color for low, normal and critical notifications
475 respectively.
476 See COLORS for more information
478 -lto/nto/cto secs
480 Defines the timeout time for low, normal and critical notifications
481 respectively. See TIME FORMAT for valid times.
482
484 Dunst now contains a command line control command that can be used to
485 interact with it. It supports all functions previously done only via
486 keyboard shortcuts but also has a lot of extra functionality. For more
487 information, see dunstctl(1).
488
490 Dunst saves a number of notifications (specified by history_length) in
491 memory. These notifications can be recalled (i.e. redisplayed) by
492 calling dunstctl history (see dunstctl(1)). Whether these notifications
493 will time out like if they have been just send depends on the value of
494 the sticky_history setting. Actions are invalidated once the
495 notification is closed, so you cannot execute that action when you
496 bring back a notification from history.
497 Past notifications are redisplayed in a first-in-last-out order,
499 meaning that pressing the history key once will bring up the most
500 recent notification that had been closed/timed out.
501
503 Dunst has Wayland support since version 1.6.0. Because the Wayland
504 protocol is more focused on security, some things that are possible in
505 X11 are not possible in Wayland. Those differences are reflected in the
506 configuration. The main things that change are that dunst on Wayland
507 cannot use global hotkeys (they are deprecated anyways, use dunstctl).
508 Some dunst features on wayland might need your compositor to support a
510 certain protocol. Dunst will warn you if an optional feature isn't
511 supported and will disable the corresponding functionality.
512 Fullscreen detection works on wayland with some limitations (see
514 fullscreen). If you want notifications to appear over fullscreen
515 windows, set layer = overlay in the global options.
516 Note that the same limitations exist when using xwayland. If something
518 doesn't quite work in Wayland, please file a bug report. In the mean
519 time, you can try if the X11 output does work on wayland. Use
520 force_xwayland = true for that.
521 If you have your dunst notifications on the same side of your display
523 as your status bar, you might notice that your notifications appear a
524 bit higher or lower than on X11. This is because the notification
525 cannot be placed on top of your status bar. The notifications are
526 placed relative to your status bar, making them appear higher or lower
527 by the height of your status bar. We cannot do anything about that
528 behavior.
529
531 Rules allow the conditional modification of notifications. They can be
532 located in a section with any name, even the special sections. The
533 special sections do not allow filters to be added, since they have
534 implied filters by default.
535 'global'
537 No filters, matches all notifications.
538 'urgency_low', 'urgency_normal' and 'urgency_critical'
540 Matches low, normal or critical urgency respectively.
541 There are 2 parts in configuring a rule: Defining the filters that
543 controls when a rule should apply and then the actions that should be
544 taken when the rule is matched. It's also possible to not specify any
545 filters, in which case the rule will match all notifications.
546 Rules are applied in order of appearance. Beware: if a notification is
548 changed by a rule, it may affect if it's being matched by a later rule.
549 filtering
551 Notifications can be matched for any of the following attributes:
552 "appname" (discouraged, see desktop_entry)
554 The name of the application as reported by the client. Be aware
555 that the name can often differ depending on the locale used.
556 "body"
558 The body of the notification
559 "category"
561 The category of the notification as defined by the notification
562 spec. See
563 https://specifications.freedesktop.org/notification-spec/latest/ar01s06.html.
564 "desktop_entry"
566 GLib based applications export their desktop-entry name. In
567 comparison to the appname, the desktop-entry won't get
568 localized.
569 "icon"
571 The icon of the notification in the form of a file path. Can be
572 empty if no icon is available or a raw icon is used instead.
573 "match_transient"
575 Match if the notification has been declared as transient by the
576 client or by some other rule.
577 See "set_transient" for more details about this attribute.
579 "msg_urgency"
581 Matches the urgency of the notification as set by the client or
582 by some other rule.
583 "stack_tag"
585 Matches the stack tag of the notification as set by the client
586 or by some other rule.
587 See set_stack_tag for more information about stack tags.
589 "summary"
591 Matches the summary, 'title', of the notification.
592 "msg_urgency" is the urgency of the notification, it is named so to
594 not conflict with trying to modify the urgency.
595 Instead of the appname filter, it's recommended to use the
597 desktop_entry filter.
598 To define a matching rule simply assign the specified value to the
600 value that should be matched, for example:
601 appname="notify-send"
603 Matches only messages that were send via notify-send. If multiple
605 filter expressions are present, all of them have to match for the
606 rule to be applied (logical AND).
607 Shell-like globing is supported.
609 modifying
611 The following attributes can be overridden:
612 "background"
614 The background color of the notification. See COLORS for
615 possible values.
616 "foreground"
618 The foreground color of the notification. See COLORS for
619 possible values.
620 "highlight"
622 The highlight color of the notification. This color is used for
623 coloring the progress bar. See COLORS for possible values.
624 "format"
626 Equivalent to the "format" setting.
627 "frame_color"
629 The frame color color of the notification. See COLORS for
630 possible values.
631 "fullscreen"
633 One of show, delay, or pushback.
634 This attribute specifies how notifications are handled if a
636 fullscreen window is focused. By default it's set to show so
637 notifications are being shown.
638 Other possible values are delay: Already shown notifications
640 are continued to be displayed until they are dismissed or time
641 out but new notifications will be held back and displayed when
642 the focus to the fullscreen window is lost.
643 Or pushback which is equivalent to delay with the difference
645 that already existing notifications are paused and hidden until
646 the focus to the fullscreen window is lost.
647 On wayland, if follow is set to mouse or keyboard, the output
649 where the notification is located cannot be determined. So
650 dunst will delay or pushback if any of the outputs is
651 fullscreen. Since the fullscreen protocol is fairly new, you
652 will need a recent version of a compositor that supports it. At
653 the time of writing, you will need the git version of sway.
654 See also layer to change if notifications appear above
655 fullscreen windows in Wayland.
656 Default: show
658 "new_icon"
660 Updates the icon of the notification, it should be a path to a
661 valid image.
662 "set_stack_tag"
664 Sets the stack tag for the notification, notifications with the
665 same (non-empty) stack tag and the same appid will replace
666 each-other so only the newest one is visible. This can be
667 useful for example in volume or brightness notifications where
668 you only want one of the same type visible.
669 The stack tag can be set by the client with the 'synchronous',
671 'private-synchronous' 'x-canonical-private-synchronous' or the
672 'x-dunst-stack-tag' hints.
673 "set_transient"
675 Sets whether the notification is considered transient.
676 Transient notifications will bypass the idle_threshold setting.
677 By default notifications are _not_ considered transient but
679 clients can set the value of this by specifying the 'transient'
680 hint when sending notifications.
681 "set_category"
683 Sets the category of the notification. See
684 https://specifications.freedesktop.org/notification-spec/latest/ar01s06.html
685 for a list of standard categories.
686 "timeout"
688 Equivalent to the "timeout" setting in the urgency sections.
689 "urgency"
691 This sets the notification urgency.
692 IMPORTANT NOTE: This currently DOES NOT re-apply the attributes
694 from the urgency_* sections. The changed urgency will only be
695 visible in rules defined later. Use "msg_urgency" to match it.
696 "skip_display"
698 Setting this to true will prevent the notification from being
699 displayed initially but will be saved in history for later
700 viewing.
701 "history_ignore"
703 Setting this to true will display the notification initially,
704 but stop it from being recalled via the history.
705 "action_name"
707 Sets the name of the action to be invoked on do_action. If not
708 specified, the action set as default action or the only
709 available action will be invoked.
710 Default: "default"
712 word_wrap (values: [true/false], default: true)
714 Specifies whether to wrap the text if the lines get longer than
715 the maximum notification width. If it's set to true, long lines
716 will be broken into multiple lines expanding the notification
717 window height as necessary for them to fit. If the text doesn't
718 fit in the window, it will be ellipsize according to ellipsize.
719 ellipsize (values: [start/middle/end], default: middle)
721 Specifies where truncated lines should be ellipsized.
722 alignment (values: [left/center/right], default: left)
724 Defines how the text should be aligned within the notification.
725 markup (values: [full/strip/no], default: no)
727 Defines how markup in notifications is handled.
728 It's important to note that markup in the format option will be
730 parsed regardless of what this is set to.
731 Possible values:
733 full
735 Allow a small subset of html markup in notifications
736 <b>bold</b>
738 <i>italic</i>
739 <s>strikethrough</s>
740 <u>underline</u>
741 For a complete reference see
743 <https://docs.gtk.org/Pango/pango_markup.html>
744 strip
746 This setting is provided for compatibility with some broken
747 clients that send markup even though it's not enabled on
748 the server.
749 Dunst will try to strip the markup but the parsing is
751 simplistic so using this option outside of matching rules
752 for specific applications IS GREATLY DISCOURAGED.
753 See RULES
755 no Disable markup parsing, incoming notifications will be
757 treated as plain text. Dunst will not advertise that it can
758 parse markup if this is set as a global setting.
759 As with the filtering attributes, each one corresponds to the
761 respective notification attribute to be modified.
762 As with filtering, to make a rule modify an attribute simply assign
764 it in the rule definition.
765 If the format is set to an empty string, the notification will not
767 be suppressed.
768 SCRIPTING
770 Within rules you can specify a script to be run every time the rule is
771 matched by assigning the 'script' option to the name of the script to
772 be run.
773 When the script is called details of the notification that triggered it
775 will be passed via environment variables. The following variables are
776 available: DUNST_APP_NAME, DUNST_SUMMARY, DUNST_BODY, DUNST_ICON_PATH,
777 DUNST_URGENCY, DUNST_ID, DUNST_PROGRESS, DUNST_CATEGORY,
778 DUNST_STACK_TAG, DUNST_URLS, DUNST_TIMEOUT, DUNST_TIMESTAMP,
779 DUNST_DESKTOP_ENTRY, and DUNST_STACK_TAG.
780 Another, less recommended way to get notifcations details from a script
782 is via command line parameters. These are passed to the script in the
783 following order: appname, summary, body, icon_path, urgency.
784 Where DUNST_ICON_PATH or icon_path is the absolute path to the icon
786 file if there is one. DUNST_URGENCY or urgency is one of "LOW",
787 "NORMAL" or "CRITICAL". DUNST_URLS is a newline-separated list of urls
788 associated with the notification.
789 Note that some variables may be empty.
791 If the notification is suppressed, the script will not be run unless
793 always_run_scripts is set to true.
794 If '~/' occurs at the beginning of the script parameter, it will get
796 replaced by the users' home directory. If the value is not an absolute
797 path, the directories in the PATH variable will be searched for an
798 executable of the same name.
799
801 Colors are interpreted as X11 color values. This includes both verbatim
802 color names such as "Yellow", "Blue", "White", etc as well as #RGB and
803 #RRGGBB values.
804 You may also specify a transparency component in #RGBA or #RRGGBBAA
806 format.
807 NOTE: '#' is interpreted as a comment, to use it the entire value needs
809 to be in quotes like so: separator_color="#123456"
810 NOTIFY-SEND
812 dunst is able to get different colors for a message via notify-send.
813 In order to do that you have to add a hint via the -h option. The
814 progress value can be set with a hint, too.
815 All hints
817 See RULES for more detailed explanations for some options.
819 fgcolor: Foreground cololor
821 bgcolor: Background color
822 frcolor: Frame color
823 hlcolor: Highlight color
824 value: Progress value.
825 image-path: Icon name. This may be a path or just the icon name.
826 image-data: A stream of raw image data.
827 category: The category.
828 desktop-entry: The desktop entry.
829 transient: The transient value.
830 Examples
832 notify-send -h string:fgcolor:#ff4444
834 notify-send -h string:bgcolor:#4444ff -h string:fgcolor:#ff4444 -h
835 string:frcolor:#44ff44
836 notify-send -h int:value:42 "Working ..."
837
839 Dunst allows notifiers (i.e.: programs that send the notifications) to
840 specify actions. Dunst has support for both displaying indicators for
841 these, and interacting with these actions.
842 If "show_indicators" is true and a notification has an action, an "(A)"
844 will be prepended to the notification format. Likewise, an "(U)" is
845 prepended to notifications with URLs. It is possible to interact with
846 notifications that have actions regardless of this setting, though it
847 may not be obvious which notifications HAVE actions.
848 The "context" keybinding is used to interact with these actions, by
850 showing a menu of possible actions. This feature requires "dmenu" or a
851 dmenu drop-in replacement present.
852 Alternatively, you can invoke an action with a middle click on the
854 notification. If there is exactly one associated action, or one is
855 marked as default, that one is invoked. If there are multiple, the
856 context menu is shown. The same applies to URLs when there are no
857 actions.
858
860 A time can be any decimal integer value suffixed with a time unit. If
861 no unit given, seconds ("s") is taken as default.
862 Time units understood by dunst are "ms", "s", "m", "h" and "d".
864 Example time: "1000ms" "10m"
866
868 Written by Sascha Kruse <knopwob@googlemail.com>
869
871 Bugs and suggestions should be reported on GitHub at
872 https://github.com/dunst-project/dunst/issues
873
875 Copyright 2013 Sascha Kruse and contributors (see LICENSE for licensing
876 information)
877 If you feel that copyrights are violated, please send me an email.
879
881 dunst(1), dunstctl(1), dmenu(1), notify-send(1)
8821.7.1 2021-11-01 dunst(5)