Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: info-gnus-english@gnu.org
Subject: Using `all.SCORE' @ ~/News/all.SCORE [regex syntax]
Date: Sat, 27 May 2017 10:58:02 -0400	[thread overview]
Message-ID: <8660gmgxdx.fsf@local.lan> (raw)


all.SCORE:

((mark -100)
 ("from"
  ("nikolys@gmail" -101 nil r)
  ("sina\.com" -101 nil r)
  ("@aol\\.com" -101 nil r)
  ("@[0-9]+\\.com>" -101 nil r)
  ("harry504@gmail" -101 nil r)
  ("s[ea]l[el]\\|discount\\|free\\|wholesale\\|paypal" -101 nil r))
 ("subject"
  ("~~" -101 nil r)
  ("~~\\|>>>\\|\\[A-Z\\]\\{4\\}" -101 nil r)
  ("!!\\|free\\|discount\\|wholesale" -101 nil r)))

I've forgotten how that was generated but would like to hand edit it.

You can see the term `free' in two places... in the last `from' element
and the last `subject' element.

I want the `free' at the last `from' element to be more restrictive as
it is hitting quite a few false positives due to network name with
various combinations of free with a dot like: `free.', `.free' and
`.free.'

This is happening in groups with thousands and thousands of messages
so I don't want to get it wrong... not sure how to re-run it.

So something like (please ignore the elisions (`[...]')):

        [...] |[^\.]free[^\.]\\|[...]

But does it need the double slashes like:

        [...] |\\[^\.\\]free\\[^\.\\] [...]
                      ^^    ^^     ^^      
Will that even accomplish what I am after; to allow `free' in any
combination of: `.free', `free.' or `.free.' to not be down scored?

Is there a handy way to test the regex?

Is there a handy way to rerun all those messages thru `all.SCORE'?



             reply	other threads:[~2017-05-27 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-27 14:58 Harry Putnam [this message]
2017-05-29 10:34 ` Ben Bacarisse
2017-05-30  0:51   ` Harry Putnam

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=8660gmgxdx.fsf@local.lan \
    --to=reader@newsguy.com \
    --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).