Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: [nnir] Suspected bug in group spec
Date: 20 Aug 2000 07:23:39 -0700	[thread overview]
Message-ID: <m21yzkypsk.fsf@ognus-5.8.8-cvs.now.playing> (raw)

The most recent nnir.el (nnir-1.58) on Kai's ftp server seems to have
buggy code in the part that allows user to specify a target group.

But first, I hope this is not some malfeasance on this end.  I've
tried to carefully make sure I've loaded a non-bytecompiled
nnir-1.58.el by evaluationg this line (with C-x C-e) in scratch buffer. 

(load "nnir-1.58.el")  Then comparing the results after doing the same
to:

(load "nnir-1.57.el")

Is there some better way to know for sure what version of nnir is
currently loaded and in use?

I first noticed the problem I'm about to report when (using glimpse as
search engine) I ran this query:

   C-u G G
   Query: reader@newsguy\.com <RET> zoot <RET>
(zoot is an nnml group containing the mailing list of a redhat linux 
distribution)

   ls ~/Mail/zoot/[0-9]* |wc -l
   702
Not particularly large..

The query seemed to be dragging on much longer than I expected, so
began to watch the time it had been running.  When it passed 6 minutes
I knew something was wrong, but thought it might be the escaped "."

Just as I was about to abort, gnus came through with the goods and
asked how many of the 12,600+ messages I wanted to view.

Huh?  where did all those come  from in a group of 700+

I told gnus to load them all, which took another couple minutes.
Finally I say what had happened is that the group spec had not been
honored.

There were messages from dozens of groups.
Tried the routine a few more times but the group spec is not honored.



                 reply	other threads:[~2000-08-20 14: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=m21yzkypsk.fsf@ognus-5.8.8-cvs.now.playing \
    --to=reader@newsguy.com \
    /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).