captoinfo.1m (2010 09)

c
captoinfo(1M) captoinfo(1M)
NAME
captoinfo - convert a termcap description into a terminfo description
SYNOPSIS
captoinfo [-1v][-wn][filenames ]
DESCRIPTION
captoinfo looks in filenames for termcap (3X) descriptions. For each one found, an equivalent ter-
minfo(4) description is written to standard output along with any comments found. The short two letter
name at the beginning of the list of names in a
termcap entry, a holdover from Version 6 UNIX, is
removed. Any description that is expressed relative to another description (as specified in the
termcap
tc= field) is reduced to the minimum superset before output.
If no filename is given, the environment variable
TERMCAP is used for the filename or entry. If TERMCAP
is a full pathname to a file, only the terminal whose name is specified in the environment variable
TERM
is extracted from that file. If the environment variable
TERMCAP is not set, the file
/usr/share/lib/termcap
is read.
Options
captoinfo recognizes the following options:
-1 Print one field per line. If this option is not selected, multiple fields are printed on each line
up to a maximum width of 60 characters.
-v Print (verbose) tracing information as the program runs. Additional -v options print more
information (for example -v -v -v or -vvv).
-wn Change the output width to n characters.
DIAGNOSTICS
tgetent failed with return code n (reason).
The termcap entry is not valid. In particular, check for an invalid ’tc=’ entry.
unknown type given for the termcap code ’cc’.
The termcap description had an entry for ’cc’ whose type was not boolean, numeric or string.
wrong type given for the boolean (numeric, string) termcap code ’cc’.
The boolean termcap entry ’cc’ was entered as a numeric or string capability.
the boolean (numeric, string) termcap code ’cc’ is not a valid name.
An unknown termcap code was specified.
tgetent failed on TERM=term.
The terminal type specified could not be found in the termcap file.
TERM=term: cap cc (info ii) is NULL: REMOVED
The termcap code was specified as a null string. The correct way to cancel an entry is with an
@,asin:bs@:. Giving a null string could cause incorrect assumptions to be made by any
software that uses termcap or terminfo.
a function key for ’cc’ was specified, but it already has the value ’vv’.
When parsing the ’ko’ capability, the key ’cc’ was specified as having the same value as the
capability ’cc’, but the key ’cc’ already had a value assigned to it.
the unknown termcap name ’cc’ was specified in the ’ko’ termcap capability.
A key that could not be handled was specified in the ’ko’ capability.
the vi character ’v’ (info ’ii’) has the value ’xx’, but ’ma’ gives ’n’.
The ’ma’ capability specified a function key with a value different from that specified in
another setting of the same key.
the unknown vi key ’v’ was specified in the ’ma’ termcap capability.
A vi key unknown to captoinfo was specified in the ’ma’ capability.
Warning: termcap sg (nn) and termcap ug (nn) had different values.
terminfo assumes that the sg (now xmc) and ug values were the same.
Warning: the string produced for ’ii’ may be inefficient.
The parameterized string being created should be rewritten by hand.
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1