From: David Edmondson <dme@dme.org>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH v3 1/4] emacs: Asynchronous retrieval of GPG keys
Date: Sat, 19 Jan 2019 11:15:11 +0000 [thread overview]
Message-ID: <m2tvi4q4ow.fsf@dme.org> (raw)
In-Reply-To: <87y37msmep.fsf@tethera.net>
On Monday, 2019-01-14 at 22:08:14 -04, David Bremner wrote:
> David Edmondson <dme@dme.org> writes:
>
>> Rather than blocking emacs while gpg does its' thing, by default run
>> key retrieval asynchronously, possibly updating the display of the
>> message on successful completion.
>> ---
>> emacs/notmuch-crypto.el | 85 +++++++++++++++++++++++++++++++++++------
>> 1 file changed, 74 insertions(+), 11 deletions(-)
>>
>> diff --git a/emacs/notmuch-crypto.el b/emacs/notmuch-crypto.el
>> index fc2b5301..c20fd4f8 100644
>> --- a/emacs/notmuch-crypto.el
>> +++ b/emacs/notmuch-crypto.el
>> @@ -43,6 +43,11 @@ mode."
>> :package-version '(notmuch . "0.25")
>> :group 'notmuch-crypto)
>>
>> +(defcustom notmuch-crypto-get-keys-asynchronously t
>> + "Retrieve gpg keys asynchronously."
>> + :type 'boolean
>> + :group 'notmuch-crypto)
>> +
>
> Sorry for the long delay. Should this have a :package-version key like
> the defcustom right about it?
Okay.
>> + (buffer (get-buffer-create "*notmuch-crypto-gpg-out*")))
>> + (if notmuch-crypto-get-keys-asynchronously
>> + (progn
>> + (notmuch-crypto--set-button-label
>> + button (format "Retrieving key %s asynchronously..." keyid))
>> + (let ((p (make-process :name "notmuch GPG key retrieval"
>> + :buffer buffer
>> + :command (list epg-gpg-program "--recv-keys" keyid)
>> + :connection-type 'pipe
>> + :sentinel #'notmuch-crypto--async-key-sentinel
>> + ;; Create the process stopped so that
>> + ;; we have time to store the key id,
>> + ;; etc. on it.
>> + :stop t)))
>
> Using make-process unconditionally seems to require emacs 25. I think
> we're still trying to support Emacs 24. That can always change, but I
> still haven't merged Tomi's patch officially deprecating emacs 23.
Would you accept something like:
(defcustom notmuch-crypto-get-keys-asynchronously (functionp 'make-process)
...)
?
dme.
--
I had my eyes closed in the dark.
next prev parent reply other threads:[~2019-01-19 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-01 16:06 [PATCH v3 0/4] Retrieve GPG keys asynchronously David Edmondson
2018-10-01 16:06 ` [PATCH v3 1/4] emacs: Asynchronous retrieval of GPG keys David Edmondson
2019-01-15 2:08 ` David Bremner
2019-01-19 11:15 ` David Edmondson [this message]
2019-01-19 12:47 ` David Bremner
2018-10-01 16:06 ` [PATCH v3 2/4] emacs: Minor refactoring of crypto code David Edmondson
2018-10-01 16:06 ` [PATCH v3 3/4] emacs: Add notmuch-crypto-gpg-program and use it David Edmondson
2018-10-01 16:06 ` [PATCH v3 4/4] emacs: Improve the reporting of key activity David Edmondson
2019-09-03 23:49 ` [PATCH v3 0/4] Retrieve GPG keys asynchronously David Bremner
2019-09-12 1:33 ` Daniel Kahn Gillmor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2tvi4q4ow.fsf@dme.org \
--to=dme@dme.org \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).