From 9009033d5991cc78c6c5af787d451ccc390c46a3 Mon Sep 17 00:00:00 2001 From: Felix Uhl Date: Sun, 1 Nov 2020 14:19:30 +0100 Subject: [PATCH] Explain transition to dunstctl in comments --- dunstrc | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/dunstrc b/dunstrc index 31a682f..5827df3 100644 --- a/dunstrc +++ b/dunstrc @@ -267,6 +267,33 @@ # where there are multiple screens with very different dpi values. per_monitor_dpi = false +# The internal keyboard shortcut support in dunst is now considered deprecated +# and should be replaced by dunstctl calls. You can use the configuration of your +# WM or DE to bind these to shortcuts of your choice. +# Check the dunstctl manual page for more info. +[shortcuts] + + # Shortcuts are specified as [modifier+][modifier+]...key + # Available modifiers are "ctrl", "mod1" (the alt-key), "mod2", + # "mod3" and "mod4" (windows-key). + # Xev might be helpful to find names for keys. + + # Close notification. Equivalent dunstctl command: + # dunstctl close + # close = ctrl+space + + # Close all notifications. Equivalent dunstctl command: + # dunstctl close-all + # close_all = ctrl+shift+space + + # Redisplay last message(s). Equivalent dunstctl command: + # dunstctl history-pop + # history = ctrl+grave + + # Context menu. Equivalent dunstctl command: + # dunstctl context + # context = ctrl+shift+period + [urgency_low] # IMPORTANT: colors have to be defined in quotation marks. # Otherwise the "#" and following would be interpreted as a comment.