From: Giorgos Keramidas <keramida@ceid.upatras.gr>
To: info-gnus-english@gnu.org
Subject: Re: per group value of gnus-summary-thread-gathering-function?
Date: Thu, 24 Jul 2008 19:37:49 +0300 [thread overview]
Message-ID: <87ljzrck6a.fsf@kobe.laptop> (raw)
In-Reply-To: <86iquwepa9.fsf@lifelogs.com>
On Wed, 23 Jul 2008 07:52:14 -0500, Ted Zlatanov <tzz@lifelogs.com> wrote:
> On Tue, 22 Jul 2008 17:48:29 +0300 Giorgos Keramidas <keramida@ceid.upatras.gr> wrote:
> GK> What is the recommended way of getting different thread gathering
> GK> logic for some of the groups?
>
> I don't know if there's a standard way; I do it in the summary entry
> hook based on the newsgroup name.
Thank you Ted,
That sounds like a good idea.
I thought adding this to the group parameters was a nice way of making
it work, but maybe it's worth trying to patch Gnus and add some sort of
wrapper function that dispatches on the group name, i.e.:
(setq-default gnus-summary-thread-gathering-function
'keramida-gnus-gather-threads)
Then I could add regexp matches to one or two new variables like:
(defvar keramida-gnus-thread-function-by-group-map
'(("mail\\.foo\\.bar" . gnus-gather-threads-by-subject)
("mail\\..*" . gnus-gather-threads-by-references)
(t . gnus-gather-threads-by-references))
"List of (regexp . function) pairs to select a thread-gathering function.")
Then with `gnus-summary-exit-hook' I can restore the thread gathering
function to a `default' value. I think I'll give this a try. If it
seems to work nicely, I will post what I wrote here when I've tested it
a bit.
next prev parent reply other threads:[~2008-07-24 16:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-22 14:48 Giorgos Keramidas
2008-07-23 12:52 ` Ted Zlatanov
2008-07-24 16:37 ` Giorgos Keramidas [this message]
2008-07-24 17:53 ` Giorgos Keramidas
2008-07-28 14:54 ` Johan Bockgård
2008-07-29 2:34 ` Giorgos Keramidas
2008-07-29 3:41 ` Giorgos Keramidas
2008-07-24 18:21 ` Ted Zlatanov
2008-07-24 19:25 ` Giorgos Keramidas
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=87ljzrck6a.fsf@kobe.laptop \
--to=keramida@ceid.upatras.gr \
--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).