<?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#"
	
	>
<channel>
	<title>
	Comments on: Learning the bash shell, continued	</title>
	<atom:link href="https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/feed/" rel="self" type="application/rss+xml" />
	<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Mar 2008 21:10:49 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.4.8</generator>
	<item>
		<title>
		By: Trinifar		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5293</link>

		<dc:creator><![CDATA[Trinifar]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 21:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5293</guid>

					<description><![CDATA[I have, at times, been particularly adroit with bash scripting, but these days I quickly tire of yet another language that I need to learn to get something done -- or of having to remember some strange syntax.  Bash is especially arcane and that&#039;s my problem with it.  Fine 30 years ago, but not good today.Cshell is another option, and tshell, and ....  Your readers should note you can tell your Unix which shell language to use as a default (Python anyone?) even while being able to override the default at will.Thing is, most of us master a new language when we have the need to use it and to the extent of that need.  If we don&#039;t use it for some time, we lose the dexterity of working with it.  That&#039;s my experience anyway.Ruby, Python, tckl, BeanShell, javascript, ... the list goes on endlessly and on the back of C, C++, COBOL, FORTRAN, Java, Forth, SmallTalk, Prolog, LISP in all its flavors, Eiffel, ....Those of us who adapt to and learn new languages quickly survive.  The large majority of people get lost in the tower of Babel.]]></description>
			<content:encoded><![CDATA[<p>I have, at times, been particularly adroit with bash scripting, but these days I quickly tire of yet another language that I need to learn to get something done &#8212; or of having to remember some strange syntax.  Bash is especially arcane and that&#8217;s my problem with it.  Fine 30 years ago, but not good today.Cshell is another option, and tshell, and &#8230;.  Your readers should note you can tell your Unix which shell language to use as a default (Python anyone?) even while being able to override the default at will.Thing is, most of us master a new language when we have the need to use it and to the extent of that need.  If we don&#8217;t use it for some time, we lose the dexterity of working with it.  That&#8217;s my experience anyway.Ruby, Python, tckl, BeanShell, javascript, &#8230; the list goes on endlessly and on the back of C, C++, COBOL, FORTRAN, Java, Forth, SmallTalk, Prolog, LISP in all its flavors, Eiffel, &#8230;.Those of us who adapt to and learn new languages quickly survive.  The large majority of people get lost in the tower of Babel.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: 386sx		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5292</link>

		<dc:creator><![CDATA[386sx]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 20:41:07 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5292</guid>

					<description><![CDATA[&lt;i&gt;If there are multiple commands on your system with the same name, there is a certain order in which the shell searches for the command.&lt;/i&gt;&quot;hash&quot; is another cool one. It can, for example, make bash know where a comand is and it doesn&#039;t have to be in $PATH.hash -p ~/stuff/other_vim vim]]></description>
			<content:encoded><![CDATA[<p><i>If there are multiple commands on your system with the same name, there is a certain order in which the shell searches for the command.</i>&#8220;hash&#8221; is another cool one. It can, for example, make bash know where a comand is and it doesn&#8217;t have to be in $PATH.hash -p ~/stuff/other_vim vim</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5291</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 15:11:34 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5291</guid>

					<description><![CDATA[Rick:THANK YOU!!!  I knew that but totally blanked on it and was going nuts trying to remember/find/look that up.Everybody:  Do what Rich said.]]></description>
			<content:encoded><![CDATA[<p>Rick:THANK YOU!!!  I knew that but totally blanked on it and was going nuts trying to remember/find/look that up.Everybody:  Do what Rich said.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rick Pikul		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5290</link>

		<dc:creator><![CDATA[Rick Pikul]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 10:34:39 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5290</guid>

					<description><![CDATA[A better way to check if a name is in use is to use the &quot;which&quot; command.This way, you don&#039;t accidentally run a command that will do something you don&#039;t like.  Also, it will give you some idea of the importance of the command based on where it is.]]></description>
			<content:encoded><![CDATA[<p>A better way to check if a name is in use is to use the &#8220;which&#8221; command.This way, you don&#8217;t accidentally run a command that will do something you don&#8217;t like.  Also, it will give you some idea of the importance of the command based on where it is.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5289</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 07:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5289</guid>

					<description><![CDATA[Cool idea. ... working on it now..]]></description>
			<content:encoded><![CDATA[<p>Cool idea. &#8230; working on it now..</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: blf		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5288</link>

		<dc:creator><![CDATA[blf]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 03:12:18 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5288</guid>

					<description><![CDATA[&lt;BLOCKQUOTE&gt;So &#039;blfnig&#039; could be a good name for a shell script you may right. [&lt;EM&gt;sic&lt;/EM&gt;]  Except it isn&#039;t because it does not convey any meaning.&lt;/BLOCKQUOTE&gt;Now hang on a second here!  I think that&#039;s a rather good name.  Or at least the first three letters of it...  ;-)Slightly more seriously, I have a small tendency to name my commands (scripts or otherwise) as words which are also acronyms.  One favourite from many years ago was &quot;dung&quot;, which stood for &quot;Distributed Unix Network Grapher&quot;.  That program found candidate paths through a unidirectional network that met various constraints on the input, intermediate steps, and output.  The name was more meaningful than it looks, since, for its intended usage, some of the nodes and links in the graph represented machines and connections in a network.In the case of &quot;blfnig&quot;, the first thing that comes to mind is &quot;blf&#039;s sNarky Interwoo Generator&quot;, which sounds like it might be a &quot;eliza&quot;(?)-type thingie to generate snarky comments for woo-woo blogs, presumably written or inspired by(? because of?) yours truly...  ;-)]]></description>
			<content:encoded><![CDATA[<blockquote><p>So &#8216;blfnig&#8217; could be a good name for a shell script you may right. [<em>sic</em>]  Except it isn&#8217;t because it does not convey any meaning.</p></blockquote>
<p>Now hang on a second here!  I think that&#8217;s a rather good name.  Or at least the first three letters of it&#8230;  ;-)Slightly more seriously, I have a small tendency to name my commands (scripts or otherwise) as words which are also acronyms.  One favourite from many years ago was &#8220;dung&#8221;, which stood for &#8220;Distributed Unix Network Grapher&#8221;.  That program found candidate paths through a unidirectional network that met various constraints on the input, intermediate steps, and output.  The name was more meaningful than it looks, since, for its intended usage, some of the nodes and links in the graph represented machines and connections in a network.In the case of &#8220;blfnig&#8221;, the first thing that comes to mind is &#8220;blf&#8217;s sNarky Interwoo Generator&#8221;, which sounds like it might be a &#8220;eliza&#8221;(?)-type thingie to generate snarky comments for woo-woo blogs, presumably written or inspired by(? because of?) yours truly&#8230;  😉</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Greg Laden		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5287</link>

		<dc:creator><![CDATA[Greg Laden]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 02:01:30 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5287</guid>

					<description><![CDATA[sed command accomplished]]></description>
			<content:encoded><![CDATA[<p>sed command accomplished</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Corey		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5286</link>

		<dc:creator><![CDATA[Corey]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 01:31:47 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5286</guid>

					<description><![CDATA[I wish they taught this stuff in grade school.  I&#039;m taking a course in bioinformatics, and time we could have spent learning bioinformatics we had to spend learning what you outlined in this post.  So wasteful]]></description>
			<content:encoded><![CDATA[<p>I wish they taught this stuff in grade school.  I&#8217;m taking a course in bioinformatics, and time we could have spent learning bioinformatics we had to spend learning what you outlined in this post.  So wasteful</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Matt Platte		</title>
		<link>https://gregladen.com/blog/2008/03/18/learning-the-bash-shell-contin/#comment-5285</link>

		<dc:creator><![CDATA[Matt Platte]]></dc:creator>
		<pubDate>Wed, 19 Mar 2008 00:17:32 +0000</pubDate>
		<guid isPermaLink="false">http://scienceblogs.com/gregladen/2008/03/18/learning-the-bash-shell-contin/#comment-5285</guid>

					<description><![CDATA[s/chmode/chmod/gI find transcripts of shell sessions way, way harder to decipher than when the command-and-response is presented in real time.  But then I&#039;m old and easily bored/distracted.]]></description>
			<content:encoded><![CDATA[<p>s/chmode/chmod/gI find transcripts of shell sessions way, way harder to decipher than when the command-and-response is presented in real time.  But then I&#8217;m old and easily bored/distracted.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
