From: Tassilo Horn <tsdh@gnu.org>
To: info-gnus-english@gnu.org
Subject: Re: Kill certain articles in certain groups all from gnus.el
Date: Thu, 25 Apr 2013 08:44:04 +0200 [thread overview]
Message-ID: <87ehdzw1mz.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <20130425030449.GA12476@ps11007.dreamhostps.com>
jidanni@jidanni.org writes:
> Gentlemen, I wish to
> Kill (so I don't see them) all articles
> that match Subject: /xxx/
> whose group name matches: /yyy/
> and have this all contained within my .gnus.el file for easy maintenance.
>
> I don't want to have 15 identical files one for each group.
>
> I don't want a global kill string that matches every group.
>
> I don't want this stuck in some binary .eld file that I have to fight
> with gnus about who gets to edit it.
This is completely untested, but I think it should do the job. It
creates a score file /tmp/gnus.score that contains just one entry
assigning to xxx articles a score of -10000. Via gnus-parameters, this
score file will be used in yyy groups only. Additionally, the expunge
below limit is set to -9999 in those groups so that you don't see the
articles at all.
--8<---------------cut here---------------start------------->8---
(defvar my-gnus-yyy-score-file
(expand-file-name "gnus.score"
temporary-file-directory))
(with-temp-buffer
;; Every article with a Subject containing "xxx" gets a score of -10000.
(insert "((\"subject\" (\"xxx\" -10000 nil r)))")
(write-file my-gnus-yyy-score-file))
(setq gnus-parameters
`(("yyy" ;; In every group matching "yyy" use the score file generated
;; above.
(score-file . ,my-gnus-yyy-score-file)
;; Don't show articles with a score lower than -9999.
(gnus-summary-expunge-below -9999))))
--8<---------------cut here---------------end--------------->8---
Not sure, maybe there's a better way to do that...
Bye,
Tassilo
next prev parent reply other threads:[~2013-04-25 6:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 3:04 jidanni
2013-04-25 6:44 ` Tassilo Horn [this message]
2013-04-25 16:57 ` jidanni
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=87ehdzw1mz.fsf@thinkpad.tsdh.de \
--to=tsdh@gnu.org \
--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).