From: Hannu Koivisto <azure@iki.fi>
Subject: Gnus reads incoming mail many, many times with C-u ... g
Date: 30 Dec 2000 23:23:51 +0200 [thread overview]
Message-ID: <87lmsxr4bc.fsf@lynx.ionific.com> (raw)
Greetings,
I have several nnml groups at level 3 (nnml is the primary select
method, there are no secondary select methods) and one nnimap group
at level 4. If I hit 'g' in the group buffer, this is what I get
to the *Messages*:
-------------------------------------------------------------------
Reading active file from private-nnml via nnml...
nnml: Reading incoming mail from directory...
nnml: Reading incoming mail (no new mail)...done
Reading active file from private-nnml via nnml...
Reading active file from private-nnml via nnml...done
Checking new news...
nnimap: Updating info for nnimap+xxx.xxx.xxx:yyy...
[4 times]
nnimap: Updating info for nnimap+xxx.xxx.xxx:yyy...done
[7 times]
Checking new news...done
-------------------------------------------------------------------
Now, let's say that I want to re-scan just nnml groups and ignore
the nnimap group, so I say 'M-3 g'. I'd expect to get about the
same messages except not those nnimap ones (I also wonder a bit why
it says it updates info for one nnimap group four times and
finishes updating info seven times), but instead I get:
-------------------------------------------------------------------
Checking new news...
nnml: Reading incoming mail from directory...
nnml: Reading incoming mail (no new mail)...done
[the two lines above repeated 67 times]
Checking new news...done
-------------------------------------------------------------------
Gnus probably works correctly and I'm not saying this is a bug, but
this all feels, uh, weird, and I'd just like to know what's going
on.
[Emacs 20.7 on Linux and Oort Gnus from CVS as of few minutes ago
but seen also with earlier Gnus versions.]
--
Hannu
reply other threads:[~2000-12-30 21:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87lmsxr4bc.fsf@lynx.ionific.com \
--to=azure@iki.fi \
/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).