The manual page of the notify-send program specifies:
[...]
SYNOPSIS
notify-send [OPTIONS] <summary> [body]
DESCRIPTION
[...]
OPTIONS
[...]
-t, --expire-time=TIME
Specifies the timeout in milliseconds at which to expire the
notification.
[...]
If the expiration time for the notifications must be hard-coded, why leave
the "-t" option?
DRM 'manages access' in the same way that jail 'manages freedom'.
On Mon, Jun 29, 2009 at 4:50 PM, Mirco Müller
<mirco.muel...@canonical.com>wrote:
> That's deliberate any by design. The timeout-policy for notifications is
> specified here here
> https://wiki.ubuntu.com/NotifyOSD#Animations%20and%20durations.
>
> ** Changed in: notify-osd (Ubuntu)
> Importance: Undecided => Wishlist
>
> ** Changed in: notify-osd (Ubuntu)
> Status: New => Won't Fix
>
> ** Changed in: notify-osd (Ubuntu)
> Assignee: (unassigned) => Mirco Müller (macslow)
>
> --
> notify-send ignores the expire timeout parameter
> https://bugs.launchpad.net/bugs/390508
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
notify-send ignores the expire timeout parameter
https://bugs.launchpad.net/bugs/390508
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
