[PATCH] emacs: process crypto for reply only when specified

[Tomi Ollila]

On Sun, Apr 13 2014, David Bremner wrote:

> Tomi Ollila <tomi.ollila at iki.fi> writes:
>
>>
>> Code looks OK. +1. I'm interested to see whether replies to signed emails
>> work on this system where sign/(de|en)cryption just doesn't work (out of
>> the box) :D
>>
>
> It's a good point. I need to insert my smartcard to sign things, which
> I'm sometimes too lazy to do. In my case, maybe I should stop being so
> lazy; I suspect my particular case is a but unusual.

Below is what happened to me when I failed to remove the 
"<#secure method=pgpmime mode=sign>" part from the beginning of the message
It is very easy to detect and there is nothing much one can use if they
have configured notmuch-crypto-process-mime to be t (like I seem to have ;)

--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--
notmuch-crypto-process-mime is a variable defined in `one-notmuch.el'.
Its value is t
Original value was nil
--8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<----8<--

Emacs stopped responding my keypresses after C-c C-c; C-g brought control
back to me -- and then I tried again...

ps output

19028 ?     SLs  0:00 /usr/bin/gpg --no-tty --status-fd 1 --yes --command-f
19029 ?     SL   0:00 gpg-agent --server
19030 ?     RL   0:50 /usr/bin/pinentry-curses
19034 ?     SLs  0:00 /usr/bin/gpg --no-tty --status-fd 1 --yes --command-f
19035 ?     SL   0:00 gpg-agent --server
19036 ?     RL   0:04 /usr/bin/pinentry-curses
19037 pts/6 R+   0:00 ps x

The 'pinentry-curses' and this emacs doesn't play along well (I've seen
this happening before when I tried to encrypt some messages). I had
to pkill gpg and pinentry-curses to get rid of the above processes.

> Perhaps people with no ability to sign are less likely to have
> "notmuch-crypto-process-mime" set?  Or we can add another configuration
> variable initialized from notmuch-crypto-process-mime, but allowing
> people to shut this off.

Well, I set notmuch-crypto-process-mime to nil -- it still wants to
sign the message and runs gpg...

... my case may be unique enough no-one else has the same problem; anyway
ideas how to automatically kill the gpg process(es) when one aborts send
attempt? 

Tomi