unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Matthias Guedemann <matthias.guedemann@ovgu.de>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: [BUG] multipart ID of show != part
Date: Mon, 23 May 2011 13:51:03 -0400	[thread overview]
Message-ID: <4DDA9E87.3050409@fifthhorseman.net> (raw)
In-Reply-To: <87ei3pqqhe.fsf@pc44es141.cs.uni-magdeburg.de>

[-- Attachment #1: Type: text/plain, Size: 964 bytes --]

On 05/23/2011 01:25 PM, Matthias Guedemann wrote:
> Hi all,
> 
> I found some problems with the multipart/mixed behavior of current
> master. I have several multipart mails where the html part is not
> displayed and a text/plain attachment is wrongly reported as text/html. 
> 
> I have no real insight into the inner workings of notmuch-show but have
> found this discrepancy between "notmuch show" and "notmuch part":

the part numbering and representations are in the middle of a major
reorganization; the part numbers should be normalized across all uses
(with the exception of decrypted messages, whose part numberings will
change based on a successful decryption) once the overhaul is done.

i believe that the "notmuch part" subcommand itself is likely to go away
in favor of a --part=X argument to "notmuch show".

We will ensure that the part numbering is correct, but i agree with you
that current master isn't there yet.

	--dkg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]

  reply	other threads:[~2011-05-23 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 17:25 [BUG] multipart ID of show != part Matthias Guedemann
2011-05-23 17:51 ` Daniel Kahn Gillmor [this message]
2011-05-23 21:41 ` Carl Worth
2011-05-24 10:07   ` Matthias Guedemann

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=4DDA9E87.3050409@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=matthias.guedemann@ovgu.de \
    --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).