From: Hannu Koivisto <azure@iki.fi>
Subject: Re: Unable to create Dejanews nnweb groups
Date: 13 Nov 1999 03:01:09 +0200 [thread overview]
Message-ID: <87iu37cii2.fsf@senstation.vvf.fi> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "12 Nov 1999 08:07:21 +0100"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
| Supercool! With total and complete headers and all!
|
| nnweb now does dejanews searches ok again.
(loop Supercool!) First I thought that the result is still not
quite correct, but now that I read the manual, the behaviour I'm
seeing seems to be a feature of nnweb. That is, if I use my
original example again and use "~g comp.lang.lisp clorb" as the
search string, I get a summary buffer like this:
"""
R [ 0: Robert Monfera ] Re: LispWorks status<clip>
R [ 0: David Hanley ] Re: java frontend for<clip>
R [ 0: David Hanley ] Re: Announcing CLORB a<clip>
R < 0: Raymond Wiker >
R < 0: Lennart Staflin >
"""
whereas Dejanews tells me (irrelevant stuff stripped; output is
from w3m):
"""
Date * Subject * Author
10/12/ Re: Announcing David
99 CLORB a Commo Hanley
10/10/ Announcing Lennart
99 CLORB a Common Staflin
Li
10/29/ Re: java David
99 frontend for Hanley
lisp?
10/11/ Re: Announcing Raymond
99 CLORB a Commo Wiker
11/04/ Re: LispWorks Robert
99 status Monfera
"""
I.e., if I understand correctly, because nnweb doesn't read
articles before that is actually requested by the user, it doesn't
know message-id and references fields and thus orders the articles
of the "Announcing CLORB.." thread randomly (well, probably in the
order it gets them or something), which in this case is the reverse
of the correct order. Right?
I wouldn't probably care about this if Gnus didn't put the initial
article of the thread in the middle of the replies, since now that
it does, I can't immediately see which one is the initial article
(which I consider as useful information when searching for
information from articles). But even if it doesn't have the normal
information for threading, couldn't it a) put the article with no
"Re:" in its subject as the first one and b) order the rest based
on the date. As far as I can see, in this case this simple logic
would produce the correct ordering. Of course, it would fail to
order replies sent on the same day, but that's not so important
anyway. Am I making any sense at all?
--
Hannu
next prev parent reply other threads:[~1999-11-13 1:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-09 16:01 Hannu Koivisto
1999-11-10 8:10 ` Steinar Bang
1999-11-11 14:03 ` Lars Magne Ingebrigtsen
1999-11-11 14:50 ` Steinar Bang
1999-11-12 7:07 ` Lars Magne Ingebrigtsen
1999-11-12 8:23 ` Lars Magne Ingebrigtsen
1999-11-12 17:59 ` Per Abrahamsen
1999-11-16 9:11 ` Lars Magne Ingebrigtsen
1999-11-16 14:34 ` Rene H. Larsen
1999-12-01 14:09 ` Lars Magne Ingebrigtsen
1999-12-01 19:38 ` Rene H. Larsen
1999-12-06 3:58 ` Lars Magne Ingebrigtsen
1999-11-13 1:01 ` Hannu Koivisto [this message]
1999-12-01 14:08 ` Lars Magne Ingebrigtsen
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=87iu37cii2.fsf@senstation.vvf.fi \
--to=azure@iki.fi \
/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).