nagbalae/dunst
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Add docs for desktop-entry filter

Browse Source
This commit is contained in:
Benedikt Heine 2019-01-23 17:22:41 +01:00
parent 3bb6df2f1e
commit 7fff1d13c1
2 changed files with 13 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/dunst.pod
View File

@ -614,12 +614,14 @@ Notifications can be matched for any of the following attributes:
=over 4
=item C<appname>
=item C<appname> (discouraged, see desktop_entry)
=item C<body>
=item C<category>
=item C<desktop_entry>
=item C<icon>
=item C<msg_urgency>
@ -633,6 +635,10 @@ Notifications can be matched for any of the following attributes:
C<msg_urgency> is the urgency of the notification, it is named so to not conflict
with trying to modify the urgency.
Instead of the appname filter, it's recommended to use the desktop_entry filter.
GLib based applications export their desktop-entry name. In comparison to the appname,
the desktop-entry won't get localized.
To define a matching rule simply assign the specified value to the value that
should be matched, for example:

7
dunstrc
View File

@ -299,9 +299,10 @@
# override settings for certain messages.
#
# Messages can be matched by
# appname
# appname (discouraged, see desktop_entry)
# body
# category
# desktop_entry
# icon
# msg_urgency
# stack_tag
@ -320,6 +321,10 @@
#
# Shell-like globbing will get expanded.
#
# Instead of the appname filter, it's recommended to use the desktop_entry filter.
# GLib based applications export their desktop-entry name. In comparison to the appname,
# the desktop-entry won't get localized.
#
# SCRIPTING
# You can specify a script that gets run when the rule matches by
# setting the "script" option.