From: Yuri D'Elia <wavexx@thregr.org>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: message.el bug: message-field-value issue with folded headers
Date: Fri, 12 Jul 2019 14:45:43 +0200 [thread overview]
Message-ID: <87muhjbevc.fsf@wavexx.thregr.org> (raw)
In a recent change in message.el the headers are folded automatically
before being sent.
If the header has no whitespace, it will essentially move the entire
value into the next line:
|Header:
| long-value
Does it make sense to do so?
Anyway, `message-fetch-field' doesn't handle this case correctly. By
substituting "\n[\t ]+" => " " we're left with a leading space:
" long value"
Can we strip leading and trailing whitespace from value at the end of
the function?
next reply other threads:[~2019-07-12 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 12:45 Yuri D'Elia [this message]
2019-07-12 12:48 ` message.el bug: message-field-value issue with folded headers Lars Ingebrigtsen
2019-07-12 14:08 ` Lars 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muhjbevc.fsf@wavexx.thregr.org \
--to=wavexx@thregr.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).