 |
From: Daniel Siemer <dan...@growl.info>
Date: Tue, 6 Mar 2012 08:27:47 -0800 (PST)
Local: Tues, Mar 6 2012 11:27 am
Subject: Re: growlnotify --wait seems to time out after about 10 seconds
GrowlNotify 1.3 has an internal timeout of 10 seconds with --wait. I
believe this has been changed in what will be GrowlNotify 1.4 to allow --wait --sticky to work as expected, and not timeout. I do not have information on when growlnotify 1.4 will be available, probably about the same time Growl.app 1.4 is available, as there is at least one GrowlNotify feature in 1.4 that will require Growl.app 1.4 to work right (Click feedback via opening a URL) On Mar 6, 9:57 am, TJ Luoma <luo...@gmail.com> wrote:
> The man page for growlnotify describes '--wait' as
> > -w, --wait Causes growlnotify to wait until the notification is
> dismissed (either by clicking or timing out) before it returns.
> I assumed that meant that if used with
> > --sticky Causes the notification to stick around until clicked.
> then I could use something like "growlnotify --wait --sticky -m test
> Unfortunately, it seems to time out after about 10 seconds.
> The message is still displayed, but the script continues:
> For example:
> $ date;growlnotify --wait --sticky -m test message;date
> I re-ran it several times and saw a similar error each time:
> 2012-03-06 10:43:38.438 growlnotify[35577:707] Got disconnected: Error
> 2012-03-06 10:43:51.639 growlnotify[35580:707] Got disconnected: Error
> 1. Is --wait plus --sticky supposed to be able to do what I am trying to do?
> 2. Is this just a bug in growl/growlnotify or is there another way to
> Thanks
> TjL You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| |||||||||||||