From: Pankaj Jangid <pankaj@codeisgreat.org>
To: Gnus Users <info-gnus-english@gnu.org>
Subject: Correct ordering of items in mail threads
Date: Sat, 21 Oct 2023 10:41:11 +0530 [thread overview]
Message-ID: <877cngr24w.fsf@codeisgreat.org> (raw)
Following is the snapshot from the go-nuts mailing list. Note that the
last item in the list was received before the parent item. This should
not be possible. What changes should I make in the in the Gnus settings
so that it appears in correct order. By correct order, I mean the last
item should have appeard at the root level, instead of appearing as a
child of the one above it.
--8<---------------cut here---------------start------------->8---
R. 02:44 AM [ 123: Victor Giordano ] => Re: [go-nuts] Re: About allowing conversion from bool to int
R. 03:17 AM [ 142: Volker Dobler ] +->
R. 06:01 AM [ 21: Ian Lance Taylor] +->
R. 08:44 AM [ 57: Victor Giordano ] +->
R. 03:44 AM { 179: Victor Giordano } +-> Fwd: [go-nuts] Re: About allowing conversion from bool to int
--8<---------------cut here---------------end--------------->8---
Following is the relevant section of my configuration:
--8<---------------cut here---------------start------------->8---
;; Summary buffer formating
'(gnus-sum-opening-bracket "[")
'(gnus-sum-closing-bracket "]")
'(gnus-sum-opening-bracket-adopted "{")
'(gnus-sum-closing-bracket-adopted "}")
'(gnus-sum-thread-tree-root "=> ")
'(gnus-sum-thread-tree-false-root ">> ")
'(gnus-sum-thread-tree-single-indent "=> ")
'(gnus-sum-thread-tree-indent " ")
'(gnus-sum-thread-tree-vertical "| ")
'(gnus-sum-thread-tree-leaf-with-other "+-> ")
'(gnus-sum-thread-tree-single-leaf "+-> ")
'(gnus-user-date-format-alist
'(((gnus-seconds-today) . "%H:%M %p")
(t . "%d-%m-%y")))
;; '(gnus-summary-line-format
;; "%U%R%z %-5&user-date; %(%[%*%-13,13f%]%) %B%s\n")
'(gnus-summary-line-format
"%U%R%z %-5&user-date; %(%[%4L: %-16,16f%]%) %B%s\n")
;; Threading
'(gnus-thread-sort-functions
'(gnus-thread-sort-by-number))
'(gnus-summary-thread-gathering-function
'gnus-gather-threads-by-references)
--8<---------------cut here---------------end--------------->8---
next reply other threads:[~2023-10-21 5:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-21 5:11 Pankaj Jangid [this message]
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
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=877cngr24w.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).