Re: Discussion: To del cached articles upon zapping group info?

[Paul Franklin <paul@cs.washington.edu>]

 > Per Abrahamsen <abraham@dina.kvl.dk> writes:

 >> Maybe an explicit command to move cached articles somewhere else, and
 >> a warning in any action that would render cached articles invalid.

>>>>> Wesley Hardaker writes:

 > I think gnus *has* to do at least a move to get them out of the way so
 > it doesn't screw up in the first place, and it should at the very
 > least warn the user as well.  Preferably, with a prompt as a simple
 > message can disappear without the user actually ever seeing it whereas
 > a prompt will sit around till the specifically acknowledge it...

Hmm.  How about this:

* Gnus asks you for permission to move them out of the way when it
  detects this problem.
* It records the directory they were moved to in the group parameters,
  along with a group count.
* There's a command to explicitly visit the old cached articles, based
  on the record in the group parameters.
* It waits until enough articles have expired on the server that
  these articles and others cached can be safely renumbered and placed
  all back in the individual group.

(These functions might also help with server migration, which has been
discussed but seems to be another one of those things that happens
occasionally enough that it isn't worth much effort.)

--Paul