From: Richard Pieri <ratinox@unilab.dfci.harvard.edu>
Subject: Re: Problem with multi-line References
Date: 26 Sep 1996 13:30:23 -0400 [thread overview]
Message-ID: <x7zq2dxjyo.fsf@unilab.dfci.harvard.edu> (raw)
In-Reply-To: Mark Boyns's message of 26 Sep 1996 09:02:35 -0700
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "MB" == Mark Boyns <boyns@sdsu.edu> writes:
MB> A friend mentioned to me that his newsreader is having problems with
MB> the References header that Gnus is generating. Apparently Free
MB> Agent and Netscape cannot deal with a multi-line References header.
Then they are broken. RFC <mumble> states that headers may span
multiple lines so long as you indent continuation lines with
whitespace.
MB> I have to assume that multi-line References are valid so I guess the
MB> other newsreaders are broken. Maybe there should be a way to keep
MB> the References on a single line?
This is GNU Emacs you are talking about, here, so of course there is a
way. But catering to someone else's broken software does not get that
software fixed.
-----BEGIN PGP SIGNATURE-----
Version: 2.6.3
Charset: noconv
iQCVAwUBMkq9sJ6VRH7BJMxHAQFLQAQAwBAKfglGJep2A//KUqGMSkQ7Eqhye7Z1
tCS0pASpM2fM8rSj9nBqFBnrIfhaSw7r+bAAwCgNMKz186yfpdH+K3IiiqLWvejp
wcuh701K1HvYnpuRYdSHH+36dWy1TWbcwhetumSAliLNKxH/SQ4oeYRHtbiCrj3w
pzmDHkHrRy8=
=Tr3p
-----END PGP SIGNATURE-----
--
Richard Pieri/Information Services \ Curiosity never killed anything, except
<ratinox@unilab.dfci.harvard.edu> \ maybe a few hours. -A cat's guide to life
http://www.dfci.harvard.edu/ \
next prev parent reply other threads:[~1996-09-26 17:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-09-26 16:02 Mark Boyns
1996-09-26 17:30 ` Richard Pieri [this message]
1996-09-27 2:51 ` Steven L Baur
1996-09-27 18:54 ` Paul Franklin
1996-09-27 19:30 ` Per Abrahamsen
1996-09-26 17:59 ` William Perry
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=x7zq2dxjyo.fsf@unilab.dfci.harvard.edu \
--to=ratinox@unilab.dfci.harvard.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).