Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: automatic Agentizing of servers (was: Summary buffer
Date: Mon, 29 Dec 2003 17:10:20 -0600	[thread overview]
Message-ID: <u3cb3gqzn.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <ilu7k0fcjqt.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> writes:

> Steinar Bang <sb@dod.no> writes:
>
>>>>>>> Simon Josefsson <jas@extundo.com>:
>>
>>> Uhm, but what would you expect to happen?  The knowledge about which
>>> servers are agentized and which are not is stored in
>>> ~/News/agent/lib/servers, so if you remove that file, Gnus will
>>> auto-agentize your servers.
>>
>> Ah, OK.  Right now it only contains the text nil, and no servers were
>> agentized when I started Gnus.
>>
>> Can I delete everything in the ~/News/agent/ directory, except this
>> file? 
>
> Yes.  You can delete that file too, of course, but then some servers
> will be auto-agentized when you restart.
>
>>> The point of the patch is that auto-agentification only happens once
>>> (unless you modify ~/News/agent/ manually).  I think if a user
>>> remove ~/News/agent she wishes to start afresh, and
>>> auto-agentification is useful in that case.
>>
>>> What do you think?  Can you suggest/describe a better logic that
>>> does what you want?
>>
>> Well, for me auto-agentizing is unexpected behaviour, and I wouldn't
>> wish it ever to occur.

That's probably because the agent was originally intended for offline
use.  Auto-agentizing was added to support client-side caching of
articles (an online performance option).  Personally, I also find it a
little strange but it is a better solution than having the agent, the
cache, AND a client-side cache storing articles on your local hard
drive.

>> I want to agentize servers when I say J a in the *Server* buffer,
>> and only then.
>
> Then don't delete ~/News/agent/lib/servers and remove the
> auto-agentized servers. :-)
>
> I guess this could be customizable.  Cvs update again and customize
> `gnus-agent-auto-agentize-methods' to an empty list.  Then you can
> wipe out ~/News/agent/ and nothing will be auto-agentized.  I have
> added this to the manual:
>
> `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.  It is also incorrect as, as I mentioned earlier, the
agent has more uses than agentizing remote backends.

Kevin




  reply	other threads:[~2003-12-29 23:10 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 15:14 Summary buffer highlighting Emerick Rogul
2003-11-24 16:17 ` automatic Agentizing of servers (was: Summary buffer highlighting) Ted Zlatanov
2003-11-24 16:42   ` automatic Agentizing of servers (was: Summary buffer Emerick Rogul
2003-11-24 16:47   ` Kevin Greiner
2003-11-24 17:05     ` Emerick Rogul
2003-11-24 17:07     ` Ted Zlatanov
2003-11-25  2:48       ` Kevin Greiner
2003-11-25  8:25         ` Simon Josefsson
2003-11-25 18:31           ` Ted Zlatanov
2003-12-29 21:22           ` Steinar Bang
2003-12-29 21:39             ` Simon Josefsson
2003-12-29 21:58               ` Steinar Bang
2003-12-29 22:23                 ` Steinar Bang
2003-12-29 22:27                   ` Steinar Bang
2003-12-29 22:36                     ` Steinar Bang
2003-12-29 22:33                 ` Simon Josefsson
2003-12-29 22:44                   ` Steinar Bang
2003-12-29 23:00                     ` Simon Josefsson
2003-12-29 23:10                       ` Kevin Greiner [this message]
2003-12-29 23:17                         ` Simon Josefsson
2003-12-29 23:37                           ` Kevin Greiner
2003-12-29 23:53                             ` Simon Josefsson
2003-12-30  2:19                               ` Harry Putnam
2003-12-30  9:44                                 ` Steinar Bang
2003-12-30 11:16                                 ` Simon Josefsson
2003-12-30 20:55                                   ` Steinar Bang
2003-12-30 21:30                                     ` Simon Josefsson
2003-12-30 22:49                                       ` Harry Putnam
2003-12-31 12:55                                       ` Steinar Bang
2003-12-30  9:40                       ` Steinar Bang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=u3cb3gqzn.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).