On Apr 3, 2010, at 16:45:31, adam n wrote: > Even then, when you try open -b, and then "growlnotify -m "test"", Growl > still doesn't work.
Did you run growlnotify immediately after open -b? Try waiting a second, to give Growl time to launch. >> open -b is the correct solution. > > But if it can't start Growl when it is stopped, then solution to what, > exactly? To Growl being turned on but, for whatever reason, not running. -- You received this message because you are subscribed to the Google Groups "Growl Discuss" group. 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.
