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

Idea: dunstify should support the option -r for ID as string instead integer #1098

Closed
Zesko opened this issue Aug 7, 2022 · 1 comment
Closed

Comments

@Zesko
Copy link

Zesko commented Aug 7, 2022

Issue description

It is not about the issue, but a new feature:

Currently ID is only integer, but it is hard for human to remember to avoid conflict of many IDs of dunstify when he creates many different systemd services, each service has an ID of dunstify and each ID must be different.

For example:
A service1 starts and a notification ID as String:

$ dunstify -u "critical" "Service1 is running" -r "Service1"

This notification will be closed when the service is done.

$ dunstify -C "Service1"

Idea: the ID "Service1" would be converted to hash like ID

@bynect
Copy link
Member

bynect commented Apr 11, 2024

Unfortunately the Desktop Notifications Specification specifies that ids are integers (https://specifications.freedesktop.org/notification-spec/latest/ar01s09.html).

Also, you should not use -r ID for new notifications but only to replace old notifications. Using -r ID when ID is not already existing is wrong according to the spec (see #1317)

@bynect bynect closed this as completed Apr 11, 2024
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