From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: \n\n\n to \n\n
Date: Fri, 7 Mar 2003 11:14:05 +0000 [thread overview]
Message-ID: <3E67E3AD.1010209@null.net> (raw)
In-Reply-To: <000801c2e3a9$36cf2b00$2a8be793@gli.cas.cz>
peter a. cejchan wrote:
> PS: I'm going to test the posted wrappers to Sam, and then, hopefully,
> forget of Edit, and |sed ;-)
The main advantage of sed is that it can process in a truly
streaming fashion, whereas sam, ed, etc. all have to see the
end of file on the input before any editing can be done to
the file.
next prev parent reply other threads:[~2003-03-07 11:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-06 6:25 peter a. cejchan
2003-03-07 11:14 ` Douglas A. Gwyn [this message]
2003-03-07 12:34 ` Fco.J.Ballesteros
-- strict thread matches above, loose matches on Subject: below --
2003-03-05 18:05 rog
2003-03-05 15:12 peter a. cejchan
2003-03-05 19:20 ` Fco.J.Ballesteros
2003-03-05 6:52 peter a. cejchan
2003-03-05 17:26 ` rob pike, esq.
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=3E67E3AD.1010209@null.net \
--to=dagwyn@null.net \
--cc=9fans@cse.psu.edu \
/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.
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).