<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Navigating the Mac Shell ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-401488/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-26T01:13:08-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[Ironic and telling]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3743409]]></link>
        <description><![CDATA[I don't really want to start a windows/mac war here, but I find it ironic that this article makes this sound like such a wonderful hidden feature! I think it is telling of the way MAC was built and the audience to which it speaks.The command window in MS Windows and the Terminal in Linux are both rather well known by users, and although the general user may not use them much (if at all), nobody is surprised when you go to open one up... yet, surprise surprise, there is a similar window on MAC...]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3743409]]></guid>
        <dc:creator><![CDATA[C-3PO]]></dc:creator>
        <pubDate>Mon, 28 Jan 2013 05:12:41 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[bash shell]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3743095]]></link>
        <description><![CDATA[I've only looked at the Mac Shell once or twice, but I recall noticing that it's a standard bash (Bourne-Again SHell) interface.  There are tons of on-line references for bash, as well as a few good books out there.  I believe the O'Reilly Nutshell book on bash is pretty good.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3743095]]></guid>
        <dc:creator><![CDATA[dbucciar]]></dc:creator>
        <pubDate>Fri, 25 Jan 2013 12:29:47 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[I would add &quot;man&quot;]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3742996]]></link>
        <description><![CDATA[I think one of the most useful tools in the shell environment is the command &quot;man&quot; which is short for manual. I also use the &quot;-k term&quot; option which is a search of &quot;term&quot; in the manuals.So &quot;man ls&quot; will return the manual page for the &quot;ls&quot; command.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3742996]]></guid>
        <dc:creator><![CDATA[rupniksc@...]]></dc:creator>
        <pubDate>Fri, 25 Jan 2013 07:50:57 -0800</pubDate>
    </item>
             

    <item>
        <title><![CDATA[Thank you]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3742786]]></link>
        <description><![CDATA[Thank you for continuing this series.  I'm familiar with most of the basics from my scant interaction with Linux.  I didn't know about the Ctrl-J.  How is it technically more aggressive than Ctrl-C?  I look forward to learning some OSX-specific shell tips and tricks in the future.]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-401488-3742786]]></guid>
        <dc:creator><![CDATA[Adam S]]></dc:creator>
        <pubDate>Thu, 24 Jan 2013 06:41:34 -0800</pubDate>
    </item>
    </channel>
</rss>

