Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!auspex!guy
From: guy@auspex.auspex.com (Guy Harris)
Newsgroups: news.software.b
Subject: Re: Turning rn into a threaded newsreader
Message-ID: <2964@auspex.auspex.com>
Date: 24 Feb 90 03:16:35 GMT
References: <15687@well.UUCP> <1990Jan25.025825.13446@ux1.cso.uiuc.edu> <-C-#CRF@b-tech.uucp>
Organization: Auspex Systems, Santa Clara
Lines: 16

>If nothing else, I think it would be a major convenience to have rn read
>articles in depth first order.   The user wouldn't see any difference
>(interface wise), things would just make more sense (less of this answer
>before the question stuff, etc).

After one day of using "tn", I've found it offers one *MASSIVE*
improvement, namely the ability to get a listing of all the *threads* in
a newsgroup.  It lets me see what's in a group without having to look at
some huge multi-screen subject listing.  The fact that it shares most of
"rn"s look&feel is useful, but frankly, given the choice between an "rn"
that just shows articles in depth-first order, and "tn", it wouldn't
even be a contest - it'd be "tn" by a parsec.

I haven't bothered worrying about walking a reference tree; being able
to zip through the threads in some "flattened" order with the standard
"rn" commands has so far been sufficient.