lots of trn problems

Tom Christiansen tchrist at convex.COM
Tue Dec 18 03:54:49 AEST 1990


>From the keyboard of sef at kithrup.com (Sean Eric Fagan):
: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*.

This is unclear.  I have used it for a long time now, since well before
its release, and I've *NEVER* had the problems you describe.  In fact, to
my perception, it's been as robust as rn (more so in a couple way -- he
fixed some rn bug along the way).  Your milage, of course, may bery, and
probably does since you're on a different hardware/software platform.
Again, I don't have troubles with mail to Davison, but haven't tried in a
few weeks.  Let's try not to be looking the gift horse in the mouth.

I, too, have become hopelessly habituated to trn.  I'd been mumbling
things to Larry Wall for well over a year about what I thought trees
of messages should work like, but Larry had embarked upon the Perlian
Way (at least partially in order to rewrite rn!) and has still not 
emerged. :-)  Davison implemented very close to what I wanted.  All
I want now are two little things:

    following threads between groups
    a newsgroup selection menu 

--tom
--
Tom Christiansen		tchrist at convex.com	convex!tchrist
"With a kernel dive, all things are possible, but it sure makes it hard
 to look at yourself in the mirror the next morning."  -me



More information about the Comp.sources.bugs mailing list