From: Sudish Joseph <sudish@mindspring.com>
Subject: Re: score files... [patch]
Date: 13 Aug 1996 21:02:57 -0400 [thread overview]
Message-ID: <m2686mixq6.fsf_-_@atreides.erehwon.org> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 13 Aug 1996 10:20:43 +0200
Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> This is now possible with the `gnus-home-score-file' alist.
Cool! It's somewhat ironic that ding provided so many hooks that were
needed in earlier versions--and removes the need for those hooks.
Since this is a new feature, can we make a small change? The patch is
self-explanatory. I hope no one is using this as yet/won't mind it
terribly.
(setq gnus-home-score-file gnus-score-file-single-match-alist) is
easier than maintaining two separate alists, for those that use both.
-Sudish
--- gnus-score.el~ Tue Aug 13 20:50:57 1996
+++ gnus-score.el Tue Aug 13 20:50:57 1996
@@ -136,9 +136,11 @@
* A list
The elements in this list can be:
- * `(regexp . file-name)'
- If the `regexp' matches the group name, the `file-name' will
- will be used as the home score file.
+ * `(regexp file-name ...)'
+ If the `regexp' matches the group name, the first `file-name' will
+ will be used as the home score file. (Multiple filenames are
+ allowed so that one may use gnus-score-file-single-match-alist to
+ set this variable.)
* A function.
If the function returns non-nil, the result will be used
@@ -2495,7 +2497,7 @@
;; Regexp-file cons
((consp elem)
(when (string-match (car elem) group)
- (cdr elem))))))
+ (cadr elem))))))
(when found
(nnheader-concat gnus-kill-files-directory found))))
next prev parent reply other threads:[~1996-08-14 1:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-10 23:09 score files robert
1996-08-11 0:33 ` Lars Magne Ingebrigtsen
1996-08-11 15:53 ` robert
1996-08-11 22:16 ` Jack Vinson
1996-08-12 0:20 ` robert
1996-08-12 4:17 ` Sudish Joseph
1996-08-13 8:20 ` Lars Magne Ingebrigtsen
1996-08-14 1:02 ` Sudish Joseph [this message]
1996-08-11 1:41 ` Sudish Joseph
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=m2686mixq6.fsf_-_@atreides.erehwon.org \
--to=sudish@mindspring.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).