infocmp.1m (2010 09)

i
infocmp(1M) infocmp(1M)
terminfo termcap Representative Terminals
%p1%c %. adm
%p1%d %d hp, ANSI standard, vt100
%p1%’x’%+%c %+x concept
%i %i ANSI standard, vt100
%p1%?%’x’%>%t%p1%’y’%+%; %>xy concept
%p2 is printed before %p1 %r hp
Use= Option: -u
-u produces a terminfo source description of the first terminal termname which is relative to
the sum of the descriptions given by the entries for the other terminals termnames . It does
this by analyzing the differences between the first termname and the other termnames and
producing a description with
use= fields for the other terminals. In this manner, it is possible
to retrofit generic terminfo entries into a terminal’s description. Or, if two similar terminals
exist, but were coded at different times or by different people so that each description is a full
description, using infocmp will show what can be done to change one description to be rela-
tive to the other.
A capability will get printed with an at-sign (@) if it no longer exists in the first termname , but one of the
other termname entries contains a value for it. A capability’s value gets printed if the value in the first
termname is not found in any of the other termname entries, or if the first of the other termname entries
that has this capability gives a different value for the capability than that in the first termname .
The order of the other termname entries is significant. Since the terminfo compiler
tic does a left-to-
right scan of the capabilities, specifying two
use= entries that contain differing entries for the same
capabilities will produce different results depending on the order that the entries are given in.
infocmp
will flag any such inconsistencies between the other termname entries as they are found.
Alternatively, specifying a capability after a
use= entry that contains that capability will cause the
second specification to be ignored. Using
infocmp to recreate a description can be a useful check to
make sure that everything was specified correctly in the original source description.
Another error that does not cause incorrect compiled files, but will slow down the compilation time, is
specifying extra
use= fields that are superfluous. infocmp will flag any other termname
use= fields
that were not needed.
Other Options: -s, -v, -V, -1, -w
-s sorts the fields within each type according to the argument below:
d leave fields in the order that they are stored in the terminfo database.
i sort by terminfo name.
l sort by the long C variable name.
c sort by the termcap name.
If the
-s option is not given, the fields printed out will be sorted alphabetically by the terminfo
name within each type, except in the case of the -C or the -L options, which cause the sorting to be
done by the termcap name or the long C variable name, respectively.
-v prints out tracing information on standard error as the program runs.
-V prints out the version of the program in use on standard error and exit.
-1 causes the fields to be printed out one to a line. Otherwise, the fields will be printed several to a
line to a maximum width of 60 characters.
-w changes the output to width characters.
Changing Databases: -A, -B
The location of the compiled
terminfo database is taken from the environment variable TERMINFO.If
the variable is not defined, or the terminal is not found in that location, the system terminfo database,
usually in /usr/lib/terminfo, will be used. The options -A and -B may be used to override this
location. The -A option will set TERMINFO for the first termname and the -B option will set TERMINFO
for the other termnames . With this, it is possible to compare descriptions for a terminal with the same
name located in two different databases. This is useful for comparing descriptions for the same terminal
created by different people.
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010