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
message" in shell scripts as a simple method of waiting for user action
before continuing.
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
Tue Mar 6 10:43:07 EST 2012
2012-03-06 10:43:18.352 growlnotify[35574:707] Got disconnected: Error
Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out"
UserInfo=0x7fc431c0ad20 {NSLocalizedDescription=Read operation timed out}
Tue Mar 6 10:43:18 EST 2012
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
Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out"
UserInfo=0x7ff7abc197f0 {NSLocalizedDescription=Read operation timed out}
2012-03-06 10:43:51.639 growlnotify[35580:707] Got disconnected: Error
Domain=GCDAsyncSocketErrorDomain Code=4 "Read operation timed out"
UserInfo=0x102119fc0 {NSLocalizedDescription=Read operation timed out}
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
accomplish it?
Thanks
TjL
--
You received this message because you are subscribed to the Google Groups
"Growl Discuss" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/growldiscuss/-/VWmCD8IZWKkJ.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/growldiscuss?hl=en.
