From owner-freebsd-questions  Wed Nov  8 13:35:06 1995
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id NAA20544
          for questions-outgoing; Wed, 8 Nov 1995 13:35:06 -0800
Received: from hermes.intel.com (hermes.intel.com [143.183.152.3])
          by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id NAA20520
          ; Wed, 8 Nov 1995 13:34:54 -0800
From: olsenc@ichips.intel.com
Received: from ichips.intel.com by hermes.intel.com (5.65/10.0i); Wed, 8 Nov 95 13:33:39 -0800
Received: from dtt034 by ichips.intel.com (5.64+/10.0i); Wed, 8 Nov 95 09:50:35 -0800
Received: by dtt034.intel.com (AIX 3.2/UCB 5.64/10.0i); Wed, 8 Nov 1995 09:50:32 -0800
Date: Wed, 8 Nov 1995 09:50:32 -0800
Message-Id: <9511081750.AA04900@dtt034.intel.com>
To: questions@freebsd.org
Subject: trn works terribly on FreeBSD
Cc: davison@borland.com, ports@freebsd.org
Sender: owner-questions@freebsd.org
Precedence: bulk


Hello:

I sent mail quite a while ago to this list mentioning that trn is quite
buggy on FreeBSD.  I got no response from the ports group or the trn 
maintainers...

First, shelling out frequently causes trn to dump core.  Another fine feature
that I get once in awhile when trying to post is:

initscr failed.
xterm: terminal type lacks necessary features.

???  What the heck is that?

I wish I could just get rid of trn and use another reader (say Mozilla), but
that is not possible since I read messages on the protected side of a 
firewall.

-Clint