Bug when renaming groups in 5.8.8 --- cache not renamed.

Bug when renaming groups in 5.8.8 --- cache not renamed.

[Scott A Crosby]

I've found two bugs in NNML group renaming, one is minor. If you
rename a group, the contents of nnmail-messageid-cache are not
renamed. Thus any followups will go to the old group name not the new
one.

I've also found a more serious bug. 

Take a group with 100 messages in it. When you rename the group, it
doesn't rename the cache file associated with it. So, say that you (by
mistakee) marked a message as 'cache'. Then you rename the group. The
cache file indicates that message (say) 521 is in the
cache. Unfortunately, the real messages are starting to be inserted at
number 1. When gnus reads the cache file, it gets confused and marks
messages 1-521 as read. But messages are being inserted with ID's
starting at one. Thus the next 500 messages will be marked as read,
read or not.

It took me about two hours to finally identify this bug and get my
main inbox folder working again.

Scott

Re: Bug when renaming groups in 5.8.8 --- cache not renamed.

[Lars Magne Ingebrigtsen]

Scott A Crosby <scrosby@cs.rice.edu> writes:

> When you rename the group, it doesn't rename the cache file
> associated with it.

Yes, that's a bug.  The cache code doesn't have any renaming logic.

On the other hand, why would you put articles into the cache from
backends that you have control over?  I mean, if it's nnml, then you
have two copies of the messages...

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Bug when renaming groups in 5.8.8 --- cache not renamed.

[Frank Schmitt]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Scott A Crosby <scrosby@cs.rice.edu> writes:
>
>> When you rename the group, it doesn't rename the cache file
>> associated with it.
>
> Yes, that's a bug.  The cache code doesn't have any renaming logic.
>
> On the other hand, why would you put articles into the cache from
> backends that you have control over?  I mean, if it's nnml, then you
> have two copies of the messages...

nnimap? (Can one rename IMAP groups?)

-- 
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.

Re: Bug when renaming groups in 5.8.8 --- cache not renamed.

[Lars Magne Ingebrigtsen]

Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:

> nnimap? (Can one rename IMAP groups?)

Hm, yes...  and caching would probably make sense for those groups.

So -- should group renaming be propagated to the cache (and the
Agent)?  (Or does the Agent already have code for doing this?  I
haven't peeked...)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Bug when renaming groups in 5.8.8 --- cache not renamed.

[Scott A Crosby]

On Fri, 17 Oct 2003 19:35:56 +0200, Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Scott A Crosby <scrosby@cs.rice.edu> writes:
> 
> > When you rename the group, it doesn't rename the cache file
> > associated with it.
> 
> Yes, that's a bug.  The cache code doesn't have any renaming logic.
> 
> On the other hand, why would you put articles into the cache from
> backends that you have control over?  I mean, if it's nnml, then you
> have two copies of the messages...

I do this in groups marked auto-expire as a way to flag messages I
don't want to disappear, but without marking them '?' or '!'. After a
month or so, the origional copy expires and the cache is the only one
left.

Scott