<?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:go='http://ns.gigaom.com/'
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: Terminal Tips: Using the Command Line With Style</title>
	<atom:link href="http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/</link>
	<description></description>
	<lastBuildDate>Fri, 10 Feb 2012 17:23:39 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Matt Rusell</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342478</link>
		<dc:creator><![CDATA[Matt Rusell]]></dc:creator>
		<pubDate>Wed, 28 Oct 2009 09:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342478</guid>
		<description><![CDATA[Did you ever figure this out? it bugs me too.]]></description>
		<content:encoded><![CDATA[<p>Did you ever figure this out? it bugs me too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ken Collins</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342477</link>
		<dc:creator><![CDATA[Ken Collins]]></dc:creator>
		<pubDate>Tue, 18 Aug 2009 16:35:05 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342477</guid>
		<description><![CDATA[I just got the latest visor working with Snow Leopard. Details here http://www.metaskills.net/2009/8/18/visor-terminal-on-snow-leopard]]></description>
		<content:encoded><![CDATA[<p>I just got the latest visor working with Snow Leopard. Details here <a href="http://www.metaskills.net/2009/8/18/visor-terminal-on-snow-leopard" rel="nofollow">http://www.metaskills.net/2009/8/18/visor-terminal-on-snow-leopard</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#124; Michael W. Vollmer</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342476</link>
		<dc:creator><![CDATA[&#124; Michael W. Vollmer]]></dc:creator>
		<pubDate>Fri, 10 Apr 2009 15:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342476</guid>
		<description><![CDATA[[...] an SQL query, make an rsync backup, or generally muck about in the system internals. Thankfully, TheAppleBlog’s Andrew Bednarz has assembled a compendium of Mac OS X terminal tips, tweaks, and tricks. He shows how to use Visor, a cool program that [...]]]></description>
		<content:encoded><![CDATA[<p>[...] an SQL query, make an rsync backup, or generally muck about in the system internals. Thankfully, TheAppleBlog’s Andrew Bednarz has assembled a compendium of Mac OS X terminal tips, tweaks, and tricks. He shows how to use Visor, a cool program that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: FreeMacUnix.com &#187; Blog Archive &#187; Make the most of the Mac OS X&#8217;s command line</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342475</link>
		<dc:creator><![CDATA[FreeMacUnix.com &#187; Blog Archive &#187; Make the most of the Mac OS X&#8217;s command line]]></dc:creator>
		<pubDate>Tue, 31 Mar 2009 20:14:50 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342475</guid>
		<description><![CDATA[[...] TheAppleBlog&#8217;s Andrew Bednarz has assembled a compendium of Mac OS X terminal tips, tweaks, and tricks. He shows how to use Visor, a cool program that [...]]]></description>
		<content:encoded><![CDATA[<p>[...] TheAppleBlog&#8217;s Andrew Bednarz has assembled a compendium of Mac OS X terminal tips, tweaks, and tricks. He shows how to use Visor, a cool program that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Arne</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342474</link>
		<dc:creator><![CDATA[Arne]]></dc:creator>
		<pubDate>Mon, 30 Mar 2009 20:04:59 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342474</guid>
		<description><![CDATA[I would suggest to activate the &quot;use option as meta key&quot; setting under settings -&gt; keyboard. Thus you can use many Bash-shortcuts. For example, if you press M-. in the shell, it repeats the last used argument. It can help:

$ mv  ~/some/complicated/long/path

Then, a &quot;cd M-.&quot; becomes:

$ cd ~/some/complicated/long/path

Tada, lots of typing saved, which is why in the end of the day we use the shell — to be faster.]]></description>
		<content:encoded><![CDATA[<p>I would suggest to activate the &#8220;use option as meta key&#8221; setting under settings -&gt; keyboard. Thus you can use many Bash-shortcuts. For example, if you press M-. in the shell, it repeats the last used argument. It can help:</p>
<p>$ mv  ~/some/complicated/long/path</p>
<p>Then, a &#8220;cd M-.&#8221; becomes:</p>
<p>$ cd ~/some/complicated/long/path</p>
<p>Tada, lots of typing saved, which is why in the end of the day we use the shell — to be faster.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Antonin Hildebrand</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342473</link>
		<dc:creator><![CDATA[Antonin Hildebrand]]></dc:creator>
		<pubDate>Mon, 30 Mar 2009 12:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342473</guid>
		<description><![CDATA[Thanks for the article, Andrew

There is maybe simpler way how to hide Terminal.app, use handy DockLess utility!
http://homepage.mac.com/fahrenba/programs/dockless/dockless.html]]></description>
		<content:encoded><![CDATA[<p>Thanks for the article, Andrew</p>
<p>There is maybe simpler way how to hide Terminal.app, use handy DockLess utility!<br />
<a href="http://homepage.mac.com/fahrenba/programs/dockless/dockless.html" rel="nofollow">http://homepage.mac.com/fahrenba/programs/dockless/dockless.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Galassi</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342472</link>
		<dc:creator><![CDATA[Michael Galassi]]></dc:creator>
		<pubDate>Fri, 27 Mar 2009 16:38:01 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342472</guid>
		<description><![CDATA[I often add .cdinrc and .cdoutrc files in directories in which specific activities take place (eg; building source for a project) and do things like change prompt, set environment variables, and what not from these files.  I then cause their automatic invocation by adding the following function to my .bash_profile:

cd() {
  [ $EUID -ne 0 ] &amp;*)
        . .cdoutrc
        ;;
     esac
    }
  }
  case $# in
  0)
    builtin cd
    ;;
  1)
    builtin cd &quot;$@&quot;
    ;;
  2)
    builtin cd &quot;${PWD%${1}*}${2}${PWD#*${1}}&quot;
    ;;
  *)
    builtin cd &quot;$@&quot;
    ;;
  esac
  [ $? -eq 0 ] &amp;*)
          . .cdinrc
          ;;
        esac
      }
    }
    # restore $? to 0 for use with &quot;cd xxx &amp;&amp; yyy&quot;
    true
  }
}
export -f cd


As an added bonus if you invoke &quot;cd&quot; with two arguments the first string in the current directory will be replaced by the second argument and the resulting directory will be switched to.  If for example I&#039;m in a directoy called &quot;/Users/mg/version1&quot; and I type &quot;cd 1 2&quot; I will find myself in the directory &quot;/Users/mg/version2&quot;.

Note that any .cdinrc and .cdoutrc files must be executable, they must be in a sub-directory of your $HOME, and you cannot be root (EUID 0).  Of course you can change all that.]]></description>
		<content:encoded><![CDATA[<p>I often add .cdinrc and .cdoutrc files in directories in which specific activities take place (eg; building source for a project) and do things like change prompt, set environment variables, and what not from these files.  I then cause their automatic invocation by adding the following function to my .bash_profile:</p>
<p>cd() {<br />
  [ $EUID -ne 0 ] &amp;*)<br />
        . .cdoutrc<br />
        ;;<br />
     esac<br />
    }<br />
  }<br />
  case $# in<br />
  0)<br />
    builtin cd<br />
    ;;<br />
  1)<br />
    builtin cd &#8220;$@&#8221;<br />
    ;;<br />
  2)<br />
    builtin cd &#8220;${PWD%${1}*}${2}${PWD#*${1}}&#8221;<br />
    ;;<br />
  *)<br />
    builtin cd &#8220;$@&#8221;<br />
    ;;<br />
  esac<br />
  [ $? -eq 0 ] &amp;*)<br />
          . .cdinrc<br />
          ;;<br />
        esac<br />
      }<br />
    }<br />
    # restore $? to 0 for use with &#8220;cd xxx &amp;&amp; yyy&#8221;<br />
    true<br />
  }<br />
}<br />
export -f cd</p>
<p>As an added bonus if you invoke &#8220;cd&#8221; with two arguments the first string in the current directory will be replaced by the second argument and the resulting directory will be switched to.  If for example I&#8217;m in a directoy called &#8220;/Users/mg/version1&#8243; and I type &#8220;cd 1 2&#8243; I will find myself in the directory &#8220;/Users/mg/version2&#8243;.</p>
<p>Note that any .cdinrc and .cdoutrc files must be executable, they must be in a sub-directory of your $HOME, and you cannot be root (EUID 0).  Of course you can change all that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andres</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342471</link>
		<dc:creator><![CDATA[Andres]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 21:35:58 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342471</guid>
		<description><![CDATA[One of the things I use most in terminal (linux and mac) is bash-completion. It can be installed via fink and mac ports and it enhances the &quot;intelligence&quot; of bash autocompletion feature. It will autocomplete not only file names and paths, but also will search for optional commands for example. 
It has more capabilities so better take a look at the developer&#039;s site http://www.caliban.org/bash/index.shtml]]></description>
		<content:encoded><![CDATA[<p>One of the things I use most in terminal (linux and mac) is bash-completion. It can be installed via fink and mac ports and it enhances the &#8220;intelligence&#8221; of bash autocompletion feature. It will autocomplete not only file names and paths, but also will search for optional commands for example.<br />
It has more capabilities so better take a look at the developer&#8217;s site <a href="http://www.caliban.org/bash/index.shtml" rel="nofollow">http://www.caliban.org/bash/index.shtml</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Leland Clemmons</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342470</link>
		<dc:creator><![CDATA[Leland Clemmons]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 19:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342470</guid>
		<description><![CDATA[I love &lt;a href=&quot;http://ciaranwal.sh/2007/11/16/blurminal&quot; rel=&quot;nofollow&quot;&gt;Blurminal&lt;/a&gt;. Basically just blurs the  terminal background when the opacity isn&#039;t 100%. Bad thing is, it needs SIMBL.]]></description>
		<content:encoded><![CDATA[<p>I love <a href="http://ciaranwal.sh/2007/11/16/blurminal" rel="nofollow">Blurminal</a>. Basically just blurs the  terminal background when the opacity isn&#8217;t 100%. Bad thing is, it needs SIMBL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Grossman</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342469</link>
		<dc:creator><![CDATA[Jeff Grossman]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 18:22:19 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342469</guid>
		<description><![CDATA[I love the colored &quot;ls&quot; -- but the colors disappear if you pipe through &quot;more&quot; or &quot;less&quot; (which is useful in long directories, as you know). Any way to keep the colors?]]></description>
		<content:encoded><![CDATA[<p>I love the colored &#8220;ls&#8221; &#8212; but the colors disappear if you pipe through &#8220;more&#8221; or &#8220;less&#8221; (which is useful in long directories, as you know). Any way to keep the colors?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Markian Hlynka</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342468</link>
		<dc:creator><![CDATA[Markian Hlynka]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 18:13:27 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342468</guid>
		<description><![CDATA[You forgot to add that you can set the prompt to modify the terminal&#039;s title bar. For example, I have:

[e]2;working in w a[e[32m]u[e[0m]@[e[32;1m]h[e[0m]:[e[0me[33;40m]W &gt; [e[0m]

The first part of that sets the title bar to display the working directory. I don&#039;t remember what the rest does!]]></description>
		<content:encoded><![CDATA[<p>You forgot to add that you can set the prompt to modify the terminal&#8217;s title bar. For example, I have:</p>
<p>[e]2;working in w a[e[32m]u[e[0m]@[e[32;1m]h[e[0m]:[e[0me[33;40m]W &gt; [e[0m]</p>
<p>The first part of that sets the title bar to display the working directory. I don&#8217;t remember what the rest does!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Edwards</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342467</link>
		<dc:creator><![CDATA[Matt Edwards]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 17:29:20 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342467</guid>
		<description><![CDATA[I am huge fan of this article for terminal coloring.

http://blog.infinitered.com/entries/show/6

http://ciaranwal.sh/2007/11/01/customising-colours-in-leopard-terminal

It required a bit more work with installing SIMBL, but you can have a pastel theme that&#039;s easier on the eyes then the default dark blue.]]></description>
		<content:encoded><![CDATA[<p>I am huge fan of this article for terminal coloring.</p>
<p><a href="http://blog.infinitered.com/entries/show/6" rel="nofollow">http://blog.infinitered.com/entries/show/6</a></p>
<p><a href="http://ciaranwal.sh/2007/11/01/customising-colours-in-leopard-terminal" rel="nofollow">http://ciaranwal.sh/2007/11/01/customising-colours-in-leopard-terminal</a></p>
<p>It required a bit more work with installing SIMBL, but you can have a pastel theme that&#8217;s easier on the eyes then the default dark blue.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BJ Neilsen</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342466</link>
		<dc:creator><![CDATA[BJ Neilsen]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 16:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342466</guid>
		<description><![CDATA[The biggest thing that drove me crazy when I started using Terminal was that it seemed like I couldn&#039;t change the keypress rate (which is unbearable slow at its default). Try typing a huge cvs commit command and then you realize that you mistyped a filename halfway through the command. SO frustrating.

I found later the simple fix to this is to go into Keyboard preferences and change the keypress rate and max it out. This does mean that everywhere in os x the keypress rate will be faster, but this is a welcome change to the default snail-paced speed.]]></description>
		<content:encoded><![CDATA[<p>The biggest thing that drove me crazy when I started using Terminal was that it seemed like I couldn&#8217;t change the keypress rate (which is unbearable slow at its default). Try typing a huge cvs commit command and then you realize that you mistyped a filename halfway through the command. SO frustrating.</p>
<p>I found later the simple fix to this is to go into Keyboard preferences and change the keypress rate and max it out. This does mean that everywhere in os x the keypress rate will be faster, but this is a welcome change to the default snail-paced speed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terminal Tips: Using the Command Line With Style — AppleTrainer</title>
		<link>http://gigaom.com/apple/terminal-tips-using-the-command-line-with-style/#comment-342465</link>
		<dc:creator><![CDATA[Terminal Tips: Using the Command Line With Style — AppleTrainer]]></dc:creator>
		<pubDate>Thu, 26 Mar 2009 16:16:40 +0000</pubDate>
		<guid isPermaLink="false">http://theappleblog.com/?p=19907#comment-342465</guid>
		<description><![CDATA[[...] (Via Terminal Tips: Using the Command Line With Style.) [...]]]></description>
		<content:encoded><![CDATA[<p>[...] (Via Terminal Tips: Using the Command Line With Style.) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

