Nikos Tsipinakis

> And about 20 lines over [here](https://github.com/dunst-project/dunst/blob/5009d444aa4cdba4b02178c07a3675686e0626b5/src/option_parser.c#L284) to add such method calls some simple parsing, (of values starting with `$` for example) and read it from the X resources database....

``` Aug 11 17:26:49 LinuxMachine-Mint dunst[18001]: BadAccess (attempt to access private resource denied) Aug 11 17:26:49 LinuxMachine-Mint dunst[18001]: BadAccess (attempt to access private resource denied) Aug 11 17:26:49 LinuxMachine-Mint dunst[18001]:...

That seems like a good idea but I'm having trouble seeing how this can be implemented without adding a lot of code complexity (at least, bar a refactor on the...

> I hope this should be good enough, albeit code part is still a mess :P That's my big worry about merging this. Plus the drawing code is entirely untested...

> Should I default them both to same color of either of body or summary or add another color setting in dunstrc for this titlebar > And should I add...

That's fine, these details can always be changed later.

To do this dunst needs to be able to handle multiple window/display setups simultaneously. Since a basic assumption is that there is only 1 notification window this would take a...

This has been requested before (#63) however, dunst was built around the assumption that the settings struct is never modified so adding that would require a rework of some other...

Hi, this is not possible as actions are something the client (read: the program that sent the notification) does, the logic isn't being run on dunst, we only send back...

Proper documentation is a long-running issue. The best (and only) sources available currently is the [manpage](https://github.com/dunst-project/dunst/blob/master/docs/dunst.pod) and the [example config](https://github.com/dunst-project/dunst/blob/master/dunstrc)