unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Mark Walters <markwalters1009@gmail.com>,
	Istvan Marko <notmuch@kismala.com>,
	notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: add buttons for all multipart/related parts
Date: Wed, 21 Aug 2013 10:26:13 -0700	[thread overview]
Message-ID: <87a9kbc5vu.fsf@servo.finestructure.net> (raw)
In-Reply-To: <87ob8ste5f.fsf@qmul.ac.uk>

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

On Tue, Aug 20 2013, Mark Walters <markwalters1009@gmail.com> wrote:
> What does the (mis-behaving)  part button say? is it [image/jpeg] or
> [application/octet-stream as image/jpeg] or? and what do correctly
> behaving part buttons say?

Hey, Mark.  That's the perplexing part: the parts seem otherwise very
similar.  For the case of the part that is *not* handled correctly, the
Content info and button are:

  Content-Type: image/jpeg; name="photo.JPG"
  Content-Transfer-Encoding: base64
  Content-Id: <...>
  Content-Disposition: inline; filename="photo.JPG"

  [ photo.JPG: image/jpeg ]

And in the case of a test message that seems to behave as expected:

  Content-Type: image/jpeg
  Content-Disposition: inline; filename=monkey.jpg
  Content-Transfer-Encoding: base64
  Content-Description: monkey!

  [ monkey.jpg: image/jpeg ]

In the first case clicking on the part button has no effect.  In the
later case the image opens fine in the external viewer.

I guess the only other difference is the rest of the MIME structure that
these parts are embedded in...

jamie.

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

  reply	other threads:[~2013-08-21 17:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-16 20:24 [PATCH] emacs: add buttons for all multipart/related parts Istvan Marko
2013-08-20 15:17 ` Jameson Graef Rollins
2013-08-20 15:43   ` Istvan Marko
2013-08-20 16:07     ` Jameson Graef Rollins
2013-08-20 16:17       ` Istvan Marko
2013-08-20 18:23   ` Mark Walters
2013-08-21 17:26     ` Jameson Graef Rollins [this message]
2013-08-23  8:36   ` Mark Walters
2013-09-01 17:13 ` Mark Walters
2013-09-10 11:15 ` 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=87a9kbc5vu.fsf@servo.finestructure.net \
    --to=jrollins@finestructure.net \
    --cc=markwalters1009@gmail.com \
    --cc=notmuch@kismala.com \
    --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).