From: Russ Allbery <eagle@eyrie.org>
To: ding@gnus.org
Subject: Re: Recent change on Emacs master: aggressive word-wrap of header lines in article display
Date: Sat, 11 Dec 2021 08:58:00 -0800 [thread overview]
Message-ID: <878rwrhyef.fsf@hope.eyrie.org> (raw)
In-Reply-To: <87sfuzyudn.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren=22's?= message of "Sat, 11 Dec 2021 17:32:52 +0100")
Adam Sjøgren <asjo@koldfront.dk> writes:
> A recent change seems to have changed the display of long header lines
> to word wrap waaaay before the end of the window:
I've noticed this happening for a while, and when I've investigated, it's
been because the header in the original is RFC-2047-encoded and the
wrapping makes sense for the encoded text but not the decoded text. My
theory was that the header was wrapped before instead of after decoding.
If you check with C-u g, does that fit the behavior you're seeing?
If so, that does seem like a bug, and like it would be better to decode
the header first and then wrap it.
--
Russ Allbery (eagle@eyrie.org) <https://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~2021-12-11 16:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 16:32 Adam Sjøgren
2021-12-11 16:58 ` Russ Allbery [this message]
2021-12-11 17:41 ` Andreas Schwab
2021-12-11 17:57 ` Adam Sjøgren
2021-12-11 19:27 ` Emanuel Berg
2021-12-11 18:49 ` Russ Allbery
2021-12-11 17:57 ` Adam Sjøgren
2021-12-11 17:31 ` Eric Abrahamsen
2021-12-11 18:01 ` Adam Sjøgren
2021-12-11 18:45 ` Jose A. Ortega Ruiz
2021-12-11 20:01 ` Adam Sjøgren
2021-12-11 19:57 ` Adam Sjøgren
2021-12-11 20:12 ` Adam Sjøgren
2021-12-11 20:23 ` Adam Sjøgren
2021-12-11 20:29 ` Adam Sjøgren
2021-12-11 20:40 ` Eric Abrahamsen
2021-12-11 20:51 ` Adam Sjøgren
2021-12-11 20:54 ` Eric Abrahamsen
2021-12-11 21:04 ` Adam Sjøgren
2021-12-11 23:21 ` Stephen Berman
2021-12-12 0:15 ` Eric Abrahamsen
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=878rwrhyef.fsf@hope.eyrie.org \
--to=eagle@eyrie.org \
--cc=ding@gnus.org \
/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).