<?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/"
		>
<channel>
	<title>Comments on: Get sed savvy &#8211; part 3</title>
	<atom:link href="http://eriwen.com/tools/get-sed-savvy-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://eriwen.com/tools/get-sed-savvy-3/</link>
	<description>Programming productively with open-source tools</description>
	<lastBuildDate>Fri, 11 May 2012 19:13:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Bookmarks about Cygwin</title>
		<link>http://eriwen.com/tools/get-sed-savvy-3/#comment-2198</link>
		<dc:creator>Bookmarks about Cygwin</dc:creator>
		<pubDate>Wed, 25 Feb 2009 18:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://eriwen.com/?p=68#comment-2198</guid>
		<description>[...] - bookmarked by 1 members originally found by anitasaunders on 2009-01-30  Get sed savvy - part 3  http://eriwen.com/tools/get-sed-savvy-3/ - bookmarked by 1 members originally found by sunside on [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8211; bookmarked by 1 members originally found by anitasaunders on 2009-01-30  Get sed savvy &#8211; part 3  <a href="http://eriwen.com/tools/get-sed-savvy-3/" rel="nofollow">http://eriwen.com/tools/get-sed-savvy-3/</a> &#8211; bookmarked by 1 members originally found by sunside on [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Wendelin</title>
		<link>http://eriwen.com/tools/get-sed-savvy-3/#comment-1209</link>
		<dc:creator>Eric Wendelin</dc:creator>
		<pubDate>Thu, 28 Aug 2008 15:48:34 +0000</pubDate>
		<guid isPermaLink="false">http://eriwen.com/?p=68#comment-1209</guid>
		<description>Thanks for your kind comment, Mark. :)</description>
		<content:encoded><![CDATA[<p>Thanks for your kind comment, Mark. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Sanborn</title>
		<link>http://eriwen.com/tools/get-sed-savvy-3/#comment-1200</link>
		<dc:creator>Mark Sanborn</dc:creator>
		<pubDate>Thu, 28 Aug 2008 04:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://eriwen.com/?p=68#comment-1200</guid>
		<description>After learning perl and regular expressions these code snippets no longer look greek.

My only regret was not learning regular expressions/sed/awk earlier.  To anyone that is looking at this post wondering when they would ever use this kinda stuff.  Do yourself a favor and learn it right away.  You wont regret it.

And Eric&#039;s posts a good place to start.

Thanks!</description>
		<content:encoded><![CDATA[<p>After learning perl and regular expressions these code snippets no longer look greek.</p>
<p>My only regret was not learning regular expressions/sed/awk earlier.  To anyone that is looking at this post wondering when they would ever use this kinda stuff.  Do yourself a favor and learn it right away.  You wont regret it.</p>
<p>And Eric&#8217;s posts a good place to start.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Wendelin</title>
		<link>http://eriwen.com/tools/get-sed-savvy-3/#comment-930</link>
		<dc:creator>Eric Wendelin</dc:creator>
		<pubDate>Mon, 11 Aug 2008 15:26:55 +0000</pubDate>
		<guid isPermaLink="false">http://eriwen.com/?p=68#comment-930</guid>
		<description>@chihung:

Thanks. I did mention this back in part 1. The appropriate way to handle this in Solaris is 
&lt;code&gt;perl -e s/foo/bar/g -i&lt;/code&gt;

I should be highlighting this more often, though. You&#039;re right :)</description>
		<content:encoded><![CDATA[<p>@chihung:</p>
<p>Thanks. I did mention this back in part 1. The appropriate way to handle this in Solaris is<br />
<code>perl -e s/foo/bar/g -i</code></p>
<p>I should be highlighting this more often, though. You&#8217;re right :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: chihung</title>
		<link>http://eriwen.com/tools/get-sed-savvy-3/#comment-924</link>
		<dc:creator>chihung</dc:creator>
		<pubDate>Mon, 11 Aug 2008 01:15:20 +0000</pubDate>
		<guid isPermaLink="false">http://eriwen.com/?p=68#comment-924</guid>
		<description>Nice article, always look forward to reading more of these.

One suggestion. Some of the flags (eg, -i in sed) may not be available in Solaris. It would nice to highlight this to your audience.</description>
		<content:encoded><![CDATA[<p>Nice article, always look forward to reading more of these.</p>
<p>One suggestion. Some of the flags (eg, -i in sed) may not be available in Solaris. It would nice to highlight this to your audience.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Wendelin</title>
		<link>http://eriwen.com/tools/get-sed-savvy-3/#comment-908</link>
		<dc:creator>Eric Wendelin</dc:creator>
		<pubDate>Thu, 07 Aug 2008 19:02:21 +0000</pubDate>
		<guid isPermaLink="false">http://eriwen.com/?p=68#comment-908</guid>
		<description>@Alex:

Thanks for your kind feedback. Escaping is dependent on your shell version, so it is something to keep in mind. 

About #1 - I&#039;ve emailed you a link to my upcoming design where all is happy and well contrasted ;) I guess I learned a good lesson in usability - do not color your forms because someones configuration isn&#039;t going to display it like you want.</description>
		<content:encoded><![CDATA[<p>@Alex:</p>
<p>Thanks for your kind feedback. Escaping is dependent on your shell version, so it is something to keep in mind. </p>
<p>About #1 &#8211; I&#8217;ve emailed you a link to my upcoming design where all is happy and well contrasted ;) I guess I learned a good lesson in usability &#8211; do not color your forms because someones configuration isn&#8217;t going to display it like you want.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://eriwen.com/tools/get-sed-savvy-3/#comment-907</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Thu, 07 Aug 2008 17:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://eriwen.com/?p=68#comment-907</guid>
		<description>Couple things-  The light yellow boxes for commenter metadata make it insanely hard to read what you&#039;ve already written (might just be my monitor, but doublecheck just in case)

Second-  I really like this series.  It seems like most of my experience trying to learn these command line utils can be condensed down to someone giving me a full solution without explaining it (helpful, but not educational) that resembles PERL Golf to the degree that I can&#039;t even begin to read it, or the elitist &quot;Read the man pages&quot;.  This series of concrete, easy to follow examples are invaluable-  You might want to consider publishing them as cheat sheets.  The one problem I&#039;ve run into so far is that the examples sometimes require different escaping mechanisms when run under cygwin in windows (ie, ; instead of \;), but a little trial and error usually irons that stuff out.

Thanks again:)

-Alex</description>
		<content:encoded><![CDATA[<p>Couple things-  The light yellow boxes for commenter metadata make it insanely hard to read what you&#8217;ve already written (might just be my monitor, but doublecheck just in case)</p>
<p>Second-  I really like this series.  It seems like most of my experience trying to learn these command line utils can be condensed down to someone giving me a full solution without explaining it (helpful, but not educational) that resembles PERL Golf to the degree that I can&#8217;t even begin to read it, or the elitist &#8220;Read the man pages&#8221;.  This series of concrete, easy to follow examples are invaluable-  You might want to consider publishing them as cheat sheets.  The one problem I&#8217;ve run into so far is that the examples sometimes require different escaping mechanisms when run under cygwin in windows (ie, ; instead of \;), but a little trial and error usually irons that stuff out.</p>
<p>Thanks again:)</p>
<p>-Alex</p>
]]></content:encoded>
	</item>
</channel>
</rss>

