Gnus development mailing list
 help / color / mirror / Atom feed
From: Dave Disser <disser@hpsdly.sdd.hp.com>
Subject: precedence of score files
Date: 20 Jun 1996 16:08:55 -0700	[thread overview]
Message-ID: <r1xlohi3wfs.fsf@hpsdly.sdd.hp.com> (raw)

Is there a specific rule of precedence for score files?  I'm using
bnews-style score files, so "comp.sys.mac.system", will, on my gnus,
use "comp.all.SCORE", "comp.sys.SCORE", etc.  I would e\bx\bp\be\bc\bt\b
gnus to load least-specific first, ie.

	all.SCORE
		blacklist.SCORE (included from all.SCORE)
	comp.SCORE
		adapt.SCORE (included from comp.SCORE)
	comp.sys.mac.SCORE
	comp.sys.mac.system.SCORE
	comp.sys.mac.system.ADAPT

In this case, I could override settings in all.SCORE from, say,
adapt.SCORE.  What I'm seeing is that adapt.SCORE's settings for mark,
expunge, orphan, etc. are being overridden by all.SCORE, which hardly
seems appropriate.

What is the load order for score files?  Should it be different?

--Dave





             reply	other threads:[~1996-06-20 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-06-20 23:08 Dave Disser [this message]
1996-06-21  6:47 ` 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=r1xlohi3wfs.fsf@hpsdly.sdd.hp.com \
    --to=disser@hpsdly.sdd.hp.com \
    /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).