From: Sanjoy Mahajan <sanjoy@olin.edu>
To: David Bremner <david@tethera.net>,
Allan Streib <astreib@indiana.edu>, <notmuch@notmuchmail.org>
Subject: Re: Bug/Issue: References header doesn't wrap in emacs package
Date: Mon, 6 Jun 2016 22:50:45 -0400 [thread overview]
Message-ID: <87d1ntg1a2.fsf@insight.mit.edu> (raw)
In-Reply-To: <878u7k21d8.fsf@zancas.localnet>
On 2015-10-02 21:21, David Bremner <david@tethera.net> wrote:
>>> The problem is a References header that is too long/not wrapped.
>>>
>>
>> Hi Allan;
>>
>> Thanks for the report. I can see how notmuch-reply would generate a
>> long references header in that situation. We rely on message-mode (part
>> of Gnus) to actually send the message, and it isn't clear to me yet if
>> message-mode (or some function it invokes) normally folds long headers.
>
> I have reported this as an emacs bug.
>
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21608
I'm not sure whether fixing it in emacs is right. The command 'notmuch
reply' is itself (with the sexp or json formats) generating the too-long
References: header. Shouldn't it generate an RFC-compliant message?
Or should the json/sexp formats remain agnostic about line length,
because wrapping doesn't make sense with key/value pairs? In that case,
I agree that message-mode should fix any long lines.
By the way, the latest Exim release (4.87), at least as configured in
Debian, does limit lines to 998 characters, and that limit has been
causing me a few hiccups -- usually when I reply to a message sent by
gmail with a zillion references (perhaps it lists every message in the
thread).
-Sanjoy
next prev parent reply other threads:[~2016-06-07 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 19:00 Bug/Issue: References header doesn't wrap in emacs package Allan Streib
2015-10-02 12:08 ` David Bremner
2015-10-03 1:21 ` David Bremner
2016-06-07 2:50 ` Sanjoy Mahajan [this message]
2016-06-07 10:28 ` David Bremner
2016-06-07 15:51 ` Sanjoy Mahajan
2017-01-27 0:32 ` David Bremner
2017-03-05 11:45 ` David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d1ntg1a2.fsf@insight.mit.edu \
--to=sanjoy@olin.edu \
--cc=astreib@indiana.edu \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).