a7b3ff1ea8
It makes more sense to handle escapes in configuration strings when we parse them, rather than after-the-fact when we handle notifications that use the relevant config options. Do this in the proper backslash handler; rather than a naive string replace which doesn't allow the backslash to be escaped (`\\n` => 0x5C0x0A rather than 0x5C0x6E). it to the proper backslash handler
Dunst
Description
Dunst is a highly configurable and lightweight notification daemon.
Compiling
Dunst has a number of build dependencies that must be present before attempting configuration. The names are different depending on distribution:
- dbus
- libxinerama
- libxft
- libxss
- libxdg-basedir
- glib
- pango/cairo
- libgtk2.0
Checkout the wiki for more information.
Bug reports
Please use the issue tracker provided by GitHub to send us bug reports or feature requests. You can also join us on the IRC channel #dunst on Freenode.
Mantainers
Nikos Tsipinakis nikos@tsipinakis.com
Jonathan Lusso jonilusso@gmail.com
Author
written by Sascha Kruse dunst@knopwob.de
Copyright
copyright 2013 Sascha Kruse and contributors (see LICENSE for licensing information)
If you feel that copyrights are violated, please send me an email.