unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Cc: Pierre Neidhardt <mail@ambrevar.xyz>
Subject: Re: wish: notmuch-emacs: notmuch-poll-and-refresh-this-buffer should use progress-reporter
Date: Fri, 29 May 2020 14:57:52 +0200	[thread overview]
Message-ID: <b71ac147ec08d6bf3c3bddef21c00fe3@condition-alpha.com> (raw)
In-Reply-To: <87v9kf1xjv.fsf@tethera.net>

Hello David,

Many thanks for your swift response. 

David Bremner <david@tethera.net> writes:

> Alexander Adolf <alexander.adolf@condition-alpha.com> writes:
> 
>> [...]
>> To give the user a visual clue that something is happening in the
>> background, and Emacs has not crashed, it would be great if a progress
>> indicator could be shown. See e.g. the Elisp manual `(info "(elisp)
>> Progress")', or [1].
>
> I don't use this functionality, but Pierre mentioned making the fetch
> asynchronous, and provided a patch to try out in
>
>       id:875zehszdp.fsf@ambrevar.xyz
>
> Maybe working on that would be a better use of effort?
> [...]

I'm not subscribed to the list, so can't comment on the patch.

In any case - synchronous or asynchronous - a visual indication of the
process would seem desirable. At least to know that something is going
on, and when it's finished.

Just my two cents anyway.


Many thanks and cheers,

  --alexander

  reply	other threads:[~2020-05-29 14:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-28 16:01 wish: notmuch-emacs: notmuch-poll-and-refresh-this-buffer should use progress-reporter Alexander Adolf
2020-05-28 22:53 ` David Bremner
2020-05-29 12:57   ` Alexander Adolf [this message]
2020-05-29 16:31     ` Pierre Neidhardt

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=b71ac147ec08d6bf3c3bddef21c00fe3@condition-alpha.com \
    --to=alexander.adolf@condition-alpha.com \
    --cc=david@tethera.net \
    --cc=mail@ambrevar.xyz \
    --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).