Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!quintus!ok
From: ok@quintus.uucp (Richard A. O'Keefe)
Newsgroups: comp.unix.wizards
Subject: Re: Re^2: terminfo
Message-ID: <353@quintus.UUCP>
Date: 5 Sep 88 09:53:41 GMT
References: <508@altos86.UUCP> <8377@smoke.ARPA> <1553@mcgp1.UUCP> <8412@smoke.ARPA> <24729@bu-cs.BU.EDU> <4034@freja.dk>
Sender: news@quintus.UUCP
Reply-To: ok@quintus.UUCP (Richard A. O'Keefe)
Organization: Quintus Computer Systems, Inc.
Lines: 13

In article <4034@freja.dk> kimcm@freja.dk (Kim Christian Madsen) writes:
>madd@bu-cs.BU.EDU (Jim Frost) writes:
>How about running the infocmp command to give you a terminfo file in
>plain ascii -- just like the good ole termcap file, edit whatever you
>like and bring it back to binary again.  Not very complicated -- The
>most complicated part is to discover the infocmp command.
>
Very complicated indeed:  infocmp is not described in Issue 2 of the
System V Interface Definition, and it is not part of System V Release
2.  You can get at *some* of the attributes with the aid of 'tput',
but not the cursor motion strings.
[Does anyone know why the index entry for "tic command" in the SVID
-- on page 462 of Volume II -- refers to page 246?  That's "clri"!]