captoinfo - convert a termcap description into a terminfo description
captoinfo [-1v] [-wn] [filenames]
captoinfo looks in filenames for termcap(3X) descriptions. For each
one found, an equivalent terminfo(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.
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.
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
the boolean (numeric, string) termcap code 'cc' is not a valid name.
An unknown termcap code was specified.
Hewlett-Packard Company - 1 - HP-UX Release 11i: November 2000
tgetent failed on TERM=term.
The terminal type specified could not be found in the
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 @, as in :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'
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
the unknown vi key 'v' was specified in the 'ma' termcap capability.
A vi key unknown to captoinfo was specified in the 'ma'
Warning: termcap sg (nn) and termcap ug (nn) had different values.
terminfo assumes that the sg (now xmc) and ug values were
Warning: the string produced for 'ii' may be inefficient.
The parameterized string being created should be rewritten
Null termname given.
The terminal type was null. This occurs when $TERM is null
or not set.
cannot open "file" for reading.
The specified file could not be opened.
Warning: cannot translate capability (unsupported in terminfo).
This termcap capability is no longer supported in terminfo,
and therefore cannot be translated.
Certain termcap defaults are assumed to be true. For example, the
bell character (terminfo bel) is assumed to be ^G. The linefeed
capability (termcap nl) is assumed to be the same for both cursor_down
Hewlett-Packard Company - 2 - HP-UX Release 11i: November 2000
and scroll_forward (terminfo cud1 and ind, respectively). Padding
information is assumed to belong at the end of the string.
The algorithm used to expand parameterized information for termcap
fields such as cursor_position (termcap cm, terminfo cup) sometimes
produces a string which, though technically correct, may not be
optimal. In particular, the rarely used termcap operation %n produces
strings that are especially long. Most occurrences of these less than
optimal strings are flagged with a warning message, and may need to be
recoded by hand.
HP supports only terminals listed on the current list of supported
devices. However, the terminfo database contains both supported and
nonsupported terminals. If you use nonsupported terminals, they may
not work correctly.
captoinfo was developed by AT&T.
tic(1M), untic(1M), curses(3X), termcap(3X), terminfo(4), infocmp(1M).
Hewlett-Packard Company - 3 - HP-UX Release 11i: November 2000