unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Matthias Guedemann <matthias.guedemann@ovgu.de>,
	"notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: [BUG] multipart ID of show != part
Date: Mon, 23 May 2011 14:41:47 -0700	[thread overview]
Message-ID: <87pqn9m6w4.fsf@yoom.home.cworth.org> (raw)
In-Reply-To: <87ei3pqqhe.fsf@pc44es141.cs.uni-magdeburg.de>

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

On Mon, 23 May 2011 19:25:01 +0200, Matthias Guedemann <matthias.guedemann@ovgu.de> wrote:
> show produces this JSON:
> 
> ^Lbody{
> ^Lpart{ ID: 1, Content-type: multipart/mixed
> ^Lpart{ ID: 2, Content-type: text/html
...
> whereas "notmuch part --part=2" produces this (the content of the
> ATT00001.c file):

It used to be that the "multipart" containers were not printed in
"notmuch show" (so they weren't counted). We recently began emitting
these, and counting them, but we neglected to update the "notmuch part"
code to count them equivalently.

I've just pushed a quick patch to "notmuch part" to fix this problem for
now.

Soon, we'll have a patch series from Jameson committed that replaces the
"notmuch part" command with "notmuch show --part". That will have the
advantage of implementing both pieces of functionality with one piece of
code, so that skew like this will no longer be possible.

Thanks for the report.

-Carl

-- 
carl.d.worth@intel.com

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2011-05-23 21:41 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
2011-05-23 21:41 ` Carl Worth [this message]
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=87pqn9m6w4.fsf@yoom.home.cworth.org \
    --to=cworth@cworth.org \
    --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).