Re: (emacs) Parsing problems replying to encrypted html

diff --git a/aa/72e3474d12810bbe5675231f7873c02010cdc9 b/aa/72e3474d12810bbe5675231f7873c02010cdc9
new file mode 100644 (file)
index 0000000..2537a3d
--- /dev/null
+++ b/aa/72e3474d12810bbe5675231f7873c02010cdc9
@@ -0,0 +1,95 @@
+Return-Path: <david@tethera.net>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+ by arlo.cworth.org (Postfix) with ESMTP id DE4786DE02CA\r
+ for <notmuch@notmuchmail.org>; Fri,  1 Apr 2016 04:34:33 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at cworth.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.021\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.021 tagged_above=-999 required=5\r
+ tests=[AWL=-0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01]\r
+ autolearn=disabled\r
+Received: from arlo.cworth.org ([127.0.0.1])\r
+ by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024)\r
+ with ESMTP id tmQeqxPfRKmU for <notmuch@notmuchmail.org>;\r
+ Fri,  1 Apr 2016 04:34:26 -0700 (PDT)\r
+Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197])\r
+ by arlo.cworth.org (Postfix) with ESMTPS id D19396DE014A\r
+ for <notmuch@notmuchmail.org>; Fri,  1 Apr 2016 04:34:25 -0700 (PDT)\r
+Received: from remotemail by fethera.tethera.net with local (Exim 4.84)\r
+ (envelope-from <david@tethera.net>)\r
+ id 1alxLs-0000TG-I8; Fri, 01 Apr 2016 07:34:56 -0400\r
+Received: (nullmailer pid 19418 invoked by uid 1000);\r
+ Fri, 01 Apr 2016 11:34:20 -0000\r
+From: David Bremner <david@tethera.net>\r
+To: Matthew Lear <matt@bubblegen.co.uk>\r
+Cc: notmuch@notmuchmail.org\r
+Subject: Re: (emacs) Parsing problems replying to encrypted html\r
+In-Reply-To: <87h9fm315q.fsf@bubblegen.co.uk>\r
+References: <f50e07855e9bbbdd780ef925d8e2d879.squirrel@webmail.plus.net>\r
+ <m2a8miwc6x.fsf@dme.org>\r
+ <c4ff9f2c141441be10b1cb4b1e0300a7.squirrel@webmail.plus.net>\r
+ <56DD48B3.90604@bubblegen.co.uk> <87mvqatr6y.fsf@zancas.localnet>\r
+ <87h9gigfyz.fsf@bubblegen.co.uk> <87pov58b9y.fsf@zancas.localnet>\r
+ <m260wxkvf3.fsf@guru.guru-group.fi> <87wpp76ctq.fsf@zancas.localnet>\r
+ <m2shzvrccn.fsf@dme.org> <87h9fm315q.fsf@bubblegen.co.uk>\r
+User-Agent: Notmuch/0.21+74~g6c60fb1 (http://notmuchmail.org) Emacs/24.5.1\r
+ (x86_64-pc-linux-gnu)\r
+Date: Fri, 01 Apr 2016 08:34:20 -0300\r
+Message-ID: <87oa9timv7.fsf@zancas.localnet>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.20\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+ <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <https://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: <https://notmuchmail.org/mailman/listinfo/notmuch>,\r
+ <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Fri, 01 Apr 2016 11:34:34 -0000\r
+\r
+Matthew Lear <matt@bubblegen.co.uk> writes:\r
+\r
+> On Sat, Mar 12 2016 at  2:37:44 pm GMT, David Edmondson <dme@dme.org> wrote:\r
+>> On Sat, Mar 12 2016, David Bremner wrote:\r
+>>> Tomi Ollila <tomi.ollila@iki.fi> writes:\r
+>>>\r
+>>>> 2016-03-08 (Tue) 14:16:01: reply --format=sexp --format-version=1 --reply-to=sender thread:0000000000004a6f\r
+>>>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=2 id:56DDE706.6060702@bubblegen.co.uk\r
+>>>> 2016-03-08 (Tue) 14:16:01: show --format=sexp --include-html --part=3 id:56DDE706.6060702@bubblegen.co.uk\r
+>>>> 2016-03-08 (Tue) 14:16:01: show --format=raw --part=3 id:56DDE706.6060702@bubblegen.co.uk\r
+>>>>\r
+>>>\r
+>>> I think the problem is in the following let form, which uses\r
+>>> notmuch-show-process-crypto. That isn't set in search mode. I'm unclear\r
+>>> on what the right solution is here; we could check\r
+>>> notmuch-crypto-process-mime, but I'm not sure how this would interact\r
+>>> with the handling of prefix arguments (for temporary toggling).\r
+>>\r
+>> Is "reply" from search mode a common pattern of use? Currently it seems\r
+>> generally un-useful (the thread has to contain just a single message -\r
+>> not just a single matching message).\r
+>>\r
+>>> (defun notmuch-mua-reply (query-string &optional sender reply-all)\r
+>>>   (let ((args '("reply" "--format=sexp" "--format-version=1"))\r
+>>>    (process-crypto notmuch-show-process-crypto)\r
+>>>    reply\r
+>>>    original)\r
+>\r
+> Hi. I just wondered if anyone had managed to make any progress on this?\r
+\r
+Hi Matthew;\r
+\r
+I'm not sure if you noticed, but there are patches in master now (and\r
+will be in a release pretty soon) that handle the part of the problem\r
+related to encrypted html, but nothing so far for the problem(s) of\r
+replying from search view.\r
+\r
+d\r