From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Simple thread sorting question
Date: Fri, 12 Jan 2007 18:05:17 +0100 [thread overview]
Message-ID: <v9odp4yy42.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <yup4ejq09vnr.fsf@sbz-32.cs.helsinki.fi>
On Fri, Jan 12 2007, Jarmo Hurri wrote:
> 3953 A [ 82: Johannes Schmidt ] Re: CNS - project work available
> 3964 < 76: Johannes Schmidt >
> 3963 [ 17: Harri Valpola ] Re: Cortical maps
> 3965 A [ 30: Harri Valpola ] Re: Tulokset
> 3972 [ 4: -> Jarmo Hurri ]
>
> As far as I have understood, the first and second thread should be in
> reverse order, right? And my ordering seems to follow the number of
> the first mail in the thread.
"< ... >" instead of "[ ... ]" indicates a loose thread. Maybe this
is the problem.
,----[ (info "(gnus)Loose Threads") ]
| `adopt'
| Gnus will make the first of the orphaned articles the parent.
| This parent will adopt all the other articles. The adopted
| articles will be marked as such by pointy brackets (`<>')
| instead of the standard square brackets (`[]'). This is the
| default method.
`----
Does it work as expected e.g. in a Usenet group or in this group?
> BTW, how do you get the following neat elisp evaluation buffer
> started:
>
> Reiner> | ELISP> gnus-summary-line-format
M-x ielm RET
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2007-01-12 17:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 17:49 Jarmo Hurri
2007-01-11 21:06 ` Reiner Steib
2007-01-12 7:10 ` Jarmo Hurri
2007-01-12 10:43 ` Reiner Steib
2007-01-12 14:17 ` Jarmo Hurri
2007-01-12 17:05 ` Reiner Steib [this message]
2007-01-13 10:37 ` Jarmo Hurri
2007-01-13 12:13 ` orphaned articles / loose threads and gnus-thread-sort-by-most-recent-number (was: Simple thread sorting question) Reiner Steib
[not found] ` <mailman.3033.1168717393.2155.info-gnus-english@gnu.org>
2007-01-15 8:15 ` orphaned articles / loose threads and gnus-thread-sort-by-most-recent-number Jarmo Hurri
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=v9odp4yy42.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).