From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: nnslashdot: the dreaded \201 bug
Date: 27 Nov 1999 21:20:18 +0100 [thread overview]
Message-ID: <vafvh6nptz1.fsf@lucy.cs.uni-dortmund.de> (raw)
Whee, after this `MULE is evil' thread on gnu.emacs.help (or was it
comp.emacs) I kinda feel sheepish that the \201 bug is back again :-/
An nnslashdot From line:
From: Jonas berg <jonas@coyote.org>
(It's from the BBS-like communities group.)
I wonder where this comes from? Can one do anything about it? I
suspect that both W3 and Gnus are trying to do muleification or maybe
demuleification, leading to one \201 too many...
kai
--
because I couldn't think of a good beginning.
next reply other threads:[~1999-11-27 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-27 20:20 Kai Großjohann [this message]
1999-12-01 23:11 ` Lars Magne Ingebrigtsen
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=vafvh6nptz1.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).