SIGCONT / SIGTSTP handling

[mjsir911]

Hello,

Currently to pause and resume dunst is SIGUSR1 (pause) and SIGUSR2 (resume)

I greatly appreciate this feature, but I believe the signals SIGTSTP (keyboard stop) and SIGCONT would be better suited for this task.

I don't really have a user story for this, but I could imagine tools would be able to take advantage of this more semantically correct signal handling.

Current behaviour of dunst is to ignore SIGTSTP signals

[bebehei]

SIGUSR* and SIGTSTP/SIGCONT signals differ in a simple and easy way.

• SIGUSR*: User defined signal, does whatever the process wants to do. If used, always documented. For server daemons, it's most often re-reading the configuration file. We at dunst use it to start/stop the functionality and start/stop displaying notifications.

• SIGTSTP/SIGCONT: This is necessary for job control. Ctrl+Z uses this signal. But all in all, the process stops by getting a signal of the terminal.

So in the semantics differ. We usually don't get spawned in a terminal and dunst has to run all the time. If we really stop the dunst process, many clients may fuck up and run into timeouts until finally DBus will probably start a new dunst instance.

I don't see where the semantics TSTP and CONT are "better suited" for dunst. Also, I'd like to remind you of #445. We plan to implement the functionality by a proper command line control.

[mjsir911]

Alright, thanks for your consideration.

Have a nice day