From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: More fun with nnweb
Date: Sun, 19 Aug 2001 22:58:05 +0200 [thread overview]
Message-ID: <m33d6ndaxu.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <y68pucqybd5.fsf@x15-cruise-basselope.mit.edu>
"David Z. Maze" <dmaze@MIT.EDU> writes:
> Now, let's leave this summary buffer ('q') and try again. From the
> group buffer, I type 'G w debbugs dmaze@debian.org', and get 'No
> matching articles' back from nnweb. That's no good. Playing around,
> it seems like this is because each URL is stuffed into nnweb-hashtb,
> and this isn't cleaned out before 'G w' calls. (At least, that's what
> it seems like; if I don't play with nnweb-get-hashtb, it works fine.)
Hmm.... Sounds like a bug. :-)
> The other problem is if I try to create a persistent group (C-u G w
> ...). This works fine, but each time I check for new articles ('g')
> it returns duplicates of every article. (That is, the first time, I
> have 19 articles, the second, 19 new out of 38, the third, 19 out of
> 57, etc.)
Ah, yes, I've seen that before, but I thought I had fixed that. The
problem was that nnweb wasn't able to create a consistent mapping
between articles and Gnus article numbers. Do the debbugs provide
something that identifies the articles uniquely?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2001-08-19 20:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 17:50 David Z. Maze
2001-05-31 8:45 ` Andreas Fuchs
2001-05-31 9:45 ` Roland Mas
2001-05-31 10:00 ` Kai Großjohann
2001-05-31 10:39 ` Andreas Fuchs
2001-06-04 17:59 ` Toby Speight
2001-06-04 20:41 ` Kai Großjohann
2001-08-19 20:58 ` Lars Magne Ingebrigtsen [this message]
2001-08-20 13:47 ` David Z. Maze
2001-08-21 21:51 ` Lars Magne Ingebrigtsen
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=m33d6ndaxu.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
/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).