From owner-freebsd-current  Mon Apr  8 07:58:04 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA01889
          for current-outgoing; Mon, 8 Apr 1996 07:58:04 -0700 (PDT)
Received: from mail.think.com (Mail1.Think.COM [131.239.33.245])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA01881
          for <current@freebsd.org>; Mon, 8 Apr 1996 07:58:00 -0700 (PDT)
Received: from Early-Bird-1.Think.COM by mail.think.com; Mon, 8 Apr 96 10:57:59 -0400
Received: from compound.think.com ([206.10.99.151]) by Early-Bird.Think.COM; Mon, 8 Apr 96 10:57:56 EDT
Received: (from alk@localhost) by compound.think.com (8.7.5/8.6.112) id JAA10195; Mon, 8 Apr 1996 09:58:02 -0500 (CDT)
Date: Mon, 8 Apr 1996 09:58:02 -0500 (CDT)
Message-Id: <199604081458.JAA10195@compound.think.com>
From: Tony Kimball <alk@Think.COM>
To: current@freebsd.org
Subject: Re: termcap/curses vs ncurses
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


  From: "Marc G. Fournier" <scrappy@ki.net>
  Date: Mon, 8 Apr 1996 01:26:38 -0400 (EDT)

  =09Is *everyone* set against terminfo?  If so, I'll work on 1.9.9
  so that it parses only termcap and doesn't create a .terminfo directory,
  just sounds crippling to me :(

One man's opinion: terminfo is gross over-engineering cruft, and more
importantly it is a bother for sysadmin.  As long as there is no need
to bring in other software that depends upon it, it seems desirable to
avoid the pollution.