<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Growling</title>
	<atom:link href="http://hans.fugal.net/blog/2008/02/13/growling/feed/" rel="self" type="application/rss+xml" />
	<link>http://hans.fugal.net/blog/2008/02/13/growling/</link>
	<description>Counterpoint by Hans Fugal</description>
	<lastBuildDate>Tue, 16 Mar 2010 15:07:10 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jacob</title>
		<link>http://hans.fugal.net/blog/2008/02/13/growling/comment-page-1/#comment-1689</link>
		<dc:creator>Jacob</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:c70d83a1-4a14-433c-b731-2c7566cb3e89#comment-1689</guid>
		<description>&lt;p&gt;Not really related to your issue, but on the topic of Growl...&lt;/p&gt;

&lt;p&gt;If you&#039;ve found yourself hooked by growl but away from OSX (or in a mixed OSX/linux  network), Mumble seems to be a pretty useful Growl-clone for linux. It not only clones the functionality, but also the protocol, such that it should be able to receive notifications from your mac boxes, if your mac boxes are sending events to the network.&lt;/p&gt;

&lt;p&gt;Disclaimer: I&#039;ve not actually used it over the network, just with local processes. And the pidgin plugin that it comes with (which listens for pidgin on dbus and rebroadcasts the dbus event as a growl/mumble event, as far as I can tell) is broken, at least on x64. But in general, it&#039;s functional and almost as clean looking as growl.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Not really related to your issue, but on the topic of Growl&#8230;</p>
<p>If you&#8217;ve found yourself hooked by growl but away from OSX (or in a mixed OSX/linux  network), Mumble seems to be a pretty useful Growl-clone for linux. It not only clones the functionality, but also the protocol, such that it should be able to receive notifications from your mac boxes, if your mac boxes are sending events to the network.</p>
<p>Disclaimer: I&#8217;ve not actually used it over the network, just with local processes. And the pidgin plugin that it comes with (which listens for pidgin on dbus and rebroadcasts the dbus event as a growl/mumble event, as far as I can tell) is broken, at least on x64. But in general, it&#8217;s functional and almost as clean looking as growl.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Viktor</title>
		<link>http://hans.fugal.net/blog/2008/02/13/growling/comment-page-1/#comment-1690</link>
		<dc:creator>Viktor</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:c70d83a1-4a14-433c-b731-2c7566cb3e89#comment-1690</guid>
		<description>&lt;p&gt;and now, another trouble with leopard. I wish they&#039;d configure it better so we could truly maximize it.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>and now, another trouble with leopard. I wish they&#8217;d configure it better so we could truly maximize it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niall</title>
		<link>http://hans.fugal.net/blog/2008/02/13/growling/comment-page-1/#comment-1691</link>
		<dc:creator>Niall</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:c70d83a1-4a14-433c-b731-2c7566cb3e89#comment-1691</guid>
		<description>&lt;p&gt;Many thanks! I&#039;ve been banging my head against this issue for the last couple of hours. You&#039;ve come up with a really simple, elegant solution.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Many thanks! I&#8217;ve been banging my head against this issue for the last couple of hours. You&#8217;ve come up with a really simple, elegant solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hans</title>
		<link>http://hans.fugal.net/blog/2008/02/13/growling/comment-page-1/#comment-1692</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:c70d83a1-4a14-433c-b731-2c7566cb3e89#comment-1692</guid>
		<description>&lt;p&gt;&lt;em&gt;Update&lt;/em&gt;: growlnotify included in Growl version 1.1.3 fixes this problem, so the workaround is no longer necessary.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p><em>Update</em>: growlnotify included in Growl version 1.1.3 fixes this problem, so the workaround is no longer necessary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://hans.fugal.net/blog/2008/02/13/growling/comment-page-1/#comment-1693</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:c70d83a1-4a14-433c-b731-2c7566cb3e89#comment-1693</guid>
		<description>&lt;p&gt;Hans,&lt;/p&gt;

&lt;p&gt;I&#039;m not so sure; I&#039;m using Growl 1.1.4 with growlnotify 1.1.4 and triggering it with autotest.  I&#039;ve experimented with pulling the generated growlnotify command line out of the autotest notification and running that repeatedly.  &lt;/p&gt;

&lt;p&gt;I got a 33% failure rate -- granted, much better than what I&#039;ve seen other folks report -  but at the beginning of a coding session, its enough to make me wonder if my test code didn&#039;t work.&lt;/p&gt;

&lt;p&gt;I&#039;ll give the workaround a shot&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>Hans,</p>
<p>I&#8217;m not so sure; I&#8217;m using Growl 1.1.4 with growlnotify 1.1.4 and triggering it with autotest.  I&#8217;ve experimented with pulling the generated growlnotify command line out of the autotest notification and running that repeatedly.  </p>
<p>I got a 33% failure rate &#8212; granted, much better than what I&#8217;ve seen other folks report &#8211;  but at the beginning of a coding session, its enough to make me wonder if my test code didn&#8217;t work.</p>
<p>I&#8217;ll give the workaround a shot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter</title>
		<link>http://hans.fugal.net/blog/2008/02/13/growling/comment-page-1/#comment-1694</link>
		<dc:creator>Peter</dc:creator>
		<pubDate>Wed, 31 Dec 1969 17:00:00 +0000</pubDate>
		<guid isPermaLink="false">urn:uuid:c70d83a1-4a14-433c-b731-2c7566cb3e89#comment-1694</guid>
		<description>&lt;p&gt;I ended up implementing the workaround from &lt;a href=&quot;http://hasseg.org/blog/?p=111&quot; rel=&quot;nofollow&quot;&gt;http://hasseg.org/blog/?p=111&lt;/a&gt;, which seems to be working reliably. &lt;/p&gt;

&lt;p&gt;As of September 8, 2008, the fine folks at growl have acknowledged the defect and logged a new bug against it (&lt;a href=&quot;https://bugs.launchpad.net/growl/+bug/267767&quot; rel=&quot;nofollow&quot;&gt;https://bugs.launchpad.net/growl/+bug/267767&lt;/a&gt;)&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>I ended up implementing the workaround from <a href="http://hasseg.org/blog/?p=111" rel="nofollow">http://hasseg.org/blog/?p=111</a>, which seems to be working reliably. </p>
<p>As of September 8, 2008, the fine folks at growl have acknowledged the defect and logged a new bug against it (<a href="https://bugs.launchpad.net/growl/+bug/267767" rel="nofollow">https://bugs.launchpad.net/growl/+bug/267767</a>)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
