<?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 on: Fixing colors in Terminal.app on 10.6</title>
	<atom:link href="http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/</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>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>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>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>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>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>
	<item>
		<title>By: Mareo</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22463</link>
		<dc:creator>Mareo</dc:creator>
		<pubDate>Tue, 29 Jun 2010 14:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22463</guid>
		<description>Ted, I edited the .plist file to accept the version.  The funny thing is that the &quot;More...&quot; button appears, meaning the TerminalColours.bundle must be working, right?  And yet, I still recieve the error message saying &quot;it has not been loaded&quot;.

I am also getting a terminal &quot;blinking&quot; issue on startup, thanks to a glitch in Visor.  I removed that bundle also and still get the blink.  there must be something stored in my computer remembering bundle information!

do you know where the most up to date version of terminalColours.bundle is?

Also, do you think uninstalling and reinstalling the terminal could solve this? (if that&#039;s even possible)

thanks!
Mac OSX 10.6.4
SIMBL (newest version, something like 0.9.7)
Terminal 2.1.1
(currently, i have terminal opening in 32 bit mode)</description>
		<content:encoded><![CDATA[<p>Ted, I edited the .plist file to accept the version.  The funny thing is that the &#8220;More&#8230;&#8221; button appears, meaning the TerminalColours.bundle must be working, right?  And yet, I still recieve the error message saying &#8220;it has not been loaded&#8221;.</p>
<p>I am also getting a terminal &#8220;blinking&#8221; issue on startup, thanks to a glitch in Visor.  I removed that bundle also and still get the blink.  there must be something stored in my computer remembering bundle information!</p>
<p>do you know where the most up to date version of terminalColours.bundle is?</p>
<p>Also, do you think uninstalling and reinstalling the terminal could solve this? (if that&#8217;s even possible)</p>
<p>thanks!<br />
Mac OSX 10.6.4<br />
SIMBL (newest version, something like 0.9.7)<br />
Terminal 2.1.1<br />
(currently, i have terminal opening in 32 bit mode)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ted Naleid</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22448</link>
		<dc:creator>Ted Naleid</dc:creator>
		<pubDate>Mon, 28 Jun 2010 14:35:37 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22448</guid>
		<description>Mareo, did you update the terminal colours Info.plist file in the bundle as described above so that it knows about version 273?

http://gist.github.com/371027

I&#039;ve got things working with that, SIMBL installed, and 32 bit checked.</description>
		<content:encoded><![CDATA[<p>Mareo, did you update the terminal colours Info.plist file in the bundle as described above so that it knows about version 273?</p>
<p><a href="http://gist.github.com/371027" rel="nofollow">http://gist.github.com/371027</a></p>
<p>I&#8217;ve got things working with that, SIMBL installed, and 32 bit checked.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mareo</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22447</link>
		<dc:creator>Mareo</dc:creator>
		<pubDate>Mon, 28 Jun 2010 14:08:36 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22447</guid>
		<description>So, let me add a little more detail.  As it turns out, Even though I get the &quot;More...&quot; button and different colors in my terminal (which I see the settings for when I click the &quot;More...&quot; button), I am unable to change these colors to what I&#039;d like.  If I edit a color under &quot;More...&quot;, it doesn&#039;t take, even though the color appears changed in the setting.  When I restart the terminal, the color in the setting is back to the default.

Also, the message “Terminal 2.1.1 (v273) has not been tested with the plugin TerminalColours (null) (v1.0). As a precaution, it has not been loaded. Please contact the plugin developer for further information.” now always appears when I launch the terminal, even when I remove the TerminalColours.bundle from ~/Library/Application\ Support/SIMBL/PlugIns/!!!!

The message says TerminalColours.bundle is v1.0.  I opened the Info.plist in the Contents folder, and changed the version #&#039;s, but I still get the SAME EXACT error message.

What this leads me to believe is that there is some other file or setting in terminal which points to TerminalColours.bundle which needs to be edited.  However, I could be wrong.  I am a newb at this stuff.

I am going to try to make sure I have the newest version of TerminalColours.bundle, but my hopes aren&#039;t high.

please reply if you can help.  thank you!

Mac OSX 10.6.4
Terminal 2.1.1
(currently, i have terminal opening in 32 bit mode)</description>
		<content:encoded><![CDATA[<p>So, let me add a little more detail.  As it turns out, Even though I get the &#8220;More&#8230;&#8221; button and different colors in my terminal (which I see the settings for when I click the &#8220;More&#8230;&#8221; button), I am unable to change these colors to what I&#8217;d like.  If I edit a color under &#8220;More&#8230;&#8221;, it doesn&#8217;t take, even though the color appears changed in the setting.  When I restart the terminal, the color in the setting is back to the default.</p>
<p>Also, the message “Terminal 2.1.1 (v273) has not been tested with the plugin TerminalColours (null) (v1.0). As a precaution, it has not been loaded. Please contact the plugin developer for further information.” now always appears when I launch the terminal, even when I remove the TerminalColours.bundle from ~/Library/Application\ Support/SIMBL/PlugIns/!!!!</p>
<p>The message says TerminalColours.bundle is v1.0.  I opened the Info.plist in the Contents folder, and changed the version #&#8217;s, but I still get the SAME EXACT error message.</p>
<p>What this leads me to believe is that there is some other file or setting in terminal which points to TerminalColours.bundle which needs to be edited.  However, I could be wrong.  I am a newb at this stuff.</p>
<p>I am going to try to make sure I have the newest version of TerminalColours.bundle, but my hopes aren&#8217;t high.</p>
<p>please reply if you can help.  thank you!</p>
<p>Mac OSX 10.6.4<br />
Terminal 2.1.1<br />
(currently, i have terminal opening in 32 bit mode)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mareo</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22438</link>
		<dc:creator>Mareo</dc:creator>
		<pubDate>Sun, 27 Jun 2010 19:18:47 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22438</guid>
		<description>So I had the same problem as Ted.  I edited the .plist because I was getting the message &quot;Terminal 2.1.1 (v273) has not been tested with the plugin TerminalColours (null) (v1.0). As a precaution, it has not been loaded. Please contact the plugin developer for further information.&quot;

After downloading IR_Black and putting into the Terminal, low and behold the More... button is there!  However, I still get the error message every time I open the Terminal, which is quite annoying</description>
		<content:encoded><![CDATA[<p>So I had the same problem as Ted.  I edited the .plist because I was getting the message &#8220;Terminal 2.1.1 (v273) has not been tested with the plugin TerminalColours (null) (v1.0). As a precaution, it has not been loaded. Please contact the plugin developer for further information.&#8221;</p>
<p>After downloading IR_Black and putting into the Terminal, low and behold the More&#8230; button is there!  However, I still get the error message every time I open the Terminal, which is quite annoying</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erick</title>
		<link>http://blog.fallingsnow.net/2009/08/28/fixing-colors-in-terminal-app-on-10-6/#comment-22414</link>
		<dc:creator>Erick</dc:creator>
		<pubDate>Sat, 26 Jun 2010 05:40:22 +0000</pubDate>
		<guid isPermaLink="false">http://evanphx.wordpress.com/?p=92#comment-22414</guid>
		<description>Shurane, this may help: 

http://www.byteengine.net/custom-colors-in-snow-leopard-terminal-64-bit</description>
		<content:encoded><![CDATA[<p>Shurane, this may help: </p>
<p><a href="http://www.byteengine.net/custom-colors-in-snow-leopard-terminal-64-bit" rel="nofollow">http://www.byteengine.net/custom-colors-in-snow-leopard-terminal-64-bit</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
