From: Clint Adams <schizo@debian.org>
To: zsh-users@sunsite.auc.dk
Subject: Re: Better ( rm foo; bar > foo ) < foo ?
Date: Sun, 3 Dec 2000 15:24:40 -0500 [thread overview]
Message-ID: <20001203152440.A23776@dman.com> (raw)
In-Reply-To: <87n1edeh8c.fsf@senstation.vvf.fi>; from azure@iki.fi on Sun, Dec 03, 2000 at 04:01:39PM +0200
> TMPFILE=$(mktemp "$(dirname "$FILE")/XXXXXX") || exit 1
> sed 's/foo/bar/g' < "$FILE" > "$TMPFILE" || { rm -f "$TMPFILE" ; exit 1 }
> mv "$TMPFILE" "$FILE"
I find that
perl -pi -e 's/foo/bar/g' $FILE
is much less of a hassle, if that's the complexity you're dealing with.
next prev parent reply other threads:[~2000-12-03 20:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-03 14:01 Hannu Koivisto
2000-12-03 17:48 ` Bart Schaefer
2000-12-03 23:17 ` Hannu Koivisto
2000-12-04 2:27 ` Bart Schaefer
2000-12-03 20:24 ` Clint Adams [this message]
2000-12-07 11:44 ` Danny Dulai
2000-12-07 14:17 ` Andrej Borsenkow
2000-12-07 17:10 ` Bart Schaefer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001203152440.A23776@dman.com \
--to=schizo@debian.org \
--cc=zsh-users@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).