From: Soren Dayton <dayton@overx.com>
Subject: Re: mm-bidy-7-or-8 seems bogus to me [pgnus 0.95]
Date: Sat, 04 Sep 1999 06:21:21 GMT [thread overview]
Message-ID: <86btbjci3j.fsf@polo.overx.com> (raw)
In-Reply-To: <ur9kph87q.fsf@lanber.cam.citrix.com>
Toby Speight <Toby.Speight@streapadair.freeserve.co.uk> writes:
> Soren> Soren Dayton <URL:mailto:dayton@overx.com>
>
> 0> In article <86k8qh3nkd.fsf@polo.overx.com>, Soren wrote:
>
> Soren> Perhaps this should be "\001-\177" or even something like
> Soren> "\027-\177". What do people think?
>
> I think the latter is not a very good idea - I'd go more for something
> more, like "\011\012\015\027-\177" to allow TAB, LF, and CR in ASCII.
> \014 (FF) is probably okay, too. Some other characters require
> thought (ESC?).
Fair enough. You get my point. pgnus does the wrong thing.
Soren
prev parent reply other threads:[~1999-09-04 6:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-08-27 3:33 Soren Dayton
1999-08-27 9:40 ` Toby Speight
1999-09-04 6:21 ` Soren Dayton [this message]
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=86btbjci3j.fsf@polo.overx.com \
--to=dayton@overx.com \
/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).