-
Notifications
You must be signed in to change notification settings - Fork 136
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
Transient Notification #541
Comments
Would it make sense to add a new configuration option to selectively disable history based on criteria? Kind of related: #477 |
Hm -- the D-Bus protocol has a "transient" hint - I wonder if that should skip history. |
@emersion this is the dunst PR for it -- |
you can follow the same way, like ignore transient hint, and only do when it's explicitly set in config. |
thanks in advance |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As a long dunst user, I have decided to try mako.
I have configured in such a way, that it almost look like my old configured dunst.
Only feature I will miss is 'Transient Notification', which when emit by notify-send via -e args, doesn't store notification in history.
I do use history a lot, and I don't want to lose my important notifications just because my mako history is filled with notify-send garbages.
I have lots of shell scripts that runs at login and are part of my workflow.
If anyone have any workaround to do this, thanks in advance.
The text was updated successfully, but these errors were encountered: