BREAKING CHANGE: Disable dunst shortcuts

They would conflict with some of my SXHKD bindings.  A notification
daemon should expose its functionality to a client that can be
controlled via the console.  This fact alone is reasone for me to search
for alternatives, including the possibility of switching to the generic
tool that ships with the MATE desktop (my fallback DE).
This commit is contained in:
Protesilaos Stavrou 2019-05-25 18:36:32 +03:00
parent 9f679b6b0b
commit f0e2b4b4bc
No known key found for this signature in database
GPG key ID: 99BD6459CD5CA3EA

View file

@ -192,23 +192,23 @@ title = Dunst
# Define the class of the windows spawned by dunst # Define the class of the windows spawned by dunst
class = Dunst class = Dunst
[shortcuts] ####[shortcuts]
# Shortcuts are specified as [modifier+][modifier+]...key ##### Shortcuts are specified as [modifier+][modifier+]...key
# Available modifiers are "ctrl", "mod1" (the alt-key), "mod2", ##### Available modifiers are "ctrl", "mod1" (the alt-key), "mod2",
# "mod3" and "mod4" (windows-key). ##### "mod3" and "mod4" (windows-key).
# Xev might be helpful to find names for keys. ##### Xev might be helpful to find names for keys.
####
# Close notification. ##### Close notification.
close = mod4+c ####close = mod4+c
####
# Close all notifications. ##### Close all notifications.
close_all = mod4+shift+c ####close_all = mod4+shift+c
####
# Redisplay last message(s). ##### Redisplay last message(s).
history = mod4+v ####history = mod4+v
####
# Context menu. ##### Context menu.
context = mod4+shift+v ####context = mod4+shift+v
# IMPORTANT: colors have to be defined in quotation marks. # IMPORTANT: colors have to be defined in quotation marks.
# Otherwise the "#" and following would be interpreted as a comment. # Otherwise the "#" and following would be interpreted as a comment.