From: Andrew Cohen <acohen@ust.hk>
To: ding@gnus.org
Subject: Re: Gnus threads too many articles together
Date: Wed, 25 Oct 2023 10:23:51 +0800 [thread overview]
Message-ID: <87il6v783s.fsf@ust.hk> (raw)
In-Reply-To: <m1a5s78qyu.fsf@johnhaman.org>
>>>>> "JH" == John Haman <mail@johnhaman.org> writes:
[...]
JH> I don't know the most informative way to ask this question, but
JH> is there a way to make Gnus just thread distinct conversations
JH> together (like Outlook.)
Do you mean you want to NOT combine messages with the same subject into
a thread, but only those that are actually related?
‘gnus-summary-thread-gathering-function’
Gnus gathers threads by looking at ‘Subject’ headers. This means
that totally unrelated articles may end up in the same “thread”,
which is confusing. An alternate approach is to look at all the
‘Message-ID’s in all the ‘References’ headers to find matches.
This will ensure that no gathered threads ever include unrelated
articles, but it also means that people who have posted with broken
newsreaders won’t be gathered properly. The choice is yours—plague
or cholera:
‘gnus-gather-threads-by-subject’
This function is the default gathering function and looks at
‘Subject’s exclusively.
‘gnus-gather-threads-by-references’
This function looks at ‘References’ headers exclusively.
If you want to test gathering by ‘References’, you could say
something like:
(setq gnus-summary-thread-gathering-function
'gnus-gather-threads-by-references)
--
Andrew Cohen
next prev parent reply other threads:[~2023-10-25 2:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 0:51 John Haman
2023-10-25 2:23 ` Andrew Cohen [this message]
2023-10-25 14:21 ` John Haman
2023-10-25 8:17 ` Eric S Fraga
2023-10-27 2:32 ` Pankaj Jangid
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=87il6v783s.fsf@ust.hk \
--to=acohen@ust.hk \
--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).