From: David Edmondson <dme@dme.org>
To: "Antoine Beaupré" <anarcat@orangeseeds.org>, notmuch@notmuchmail.org
Subject: Re: feature request: fetch missing keys in the background
Date: Fri, 07 Sep 2018 12:31:26 +0100 [thread overview]
Message-ID: <cun8t4do86p.fsf@constant-mown.hh.sledj.net> (raw)
In-Reply-To: <87bm9duzbj.fsf@curie.anarc.at>
On Tuesday, 2018-09-04 at 10:12:00 -04, Antoine Beaupré wrote:
> So I tried that and it works, if I really don't touch anything. It's
> certainly an improvement over the previous behavior. Once the "message"
> is gone (ie. as soon as anything else is done in Emacs), it's a little
> hard to figure out what is happening without going through the status
> buffer.
>
> Maybe that's fine, but it would be nice if the button would immediately
> update with that status. For example, the text could change to
> "... updating" or something. Of course, we're back to the same place
> that it can't be updated without shuffling the buffer around if the
> point moved, but at least the UI would "remember" there was some change
> in the status (it's not just "Failure" but "We're working on it").
v2 of the patch does this.
dme.
--
When I grow up I'll be stable.
prev parent reply other threads:[~2018-09-07 11:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 15:49 feature request: fetch missing keys in the background Antoine Beaupré
2018-09-03 16:46 ` 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 [this message]
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=cun8t4do86p.fsf@constant-mown.hh.sledj.net \
--to=dme@dme.org \
--cc=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).