From: Emmanuel Michon <michon@enst.fr>
Subject: a certain summer night...
Date: 09 Nov 1998 11:19:52 +0100 [thread overview]
Message-ID: <y9fxemrdw4l3.fsf@enst.fr> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=NIL, Size: 554 bytes --]
Michael R Cook <cook@clearviewtech.com> wrote:
>That behavior seems to be kind of braindead to begin with.
indeed.
>But what's interesting is how Gnus handles these Subject lines.
>These ^Ms cause Gnus (Pterodactyl Gnus v0.40) to create a
>funny-looking *Summary* buffer. Gnus seems to convert each ^M
>character into a newline character, and each *Summary* line ends up
>displaying as multiple lines.
Greatly damages the behavior of commands like M P b (mark all
to prepare respooling), or reply.
--
Emmanuel Michon (http://www.enst.fr/~michon)
reply other threads:[~1998-11-09 10:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=y9fxemrdw4l3.fsf@enst.fr \
--to=michon@enst.fr \
/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).