unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Edmondson <dme@dme.org>
To: Jameson Graef Rollins <jrollins@finestructure.net>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: [PATCH] emacs: Make the part content available to `mm-inlinable-p'.
Date: Mon, 23 Jan 2012 08:02:16 +0000	[thread overview]
Message-ID: <cunbopu6e47.fsf@hotblack-desiato.hh.sledj.net> (raw)
In-Reply-To: <8762g6m984.fsf@servo.finestructure.net>

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

On Fri, 20 Jan 2012 12:04:27 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Thu, 19 Jan 2012 09:34:07 +0000, David Edmondson <dme@dme.org> wrote:
> > The `mm-inlinable-p' function works better if it has access to the
> > data of the relevant part, so load that content before calling it.
> > 
> > Don't load the content for parts that the user has indicated no desire
> > to inline.
> 
> So I'm a little confused here.  Is there some variable I need to set to
> get inlinable stuff to display inline?  If so, I can't figure out what
> it is.  I don't see anything relevant in notmuch config, and I'm not
> finding anything in mm- either, although I'm not quite sure what I'm
> looking for.
> 
> Currently I'm not getting any images displayed inline.  I used to get
> some, but not all, but at the moment I'm just getting a little white box
> with no image in it.  After applying this patch, I'm not getting any
> attempt to inline images at all.  But I'm assuming there is some
> variable I need to set that I haven't...

Are you talking about:
    - straightforward image/* attachments,
    - images in HTML which are part of a multipart/related ('cid:'
      images),
    - images in HTML which are referenced using HTTP (or FTP or ... I
      suppose).
?

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

  reply	other threads:[~2012-01-23  8:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18 17:33 [PATCH] emacs: Make the part content available to the mm-inline* checks David Edmondson
2012-01-18 17:35 ` David Edmondson
2012-01-18 17:39 ` [PATCH v2] " David Edmondson
2012-01-18 18:04   ` Dmitry Kurochkin
2012-01-18 18:30     ` David Edmondson
2012-01-18 19:00       ` Dmitry Kurochkin
2012-01-18 19:35         ` Austin Clements
2012-01-18 19:59           ` Dmitry Kurochkin
2012-01-20 20:13           ` Jameson Graef Rollins
2012-01-23  8:00             ` David Edmondson
2012-01-19  7:39         ` David Edmondson
2012-01-19  9:23           ` Dmitry Kurochkin
2012-01-19  9:34             ` [PATCH] emacs: Make the part content available to `mm-inlinable-p' David Edmondson
2012-01-19  9:37               ` Dmitry Kurochkin
2012-01-19 17:31               ` Aaron Ecay
2012-01-20 14:18               ` Tomi Ollila
2012-01-20 20:04               ` Jameson Graef Rollins
2012-01-23  8:02                 ` David Edmondson [this message]
2012-01-26 12:28               ` 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=cunbopu6e47.fsf@hotblack-desiato.hh.sledj.net \
    --to=dme@dme.org \
    --cc=jrollins@finestructure.net \
    --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).