From: Guido Van Hoecke <Guido.VanHoecke@advalvas.be>
Cc: Gnus mailing list <ding@gnus.org>,
nnimap mailing list <gnus-imap@vic20.dzp.se>
Subject: Re: B m completion
Date: 29 Sep 1999 16:13:35 +0200 [thread overview]
Message-ID: <uln9p3iwg.fsf@advalvas.be> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "29 Sep 1999 12:13:30 +0200"
Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> Guido Van Hoecke <Guido.VanHoecke@advalvas.be> writes:
>
> > However, the drawback is that nnimap/gnus queries my imap server for
> > new mail in each of these folders. This is time consuming and
> > completely useless: I never have any mail delivered to any of these
> > folders.
>
> Sometimes, nnimap says `checking group foo' for all groups. This is
> really fast. At other times, it says `updating info for group foo'
> for all groups. This is really slow. If you see the latter, I think
> it would be best for you to make it so that nnimap says `checking'
> instead. I think you will observe an order of magnitude in speed
> increase, much more than could be achieved otherwise.
Yes, I have now observed this, and indeed the difference is an order
of magnitude. I used to call (gnus 5). Now I just call (gnus) and the
initial phase uses 'checking...' rather than 'updating...'. Boy this
is fast.
However, no matter what I do, the next time around, e.g. by keing 'g'
in the group buffer, or M-x gnus again, it always reverts to 'updating...'
>
> I'm not sure what needs to be done to make it so, but I think the
> problem is the select method. I have (manually!) set the select method
> of all my nnimap groups to "nnimap:" (no parentheses!), and this
> seemed to work well. Maybe you need "nnimap+foo:", though.
I have manually edited my select method, and set them to "nnimap:se"
for all my imap groups. But this does not make any difference.
>
> And I find that nnimap switches from `checking' to `updating info'
> when doing M-x gnus-no-server RET as well as when invoking M-x gnus
> RET with a specific level. Oh, well.
>
> But maybe this discussion should be in the nnimap list...
Even if somebody can help me with a mechanism to stick to the
'checking' method, I still would like to be able to define that some
groups never need a 'get-new-mail': such a group parameter would still
provide a faster method than the 'checking' approach.
Guido.
next prev parent reply other threads:[~1999-09-29 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 6:52 Guido Van Hoecke
1999-09-29 10:13 ` Kai Großjohann
1999-09-29 14:13 ` Guido Van Hoecke [this message]
1999-10-01 18:36 ` Kai Großjohann
1999-10-04 21:02 ` Guido Van Hoecke
1999-09-29 14:01 ` Guido Van Hoecke
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=uln9p3iwg.fsf@advalvas.be \
--to=guido.vanhoecke@advalvas.be \
--cc=ding@gnus.org \
--cc=gnus-imap@vic20.dzp.se \
/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).