Re: Entering nnimap group got much slower with 5.10

[Lloyd Zusman <ljz@asfast.com>]

Simon Josefsson <jas@extundo.com> writes:

> Lloyd Zusman <ljz@asfast.com> writes:
>
>> OK.  So now I understand that my day-to-day gnus experience won't be any
>> different when using an agentized nnimap server, at least with regard to
>> the commands I need to issue for reading, posting, replying, etc.
>
> Yes.  If you discover anything else, please mention it.

Will do.


>> So in order to set this up, are these the only things I have to do?
>>
>> - make sure that the gnus-agent variable is set to t when 
>>   starting gnus
>
> Yup.  (It is the default.)

I had set that variable to nil ages ago because of some problems that
were occurring back then.  I don't recall what those problems were, but
at the time (probably more than a year ago), they kept me from starting
gnus.

But it's fixed now ... setting gnus-agent to t works just fine.


>> - do a 'J s' in the server buffer for each nnimap group that I
>>   wish to agentize
>
> `J a'.
>
> If you have never used the Agent before (~/News/agent/lib/servers
> doesn't exist) this should happen automatically.  I guess you at some
> point (before the agent revamp in Oort) tried the Agent, and it left a
> .../servers file around that is now inhibiting the auto-adding of
> nntp/nnimap groups.  This is probably why not more people are seeing
> the slowdown -- for them, the agent is enabled for nnimap groups out
> of the box.

Indeed.  I had a slew of things under ~/News/agent before retrying this.
However, once I did the `J a' (when said `J s' it was a typo),
everything speeded up in my nnimap groups.  Perhaps some of the ancient
stuff that had been created by the non-working agent code had inhibited
the proper working of the agent until I did the `J a' last night.


> It might be easier to simply rm -r ~/News/agent and restart Gnus.
> (This should be possible to do at any time, I believe Gnus regenerates
> all agent files if they are missing.)

I just did this.  It worked fine.  Thanks.

However, what got created was this:

  ~/News/agent/nnimap

Under it is a subdirectory for each of the nnimap servers that I'm
using, and in each of these subdirectories is a subdirectory for each of
the individual nnimap groups, plus one additional subdirectory called
`agent,lib'.  That is ...

  ~/News/agent/nnimap
  ~/News/agent/nnimap/email   ("email" is one of my nnimap server names)
  ~/News/agent/nnimap/email/INBOX.gnus
  ~/News/agent/nnimap/email/INBOX.ruby
  ~/News/agent/nnimap/email/INBOX.[whatever]
  ~/News/agent/nnimap/email/agent.lib
  
-- 
 Lloyd Zusman
 ljz@asfast.com