From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Gnus v5.2.8 is released
Date: 06 Jun 1996 14:37:07 +0200 [thread overview]
Message-ID: <x6loi1kt1o.fsf@eyesore.no> (raw)
In-Reply-To: Sudish Joseph's message of 05 Jun 1996 21:48:21 -0400
Sudish Joseph <sudish@ix.netcom.com> writes:
> On the subject of mail speedups, it'd be nice if nnmail-get-new-mail
> didn't loop over all the specified spools for every single group.
> This doesn't seem like a speed hit when all you're paying is a stat on
> an guaranteed-to-be-empty spool file for all groups after the
> first...but it's -huge- when one of those spools is a pop server
> accessed over a PPP link. I'd even consider this a bug. :-)
nnmail tries to avoid querying POP servers by maintaining a
`nnmail-moved-inboxes' list that it checks. Perhaps this doesn't work
as it's supposed to? I'm not sure -- I don't have access to a POP
server. Could somebody have a closer look at `nnmail-move-inbox' in
"nnmail.el" and see whether things work or not?
(The `nnmail-moved-inboxes' variable is cleared in `post-command-hook'
in the group buffer, so `g' `g' will read the spools twice.)
> It'd also make it easier to make GNUS extensible in the sense of being
> able to
> 1) add nnfoo.elc to your load-path
> 2) set a few variables that completely specify it's behaviour
> 3) call a GNUS-provided function to register itself with GNUS.
> and have it work just as well as any native backend.
I've added this last item to the Red Gnus todo list.
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-06-06 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-05 17:34 Lars Magne Ingebrigtsen
1996-06-06 1:48 ` Sudish Joseph
1996-06-06 12:37 ` Lars Magne Ingebrigtsen [this message]
1996-06-06 21:04 ` Colin Rafferty
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=x6loi1kt1o.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).