Re: [PATCH 4/4] emacs: Use the new JSON reply format.

diff --git a/c7/229881f6b0af45987f64216d6e24f1611b87ff b/c7/229881f6b0af45987f64216d6e24f1611b87ff
new file mode 100644 (file)
index 0000000..52262c8
--- /dev/null
+++ b/c7/229881f6b0af45987f64216d6e24f1611b87ff
@@ -0,0 +1,88 @@
+Return-Path: <dme@dme.org>\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 5789B429E25\r
+       for <notmuch@notmuchmail.org>; Thu, 12 Jan 2012 04:07:49 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.7\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.7 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_LOW=-0.7] autolearn=disabled\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 Pbf00ejCYPpV for <notmuch@notmuchmail.org>;\r
+       Thu, 12 Jan 2012 04:07:49 -0800 (PST)\r
+Received: from mail-wi0-f181.google.com (mail-wi0-f181.google.com\r
+       [209.85.212.181]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id C74C6431FB6\r
+       for <notmuch@notmuchmail.org>; Thu, 12 Jan 2012 04:07:48 -0800 (PST)\r
+Received: by wibhr12 with SMTP id hr12so1249589wib.26\r
+       for <notmuch@notmuchmail.org>; Thu, 12 Jan 2012 04:07:47 -0800 (PST)\r
+Received: by 10.181.13.17 with SMTP id eu17mr5566613wid.12.1326370067609;\r
+       Thu, 12 Jan 2012 04:07:47 -0800 (PST)\r
+Received: from hotblack-desiato.hh.sledj.net\r
+       (host81-149-164-25.in-addr.btopenworld.com. [81.149.164.25])\r
+       by mx.google.com with ESMTPS id v13sm5479208wbm.14.2012.01.12.04.07.45\r
+       (version=TLSv1/SSLv3 cipher=OTHER);\r
+       Thu, 12 Jan 2012 04:07:46 -0800 (PST)\r
+Received: by hotblack-desiato.hh.sledj.net (Postfix, from userid 30000)\r
+       id 718719FEE3; Thu, 12 Jan 2012 12:07:43 +0000 (GMT)\r
+To: Dmitry Kurochkin <dmitry.kurochkin@gmail.com>,\r
+       Adam Wolfe Gordon <awg@xvx.ca>\r
+Subject: Re: [PATCH 4/4] emacs: Use the new JSON reply format.\r
+In-Reply-To: <87k44xgw09.fsf@gmail.com>\r
+References: <1326009162-19524-1-git-send-email-awg+notmuch@xvx.ca>\r
+       <1326009162-19524-5-git-send-email-awg+notmuch@xvx.ca>\r
+       <cun62gl1cqv.fsf@hotblack-desiato.hh.sledj.net>\r
+       <CAMoJFUt8F417wzSmiHDv2KHa9y5ARYh=xRHKEsWBXYXHfaN64A@mail.gmail.com>\r
+       <87k44xgw09.fsf@gmail.com>\r
+User-Agent: Notmuch/0.10.2+186~gd0f7804 (http://notmuchmail.org)\r
+       Emacs/24.0.92.1 (x86_64-pc-linux-gnu)\r
+From: David Edmondson <dme@dme.org>\r
+Date: Thu, 12 Jan 2012 12:07:40 +0000\r
+Message-ID: <cunzkdtkttf.fsf@hotblack-desiato.hh.sledj.net>\r
+MIME-Version: 1.0\r
+Content-Type: multipart/signed; boundary="=-=-=";\r
+       micalg=pgp-sha1; protocol="application/pgp-signature"\r
+Cc: notmuch@notmuchmail.org\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: Thu, 12 Jan 2012 12:07:49 -0000\r
+\r
+--=-=-=\r
+Content-Type: text/plain\r
+\r
+On Thu, 12 Jan 2012 12:33:58 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote:\r
+> I did not follow the rest of the discussion, so sorry if I missed\r
+> something obvious.  But why can't we render HTML parts in replies the\r
+> same way we do in notmuch-show (using `mm-display-part')?  That should\r
+> not introduce a w3m.el requirement, would use the same renderer as\r
+> configured for show and hence would produce consistent output in show\r
+> and reply.\r
+\r
+Agreed, that would be good. It could be done as a second stage, though.\r
+\r
+--=-=-=\r
+Content-Type: application/pgp-signature\r
+\r
+-----BEGIN PGP SIGNATURE-----\r
+Version: GnuPG v1.4.11 (GNU/Linux)\r
+\r
+iEYEARECAAYFAk8OzQwACgkQaezQq/BJZRbV0QCeJ8i18celFbObMRb+xuf4noFV\r
+hs0An1gsnM1auF21mofCKh3OPY4MX8Tl\r
+=LxsK\r
+-----END PGP SIGNATURE-----\r
+--=-=-=--\r