Discussion: To del cached articles upon zapping group info?

[Wesley.Hardaker@sphys.unil.ch]

Lars and I have been going back and forth about the following situation:

   When I zapped my group attributes (ie, numbers associated with read
   articles) gnus didn't clear my cache, which affected what it
   thought was the current article range later on.  For instance, I
   had an article cached in comp.protocols.snmp with a article number
   of 832 or something like that, but the articles in the newsgroup
   were now 1-315 or so (due to the new news server).  Gnus keyt
   saying there were no new articles because it had marked 1-832 as
   read after the first time I read the group...

We are trying to decide what it should do about the cached
articles...  In the above situation, its horrible (no new news till
after 832 appears).

I said it should delete the cached articles, simply because they are
no longer valid and will conflict with new numbered articles.  There
is simply no place in the 1-* range for them as they have been taken
up by new numbers.

I suppose you could re-order them to something like -3 -> -1 or
something similar, but I don't know how gnus would handle that (this
is a new idea Lars).

So, in the end, Lars needs other suggestions?

Ideas?

Wes