From: "Antoine Beaupré" <anarcat@orangeseeds.org>
To: notmuch@notmuchmail.org
Subject: feature request: fetch missing keys in the background
Date: Mon, 03 Sep 2018 11:49:09 -0400 [thread overview]
Message-ID: <871saawphm.fsf@curie.anarc.at> (raw)
Hi!
Because I have a rather large keyring, fetching new keys or refreshing
old ones takes a long time. When I click on the red red button saying
"Unknown key ID [...] or unsupported algorithm", Emacs freezes for a
good 90 seconds. Considering I use that editor^Wvirtual machine for
nearly everything, it's quite annoying and sends me off browsing the web
in Firefox forever. I end up having a horde of shaven yaks and then
finally remember that I had that key update, by which time I had
forgotten what I was doing reading email in the first place, let alone
what I was doing *before* opening my inbox...
So. It would be great if Notmuch would run those key updates
asynchronously. I am not sure how that would work: as Bremner said on
IRC, it might make it difficult to update the button automatically. But
I don't mind that: I can refresh the page myself. He suggested running
things in the background when clicking with a prefix (C-u?) but I would
argue that freezing Emacs is just a no-no in general.
I couldn't find directly what function was called behind that button:
"C-h k" just says it's, obviously, `push-button'. Bremner says it might
be `notmuch-crypto-sigstatus-good-callback' which looks reasonable. I'm
only a junior elisp programmer, but it seems to me the
`notmuch-show-refresh-view' call there could be an asynchronous callback
to an async `make-process' call, as opposed to `call-process', which is
synchronous.
But I'd like others to chime in here: is this something that would be
accepted? Would the above work?
A.
--
If quantum mechanics hasn't profoundly shocked you, you haven't
understood it yet.
- Niels Bohr
next reply other threads:[~2018-09-03 15:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 15:49 Antoine Beaupré [this message]
2018-09-03 16:46 ` feature request: fetch missing keys in the background David Edmondson
2018-09-03 16:50 ` David Edmondson
2018-09-03 17:10 ` Antoine Beaupré
2018-09-03 17:21 ` David Edmondson
2018-09-03 17:23 ` David Edmondson
2018-09-03 17:47 ` PATCH: " Antoine Beaupré
2018-09-03 18:19 ` David Edmondson
2018-09-03 19:49 ` feature request: " Antoine Beaupré
2018-09-04 13:32 ` David Edmondson
2018-09-04 13:34 ` Antoine Beaupré
2018-09-04 13:39 ` David Edmondson
2018-09-04 14:12 ` Antoine Beaupré
2018-09-04 14:39 ` David Bremner
2018-09-07 11:31 ` David Edmondson
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=871saawphm.fsf@curie.anarc.at \
--to=anarcat@orangeseeds.org \
--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).