-
Notifications
You must be signed in to change notification settings - Fork 343
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
Feature request: notification snoozing #1304
Comments
So you basically want to hide a notification and reschedule it after some time? I am not sure we can do that at the moment but it would be a cool feature indeed |
Maybe you can pause instead of dismiss? Then unpause it when you want to unsnooze. |
That's kind of what I want, but on a per-notification basis – I don't want to miss some important "your house is on fire" notification just because I paused notifications to get rid of a "remember to water the plants" message. (I realised what I actually want is a notification daemon that treats notifications like Android treats them, which is a substantial departure from how dunst works and is probably not feasible, so I've mentally added "write a notification daemon" to my list of rainy-day projects...) |
you can set a pause level, so that you filter only low importance notifications to your discretion. it is a fairly new feature, so maybe you should try the latest versions |
Something I often find myself wanting to do is get a notification out of the way for the time being, but not lose sight of the fact that I have a notification that I haven't properly dealt with yet. Maybe I could hack together some script to increment a counter when notifications arrive and decrement the counter when I dismiss them, and have a keyboard shortcut for "hide for now" which hides the notification but doesn't decrement the counter (and then I could display the counter in bright red in my status bar if it's nonzero or something) – but the issue I can't really work around is that
dunstctl context
doesn't work on notifications pulled from history, so any snoozed notification would lose its attached actions.Is there any way dunst could help solve this?
The text was updated successfully, but these errors were encountered: