On Sat, Nov 30, 2013 at 11:01 PM, Rudy Richter <[email protected]> wrote: > I also notice that you seem to be quitting and relaunching Growl before > registering? is there a reason you did that? (i can't think of a reason that > should be necessary)
My guess is that it *may* have been done to deal with those situations when Growl is 'running' (i.e. would show up in process listing) but not responding. Killing it and restarting it would "guarantee" that it was responding. Not sure that's why, I just know that I have, in the past, been burned by just checking to see if Growl is running, but for some reason it was 'hung up' so what I really needed to do was test to see if the `growlnotify` command exited successfully even if I had checked that Growl was running. (FWIW this doesn't seem to happen as often now as it used to, but considering that the script is 3 years old, the developer might have been trying to work around that issue.) TjL -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/growldiscuss. For more options, visit https://groups.google.com/groups/opt_out.
