Simon Ser

Can you provide a `WAYLAND_DEBUG=1` log of your client? ```sh WAYLAND_DEBUG=1 your-client >client.log 2>&1 # Then reproduce the bug ```

Hm, this can almost be done with Sway output config. Just missing a way to match the output type. (This could be done with a script via the Sway IPC...

Kind of related is https://github.com/swaywm/sway/issues/6410 (for improved output matching).

This sounds like an upstream Steam issue.

I don't think users should configure mako to reload the state of indicators such as waybar. Instead, I think mako should provide APIs to allow indicators to subscribe to state...

mako has two D-Bus APIs: the standard D-Bus one for applications submitting notifications, and a mako-specific one for makoctl and other tools. We already expose the current list of notifications...

No: `on-X` is meant to be used by users, while D-Bus events are meant to be used by other tools interacting with mako.

See https://github.com/emersion/mako/pull/552 for an example of a D-Bus event approach, for modes.

In this situation: C: PRIVMSG #ircdocs :emersion: I'm not sure, try asking val when they're around? How would the client indicate that emersion needs to be notified but val should...

Your bug report is missing debug logs. Please add a link to the full debug log file.