Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: scoring
Date: 02 Dec 1999 12:41:06 +1100	[thread overview]
Message-ID: <t4iwvqyazm5.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Wed, 01 Dec 1999 21:56:42 +0100"

>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

    Lars> Brian May <bmay@csse.monash.edu.au> writes:
    >> ("xref" ("[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+ +[^:\n]+:[0-9]+" -1000 nil r))
    >> 
    >> However, this doesn't work, instead I have to use:
    >> 
    >> ("xref" ("[^:]+:[0-9]+ +[^:]+:[0-9]+ +[^:]+:[0-9]+" -1000 nil r))
    >> 
    >> Which really puzzles me, as PGnus doesn't display any newlines
    >> within the Xref line. Is that notation a legal R.E.? Or perhaps
    >> PGnus removes newlines within the Xref line before displaying it?

    Lars> The newline bits are in there to avoid having the score code
    Lars> go to multi-line matching, which it will do, giving spurious
    Lars> results and stuff.

I know - however it doesn't work...

    >> (My guess is that the example is wrong, and PGnus interprets "\"
    >> and "n" as two distinct characters, within [ and ] --- am I correct?

    Lars> No, Gnus reads the score files with `read', which will do the right
    Lars> thing. 

    Lars> So I don't understand this.  The [^:\n]+ should work while the [^:]+
    Lars> should match articles where there aren't that many Xref headers.

It wasn't working.

In fact, I never have got any control characters to work within [ .. ] 
yet (except for ^). As this example is documented, I felt it should
work (and isn't just me doing something wrong).

My rule does do the right think, but perhaps that is coincidence in
that Xref usually is the last header.

    >> Another thing, while scoring based on the "Message-Id" works, scoring
    >> based on "thread" doesn't work (nothing matches). This has me rather
    >> puzzled, because I thought matching on thread is the same thing as
    >> matching on the "Message-Id", but with followups included, too.

    Lars> Scoring on threads create lots of ADAPT files that it later uses when
    Lars> scoring.  It seems to work for me...

I managed to get it to create the adapt file, with the correct
reference entries, etc. However, none of the articles were
being highlighted. I don't understand why.

Even more weird, it that scoring of "followups" works fine.
I believe the two are very similar.

PGnus 0.98
-- 
Brian May <bmay@csse.monash.edu.au>


  reply	other threads:[~1999-12-02  1:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-25  0:03 scoring Brian May
1999-12-01 20:56 ` scoring Lars Magne Ingebrigtsen
1999-12-02  1:41   ` Brian May [this message]
1999-12-05 21:53     ` scoring Kai Großjohann
1999-12-06  2:58       ` scoring Brian May
1999-12-06  4:11         ` scoring Lars Magne Ingebrigtsen
1999-12-06 12:53           ` scoring Jan Vroonhof
1999-12-06 13:09             ` scoring Per Abrahamsen
1999-12-06 13:21               ` scoring Hrvoje Niksic
1999-12-06 13:02           ` scoring Kai Großjohann
1999-12-06 23:29             ` scoring Brian May
1999-12-07 12:56               ` scoring Per Abrahamsen
2000-04-21 20:00                 ` scoring Lars Magne Ingebrigtsen
  -- strict thread matches above, loose matches on Subject: below --
1996-06-12 18:14 scoring michael lamoureux
1996-06-12 22:02 ` scoring Lars Magne Ingebrigtsen
1996-06-12 22:15 ` scoring Steven L Baur

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=t4iwvqyazm5.fsf@silas-2.cc.monash.edu.au \
    --to=bmay@csse.monash.edu.au \
    /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).