Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Do not want agantized, nnml backend.
Date: Tue, 27 Aug 2002 20:06:30 +0200	[thread overview]
Message-ID: <ilu1y8k6us9.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3bs7os0z4.fsf@newsguy.com> (Harry Putnam's message of "Tue, 27 Aug 2002 09:47:11 -0700")

Harry Putnam <reader@newsguy.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
> Read you answer to me [Putnam] so included your clarified comments:
>> I think "not" was correct (headears are not downloaded from servers,
>> they are retrieved from the agent cache), but it was rather muddy.
>> Another try:
>>
>>   The Gnus Agent is now enabled by default, and all nntp and nnimap
>>   servers from gnus-select-method and gnus-secondary-select-method are
>>   agentized by default (earlier only the server in gnus-select-method
>>   was agentized by the default, when the agent was enabled).  This
>>   means that, e.g., headers are retrieved from the Agent cache instead
>>   of the backends when possible.  You can enroll or remove servers
>>   with `J a' and `J r' in the server buffer.  Gnus will not download
>>   articles unless you instruct it to do so, though, by using `J u' or
>>   `J s' from the Group buffer.  Revert to the old behaviour with
>>   `(setq gnus-agent nil)'.  Note that putting (gnus-agentize) in
>>   ~/.gnus is not needed any more.
>
> So, it is the case that nothing gets downloaded by default, even in
> agentized groups?.  That seems wrong.

Hm.  By default, in agentized groups, headers are downloaded into the
agent cache once and then retrieved from the agent cache only.
Regardless of pluggedness.

> By `Revert to the old behavior' do we mean revert to downloading
> agentized groups by default? Or, not having agent enabled by default?

Not having agent enabled by default.

> Depending on above answers:
> I don't see the advantage of not using gnus-agentize, but using 
> (setq gnus-agent nil) to do what `gnus-agentize' used to do.
> Especially since the syntax, on first glance, looks as if it would
> shut the agent off.

The first glance is correct.  To get the old behaviour, no agent at
all, you disable the agent, and in Oort you do this by setting
gnus-agent to nil.  Calling `gnus-agentize' is a obsolete way of
enabling the agent, equal to setting gnus-agent non-nil.

> Seems like asking for confusion.... but maybe its just me.

Is it less confusing now?  Is the text consistent with this?  Could
you perhaps suggest improved text?

> If a group is set agentized, it seems the default one would expect is
> that downloading of headers would be controlled by the default
> predicate.  Further categories would take it from there by user
> specifying them as always.

Categories only affect articles.  Header downloads are not affected by
predicates.




  reply	other threads:[~2002-08-27 18:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-26  2:21 小関 吉則
2002-08-26 17:51 ` Simon Josefsson
2002-08-26 22:49   ` Dan Christensen
2002-08-27  2:28     ` Harry Putnam
2002-08-27 10:30       ` Simon Josefsson
2002-08-27 10:26     ` Simon Josefsson
2002-08-27 16:47       ` Harry Putnam
2002-08-27 18:06         ` Simon Josefsson [this message]
2002-08-28  3:43           ` Harry Putnam
2002-08-30  1:26       ` Jesper Harder
2002-09-01 14:24         ` Simon Josefsson
2002-08-27  0:58   ` 小関 吉則

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=ilu1y8k6us9.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --cc=ding@gnus.org \
    /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).