Re: Performance Problems

[David Cohen <dcohen@webmethods.com>]

Ok, now I'm in real trouble.  For one of my groups, I tried changing
the method (via 'G e') from "native" to
"nnimap+dcohen@webmethods.com:".  Now, when I try to read that group,
it fails with a message: "Trying to require a method that doesn't
exist".  The real problem is that I can't change the method back now.
When I try to change the sekect method back, I type 'G e', then edit
the value to "native" as it was before.  I type C-c C-c to save.  Then
if I type 'G e' again, I see that the value was not changed.  Where is
this select method stored, and what can I do to read this group again?

Also, Ive noticed something about the 'checking' versus 'updating'
messages.  I see 'checking' when I hit 'g' in the *Group* buffer.  I
see 'updating' when I hit space to actually visit a group.  Is this
right, or can I make performance better when visiting the group?

Thanks. 

-Dave


Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

> For me, things are slow when nnimap emits messages `updating info for
> mailbox foo' rather than `checking mailbox foo'.  I'm estimating a
> factor of five to ten in speed.
> 
> I was able to move from the `updating' messages to the `checking'
> messages by typing `G e' on each nnimap group and replacing the
> following:
> 
>     (nnimap "foo")
> 
> with:
> 
>     "nnimap+foo:"
> 
> (Here, (nnimap "") would be replaced with "nnimap:".)  Does this work
> for you?  (This presumes that there is an nnimap entry in
> gnus-secondary-select-methods.) 
> 
> kai
> -- 
> This gubblick contains many nonsklarkish English flutzpahs,
> but the overall pluggandisp can be glorked from context. -- David Moser