Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Anonymous <noreply@breaka.net>
To: info-gnus-english@gnu.org
Subject: Re: Re: simple "advanced" score file is apparently ignored (and Gnus
Date: Tue, 09 Oct 2012 03:15:02 -0600	[thread overview]
Message-ID: <5fa8df10f2a597e3257a524fa12c2279@breaka.net> (raw)
In-Reply-To: <mailman.9989.1348950156.855.info-gnus-english@gnu.org>

>The structure of my ~/News/all.SCORE looks like this:

Thanks.

>You can cause the global score file to be reloaded by using W f in the
>*Group* buffer.

Very useful.  I've been restarting repeatedly as I build the score
file.. this will save me some time.

>(I've never tried anything in the Advanced category.)

My end game is to mirror the slrn score file, which is quite powerful.
This forced me down the path of the advanced format in Gnus.  It was
quite confusing at first because there's a temptation to combine
constructs and features from the advanced rules and the simple rules,
which turns out to be impossible.  It turns out the scores cannot be
influenced in each match criteria and also the whole rule -- it's one
or the other.  E.g., this does *not* work:

  ((& 
    ("xref"    "some-group" 50 nil s)
    ("subject" "some-topic" 20 nil s))
   200)

The other major stumbling block to understanding the scoring is that
the simple rule format has an extra set of a paranthesis to group the
match type with the match string.  E.g., this:

    ("subject" ("some-topic" 20 nil s))
 vs.
    ("subject" "some-topic" s)

It took me hours to discover that inconsistency (amid other
differences between the two formats).  Was painful.

In the end, the Gnus score file is certainly less readable than slrn
with a very unforgiving parser, but it seems to have the same
capability.

So I finally got something working.  If anyone wants to see a complete
example of an advanced score file, I have pasted one below because the
manual does not have one, and web searches come up dry on this.

In this example, the first rule gives a high score to articles
appearing in newsgroups with "android" or "mobile" in the name, and
with a subject matter being multi-sim phones, or a Galaxy S Duo in
particular.

The second rule is designed to give a high score to airports of
interest in the
nntp+news.gmane.org:gwene.com.flyertalk.mileage-run.deals newsgroup.

(
 ((& 
   (|
    ("xref" "droid"  S)
    ("xref" "mobile" s))
   (|
    (&
     ("subject" "sim")
     (|
      ("subject" "dual")
      ("subject" "triple")
      ("subject" "quad")
     )
    )
    ("subject" "galaxy.s.duo" r)
  )
  1000)

 ((& 
   (|
    ("xref" "flyer.*mileage" r)
    ("xref" "travel"         s))
   (|
    ("subject" "\\<ams\\>" r)
    ("subject" "\\<lax\\>" r)
    ("subject" "\\<lgw\\>" r)
    ("subject" "\\<lhr\\>" r)
    ("subject" "\\<ord\\>" r)
    ("subject" "\\<sjc\\>" r)
  )
  1000)
)

      parent reply	other threads:[~2012-10-09  9:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-29 17:33 Fritz Wuehler
2012-09-29 20:22 ` Adam Sjøgren
     [not found] ` <mailman.9989.1348950156.855.info-gnus-english@gnu.org>
2012-10-09  9:15   ` Anonymous [this message]

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=5fa8df10f2a597e3257a524fa12c2279@breaka.net \
    --to=noreply@breaka.net \
    --cc=info-gnus-english@gnu.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).