Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: all.SCORE for agent categories
Date: Tue, 20 Nov 2001 18:15:30 +0100	[thread overview]
Message-ID: <vafherpnz2l.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m1u1vpquyd.fsf@reader.newsguy.com> (Harry Putnam's message of "Tue, 20 Nov 2001 08:16:10 -0800")

Harry Putnam <reader@newsguy.com> writes:

> Oh, cool.  I went looking for that stuff a few times and didn't find
> it.  But unless I'm misreading the section it appears that something
> still has to be entered into a group param to cause the agent to use a
> specific score file.  Something like:
>
> (agent-score "~/News/all.SCORE")
>
> Would have to be entered into each groups group-params, and yes that
> would do it but isn't really any different than having to enter
> something in each agent category score file.
>
> Also it isn't clear without experimentation if the group param setting
> would override the category score or add to it.
>
> When you say "It appears that it is possible to tell the Agent to use
> normal score files....."
>
> Are you refering to the same section on syntax? Or is there another
> section that shows a way to tell the agent globally to use regular
> scoring? 
>
> An `s' search in gnus info on `agent-score' only finds hits in the
> syntax section cited.
>
> The mechanism of all.SCORE requires no special effort in regular
> scoring right? If it is there it gets used globally.  Is there a way
> to tell the agent to use that file globally too? But to let it add to
> any category score already in place.

It appears the spec should be (agent-score . file), not (agent-score
. "/some/file/name").

Since the group parameter is the same for all groups, you could set it
in the top-level topic, or via the gnus-parameters variable, or
something.

But note that I've only read the documentation, not actually tried it.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)



      parent reply	other threads:[~2001-11-20 17:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-20 15:31 Harry Putnam
2001-11-20 15:49 ` Kai Großjohann
2001-11-20 16:16   ` Harry Putnam
2001-11-20 16:43     ` Harry Putnam
2001-11-20 17:19       ` Kai Großjohann
2001-11-20 19:40         ` Harry Putnam
2001-11-21 14:26         ` Robert Epprecht
2001-11-21 23:47           ` Harry Putnam
2001-11-22  9:40             ` Kai Großjohann
2001-11-22 11:39               ` Harry Putnam
2001-11-22 12:27                 ` Kai Großjohann
2001-11-22 15:32             ` Robert Epprecht
2001-11-22 17:05               ` Harry Putnam
2001-11-23 14:12                 ` Robert Epprecht
2001-11-24  4:14                   ` Harry Putnam
2001-11-20 17:15     ` Kai Großjohann [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=vafherpnz2l.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    --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).