|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
The score commands that alter score entries do not actually modify real score files. That would be too inefficient. Gnus maintains a cache of previously loaded score files, one of which is considered the current score file alist. The score commands simply insert entries into this list, and upon group exit, this list is saved.
The current score file is by default the group’s local score file, even if no such score file actually exists. To insert score commands into some other score file (e.g., ‘all.SCORE’), you must first make this score file the current one.
General score commands that don’t actually change the score file:
Set the score of the current article (
Display the score of the current article
Display all score rules that have been used on the current article
gnus-score-find-trace). In the ‘*Score Trace*’ buffer, you
may type e to edit score file corresponding to the score rule on
current line and f to format (
score file and edit it.
List words used in scoring (
Run the current summary through the scoring process
gnus-summary-rescore). This might be useful if you’re playing
around with your score files behind Gnus’ back and want to see the
effect you’re having.
Make a different score file the current
Edit the current score file (
You will be popped into a
gnus-score-mode buffer (see section Score File Editing).
Edit a score file and make this score file the current one
Flush the score cache (
gnus-score-flush-cache). This is useful
after editing score files.
Customize a score file in a visually pleasing manner
The rest of these commands modify the local score file.
Prompt for a score, and mark all articles with a score below this as
Prompt for a score, and add a score rule to the current score file to
expunge all articles below this score
The keystrokes for actually making score entries follow a very regular pattern, so there’s no need to list all the commands. (Hundreds of them.)
Score on the author name.
Score on the subject line.
Score on the
Xref line—i.e., the cross-posting line.
Score on the
Score on the date.
Score on the number of lines.
Score on the
Score on an “extra” header, that is, one of those in gnus-extra-headers, if your NNTP server tracks additional header data in overviews.
Score on followups—this matches the author name, and adds scores to the followups to this author. (Using this key leads to the creation of ‘ADAPT’ files.)
Score on the body.
Score on the head.
Score on thread. (Using this key leads to the creation of ‘ADAPT’ files.)
Fuzzy matching (see section Fuzzy Matching).
Less than number.
Equal to number.
Greater than number.
Temporary score entry.
Permanent score entry.
So, let’s say you want to increase the score on the current author with exact matching permanently: I a e p. If you want to lower the score based on the subject line, using substring matching, and make a temporary score entry: L s s t. Pretty easy.
To make things a bit more complicated, there are shortcuts. If you use a capital letter on either the second or third keys, Gnus will use defaults for the remaining one or two keystrokes. The defaults are “substring” and “temporary”. So I A is the same as I a s t, and I a R is the same as I a r t.
These functions take both the numerical prefix and the symbolic prefix
(see section Symbolic Prefixes). A numerical prefix says how much to lower
(or increase) the score of the article. A symbolic prefix of
says to use the ‘all.SCORE’ file for the command instead of the
current score file.
gnus-score-mimic-keymap says whether these commands will
pretend they are keymaps or not.
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]|
This document was generated on January 25, 2015 using texi2html 1.82.