Skip to content
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: dunstctl close notifications based on conditions #1242

Open
febs opened this issue Dec 22, 2023 · 2 comments · May be fixed by #1348
Open

Feature request: dunstctl close notifications based on conditions #1242

febs opened this issue Dec 22, 2023 · 2 comments · May be fixed by #1348

Comments

@febs
Copy link

febs commented Dec 22, 2023

It would be handy to be able to se dunstctly to only close notifications pertaining a single app, or all the notifications containing a specified text/pattern.

also apparently the history-rm command is not documented in the docs folder of the source code.

Thanks!

@febs febs changed the title Feature request: dunstctl close notiication based on conditions Feature request: dunstctl close notifications based on conditions Dec 22, 2023
@bynect
Copy link
Member

bynect commented Feb 19, 2024

This is an interesting idea.
As a future reference: It can be done by defining a new dbus method similar to NotificationCloseLast that accepts a string and matches against that. Maybe two different methods, one matching the title and the other the body/everything.

Anyway if I get some spare time I'll try it

@zappolowski
Copy link
Member

I have a proposal for a (I think) more extensible approach: provide a new method for listing currently displayed notifications (like NotificationListHistory; this could be reused by just using a different queue to pick from). Then a client could use that output to apply its own rules for filtering and then issue calls to the already existing CloseNotification.

@zappolowski zappolowski linked a pull request May 1, 2024 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants