<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments for evan.musing &lt;&lt; current</title>
	<atom:link href="http://blog.fallingsnow.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fallingsnow.net</link>
	<description>life and tech stuff by Evan Phoenix</description>
	<lastBuildDate>Tue, 24 Aug 2010 02:53:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>Comment on Helpful syntax errors by Diego Scataglini</title>
		<link>http://blog.fallingsnow.net/2009/11/29/helpful-syntax-errors/#comment-23073</link>
		<dc:creator>Diego Scataglini</dc:creator>
		<pubDate>Tue, 24 Aug 2010 02:53:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fallingsnow.net/?p=97#comment-23073</guid>
		<description>Wow just realized how old is this post :D</description>
		<content:encoded><![CDATA[<p>Wow just realized how old is this post <img src='http://s.wordpress.com/wp-includes/images/smilies/icon_biggrin.gif' alt=':D' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Helpful syntax errors by Diego Scataglini</title>
		<link>http://blog.fallingsnow.net/2009/11/29/helpful-syntax-errors/#comment-23072</link>
		<dc:creator>Diego Scataglini</dc:creator>
		<pubDate>Tue, 24 Aug 2010 02:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fallingsnow.net/?p=97#comment-23072</guid>
		<description>That&#039;s awesome, great job. 
I wonder though if it&#039;d be possible and then if it&#039;d be useful if it also printed out the name of the unclosed element like so:

missing ‘end’ for ‘class’ ‘Spaghetti’ started on line 1.

or

missing ‘end’ for ‘class Spaghetti’ started on line 1.

Although easier to read/understand, would that be more helpful or is it superfluous information?</description>
		<content:encoded><![CDATA[<p>That&#8217;s awesome, great job.<br />
I wonder though if it&#8217;d be possible and then if it&#8217;d be useful if it also printed out the name of the unclosed element like so:</p>
<p>missing ‘end’ for ‘class’ ‘Spaghetti’ started on line 1.</p>
<p>or</p>
<p>missing ‘end’ for ‘class Spaghetti’ started on line 1.</p>
<p>Although easier to read/understand, would that be more helpful or is it superfluous information?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Helpful syntax errors by Jobs In Manchester</title>
		<link>http://blog.fallingsnow.net/2009/11/29/helpful-syntax-errors/#comment-22820</link>
		<dc:creator>Jobs In Manchester</dc:creator>
		<pubDate>Mon, 02 Aug 2010 10:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fallingsnow.net/?p=97#comment-22820</guid>
		<description>Seems like only a minor update but it will help the debugging process dramatically. It&#039;s always useful to find the offending piece of code as you&#039;ve hugely reduced the area you&#039;re looking for an error in. I&#039;ve spent hours debugging code ust to find on missing end or an open bracket i forgot to close! So frustrating!
Reece</description>
		<content:encoded><![CDATA[<p>Seems like only a minor update but it will help the debugging process dramatically. It&#8217;s always useful to find the offending piece of code as you&#8217;ve hugely reduced the area you&#8217;re looking for an error in. I&#8217;ve spent hours debugging code ust to find on missing end or an open bracket i forgot to close! So frustrating!<br />
Reece</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Doing a Time Machine full restore even if it doesn&#8217;t want to by PK</title>
		<link>http://blog.fallingsnow.net/2009/06/02/doing-a-time-machine-full-restore-even-if-it-doesnt-want-to/#comment-22796</link>
		<dc:creator>PK</dc:creator>
		<pubDate>Fri, 30 Jul 2010 02:29:55 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fallingsnow.net/?p=85#comment-22796</guid>
		<description>dude you are the man.</description>
		<content:encoded><![CDATA[<p>dude you are the man.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing colors in Terminal.app on 10.6 by Morgan</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22763</link>
		<dc:creator>Morgan</dc:creator>
		<pubDate>Mon, 26 Jul 2010 00:55:43 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22763</guid>
		<description>@Mareo thanks for the new package -- that did the trick for me on 10.6.4. I can even use Terminal.app in 64 bit mode.</description>
		<content:encoded><![CDATA[<p>@Mareo thanks for the new package &#8212; that did the trick for me on 10.6.4. I can even use Terminal.app in 64 bit mode.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing colors in Terminal.app on 10.6 by Konstantin Haase</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22630</link>
		<dc:creator>Konstantin Haase</dc:creator>
		<pubDate>Fri, 16 Jul 2010 07:32:30 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22630</guid>
		<description>Evan, I love you.</description>
		<content:encoded><![CDATA[<p>Evan, I love you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing colors in Terminal.app on 10.6 by Mareo</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22543</link>
		<dc:creator>Mareo</dc:creator>
		<pubDate>Mon, 05 Jul 2010 19:54:37 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22543</guid>
		<description>Problem Resolved!  Thanks to tips from you guys and some troubleshooting on my own, I have fixed the issue on my SnowLeopard (10.6.4) and would like to post the solution for anyone else with the same problem.

Requirements:
Snow Leopard (I have 10.6.4)
Terminal running in 64 bit mode, version 2.1.1
SIMBL (0.9.7) (older version should be fine)
Visor 2.2 or TerminalColours.bundle (NOT newest version: will explain shortly)

Procedure:
If you are getting the following error message &quot;Terminal 2.1.1 (v273) has not been tested with the plugin TerminalColours (null) (v1.0). As a precaution...&quot;, and you can&#039;t get rid of it by removing TerminalColours.bundle, then you must completely remove SIMBL and re-install it.  This includes the simbl.osax file.  Before removing SIMBL, store any .bundle files you might have currently installed temporarily on your desktop.  Delete the TerminalColours.bundle.  They are located at ~/Library/Application Support/SIMBL.

The files you must remove are:

1. /Library/ScriptingAdditions/simbl.osax
2. /Library/Application Support/SIMBL
3. ~/Library/Application Support/SIMBL

Now re-intall SIMBL (http://www.culater.net/software/SIMBL/SIMBL.php) and the error message should be GONE.  If not, you didn&#039;t completely uninstall SIMBL.

Now you should install Visor 2.2 (http://visor.binaryage.com/) or if you don&#039;t want visor, just the TerminalColours.bundle which DOESN&#039;T cause the error message (http://bwaht.net/code/TerminalColours.bundle.zip).  That said, I really really recommend Visor.  Even if you don&#039;t want the dropdown, you don&#039;t have to enable this feature in Visor.  Also, I have tested this method using Visor on two computers and it works.

If you decide to use TerminalColours.bundle, you need to right click on the bundle in finder, and click &quot;Show Package Contents…&quot;, open the &quot;Info.plist&quot; file and change the MaxBundleVersion to 273, and CFBundleIdentifier to sh.ciaranwal.terminal-colours, or just see Ted Naleid&#039;s post above.

The next step is to create a text file called .bash_profile which has the following content:

#colorize the Terminal
export GREP_OPTIONS=&#039;--color=auto&#039;
export CLICOLOR=1;

save the file in your home directory (~)

Open Terminal and it should be working.

If you are annoyed by the &quot;window blinking&quot; issue when Terminal Opens (caused by Visor), i highly recommend adding Terminal to your login items and checking the &quot;Hide&quot; box.</description>
		<content:encoded><![CDATA[<p>Problem Resolved!  Thanks to tips from you guys and some troubleshooting on my own, I have fixed the issue on my SnowLeopard (10.6.4) and would like to post the solution for anyone else with the same problem.</p>
<p>Requirements:<br />
Snow Leopard (I have 10.6.4)<br />
Terminal running in 64 bit mode, version 2.1.1<br />
SIMBL (0.9.7) (older version should be fine)<br />
Visor 2.2 or TerminalColours.bundle (NOT newest version: will explain shortly)</p>
<p>Procedure:<br />
If you are getting the following error message &#8220;Terminal 2.1.1 (v273) has not been tested with the plugin TerminalColours (null) (v1.0). As a precaution&#8230;&#8221;, and you can&#8217;t get rid of it by removing TerminalColours.bundle, then you must completely remove SIMBL and re-install it.  This includes the simbl.osax file.  Before removing SIMBL, store any .bundle files you might have currently installed temporarily on your desktop.  Delete the TerminalColours.bundle.  They are located at ~/Library/Application Support/SIMBL.</p>
<p>The files you must remove are:</p>
<p>1. /Library/ScriptingAdditions/simbl.osax<br />
2. /Library/Application Support/SIMBL<br />
3. ~/Library/Application Support/SIMBL</p>
<p>Now re-intall SIMBL (<a href="http://www.culater.net/software/SIMBL/SIMBL.php" rel="nofollow">http://www.culater.net/software/SIMBL/SIMBL.php</a>) and the error message should be GONE.  If not, you didn&#8217;t completely uninstall SIMBL.</p>
<p>Now you should install Visor 2.2 (<a href="http://visor.binaryage.com/" rel="nofollow">http://visor.binaryage.com/</a>) or if you don&#8217;t want visor, just the TerminalColours.bundle which DOESN&#8217;T cause the error message (<a href="http://bwaht.net/code/TerminalColours.bundle.zip" rel="nofollow">http://bwaht.net/code/TerminalColours.bundle.zip</a>).  That said, I really really recommend Visor.  Even if you don&#8217;t want the dropdown, you don&#8217;t have to enable this feature in Visor.  Also, I have tested this method using Visor on two computers and it works.</p>
<p>If you decide to use TerminalColours.bundle, you need to right click on the bundle in finder, and click &#8220;Show Package Contents…&#8221;, open the &#8220;Info.plist&#8221; file and change the MaxBundleVersion to 273, and CFBundleIdentifier to sh.ciaranwal.terminal-colours, or just see Ted Naleid&#8217;s post above.</p>
<p>The next step is to create a text file called .bash_profile which has the following content:</p>
<p>#colorize the Terminal<br />
export GREP_OPTIONS=&#8217;&#8211;color=auto&#8217;<br />
export CLICOLOR=1;</p>
<p>save the file in your home directory (~)</p>
<p>Open Terminal and it should be working.</p>
<p>If you are annoyed by the &#8220;window blinking&#8221; issue when Terminal Opens (caused by Visor), i highly recommend adding Terminal to your login items and checking the &#8220;Hide&#8221; box.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Rumors of our Demise are Greatly Exaggerated by The Why, What, and How of Rubinius 1.0’s Release &#124; Best Web Magazine</title>
		<link>http://blog.fallingsnow.net/2009/05/28/rumors-of-our-demise-are-greatly-exaggerated/#comment-22505</link>
		<dc:creator>The Why, What, and How of Rubinius 1.0’s Release &#124; Best Web Magazine</dc:creator>
		<pubDate>Fri, 02 Jul 2010 12:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.fallingsnow.net/?p=75#comment-22505</guid>
		<description>[...] their time for free. Regardless, the future didn&#039;t seem particularly bright, and in May 2009, Evan announced that &quot;the rumors of our demise are greatly exaggerated&quot; (in reference to Mark Twain) and that [...]</description>
		<content:encoded><![CDATA[<p>[...] their time for free. Regardless, the future didn&#039;t seem particularly bright, and in May 2009, Evan announced that &quot;the rumors of our demise are greatly exaggerated&quot; (in reference to Mark Twain) and that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing colors in Terminal.app on 10.6 by Mareo</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22495</link>
		<dc:creator>Mareo</dc:creator>
		<pubDate>Fri, 02 Jul 2010 01:03:07 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22495</guid>
		<description>IMPORTANT

alright, so i figured out that its the version on github (i&#039;m guessing that&#039;s the NEWER one) which is causing the error message.

the termialcolours link below causes no error message for me AND works perfectly.

http://bwaht.net/code/TerminalColours.bundle.zip

(unfortunately, i still can&#039;t get RID of the messages which already began appearing.  once one of them is there, they don&#039;t go away)</description>
		<content:encoded><![CDATA[<p>IMPORTANT</p>
<p>alright, so i figured out that its the version on github (i&#8217;m guessing that&#8217;s the NEWER one) which is causing the error message.</p>
<p>the termialcolours link below causes no error message for me AND works perfectly.</p>
<p><a href="http://bwaht.net/code/TerminalColours.bundle.zip" rel="nofollow">http://bwaht.net/code/TerminalColours.bundle.zip</a></p>
<p>(unfortunately, i still can&#8217;t get RID of the messages which already began appearing.  once one of them is there, they don&#8217;t go away)</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Fixing colors in Terminal.app on 10.6 by Mareo</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22494</link>
		<dc:creator>Mareo</dc:creator>
		<pubDate>Fri, 02 Jul 2010 00:46:53 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22494</guid>
		<description>*Correction, when visor is removed, the blink issue goes away.*    Still the terminalcolours.bundle error message refuses to go away.

Thanks to visor, color editing now seems to be working and saving my edits.  For some reason, I believe it was by installing an OLDER version of visor (2.0 and/or 2.0.1) (I ran the two &quot;exe&quot; files in 2.0 and I don&#039;t know if that did anything) that changing colors in visor began actually working.  Now I put the newest 2.2 version on my computer and it works great.

I still get the window &quot;blink&quot; when terminal first launched, but I think this is unavoidable.  It seems that terminal must launch normally before visor adds its effects.

So my only problem now is the error message which will not go away.  Do you think re-installing terminal could fix this?

thanks very much for your help.  if anyone needs info on how i got visor to start working I will be happy to elaborate.</description>
		<content:encoded><![CDATA[<p>*Correction, when visor is removed, the blink issue goes away.*    Still the terminalcolours.bundle error message refuses to go away.</p>
<p>Thanks to visor, color editing now seems to be working and saving my edits.  For some reason, I believe it was by installing an OLDER version of visor (2.0 and/or 2.0.1) (I ran the two &#8220;exe&#8221; files in 2.0 and I don&#8217;t know if that did anything) that changing colors in visor began actually working.  Now I put the newest 2.2 version on my computer and it works great.</p>
<p>I still get the window &#8220;blink&#8221; when terminal first launched, but I think this is unavoidable.  It seems that terminal must launch normally before visor adds its effects.</p>
<p>So my only problem now is the error message which will not go away.  Do you think re-installing terminal could fix this?</p>
<p>thanks very much for your help.  if anyone needs info on how i got visor to start working I will be happy to elaborate.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
