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