On Oct 5, 3:11 pm, Watts Martin <[email protected]> wrote: > You can re-enable the command line app by running this AppleScript in > AppleScript Editor: > > tell application "Growl" > set allNotifications to {"Command-Line Growl Notification"} > register as application "GrowlNotify" all notifications > allNotifications default notifications allNotifications icon of > application "Terminal.app" > end tell > > Then, you can run a command with something like: > > growlnotify -m 'My message' -n 'GrowlNotify' 'Title' > > The parameter to -n *must* match the application name in the > AppleScript (register as application "Name") or the notification won't > be sent. Theoretically, you could register growlnotify under multiple > application names, but I don't think it gets you anything. Also note > that the new history function uses the 'Title' parameter for its > headings, so while growlnotify doesn't require title to be set, your > history will be full of blank lines if you don't use it. > > This is not precisely a bug, but growlnotify really needs to be > updated to execute these commands for a user.
Thank you so much! This fixed growlnotify for me. I did not ever have prior versions of Growl installed under Lion, I'm not sure if that's why it worked for me but not others. -- 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.
