1 Return-Path: <dmitry.kurochkin@gmail.com>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 1AFD1431FAF
\r
6 for <notmuch@notmuchmail.org>; Thu, 19 Jan 2012 01:24:38 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
11 X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5
\r
12 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
\r
13 FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled
\r
14 Received: from olra.theworths.org ([127.0.0.1])
\r
15 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
16 with ESMTP id vpvSiu3yNHxt for <notmuch@notmuchmail.org>;
\r
17 Thu, 19 Jan 2012 01:24:37 -0800 (PST)
\r
18 Received: from mail-bk0-f53.google.com (mail-bk0-f53.google.com
\r
19 [209.85.214.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits))
\r
20 (No client certificate requested)
\r
21 by olra.theworths.org (Postfix) with ESMTPS id 52614431FAE
\r
22 for <notmuch@notmuchmail.org>; Thu, 19 Jan 2012 01:24:37 -0800 (PST)
\r
23 Received: by bkty12 with SMTP id y12so2536168bkt.26
\r
24 for <notmuch@notmuchmail.org>; Thu, 19 Jan 2012 01:24:34 -0800 (PST)
\r
25 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma;
\r
26 h=from:to:subject:in-reply-to:references:user-agent:date:message-id
\r
27 :mime-version:content-type;
\r
28 bh=7m4rYhfmiyLv8fxdV/gtUtpi4xigQrfMTHUV/eDmT8k=;
\r
29 b=B6Ss3XVLo6/RYAIHaZVKbFMX4TpIMe2oPdQ03Wi0V3snlA5SojET/u2LVuUTLdyO1/
\r
30 qIe7h+nEfqmFFUpcF0mdwYmr9oc88ygH9XIdN2WDYmc+uYTOrGnGGv+vQZz6cSa7E6QV
\r
31 jlWu3OVC4cP0mvJZYYmWhTQYMK/Q/5VwGQTKc=
\r
32 Received: by 10.205.133.137 with SMTP id hy9mr8148074bkc.46.1326965074479;
\r
33 Thu, 19 Jan 2012 01:24:34 -0800 (PST)
\r
34 Received: from localhost ([91.144.186.21])
\r
35 by mx.google.com with ESMTPS id sp6sm37293966bkb.2.2012.01.19.01.24.33
\r
36 (version=TLSv1/SSLv3 cipher=OTHER);
\r
37 Thu, 19 Jan 2012 01:24:33 -0800 (PST)
\r
38 From: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>
\r
39 To: David Edmondson <dme@dme.org>, notmuch <notmuch@notmuchmail.org>
\r
40 Subject: Re: [PATCH v2] emacs: Make the part content available to the
\r
42 In-Reply-To: <cunboq06szv.fsf@hotblack-desiato.hh.sledj.net>
\r
43 References: <1326907993-11054-1-git-send-email-dme@dme.org>
\r
44 <1326908371-11949-1-git-send-email-dme@dme.org>
\r
45 <877h0o99aj.fsf@gmail.com>
\r
46 <cunlip47tir.fsf@hotblack-desiato.hh.sledj.net>
\r
47 <874nvs96ps.fsf@gmail.com>
\r
48 <cunboq06szv.fsf@hotblack-desiato.hh.sledj.net>
\r
49 User-Agent: Notmuch/0.11+73~g8a5402e (http://notmuchmail.org) Emacs/23.3.1
\r
50 (x86_64-pc-linux-gnu)
\r
51 Date: Thu, 19 Jan 2012 13:23:37 +0400
\r
52 Message-ID: <87k44o6o6e.fsf@gmail.com>
\r
54 Content-Type: text/plain; charset=us-ascii
\r
55 X-BeenThere: notmuch@notmuchmail.org
\r
56 X-Mailman-Version: 2.1.13
\r
58 List-Id: "Use and development of the notmuch mail system."
\r
59 <notmuch.notmuchmail.org>
\r
60 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
61 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
62 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
63 List-Post: <mailto:notmuch@notmuchmail.org>
\r
64 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
65 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
66 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
67 X-List-Received-Date: Thu, 19 Jan 2012 09:24:38 -0000
\r
69 On Thu, 19 Jan 2012 07:39:32 +0000, David Edmondson <dme@dme.org> wrote:
\r
70 > On Wed, 18 Jan 2012 23:00:15 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:
\r
71 > > > That would allow a sane default (("image/*" "text/*") perhaps), but also
\r
72 > > > allow more to be added to that list (or some to be removed), either by
\r
73 > > > code that detected the (in)ability to render it or the user.
\r
75 > > Perhaps there is such a list in mm already?
\r
77 > There's a function which does almost exactly this - `mm-inlinable-p'. It
\r
78 > has a list of types and tests, `mm-inline-media-tests'. Some of those
\r
79 > tests require access to the part content to decide if the part is
\r
80 > inlinable. Many of them don't. The image/jpeg test _does_ want access to
\r
83 > We're already using this function, of course.
\r
85 > `mm-inlined-p' is the corresponding "does the user want this part
\r
86 > inlined" test. It's much simpler and never looks at the part content.
\r
88 > Currently we merge those tests into one:
\r
90 > (if (and (mm-inlinable-p handle)
\r
91 > (mm-inlined-p handle))
\r
93 > and have acquired part content either before or after the combined test.
\r
95 > Perhaps we could test `mm-inlined-p' first, then insert the content,
\r
96 > then test `mm-inlinable-p'? That way we would not acquire the content
\r
97 > for parts for which the user (or code) has selected not to inline the
\r
103 > Currently `mm-inlined-p' suggests that the following should be inlined
\r
106 > "image/.*" "text/.*" "message/delivery-status" "message/rfc822"
\r
107 > "message/partial" "message/external-body" "application/emacs-lisp"
\r
108 > "application/x-emacs-lisp" "application/pgp-signature"
\r
109 > "application/x-pkcs7-signature" "application/pkcs7-signature"
\r
110 > "application/x-pkcs7-mime" "application/pkcs7-mime"
\r
112 > These are the only types for which we'd acquire the part content for
\r
113 > examination by `mm-inlinable-p' (by default).
\r