You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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)
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 ofdunstify
and each ID must be different.For example:
A service1 starts and a notification ID as String:
This notification will be closed when the service is done.
Idea: the ID "Service1" would be converted to hash like ID
The text was updated successfully, but these errors were encountered: