From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: Laura Conrad <lconrad@laymusic.org>, 13010@debbugs.gnu.org
Subject: bug#13010: 24.2; Gnus hangs getting mail
Date: Mon, 31 Dec 2012 15:53:59 +0100 [thread overview]
Message-ID: <m31ue6qnlk.fsf@stories.gnus.org> (raw)
In-Reply-To: <jwvd2xtl92b.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sat, 29 Dec 2012 00:31:20 -0500")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> But we still only need one message per backend: basically every time
> a backend ends, state either which backend ended or which backends are
> still busy.
I don't really see that helping much. When opening the server, that may
take time, so we should say "Opening imap.gmail.com". Then we probably
open a different server. Then we issue commands to Gmail, which may
hang, so we should say "Retrieving group data from imap.gmail.com".
Then we issue similar commands to other servers. Then we wait for the
data from Gmail, which will most likely block, so we should say "Waiting
for data from imap.gmail.com".
Multiply that by six servers, and you get a constant flutter in the
minibuffer if none of these commands actually hand.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2012-12-31 14:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 13:26 bug#13010: 24.2; Gnus hangs getting mail Laura Conrad
2012-12-24 12:19 ` Lars Ingebrigtsen
2012-12-24 16:06 ` Stefan Monnier
2012-12-24 16:15 ` Lars Ingebrigtsen
2012-12-24 16:35 ` Stefan Monnier
2012-12-24 16:41 ` Lars Ingebrigtsen
2012-12-29 5:31 ` Stefan Monnier
2012-12-31 14:53 ` Lars Magne Ingebrigtsen [this message]
2013-01-03 16:52 ` Stefan Monnier
2014-01-30 23:44 ` Lars Ingebrigtsen
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m31ue6qnlk.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=13010@debbugs.gnu.org \
--cc=lconrad@laymusic.org \
--cc=monnier@IRO.UMontreal.CA \
/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://git.savannah.gnu.org/cgit/emacs.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).