From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] \n\n\n to \n\n
Date: Fri, 28 Feb 2003 13:11:48 -0500 [thread overview]
Message-ID: <2efc51fb86bf2f73c80609624ba2c218@plan9.bell-labs.com> (raw)
In-Reply-To: <001301c2df26$de171080$2a8be793@gli.cas.cz>
you could do it in sam: s/\n\n\n/\n\n/g
next prev parent reply other threads:[~2003-02-28 18:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-28 12:42 peter a. cejchan
2003-02-28 18:11 ` Russ Cox [this message]
2003-03-03 10:08 ` Ralph Corderoy
2003-02-28 18:48 Joel Salomon
2003-03-03 10:09 ` Douglas A. Gwyn
2003-03-03 14:25 ` Dan Cross
[not found] <1900322893@snellwilcox.com>
2003-03-03 11:14 ` Steve Simon
2003-03-04 10:26 ` Fco.J.Ballesteros
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=2efc51fb86bf2f73c80609624ba2c218@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--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).