The problem appears to be two-fold:
(1) growlnotify can't register itself with the new Growl, so messages
are rejected.
(2) Notifications *must* be named correctly to be passed, or Growl
reports that the user didn't authorize them. Growl 1.3 treats all
notifications from growlnotify as "Command-Line Growl Notification,"
so that's the one and only notification that you must enable.
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.
On Oct 4, 9:09 pm, phill <[email protected]> wrote:
> Along with many other programs growlnotify has stopped working for me
> since 'upgrading' to 1.3.
> I'm using growlnotify installed from 1.2.2, any suggestions how I can
> get this working again?
>
> Will there be 'Extras' for 1.3?
--
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.
