The bug isn't in notify-send; this is part of libnotify which properly implements the timeout specification (you can send the timeout parameter).
The problem is in notify-osd (Canonical's notification front-end) which does not properly implement the timeout specification (it will not receive the timeout parameter) for no justifiable reason as I have pointed out with quotations from Canonical's notification specs, the freedesktop specs, and specific real-world use cases.
>>franglais.125
Welcome to the fold.
>> Everyone
Let me at this time express my appreciation for pantheon-notify, a notification front-end from that does everything right. The notifications do honor the timeout parameter and feature a close button as well for when you want them to just go away. It does nothing less than notify-osd can do and everything more.
>>duncan bayne
The bug isn't in notify-send; this is part of libnotify which properly implements the timeout specification (you can send the timeout parameter).
The problem is in notify-osd (Canonical's notification front-end) which does not properly implement the timeout specification (it will not receive the timeout parameter) for no justifiable reason as I have pointed out with quotations from Canonical's notification specs, the freedesktop specs, and specific real-world use cases.
>>franglais.125
Welcome to the fold.
>> Everyone
Let me at this time express my appreciation for pantheon-notify, a notification front-end from that does everything right. The notifications do honor the timeout parameter and feature a close button as well for when you want them to just go away. It does nothing less than notify-osd can do and everything more.