Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: What does `gathering loose threads' mean?
Date: 09 Aug 2000 23:16:35 +0200	[thread overview]
Message-ID: <vafu2cuqgng.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: prj@po.cwru.edu's message of "09 Aug 2000 15:27:09 -0400"

On 09 Aug 2000, Paul Jarc wrote:

> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai
> =?iso-8859-1?q?Gro=DFjohann?=) writes:
>> I want two articles with the same subject to be sorted together,
>> even if neither of them contains a References header.
> 
> Then you want gnus-summary-thread-gathering-function to be
> gnus-gather-threads-by-subject, which I think is the default.

Ah.  Well.

>> Is it sufficient to set gnus-summary-thread-gathering-function to
>> gnus-gather-threads-by-subject to achieve this, or is it also
>> necessary to set gnus-summary-make-false-root?
> 
> Depends what you mean by `sorted together'. [...]

They are displayed on adjacent lines in the summary buffer.

Okay, so the settings of two variables are important:
gnus-summary-thread-gathering-function and
gnus-summary-make-false-root.

Further improvement can be had by fiddling with the fuzzy and subject
simplification thingies.

Somebody in a German newsgroup continues to claim that setting
gnus-thread-ignore-subject to nil is a useful thing to do in the above
context.  But of course, it isn't.  Does something different
entirely.  Now I'll go back and try to explain again.

Thanks,
kai
-- 
I like BOTH kinds of music.



  reply	other threads:[~2000-08-09 21:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-09 16:00 Kai Großjohann
2000-08-09 16:17 ` Paul Jarc
2000-08-09 17:49   ` Kai Großjohann
2000-08-09 19:27     ` Paul Jarc
2000-08-09 21:16       ` Kai Großjohann [this message]
2000-08-09 21:41         ` Paul Jarc

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=vafu2cuqgng.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.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).