Comments on: iTerm and Growl http://damonparker.org/blog/2006/11/13/iterm-and-growl/ code / ecommerce / life Sat, 21 Jan 2012 20:11:20 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Josh The Geek http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26827 Josh The Geek Sun, 17 Jul 2011 20:46:58 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26827 Thank you! Thank you!

]]> By: iTerm2: advanced features : World Gone Web http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26738 iTerm2: advanced features : World Gone Web Sat, 29 Jan 2011 17:08:28 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26738 [...] this is a hard command to remember, Damon Parker suggested adding the following line to your .bashrc or your .bash_profile 1growl() { echo -e [...] [...] this is a hard command to remember, Damon Parker suggested adding the following line to your .bashrc or your .bash_profile 1growl() { echo -e [...]

]]> By: Notify me when the script is done « oae's Blog http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26562 Notify me when the script is done « oae's Blog Sun, 26 Sep 2010 12:43:22 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26562 [...] can fire growl notifications right from the bash to growl (see this blog post). To easify this add the following line to your [...] [...] can fire growl notifications right from the bash to growl (see this blog post). To easify this add the following line to your [...]

]]> By: links for 2009-06-17 | blog/shl@INTERDOSE http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26470 links for 2009-06-17 | blog/shl@INTERDOSE Tue, 22 Dec 2009 13:07:31 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26470 [...] iTerm and Growl – damonparker.org (tags: apple shell) [...] [...] iTerm and Growl – damonparker.org (tags: apple shell) [...]

]]> By: nobody http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26452 nobody Tue, 10 Nov 2009 21:28:25 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26452 [ccL_bash]growl() { if [ "$TERM_PROGRAM" == "iTerm.app" -a "$TERM" != "screen" ] then echo -e $'\e]9;'${1}'07' else growlnotify -m ${1} "Alert" fi }[/ccL_bash]
growl()
{
        if [ "$TERM_PROGRAM" == "iTerm.app" -a "$TERM" != "screen" ]
        then
                echo -e $'\e]9;'${1}'07'
        else
                growlnotify -m ${1} "Alert"
        fi
}
]]> By: Evan Krall http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26243 Evan Krall Sun, 08 Feb 2009 11:54:27 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26243 Wow, so I messed that up a little bit. That should read: [ccL_bash]growl() { echo $'\e]9;'"${@}"$'07'; }[/ccL_bash] Also, be careful about the quotes. I'm not sure exactly why, but some of the quotes in my previous post got transformed to forward and backwards quotes, which will mess with things in the shell. Wow, so I messed that up a little bit.
That should read:

growl() { echo $'\e]9;'"${@}"$'07'; }

Also, be careful about the quotes. I’m not sure exactly why, but some of the quotes in my previous post got transformed to forward and backwards quotes, which will mess with things in the shell.

]]> By: Evan Krall http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26242 Evan Krall Sun, 08 Feb 2009 10:55:26 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26242 You should always quote when you use arguments, unless you have a very good reason not to. Bad things happen otherwise; mostly, newlines and tabs become spaces, globs get expanded, etc. Also, what's with using echo -e and $' ' at the same time? Here's a better way, IMO: growl() { echo $'\e]9;'"${@}"$'07' ; return ; } You should always quote when you use arguments, unless you have a very good reason not to. Bad things happen otherwise; mostly, newlines and tabs become spaces, globs get expanded, etc. Also, what’s with using echo -e and $’ ‘ at the same time?
Here’s a better way, IMO:

growl() { echo $’\e]9;’”${@}”$’07′ ; return ; }

]]> By: Dag Høidahl http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26239 Dag Høidahl Thu, 29 Jan 2009 09:05:51 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-26239 If you substitue ${1} with ${*} in the shell function, you don't need to put the notification text within quotes. If you substitue ${1} with ${*} in the shell function, you don’t need to put the notification text within quotes.

]]> By: avdempsey http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-25618 avdempsey Wed, 01 Aug 2007 20:17:14 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-25618 Works great, good tip. Now, I'm gonna have to figure out how to make growl notifications work for remote jobs. Works great, good tip. Now, I’m gonna have to figure out how to make growl notifications work for remote jobs.

]]> By: oudeis http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-17151 oudeis Mon, 15 Jan 2007 01:58:20 +0000 http://damonparker.org/blog/2006/11/13/iterm-and-growl/#comment-17151 If you want more control or use a different terminal app, you may want to look at growlnotify: http://growl.info/documentation/growlnotify.php If you want more control or use a different terminal app, you may want to look at growlnotify:
http://growl.info/documentation/growlnotify.php

]]>