Date: Wed, 9 Oct 2002 22:58:55 -0700 From: Adam Weinberger <adam@vectors.cx> To: Yoshinori KASAZAKI <mia@gold.ocn.ne.jp> Cc: dsyphers@uchicago.edu, freebsd-stable@FreeBSD.ORG Subject: Re: New sed breaks ports Message-ID: <20021010055855.GQ81796@vectors.cx> In-Reply-To: <20021010144447.090ec5c3.mia@gold.ocn.ne.jp> References: <20021009210042.A3027@klentaq.com> <20021010040550.2539c6f2.corecode@corecode.ath.cx> <20021009211658.A3071@klentaq.com> <200210092131.11605.dsyphers@uchicago.edu> <20021010144447.090ec5c3.mia@gold.ocn.ne.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
>> (10.09.2002 @ 2244 PST): Yoshinori KASAZAKI said, in 1.2K: <<
> I get following ...
>
> > sed -i
> sed: option requires an argument -- i
> usage: sed script [-Ean] [-i extension] [file ...]
> sed [-an] [-i extension] [-e script] ... [-f script_file] ... [file ...]
> > sed -i foo
> sed: -i may not be used with stdin
>
> If this is the case, it seems like sed is invoked without extension.
> (I don't know why, though...)
>> end of "Re: New sed breaks ports" from Yoshinori KASAZAKI <<
this is not a problem with an out-of-date ports tree. this is not a
problem with your source tree. this is not a problem with the wrong
version of sed being installed.
this is a probem of you not using sed the right way.
read sed(1).
sed -i edits a file in-place. you can't edit stdin in-place. sed -i foo
says to edit whatever file you didn't specify, and save a backup with
extension .foo.
your sed is working properly.
-Adam
--
"Oh good, my dog found the chainsaw."
-Lilo, "Lilo & Stitch"
Adam Weinberger
adam@vectors.cx
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021010055855.GQ81796>