Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Cc: ding@gnus.org
Subject: Re: [patch] gnus agent
Date: 03 Jul 2000 10:43:28 +0200	[thread overview]
Message-ID: <ilubt0f4n9r.fsf@localhost.localdomain> (raw)
In-Reply-To: John Prevost's message of "01 Jul 2000 23:49:10 -0400"

Harry Putnam <reader@newsguy.com> writes:

> I'd like to try this out but I'm not real clear what to expect.
> What does this mean in practice?  (`filtered only by predicates') No
> agent score involved?  Still requires marking with % if read?

The patch does two things:

. Make sure all articles are eligible for agent download, see below.

. Introduce a new predicate `read' to match read mail.  Replacing your
current Agent predicates with

        (and (not read)
                <yourearlierpredicate>)

should make things the same as it was before.  The default predicate
has been changed, so if you didn't define any categories, there should
be no change at all (except for new features).

I'm not sure this should be commited to Gnus 5.8 since it alter the
current behaviour, even though it make it consistent with
documentation.  The current `bug' is probably more of a `feature', I
think.

The documentation for categories below, note the "...every available
articles...".  Earlier this just wasn't true, only UNREAD articles
(having article numbers larger than the highest already downloaded
article) was eligible for agent scoring/predicate rules.

Category Syntax
...............

   A category consists of two things.

  1. A predicate which (generally) gives a rough outline of which
     articles are eligible for downloading; and

  2. a score rule which (generally) gives you a finer granularity when
     deciding what articles to download.  (Note that this "download
     score" is not necessarily related to normal scores.)

   A predicate in its simplest form can be a single predicate such as
`true' or `false'.  These two will download every available article or
nothing respectively.  In the case of these two special predicates an
additional score rule is superfluous.




  parent reply	other threads:[~2000-07-03  8:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-01 18:24 Simon Josefsson
2000-07-01 19:25 ` Harry Putnam
2000-07-02  3:49   ` John Prevost
2000-07-03  8:43   ` Simon Josefsson [this message]
2000-08-08 19:06 ` Christoph Rohland
2000-08-10 11:03 ` Christoph Rohland
2000-08-10 12:44   ` simon
2000-08-10 13:17     ` Christoph Rohland
2000-08-14 18:45 ` Lars Magne Ingebrigtsen
2000-08-14 19:48   ` simon

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=ilubt0f4n9r.fsf@localhost.localdomain \
    --to=simon@josefsson.org \
    --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).