Re: [notmuch] emacs: On getting support for inline images

diff --git a/f0/1ca72adc67b220c77d0edb7f6caba61f500c64 b/f0/1ca72adc67b220c77d0edb7f6caba61f500c64
new file mode 100644 (file)
index 0000000..8d41a36
--- /dev/null
+++ b/f0/1ca72adc67b220c77d0edb7f6caba61f500c64
@@ -0,0 +1,78 @@
+Return-Path: <prvs=jrosenthal=650410043@jhu.edu>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id E74AE431FBD\r
+       for <notmuch@notmuchmail.org>; Wed, 10 Feb 2010 14:10:21 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.918\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.918 tagged_above=-999 required=5 tests=[AWL=1.081,\r
+       BAYES_50=0.001, RCVD_IN_DNSWL_MED=-4] autolearn=unavailable\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id AG93N3W9iYD7 for <notmuch@notmuchmail.org>;\r
+       Wed, 10 Feb 2010 14:10:20 -0800 (PST)\r
+X-Greylist: delayed 3602 seconds by postgrey-1.32 at olra;\r
+       Wed, 10 Feb 2010 14:10:20 PST\r
+Received: from ipex2.johnshopkins.edu (ipex2.johnshopkins.edu [162.129.8.151])\r
+       by olra.theworths.org (Postfix) with ESMTP id 09E63431FAE\r
+       for <notmuch@notmuchmail.org>; Wed, 10 Feb 2010 14:10:19 -0800 (PST)\r
+X-IronPort-AV: E=Sophos;i="4.49,446,1262581200"; d="scan'208";a="302469174"\r
+Received: from c-69-255-36-229.hsd1.md.comcast.net (HELO lucky)\r
+       ([69.255.36.229])\r
+       by ipex2.johnshopkins.edu with ESMTP/TLS/AES256-SHA;\r
+       10 Feb 2010 16:10:16 -0500\r
+Received: from jkr by lucky with local (Exim 4.69)\r
+       (envelope-from <jrosenthal@jhu.edu>)\r
+       id 1NfJoy-0006fm-3O; Wed, 10 Feb 2010 16:10:04 -0500\r
+From: Jesse Rosenthal <jrosenthal@jhu.edu>\r
+To: Carl Worth <cworth@cworth.org>, notmuch@notmuchmail.org\r
+In-Reply-To: <87vde4derz.fsf@yoom.home.cworth.org>\r
+References: <87vde4derz.fsf@yoom.home.cworth.org>\r
+Date: Wed, 10 Feb 2010 16:10:03 -0500\r
+Message-ID: <87aavg6bmc.fsf@jhu.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+Subject: Re: [notmuch] emacs: On getting support for inline images\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Wed, 10 Feb 2010 22:10:22 -0000\r
+\r
+On Wed, 10 Feb 2010 12:20:00 -0800, Carl Worth <cworth@cworth.org> wrote:\r
+> Here are some ideas for possible (and independent) fixes:\r
+> ....\r
+> 3. We could move away from these various mm- functions for displaying\r
+>    MIME parts and simply add functionality to the notmuch command line\r
+>    for extracting individual MIME parts from messages, (which is\r
+>    something that a non-emacs client will likely want anyway). Then we\r
+>    can use the lower-level functions to display things directly. (For\r
+>    example, displaying an image looks as simple as calling the\r
+>    create-image and put-image functions).\r
+\r
+I really think that this (#3) is the way to go, going forward. First, it\r
+frees us up from the various slownesses and eccentricities of the mm-\r
+modes. Second, and more importantly, it makes it a *lot* easier for\r
+other clients to play, for the remote use of the existing emacs client,\r
+and for scripted command-line usage (e.g. put all the attached vcards in\r
+your maildir into a directory).\r
+\r
+I've been playing around with this a bit, for my own purposes,\r
+already. Unfortunately, my autodidact's c code is probably all sorts of\r
+wrong, and I wouldn't want to subject anyone to it. But it does seem\r
+like the way to go, and I'd be very happy to help out with any testing,\r
+if anyone goes forwad with this.\r
+\r
+Best,\r
+Jesse\r