Re: automatic Agentizing of servers (was: Summary buffer

[Simon Josefsson <jas@extundo.com>]

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?