Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rutgers!ub!acsu.buffalo.edu
From: pjg@acsu.buffalo.edu (Paul Graham)
Newsgroups: comp.sources.d
Subject: Re: lots of trn problems
Message-ID: <53569@eerie.acsu.Buffalo.EDU>
Date: 6 Jan 91 04:58:37 GMT
References: <1990Dec29.015540.3445@kithrup.COM> <4046@dah.sub.org>
Sender: news@acsu.Buffalo.EDU
Organization: University at Buffalo
Lines: 25
Nntp-Posting-Host: urth.acsu.buffalo.edu

ed@dah.de.intel.com writes:
|I don't understand all the fuss
|over trn.  I find that nn is much more robust and if I'm not mistaken
|also follows "threads".  Would someone who has used both like to comment?
|Are nn and trn comparable in features?  Am I missing out on something
|trn does that nn doesn't do?  

i used rn for years then gave it up for gnews.  i still miss gnews but . . .
i switched to nn when the .newsrc was fixed.  it's great, *real* fast
and it has a number of convenience features i really like.

however i now read news with trn because i like to follow threads in
reply order.  nn groups by subjects and sorts by date.  trn uses the
references line (and falls back to the subject line sorted by date) so
you can slip right along in *order*.

if trn were as fast as nn and could follow threads across groups i'd
stop missing gnews.  or if thread following is added to nn i'll move
right back.

i still use nn to read digested groups and certain other ones.

-- 
pjg@acsu.buffalo.edu / rutgers!ub!pjg / pjg@ubvms (Bitnet)
opinions found above are mine unless marked otherwise.