Matthew Lear <matt@bubblegen.co.uk> writes:

> On Sat, Mar 12 2016 at  2:37:44 pm GMT, David Edmondson <dme@dme.org> wrote:
>> On Sat, Mar 12 2016, David Bremner wrote:
>>> Tomi Ollila <tomi.ollila@iki.fi> 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