HP-UX Reference (11i v1 00/12) - 1M System Administration Commands A-M (vol 3)
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1m/!!!intro.1m
________________________________________________________________
___ ___
i
infocmp(1M) infocmp(1M)
NAME
infocmp - compare or print out terminfo descriptions
SYNOPSIS
infocmp [-d][-c][-n][-I][-L][-C][-r][-u][-s d|i|l|c][-v][-V][-1]
[-w width][-A directory][-B directory][termname... ]
DESCRIPTION
infocmp can be used to compare a binary terminfo entry with other terminfo entries, rewrite a ter-
minfo
description to take advantage of the use= terminfo field, or print out a terminfo description
from the binary file (term) in a variety of formats. In all cases, the boolean fields will be printed first, fol-
lowed by the numeric fields, followed by the string fields.
Default Options
If no options are specified and zero or one termnames are specified, the -I option will be assumed. If more
than one termname is specified, the -d option will be assumed.
Comparison Options [-d] [-c] [-n]
infocmp compares the terminfo description of the first terminal termname with each of the descrip-
tions given by the entries for the other terminal’s termnames. If a capability is defined for only one of the
terminals, the value returned will depend on the type of the capability:
F for boolean variables, -1 for
integer variables, and
NULL for string variables.
-d produces a list of each capability that is different between two entries. This option is useful to show
the difference between two entries, created by different people, for the same or similar terminals.
-c produces a list of each capability that is common between two entries. Capabilities that are not set
are ignored. This option can be used as a quick check to see if the
-u option is worth using.
-n produces a list of each capability that is in neither entry. If no termnames are given, the environment
variable
TERM will be used for both of the termnames. This can be used as a quick check to see if any-
thing was left out of a description.
Source Listing Options [-I] [-L] [-C] [-r]
The -I, -L, and -C options will produce a source listing for each terminal named.
-I use the terminf names
-L use the long C variable name listed in <term.h>
-C use the termcap names
-r when using -C, put out all capabilitiesin termcap form
If no termnames are given, the environment variable TERM will be used for the terminal name.
The source produced by the -C option may be used directly as a termcap entry, but not all of the
parameterized strings may be changed to th termcap format. infocmp will attempt to convert most of
the parameterized information, but anything not converted will be plainly marked in the output and com-
mented out. These should be edited by hand.
All padding information for strings will be collected together and placed at the beginning of the string
where termcap expects it. Mandatory padding (padding information with a trailing ’/’) will become
optional.
All termcap variables no longer supported by terminfo, but which are derivable from other ter-
minfo
variables, will be output. Not all terminfo capabilities will be translated; only those variables
which were part of termcap will normally be output. Specifying the -r option will take off this restric-
tion, allowing all capabilitiesto be output in termcap form.
Note that because padding is collected to the beginning of the capability, not all capabilities are output.
Mandatory padding is not supported. Because termcap strings are not as flexible, it is not always possi-
ble to convert a terminfo string capability into an equivalent termcap format. A subsequent conver-
sion of the termcap file back into terminfo format will not necessarily reproduce the original ter-
minfo
source.
Some common terminfo parameter sequences, their termcap equivalents, and some terminal types
which commonly have such sequences, are:
HP-UX Release 11i: December 2000 − 1 − Section 1M−−345
___
___