From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: ahh... it's the problem noted a few months back
Date: 03 Nov 1999 22:36:30 +0100 [thread overview]
Message-ID: <vafg0ynl0kh.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: dsg@mitre.org's message of "03 Nov 1999 12:35:17 -0500"
David S. Goldberg <dsg@mitre.org> writes:
> I don't do server side splitting in nnimap (I use nnimap-split-rules)
> but I do notice that even for nnimap, all groups subscribed at a
> particular level get checked (e.g. I see the "updating info for ..."
> message, even for groups that never get mails split to them).
That's bad. If you can make it show `checking mailbox foo', then this
will be about an order of magnitude faster than `updating info for
foo'. Really! (Well, maybe it's only a factor of five.)
I used to have `updating info for...' as well, but I managed to make
it show `checking mailbox ...' by fiddling with the select method.
And with the level, I think.
M-x gnus RET would show `checking', whereas M-x gnus-no-server RET and
C-u 4 2 M-x gnus RET would show `updating'. I think.
Simon knows more, for sure.
kai
--
This gubblick contains many nonsklarkish English flutzpahs,
but the overall pluggandisp can be glorked from context. -- David Moser
next prev parent reply other threads:[~1999-11-03 21:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-02 16:23 Randal L. Schwartz
1999-11-02 17:06 ` David S. Goldberg
1999-11-03 8:19 ` Steinar Bang
1999-11-03 8:27 ` Kai Großjohann
1999-11-03 17:35 ` David S. Goldberg
1999-11-03 21:36 ` Kai Großjohann [this message]
1999-11-04 8:28 ` Tibor Simko
1999-11-04 14:06 ` David S. Goldberg
1999-11-04 16:14 ` Simon Josefsson
1999-11-07 0:46 ` Lars Magne Ingebrigtsen
1999-11-07 15:05 ` Simon Josefsson
1999-11-11 3:28 ` Lars Magne Ingebrigtsen
1999-11-12 17:05 ` Simon Josefsson
1999-11-13 18:03 ` Lars Magne Ingebrigtsen
1999-11-13 21:39 ` Simon Josefsson
1999-11-14 4:54 ` Randal L. Schwartz
1999-11-15 13:32 ` Tibor Simko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vafg0ynl0kh.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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.
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 NNTP newsgroup(s).