7a057b0b2e
Notification spec prohibits to reuse notification IDs (unless uint32 is exhausted). Therefore returning the same ID twice must not happen. Sending a signal, that the old notification timed out makes most sense. It wasn't closed by the user, nor by a CloseNotification call either. When we stack notifications, no interaction happened (the equivalent of timing out).
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
- libxrandr
- libxss
- libxdg-basedir
- glib
- pango/cairo
- libgtk-3-dev
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.