<?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: Quick note about sed&#8217;s edit in place option</title>
	<atom:link href="http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/feed/" rel="self" type="application/rss+xml" />
	<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/</link>
	<description>.com</description>
	<lastBuildDate>Wed, 08 Feb 2012 10:14:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: Zachary Burke</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-235064</link>
		<dc:creator>Zachary Burke</dc:creator>
		<pubDate>Fri, 16 Dec 2011 20:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-235064</guid>
		<description>Thank you for this post, 4 years later I&#039;m blown away that my mac is using utilities written in 1977 that have apparently never been updated.</description>
		<content:encoded><![CDATA[<p>Thank you for this post, 4 years later I&#8217;m blown away that my mac is using utilities written in 1977 that have apparently never been updated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-235062</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Wed, 14 Dec 2011 17:55:00 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-235062</guid>
		<description>Thanks, saved me a lot of frustration when I trying to run a script on os x that worked fine elsewhere!</description>
		<content:encoded><![CDATA[<p>Thanks, saved me a lot of frustration when I trying to run a script on os x that worked fine elsewhere!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Long</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-234953</link>
		<dc:creator>Nathan Long</dc:creator>
		<pubDate>Wed, 31 Aug 2011 17:54:00 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-234953</guid>
		<description>It&#039;s not dangerous at all if the files you&#039;re working with are under version control. With git, starting from a clean commit, a simple `git diff` lets you verify that you&#039;ve changed what you think you have.

Thanks for the post! You saved me some time.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not dangerous at all if the files you&#8217;re working with are under version control. With git, starting from a clean commit, a simple `git diff` lets you verify that you&#8217;ve changed what you think you have.</p>
<p>Thanks for the post! You saved me some time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: me</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-234732</link>
		<dc:creator>me</dc:creator>
		<pubDate>Thu, 05 May 2011 01:47:00 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-234732</guid>
		<description>Thanks! That was driving me nuts. I&#039;m running MacOSX.

sed --version
sed: illegal option -- -
usage: sed script [-Ealn] [-i extension] [file ...]
       sed [-Ealn] [-i extension] [-e script] ... [-f script_file] ... [file ...]</description>
		<content:encoded><![CDATA[<p>Thanks! That was driving me nuts. I&#8217;m running MacOSX.</p>
<p>sed &#8211;version<br />
sed: illegal option &#8212; -<br />
usage: sed script [-Ealn] [-i extension] [file ...]<br />
       sed [-Ealn] [-i extension] [-e script] &#8230; [-f script_file] &#8230; [file ...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Guest</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-234699</link>
		<dc:creator>Guest</dc:creator>
		<pubDate>Wed, 06 Apr 2011 19:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-234699</guid>
		<description>Just a hint: If sed is used on symlinks, the link is destroyed and replaced by a copy of the link target.
</description>
		<content:encoded><![CDATA[<p>Just a hint: If sed is used on symlinks, the link is destroyed and replaced by a copy of the link target.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stealthcupcake</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-234660</link>
		<dc:creator>Stealthcupcake</dc:creator>
		<pubDate>Wed, 16 Mar 2011 18:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-234660</guid>
		<description>Why don&#039;t they just fix this?  It is stupid to have an &quot;edit in place&quot; flag that doesn&#039;t work unless you do some undocumented obscure thing that wastes a bunch of time to find on the internet.</description>
		<content:encoded><![CDATA[<p>Why don&#8217;t they just fix this?  It is stupid to have an &#8220;edit in place&#8221; flag that doesn&#8217;t work unless you do some undocumented obscure thing that wastes a bunch of time to find on the internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Callum</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-223469</link>
		<dc:creator>Callum</dc:creator>
		<pubDate>Fri, 28 Jan 2011 14:49:34 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-223469</guid>
		<description>$ sed --version
GNU sed version 4.2.1

$ sed -i &#039;.orig&#039; -e &#039;s/oranges/apples/&#039; file
Returns a misleading error about not being able to read .orig, turns out the space between the -i and the &#039;.orig&#039; throws it off. Instead, this works as expected:
$ sed -i&#039;.orig&#039; -e &#039;s/oranges/apples/&#039; file

Thanks for the helpful article, congrats on being the first result for &quot;sed in place&quot; on Scroogle. :-)</description>
		<content:encoded><![CDATA[<p>$ sed &#8211;version<br />
GNU sed version 4.2.1</p>
<p>$ sed -i &#8216;.orig&#8217; -e &#8216;s/oranges/apples/&#8217; file<br />
Returns a misleading error about not being able to read .orig, turns out the space between the -i and the &#8216;.orig&#8217; throws it off. Instead, this works as expected:<br />
$ sed -i&#8217;.orig&#8217; -e &#8216;s/oranges/apples/&#8217; file</p>
<p>Thanks for the helpful article, congrats on being the first result for &#8220;sed in place&#8221; on Scroogle. :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hakova</title>
		<link>http://joemaller.com/823/quick-note-about-seds-edit-in-place-option/#comment-168298</link>
		<dc:creator>hakova</dc:creator>
		<pubDate>Tue, 29 Dec 2009 20:47:51 +0000</pubDate>
		<guid isPermaLink="false">http://joemaller.com/2007/09/16/quick-note-about-seds-edit-in-place-option/#comment-168298</guid>
		<description>Thanks, I was excited to find this, but I couldn&#039;t get -i to work in FreeBSD 8.0 period; that is with or without extension. Always get the same error (&#039;sed: -i may not be used with stdin&#039;) with all the example lines below: 

sed -i &#039;tmp&#039; -e &#039;s/apples/oranges/&#039; &lt;test.txt
sed -i &#039;&#039; -e &#039;s/apples/oranges/&#039; &lt;test.txt
sed -i&#039;&#039; -e &#039;s/apples/oranges/&#039; &lt;test.txt
sed -i&#039; &#039; -e &#039;s/apples/oranges/&#039; &lt;test.txt
and so forth.

These work:
sed &#039;s/apples/oranges/&#039; testnew.txt
sed -e&#039;s/apples/oranges/&#039; testnew.txt
sed -e &#039;s/apples/oranges/&#039; testnew.txt</description>
		<content:encoded><![CDATA[<p>Thanks, I was excited to find this, but I couldn&#8217;t get -i to work in FreeBSD 8.0 period; that is with or without extension. Always get the same error (&#8216;sed: -i may not be used with stdin&#8217;) with all the example lines below: </p>
<p>sed -i &#8216;tmp&#8217; -e &#8216;s/apples/oranges/&#8217; &lt;test.txt<br />
sed -i &#039;&#039; -e &#039;s/apples/oranges/&#039; &lt;test.txt<br />
sed -i&#039;&#039; -e &#039;s/apples/oranges/&#039; &lt;test.txt<br />
sed -i&#039; &#039; -e &#039;s/apples/oranges/&#039; &lt;test.txt<br />
and so forth.</p>
<p>These work:<br />
sed &#039;s/apples/oranges/&#039; testnew.txt<br />
sed -e&#8217;s/apples/oranges/&#8217; testnew.txt<br />
sed -e &#8216;s/apples/oranges/&#8217; testnew.txt</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Database Caching 1/4 queries in 0.003 seconds using disk: basic
Object Caching 244/245 objects using disk: basic

Served from: joemaller.com @ 2012-02-09 06:27:24 -->

<!-- W3 Total Cache: Page cache debug info:
Engine:             disk: enhanced
Cache key:          823/quick-note-about-seds-edit-in-place-option/feed/_index.xml_gzip
Caching:            enabled
Status:             not cached
Creation Time:      0.445s
Header info:
Set-Cookie:         bb2_screener_=1328786844+38.107.179.220+38.107.179.220; path=/
X-Pingback:         http://joemaller.com/wordpress/xmlrpc.php
Link:               <http://joemaller.com/?p=823>; rel=shortlink
Content-Type:       text/xml; charset=UTF-8
Last-Modified:      Thu, 09 Feb 2012 11:27:24 GMT
Vary:               Accept-Encoding, Cookie
Expires:            Thu, 09 Feb 2012 12:27:24 GMT
Pragma:             public
Cache-Control:      public, must-revalidate, proxy-revalidate
Etag:               2045f7637e91651f4373c5900f9d467f
X-Powered-By:       W3 Total Cache/0.9.2.4
Content-Encoding:   gzip
-->
