Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Say I run the following script that includes growlnotify.

#! /bin/bash

# do something ...

echo 'I want growlnotify to say this' | \
growlnotify -a '[Some Application]' 'Growl Headline'; \


If the script is run from Terminal or chmod +x'd and double-clicked, then growlnotify works. If it is run from Quicksilver instead, then the script works, but it doesn't say anything to Growl.

How can it be made to work?

share|improve this question
up vote 2 down vote accepted

I suspect growlnotify is not in the PATH when run from quicksilver.

In a Terminal, run which growlnotify. It will tell you where the executable is located. (For me, it returns "/usr/local/bin/growlnotify"). Then, use the full path in your script, and it will always work, regardless of what is in the PATH environment variable.

share|improve this answer
Works like a charm! Thanks – trolle3000 Mar 4 '10 at 17:45

I've had to do the following to get reliable growl notifications

growlnotify -H localhost -m "message"
share|improve this answer
+1 for a cleaner way to send text to growlnotify – trolle3000 Mar 4 '10 at 17:44

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.