-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
History-pop shortcut don't work #893
Comments
Well, the global hotkeys of dunst were deprecated and got removed. Edit: At least they were deprecated. But I'm having a hard time finding the PR which removes them. Only found this :D And I remember reading it got removed.. Well, what remains is, that it is advised to change keybinds like stated above. |
The built in shortcuts were indeed removed (in #803). As narrat noted, you can replace them by adding shortcuts to you window manager, desktop environment, etc. and letting those shortcuts call |
Oh! I was not aware that it was a relegated feature. Thanks to both for the clarification; I admit that I found it a bit strange to have access to shortcuts through configuration and also through dunsctl with hotkey daemons. I proceed to close the issue, and thank you again! |
Hi
I would like to report an error that my dunst has been having for a couple of weeks (but I had not had time to detail it until now)
Before the shortcut 'ctrl + grave' worked perfectly to see the last closed notifications. However some time ago this shortcut did not work, so I did some tests
What I got was that when I tried to bind any shortcut to the history-pop action FROM the dunst file, this shortcut didn't work (I tried ctrl + grave, ctrl + space, and even ctrl + a, just by trying any combination). With that I ruled out that it was some other program 'stealing' my shortcut, since for example the action 'close' linked to ctrl + space, worked perfectly.
Then I tried adding the 'dunstctl history-pop' command to sxhkd with ctrl + grave, and this time it did work, as did all the other actions.
I tried using dunstctl debug in case there was something useful there, but its only output was the dunst version.
Could I have forgotten something? Any other information that I can add, I remain available
(Oh, and by the way, thanks for Dunst, it's amazing!)
Installation info
The text was updated successfully, but these errors were encountered: