Gnus development mailing list
 help / color / mirror / Atom feed
From: Andreas Fuchs <asf@acm.org>
Cc: ding@gnus.org
Subject: Re: thread ordering, root last
Date: Mon, 24 Jul 2000 14:38:12 +0200	[thread overview]
Message-ID: <878zur66vf.fsf@dahaIM.dyndns.org> (raw)
In-Reply-To: Bud Rogers's message of "24 Jul 2000 04:56:26 -0500"


Today, Bud Rogers <budr@sirinet.net> wrote:
> I just subscribed to the pgsql-hackers list.  Haven't yet made any changes
> to group parameters, etc.  In the summary buffer the messages are arranged
> in threads but in every case the root of the thread is listed last.  I have
> seen this occasionally with other groups, but never quite so consistently.

> Is this a problem with gnus, with the list, or with my setup?

It's your setup, I think. It seems that you do message-ordering by
Subject string. Let's see now:

> R +[ 43: Adriaan Jouber] Re: [HACKERS] Loading binary data into the database
>   +[ 33: Tom Lane      ] Re: [HACKERS] Loading binary data into the database
>   +[ 36: Adriaan Jouber] Re: [HACKERS] Loading binary data into the database
>   +[ 15: Tom Lane      ] Re: [HACKERS] Loading binary data into the database
>   +[ 36: Adriaan Jouber] [HACKERS] Loading binary data into the database

And now:

[0]asf@dahaIM:~% echo "R" | char
82 52 122
[0]asf@dahaIM:~% echo "[" | char
91 5b 133
(char is a little hack I have written myself, which outputs the value
in bin, hex, oct of a character it reads from stdin)

As you can see, [ has a higher value than R, so the replies get sorted
in before the root. The same applies for Subjects that start with an
S, T, U, V, W or a { (-:

I suggest that you activate threading in Summary mode.

regards,
-- 
Andreas Stefan Fuchs                             in Real Life aka
asf@acm.org, asfuchs@gmx.at, asf@ycom.at         in NNTP and SMTP,
antifuchs                                        in IRCNet and
Relf Herbstfresser, Male 1/2 Elf Priest          in AD&D



  reply	other threads:[~2000-07-24 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-24  9:56 Bud Rogers
2000-07-24 12:38 ` Andreas Fuchs [this message]
     [not found] ` <vafr98cdg5u.fsf@lucy.cs.uni-dortmund.de>
     [not found]   ` <87hf9897at.fsf@dahaIM.dyndns.org>
     [not found]     ` <vaf8zuk94c1.fsf@lucy.cs.uni-dortmund.de>
2000-07-30 20:54       ` Bud Rogers

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=878zur66vf.fsf@dahaIM.dyndns.org \
    --to=asf@acm.org \
    --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).