dunst-project
Idea: Don't close actions immediately upon a notification timing out
When a notification with an action is closed, it becomes impossible to activate the action.
Dunst could keep the action valid for a minute or so after a notification is closed. This way you could retrieve a notification from history and still activate the action.
my only concern is that to implement this we would need to leave all the programs awaiting actions hanging for the time being (1minute). maybe we can make an action_timeout that by default is 0 and can be customized by a rule?
I'm not sure if a timeout would be a good idea. For programs that hang while waiting for an action, it would also be bad to hang for 10 seconds. It would also be a bad user experience if actions would only stay active for a certain amount of time. You want them to always stay available. I would say that it's better to give the option not timeout the action at all for programs that can handle it.
But I don't know how other programs implement their action code. It would be useful to know how many programs can handle waiting for an action indefinitely without problems
But I don't know how other programs implement their action code. It would be useful to know how many programs can handle waiting for an action indefinitely without problems
This is unfortunately a gray area of the notification protocol. That's why a timeout option that could be tailored to the specific programs could be used. But I am not sure