<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Self As Team &#187; osx</title>
	<atom:link href="http://blog.intraspectivecorp.com/tag/osx/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.intraspectivecorp.com</link>
	<description>Dallas based Ruby on Rails and Java Consulting</description>
	<lastBuildDate>Mon, 21 Sep 2009 02:06:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Leopard&#8217;s Growl</title>
		<link>http://blog.intraspectivecorp.com/2009/08/17/leopards-growl/</link>
		<comments>http://blog.intraspectivecorp.com/2009/08/17/leopards-growl/#comments</comments>
		<pubDate>Mon, 17 Aug 2009 20:24:57 +0000</pubDate>
		<dc:creator>David Hainlin</dc:creator>
				<category><![CDATA[development]]></category>
		<category><![CDATA[rails]]></category>
		<category><![CDATA[autotest]]></category>
		<category><![CDATA[growl]]></category>
		<category><![CDATA[osx]]></category>

		<guid isPermaLink="false">http://blog.intraspectivecorp.com/?p=60</guid>
		<description><![CDATA[I&#8217;m setting up a new MacBook Pro and everything is going so much better than on a previous configuration (with a vendor supplied mac ports, etc&#8230;) but that is another story.  I was setting up autotest and growl and ran into the same issues that I discovered with Leopard and growlnotify (see here, here [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m setting up a new <a href="http://www.apple.com/macbookpro/">MacBook Pro</a> and everything is going so much better than on a previous configuration (with a vendor supplied mac ports, etc&#8230;) but that is another story.  I was setting up <a href="http://www.zenspider.com/ZSS/Products/ZenTest/">autotest</a> and <a href="http://growl.info/">growl</a> and ran into the same issues that I discovered with Leopard and growlnotify (see <a href="http://hasseg.org/blog/?p=111">here</a>, <a href="http://blog.aisleten.com/2008/02/21/installing-growlnotify-and-autotest-for-bdd-use-with-rspec-on-leopard/">here</a> and <a href="http://groups.google.com/group/growldiscuss/browse_thread/thread/f1e63a1e04c30cd1/a3d0cb3bceecf32b">here</a>).  Anyway, none of the suggested configs worked  at all this time around.</p>
<p>So I played around with the settings and ended up with this config which (knock on wood) seems to work pretty well.</p>
<p>I started with the following versions:</p>
<ol>
<li>Leopard 10.5.8</li>
<li>ZenTest 4.1.4</li>
<li>Growl 1.1.6</li>
<li>autotest-growl gem 0.1.6</li>
<li>autotest-fsevent 0.1.1</li>
<li>autotest-rails 4.1.0</li>
</ol>
<p>I didn&#8217;t need to make any adjustments to the growl configuration (via System Preferences) as reported in some solutions.  </p>
<p>I added the following to the ~/.autotest file<br />
<code><br />
require 'autotest/growl'<br />
require 'autotest/fsevent'<br />
Autotest::Growl::show_modified_files = true<br />
Autotest::Growl::remote_notification = false<br />
Autotest.add_hook :initialize do |at|<br />
  %w{.git .svn .hg .DS_Store ._* log}.each {|exception|at.add_exception(exception)}<br />
end<br />
</code></p>
<p>I added some appropriately named images to the suggested ~/.autotest-growl directory per the really good (don&#8217;t skip over them, lots to learn if you have used an older config) <a href="http://github.com/svoop/autotest-growl">instructions</a>.</p>
<p>I then renamed the growlnotify app in /usr/local/bin to /usr/local/bin/growlnotify.wrapper (make sure it is executable with chmod if needed) and added the following wrapper (taken from <a href="http://craigjolicoeur.com/blog/problem-with-growlnotify-on-os-x-leopard">Craig P Jolicoeu&#8217;s</a> suggestion) as /usr/local/bin/growlnotify</p>
<p><code><br />
#!/bin/bash<br />
exec /usr/local/bin/growlnotify.wrapped -w "$@" &#038;<br />
</code></p>
<p>That was it, autotest (and other apps) growl everytime now.  Pretty easy (after I tried three or four other things that didn&#8217;t work).  It seems the networked approaches with -H and other configs didn&#8217;t really work for me.  The simplified wrapper seems to be all that is needed.</p>
<p>The other reported issues about growl not working if configured near the dock didn&#8217;t seem to cause me any issues (dock is on the bottom, growl is lower left).</p>
<p>Now my little robot friend (autotest) keeps me honest without fail. </p>
<p>Hope this helps.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.intraspectivecorp.com/2009/08/17/leopards-growl/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
