Add a way to ignore notifications

[emersion]

Add a way to drop notifications matching some criteria.

I think @AN3223 is interested in this.

[matt-snider]

It would also be interesting to turn off or silence notifications completely (e.g. when in a meeting). Something like:

$ makoctl disable [--until ...]

# later...
$ makoctl enable

When combined with history (see #91) this could be really neat, as enable could trigger a notification of its own saying something like "Notifications enabled: 42 missed notifications (use history command to view)".

[emersion]

For this, see https://github.com/emersion/mako/issues/138

[Jpfonseca]

I have a issue with an app which sents a notificication, and when I click the notification, someone will receive a notification, which will then create another notification. Is there any way to ignore the notification, besides, having to kill mako and launch it again?

[emersion]

Send a patch implementing this feature ;)

[triallax]

I'd like to get this feature to ignore some rather spammy notifications from Plover. Here's what I do now:

on-notify=exec pw-cat --playback /usr/share/sounds/freedesktop/stereo/message.oga

[app-name=Plover body~="Wayland does not support QWindow::requestActivate\(\)"]
invisible=1
on-notify=dismiss

This almost works, with the only (at least as far as I can tell) caveat that mako stores these dismessed notifications in history. What I'm imagining to fix this is adding a new value for on-notify (and probably for the other on-* events) called delete (bikeshedding on name welcome) that would delete the notification entirely.

What do you think? I'm up for sending a patch if you think this idea looks good.

[emersion]

I think I'd prefer something like ignore=1 rather than an on-notify hook.

[triallax]

That's fine with me too, I'll send a PR when I get the chance.

[triallax]

I opened a PR https://github.com/emersion/mako/pull/477, reviewing and/or testing would be appreciated.