Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA
Path: utzoo!watmath!clyde!cbosgd!cbdkc1!desoto!packard!hoxna!houxm!whuxlm!akgua!mcnc!decvax!genrad!mit-eddie!godot!harvard!seismo!brl-tgr!tgr!prindle@nadc
From: prindle@nadc
Newsgroups: net.micro
Subject: termcaps *!#@$#!!
Message-ID: <7539@brl-tgr.ARPA>
Date: Fri, 18-Jan-85 20:35:53 EST
Article-I.D.: brl-tgr.7539
Posted: Fri Jan 18 20:35:53 1985
Date-Received: Wed, 23-Jan-85 07:55:42 EST
Sender: news@brl-tgr.ARPA
Organization: Ballistic Research Lab
Lines: 14

Does anyone know that there is a lengthy dissertation in the UNIX
manual (TERMCAP (5)) which tells you exactly how to define a termcap
entry for any terminal as long as you know what it can do, and what it
can't!  For the umpteenth time, there is no such thing as a termcap
entry for a *computer*!  There can only be a termcap entry for a
computer/terminal-emulation-program combination, and it is 99%
dependent on the terminal-emulation-program.  If you are using a dumb
terminal program, then you might as well settle for a terminal type of
"du" and use "vi" in the "open" mode; no amount of diddling with a
termcap entry will make your terminal program any smarter.  Also, even
if you define a perfect termcap entry for your computer/program combo,
many programs are hopelessly frustrated (eg. rogue) or lose
information (eg. emacs) when the screen width is less than 80 columns;
vi is the most adaptable.