From: Pankaj Jangid <pankaj@codeisgreat.org>
To: info-gnus-english@gnu.org
Subject: Re: Correct ordering of items in mail threads
Date: Mon, 23 Oct 2023 20:11:48 +0530 [thread overview]
Message-ID: <874jiho0yb.fsf@codeisgreat.org> (raw)
In-Reply-To: <87ttqhy1mx.fsf@tullinup.koldfront.dk>
Adam Sjøgren <asjo@koldfront.dk> writes:
> Pankaj writes:
>
>> E 20-10-23 23:18 PM [ 107: Victor Giordano ] => Re: [go-nuts] Re: About allowing conversion from bool to int
>> O 21-10-23 02:44 AM [ 123: Victor Giordano ] +->
>> O 21-10-23 03:17 AM [ 142: Volker Dobler ] +->
>> O 21-10-23 06:01 AM [ 21: Ian Lance Taylor] +->
>> O 21-10-23 08:44 AM [ 57: Victor Giordano ] +->
>> E 21-10-23 18:27 PM [ 69: Victor Giordano ] +->
>> O 21-10-23 03:44 AM { 179: Victor Giordano } +-> Fwd: [go-nuts] Re: About allowing conversion from bool to int
>>
>> In the above snapshot, items are still ordered incorrectly.
>
> Just to make sure: you are expecting the article in the last row to be
> shown in the 4th row?
No. I want the indentation to be proper. It cannot be child of a later message.
> I would expect the reason that the last line is put last is because
> the References: header includes the Message-ID of the second to last
> article.
>
> Is that not the case?
As we can see this is not possible. Becase the second last message came
after the last one.
> But wait, the curly braces means "adopted". What does that mean?
>
> · https://www.gnu.org/software/emacs/manual/html_node/gnus/Loose-Threads.html
>
> What happens if you change the value of gnus-summary-make-false-root?
> Perhaps to nil?
Wow. Good pointer. The default value of the variable is 'adopt'. I
experimented with the other three possible values. And here are the
results, along with the quoted docstring
> If this variable is ‘adopt’, Gnus will make one of the "children"
> the parent and mark all the step-children as such.
> If this variable is ‘none’, Gnus will not make a false root, but just
> present the sub-threads after another.
(setq gnus-summary-make-false-root 'none)
--8<---------------cut here---------------start------------->8---
E 20-10-23 23:18 PM [ 107: Victor Giordano ] => Re: [go-nuts] Re: About allowing conversion from bool to int
O 21-10-23 02:44 AM [ 123: Victor Giordano ] | +->
O 21-10-23 03:17 AM [ 142: Volker Dobler ] | +->
O 21-10-23 06:01 AM [ 21: Ian Lance Taylor] | +->
O 21-10-23 08:44 AM [ 57: Victor Giordano ] | +->
E 21-10-23 18:27 PM [ 69: Victor Giordano ] | +->
O 21-10-23 03:44 AM [ 179: Victor Giordano ] => Fwd: [go-nuts] Re: About allowing conversion from bool to int
--8<---------------cut here---------------end--------------->8---
> If this variable is ‘dummy’, Gnus will create a dummy root that will
> have all the sub-threads as children.
(setq gnus-summary-make-false-root 'dummy)
--8<---------------cut here---------------start------------->8---
: : Re: [go-nuts] Re: About allowing conversion from bool to int
E 20-10-23 23:18 PM [ 107: Victor Giordano ] +->
O 21-10-23 02:44 AM [ 123: Victor Giordano ] | +->
O 21-10-23 03:17 AM [ 142: Volker Dobler ] | +->
O 21-10-23 06:01 AM [ 21: Ian Lance Taylor] | +->
O 21-10-23 08:44 AM [ 57: Victor Giordano ] | +->
E 21-10-23 18:27 PM [ 69: Victor Giordano ] | +->
O 21-10-23 03:44 AM [ 179: Victor Giordano ] +-> Fwd: [go-nuts] Re: About allowing conversion from bool to int
--8<---------------cut here---------------end--------------->8---
> If this variable is ‘empty’, the "children" are printed with empty
> subject fields. (Or rather, they will be printed with a string given
> by the ‘gnus-summary-same-subject’ variable.)
(setq gnus-summary-make-false-root 'empty)
--8<---------------cut here---------------start------------->8---
E 20-10-23 23:18 PM [ 107: Victor Giordano ] => Re: [go-nuts] Re: About allowing conversion from bool to int
O 21-10-23 02:44 AM [ 123: Victor Giordano ] | +->
O 21-10-23 03:17 AM [ 142: Volker Dobler ] | +->
O 21-10-23 06:01 AM [ 21: Ian Lance Taylor] | +->
O 21-10-23 08:44 AM [ 57: Victor Giordano ] | +->
E 21-10-23 18:27 PM [ 69: Victor Giordano ] | +->
O 21-10-23 03:44 AM [ 179: Victor Giordano ] => Fwd: [go-nuts] Re: About allowing conversion from bool to int
--8<---------------cut here---------------end--------------->8---
I think 'none' and 'empty' works best for the situation. May be I should
try each of these for a couple of days and decide.
next prev parent reply other threads:[~2023-10-23 14:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 5:11 Pankaj Jangid
2023-10-22 11:24 ` Eric S Fraga
2023-10-22 16:15 ` Pankaj Jangid
2023-10-22 16:22 ` Adam Sjøgren
2023-10-22 16:29 ` Eric Abrahamsen
2023-10-22 16:53 ` Adam Sjøgren
2023-10-22 17:00 ` Eric Abrahamsen
2023-10-22 17:05 ` Adam Sjøgren
2023-10-22 17:11 ` Eric Abrahamsen
2023-10-23 7:39 ` Pankaj Jangid
2023-10-23 12:16 ` Adam Sjøgren
2023-10-23 14:41 ` Pankaj Jangid [this message]
2023-10-23 18:38 ` Adam Sjøgren
2023-10-24 4:33 ` Pankaj Jangid
2023-10-23 19:15 ` Björn Bidar
[not found] ` <1427.43186313368$1698088555@news.gmane.org>
2023-10-24 4:43 ` Pankaj Jangid
2023-10-23 17:12 ` Eric S Fraga
2023-10-24 4:28 ` Pankaj Jangid
2023-10-24 6:14 ` Eric S Fraga
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=874jiho0yb.fsf@codeisgreat.org \
--to=pankaj@codeisgreat.org \
--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).