From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Set gnus-simplify-subject-functions in group parameters?
Date: Sat, 25 Feb 2017 12:00:08 +0100 [thread overview]
Message-ID: <877f4ebknb.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mino01im7.fsf@jpl.org> (Katsumi Yamaoka's message of "Fri, 24 Feb 2017 10:29:36 +0900")
On Fri, Feb 24 2017, Katsumi Yamaoka wrote:
> 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. :(
I guess `gnus-simplify-subject-functions' is used for threading and
scoring and doesn't influence the display (in summary and article
buffers). For the latter, `gnus-list-identifiers' might be useful.
With the following code, I can see that the function rs-test is called
twice for each article (after turning on threading):
| Generating summary...done
| No more unseen articles
| No more unread articles
| SIMPLIFY: subdomain adressing
| SIMPLIFY: Test-von-Reiner
| Generating summary...
| SIMPLIFY: subdomain adressing
| SIMPLIFY: Test-von-Reiner
| Generating summary...done
| Threading is now on
(defun rs-test (s) (message "SIMPLIFY: %s" s))
(setq
gnus-parameters
`(;; ...
("misc\\.test"
(gnus-simplify-subject-functions
'(gnus-simplify-subject-re
gnus-simplify-whitespace
rs-test))
(gnus-summary-line-format "..."))
...))
Bye, Reiner.
next prev parent reply other threads:[~2017-02-25 11:00 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
2017-02-24 11:10 ` Andreas Schwab
2017-02-25 11:00 ` Reiner Steib [this message]
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=877f4ebknb.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.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).