lots of trn problems

Sean Eric Fagan sef at kithrup.com
Mon Dec 17 21:19:20 AEST 1990


Not meaning to be disrepectful to either the author nor Rich, but trn was
the *worst* package I've ever played with from the net.  The first postings
weren't workable, *period*, and, even after I got the reposted parts nine
and ten, it *still* died when unsharing.

So I didn't bother with the posted version, but got a version from off of
tut.cis.ohio-state (good folks there...).  That one I managed to compile,
and has worked quite well on kithrup.

At work, however, where we use NNTP, and I was far behind in some groups,
trn gets a SIGSEGV and dies.  At first, I thought it had to do with being,
oh, 340+ articles behind, but, tonight, when I was reading comp.arch, where
I had (originally) 66 unread articles, I managed to get throuh 22 of them,
and then it core dumped between one article and the next.

My next complaint with it is that it has the articles in reverse order when
listing them for thread selection, and if you bypass that, you are at the
last article, instead of the first.

The author has not replied to any of my messages; several of them, in fact,
bounced, because they could not be delivered in three days.

I *really* like trn; I've become habituated to it, in fact.  But it is not
usable as it is, and should not have been released to c.s.u; it should have
been sent out to alt.sources, and gone through at least one more beta
period.  Also, the author should be responsive towards email, assuming he
gets it.  If he's not getting it, then he should do something about *that*.

(I know, I know:  bitch, bitch, bitch...)

-- 
Sean Eric Fagan  | "I made the universe, but please don't blame me for it;
sef at kithrup.COM  |  I had a bellyache at the time."
-----------------+           -- The Turtle (Stephen King, _It_)
Any opinions expressed are my own, and generally unpopular with others.



More information about the Comp.sources.bugs mailing list