unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
	notmuch@notmuchmail.org, notmuch@freelists.org
Subject: Re: changing behaviour of notmuch show --part=1
Date: Mon, 22 May 2017 17:06:13 -0400	[thread overview]
Message-ID: <874lwctxdm.fsf@fifthhorseman.net> (raw)
In-Reply-To: <878tlpyyfi.fsf@tethera.net>

On Mon 2017-05-22 07:32:17 -0300, David Bremner wrote:
> The current behaviour of "notmuch show --part=1 --raw" is somewhat
> peculiar. This is supposed to be the message body, but if the message is
> multipart, it also includes the headers. This seems to be a direct
> translation of an implimentation of quirk of gmime. In gmime 3.0 this
> quirk goes away, and the behaviour of notmuch consequently changes,
> unless we do something about it. I actually think the new behaviour
> makes more sense (you only get the headers with part=0). There seem to
> be several options
>
> 1) Bug-for-Bug-compatibility: Add special case code for gmime-3.0 to
>    output headers.
>
> 2) Allow-varying-output: Consider the previous behaviour a bug, fixed by
>    using gmime-3.0.  This makes it hard for people to rely on, although
>    how one relies on it currently since it varies by message is a
>    mystery.
>
> 3) Fix the alleged bug: special case the output of the body with
>    gmime-2.6 to avoid outputting headers.

i favor (2) for the short term, while treating (3) as an open bug to be
fixed.

thanks for identifying this, David.

       --dkg

  reply	other threads:[~2017-05-23  1:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-22 10:32 changing behaviour of notmuch show --part=1 David Bremner
2017-05-22 21:06 ` Daniel Kahn Gillmor [this message]
2017-05-23 11:17   ` 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=874lwctxdm.fsf@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=david@tethera.net \
    --cc=notmuch@freelists.org \
    --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).