unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: Allan Streib <astreib@indiana.edu>, notmuch@notmuchmail.org
Subject: Re: Bug/Issue: References header doesn't wrap in emacs package
Date: Thu, 26 Jan 2017 20:32:37 -0400	[thread overview]
Message-ID: <874m0le40q.fsf@tethera.net> (raw)
In-Reply-To: <87twh5dmki.fsf@insight.mit.edu>

Sanjoy Mahajan <sanjoy@olin.edu> writes:

> On 2016-06-07 06:28, David Bremner <david@tethera.net> wrote:
>
>> Sanjoy Mahajan <sanjoy@olin.edu> writes:
>>
>>
>>> 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.
>>
>> For me the main issue is that the references header is editable by the
>> user before sending. So some input sanitization is needed at the sending
>> stage.
>
> Further supporting that argument, the user could also include a
> 1000-character line in the message body, which would require sanitizing
> at the sending stage.
>
> -Sanjoy

Headers are now folded in emacs master, apparently

        http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21608

  reply	other threads:[~2017-01-27  0:32 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
2016-06-07 10:28       ` David Bremner
2016-06-07 15:51         ` Sanjoy Mahajan
2017-01-27  0:32           ` David Bremner [this message]
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=874m0le40q.fsf@tethera.net \
    --to=david@tethera.net \
    --cc=astreib@indiana.edu \
    --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).