Re: bug in gnus-fixup-nnimap-unread-after-getting-new-news?

[Ted Zlatanov <tzz@lifelogs.com>]

On Sun, 25 May 2003, tzz@lifelogs.com wrote:
> On Sat, 24 May 2003, jas@extundo.com wrote:
>> Looking closer at the problem, I see that at least my
>> nnimap-mailbox-info contains fully qualified group names.  So I
>> don't see how it would fail, it iterates over all fully qualified
>> names and update the info for each of those groups.  Perhaps you
>> could edebug the function to see where and why it overwrites
>> non-nnimap group info?  What's your value of nnimap-mailbox-info?
> 
> I read my mail on two machines, one of them has nnimap-mailbox-info
> as
> 
> (machine A)
> 
> [0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
> nnimap+mail\.lifelogs\.com:ding\.archive ....]
> 
> and the other as 
> 
> (machine B)
> 
> [0 0 ding\.archive lifelogs 0 0 0 0 0 0 0 0 0 ....]
> 
> On both machines nnimap is secondary:
> 
> (A) gnus-secondary-select-methods's value is 
> ((nnimap "mail.lifelogs.com"))
> 
> (B) gnus-secondary-select-methods's value is 
> ((nnimap "mail.lifelogs.com"))
> 
> So machine A is somehow misbehaving.  I'll look at the problem when
> I get to work, where A is.  A and B are *very* similar in
> configuration, though.

I thought the problem might have been with Emacs versions, but alas...

- A and B have Emacs 21.3

- CVS Gnus, updated at the same time

- exact same startup files, Gnus options, and Emacs libraries with
  small unrelated variations in .gnus.el based on the host name

- A is Solaris, B is Linux

Let me know where to look next to find where the short group names are
getting generated...

Thanks
Ted