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: kill notification with given tag #41

Open
adrianFD22 opened this issue Oct 9, 2023 · 2 comments
Open

Feature: kill notification with given tag #41

adrianFD22 opened this issue Oct 9, 2023 · 2 comments

Comments

@adrianFD22
Copy link

The title. This would be great for scripting usage. I am currently using xnotify to send a "low battery" notification and with this feature I would be able to automatically remove the notification when pluging the charger. Thanks 4 the repo.

@adrianFD22
Copy link
Author

I found a way more or less. I create a notification with the TAG I want to close and SEC:1. This solution closes the notification with one second of delay, pretty usable.

@phillbush
Copy link
Owner

One feature i had in mind to implement in XNotify is to add commands.
For example, if a notification line begins with, say, an exclamation point, it is interpreted as a command instructing XNotify what to do with the currently open notifications (such as close notifications with a given tag).
That feature would then replace the signal interface, which is clumsy and limited to two or three static operations without any argument or object to act upon.

That should be a major change on the interface. And the command syntax particularly should be simple but also extensible, with a handful set of commands.
I am going to think on possible commands (such as close, which can be parameterized by TAG or position of the notification on the queue) and on a syntax for them. Feel free to comment ideas on that in this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants