Gnus development mailing list
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: ding@gnus.org
Subject: Re: Agent again
Date: Mon, 20 Dec 2010 18:06:26 +0100	[thread overview]
Message-ID: <pknlj3k1ii5.fsf@this.is.really.invalid> (raw)
In-Reply-To: <9jhbe8h0t6.fsf@news.eternal-september.org>

Richard Riley <rileyrg@googlemail.com> writes:

> J s and "g" when plugged dont do the same thing for me. "J s" does
> something, but "plugged" groups dont get a new article count. "g" does
> get the new article count. What does, in the docs,
>
> "Fetch all articles and headers that are eligible for fetching."
>
> mean? I assumed all articles which pass the category predicate.
>
> I have a category "fun" with a predicate of "true". I am assuming this
> means fetch all articles. The groups in question are added to this
> category. Is that correct?
>

Yes

> Or another way of asking, what are the conditions that mean J s and g
> DONT do the same thing when plugged?

As I understand it:

g => query servers for info about any new articles that have
arrived. For 'mail-like' backends this may end up retrieving mail, for
nntp/nnimap it just updates article counts.

J s => download articles based on currently available headers according
to configured category predicates.

Informally: g means 'do I have anything new to read', and J s is 'download
stuff'.

Robert




  reply	other threads:[~2010-12-20 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-20 16:21 Richard Riley
2010-12-20 17:06 ` Robert Pluim [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-09-21  3:22 agent again Matt Simmons
1997-09-21  5:16 ` Lars Magne Ingebrigtsen
1997-09-21  5:28 ` Matt Simmons
1997-09-21 16:29   ` Lars Magne Ingebrigtsen

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=pknlj3k1ii5.fsf@this.is.really.invalid \
    --to=rpluim@gmail.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).