From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: Threading is messed up
Date: 02 Dec 1999 12:01:45 +1100 [thread overview]
Message-ID: <t4ibt8acg06.fsf@silas-2.cc.monash.edu.au> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "Wed, 01 Dec 1999 17:10:16 +0100"
>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
Lars> Brian May <bam@silas-2.cc.monash.edu.au> writes:
>> O* [ 27: Lars Magne Ingebrigt] Re: Suggested features
>> R [ 25: Kai Großjohann ]
>> R [ 24: Hrvoje Niksic ]
>> R [ 13: Lars Magne Ingebrigt]
>> R [ 18: Hrvoje Niksic ]
>> R [ 23: Kai Großjohann ]
>> R [ 18: Hrvoje Niksic ]
>> R* [ 15: Brian May ] <----
>> R* [ 13: Lars Magne Ingebrigt]
>>
>> ie the original article is down below the reply.
Lars> So the original article here is the one marked "<----"?
Yes. All other articles are replies. I can't remember the
details of this test though, so I may have forgotten something.
>> sometimes, when PGnus
>> gets really confused articles might even appear under the *next* thread.
>>
>> Reloading the entire thread fixes this problem.
>>
>> Obviously something is not working like it should...
Lars> The re-threading code has been fiddled with extensively, and if it
Lars> works all the time now, I'll be really surprised. :-)
Lars> I'm not able to reproduce this particular bug, though.
I think the problem (did I say so in my original message?) Is
that /* inserts articles above the current cursor position.
Will try to see if I can reproduce the problem with 0.99, ASAP.
--
Brian May <bmay@csse.monash.edu.au>
next prev parent reply other threads:[~1999-12-02 1:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-18 1:22 Brian May
1999-11-18 3:25 ` Justin Sheehy
1999-11-18 11:32 ` Bud Rogers
1999-12-01 16:10 ` Lars Magne Ingebrigtsen
1999-12-02 1:01 ` Brian May [this message]
1999-12-02 7:37 ` Yair Friedman (Jerusalem)
1999-12-02 23:10 ` Lars Magne Ingebrigtsen
1999-12-06 0:13 ` Brian May
2000-04-21 20:35 ` Lars Magne Ingebrigtsen
2000-04-21 21:47 ` Kai Großjohann
2000-04-22 12:12 ` 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=t4ibt8acg06.fsf@silas-2.cc.monash.edu.au \
--to=bmay@csse.monash.edu.au \
/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).