From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Threading is messed up
Date: Fri, 21 Apr 2000 23:47:26 +0200 [thread overview]
Message-ID: <200004212147.XAA03744@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "21 Apr 2000 22:35:41 +0200"
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Brian May <bmay@csse.monash.edu.au> writes:
>
> > / * inserts cached articles above the current cursor position.
>
> [...] I don't think this state of affairs is bad...
I think the articles should be inserted in the right position. In the
same position they would be in if they were ticked, say.
Currently, cached articles will be displayed in reverse order.
kai
--
Beware of flying birch trees.
next prev parent reply other threads:[~2000-04-21 21:47 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
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 [this message]
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=200004212147.XAA03744@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.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).