Comment 127 for bug 390508
Revision history for this message
| quequotion (quequotion) wrote Re: notify-send ignores the expire timeout parameter | #127 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Before I get scolded: You may find that I posted a very similar comment on bug #257135, regarding the lack of access to replaces_id, however this comment is regarding the behavior of --expire-time.
Red_Acid++
Leolik's notify-osd + notifyosdconfig = vastly superior, and faster, messages.
There's still a little funniness with the --expire-time parameter however.
Case in Point: To get messages at the speed of channel surfing, temperature changes, bandwidth use, etc, etc, etc it's necessary to set an arbitrary, system-wide timeout of 1sec with notifyosdconfig (see above PPAs) and set --expire-time < 1000.
This makes a notification which blinks in and out of existence since an expire time of anything less than 1000 is equal to 0. I'd actually like to have messages linger for about 600~800msec, which I figure to be ample time for reading a channel number (and could also be useful for reading many kinds of things that don't need to be studied carefully).
To be precise I want to do this (note the imaginary --replaces_id parameter):
notify-send --replaces_