From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Set gnus-simplify-subject-functions in group parameters?
Date: Fri, 24 Feb 2017 10:29:36 +0900 [thread overview]
Message-ID: <b4mino01im7.fsf@jpl.org> (raw)
In-Reply-To: <87ino1vwvt.fsf@passepartout.tim-landscheidt.de>
Er, first of all, does `gnus-simplify-subject-functions' really
work? I tried this,
(setq gnus-simplify-subject-functions '(gnus-simplify-subject-re))
and confirmed that `gnus-simplify-subject-re' runs. However I
can still see "Re: "s in the summary lines. :(
On Thu, 23 Feb 2017 13:51:02 +0000, Tim Landscheidt wrote:
> How can I set gnus-simplify-subject-functions for a group to
> a different value?
If it works, something like the following will probably work:
--8<---------------cut here---------------start------------->8---
(defun my-gnus-simplify-subject ()
(setq gnus-simplify-subject-functions
(cond ((string-equal "nnfolder:foo.bar" gnus-newsgroup-name)
'(tl-watchlist-subject-munger))
((string-match "\\`nnimap:foo\\." gnus-newsgroup-name)
'(tl-subject-filter-2))
(t nil))))
(add-hook 'gnus-select-group-hook 'my-gnus-simplify-subject)
--8<---------------cut here---------------end--------------->8---
(string-equal "nnfolder:foo.bar" ...) matches the group.
(string-match "\\`nnimap:foo\\." ...) matches the groups of which
the group names begin with "nnimap:foo." .
The last (t nil) must be there.
Unfortunately Gnus isn't designed assuming
`gnus-simplify-subject-functions' to be a group parameter, IIUC.
next prev parent reply other threads:[~2017-02-24 1:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 13:51 Tim Landscheidt
2017-02-24 1:29 ` Katsumi Yamaoka [this message]
2017-02-24 11:10 ` Andreas Schwab
2017-02-25 11:00 ` Reiner Steib
2017-02-27 6:35 ` Katsumi Yamaoka
2017-03-06 2:16 ` Tim Landscheidt
2017-03-06 2:31 ` Tim Landscheidt
2017-03-16 19:36 ` Tim Landscheidt
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=b4mino01im7.fsf@jpl.org \
--to=yamaoka@jpl.org \
--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).