I'm adding my name to the list of folks who have this startup problem. Just created the plist file from TJ's code but haven't tested yet. Thanks.
On Wednesday, August 15, 2012 1:24:04 PM UTC-4, TJ Luoma wrote: > On Tue, Aug 14, 2012 at 6:37 PM, Andrew Williams <[email protected]> wrote: > > > > I use this technique to ensure Growl (and other apps) are always open, even > if they crash: http://hints.macworld.com/article.php?story=20110617204111325 > > > > > I don't have Mountain Lion, so I can't test it, but maybe it will work for > your problem too. Let me know if you try it out. I'd like to know how it > works. > > > Oh, and I use an Automator workflow to kill Growl when I need > to: http://cl.ly/Ikda Edit that workflow to match the file name you set up > and then File > "Duplicate To..." to save a copy as an application instead of > a workflow. When you click the app, it closes Growl and stops it from > re-launching itself. You can then re-open it with a button or relog into Mac > OS to restore it. > > > > You can avoid that "Growl keeps reloading when I quit it on purpose" by > changing your launchd plist. > > > See https://gist.github.com/3361651 > > > > > I can't remember where I saw this trick, but the key (no pun intended) is to > use SuccessfulExit to indicate when the app quit, but did not crash. > > > 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/-/tzE4xGkAot4J. 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.
