Re: automatic Agentizing of servers (was: Summary buffer

[Kevin Greiner <kgreiner@xpediantsolutions.com>]

Simon Josefsson <jas@extundo.com> writes:

> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>>> `gnus-agent-auto-agentize-methods'
>>>      If you have never used the Agent before (or more technically, if
>>>      `~/News/agent/lib/servers' does not exist), Gnus will
>>>      automatically agentize a few servers for you.  This variable
>>>      control which backends should be auto-agentized.  It is typically
>>>      only useful to agentize remote backends.  The auto-agentizing has
>>>      the same effect as running `J a' on the servers (see *note Server
>>>      Agent Commands::).  If the file exist, you must manage the servers
>>>      manually by adding or removing them, this variable is only
>>>      applicable the first time you start Gnus.  The default is `(nntp
>>>      nnimap)'.
>>
>> That's inappropriate as gnus-agent-auto-agentize-methods isn't
>> customizable.
>
> Try 'cvs up'.
>
>> It is also incorrect as, as I mentioned earlier, the agent has more
>> uses than agentizing remote backends.
>
> When do you want to agentize a non-remote backend like nnml or
> nnfolder?  In any case, it does say 'typically', so weird situations
> like nnml over slow remote NFS is conceivable.  Can you suggest (or
> better, commit) improved wording?

My apologies for mispeaking.  I don't like stepping on capabilities
that other people introduced and, as this thread progressed, that is
what seemed to be happening here.  I just checked backwards in the log
only to find that you introduced the gnus-agent-auto-agentize-methods
variable.  That makes you the expert on how it should be used, or in
this case initialized.

Kevin