Nikos Tsipinakis

Glad you fixed it, but this shouldn't have been necessary. We don't enable the service on purpose, dbus is supposed to start it automatically when a notification comes through.

What would be the usecase for this? Can you provide a few examples? Additionally, `closes` is a bit ambiguous as there are many cases where a notification is closed but...

> I use my implementation of it to, when the notification is clicked, activate the proper window with xdotool when the application has a poor notification implementation, like RuneLite, that...

> What you are proposing is a step in the right direction, but in practice it would be the same thing as I said- except for it adding the default...

> It would be nice to just be able to add a bunch of actions like you say if they don't already exist on the notification but that could be...

> When you say action you are still talking the notification action (like Activate) right? Yes > Would action_script still be called when do_action isn't called? Ideally, yes, we can...

The problem with the `close_script` name is that it implies it's run when the notification is closed but is not always the case: You can call many actions on a...

Whoops sorry I totally forgot to update this. The best I came up with was `event_script` (i.e. it's run when an event happens on a notification).

Well `markup = strip` should have worked, but our parser is simplistic and only understands `'` for apostrophes. Why not set `markup = full`? This will hand over the parsing...

> One possible solution to similar issues where modifying the content or other attributes of a notification in arbitrary ways is desirable could be to allow scripts to modify the...