Query: captoinfo
OS: hpux
Section: 1m
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
captoinfo(1M) captoinfo(1M)NAMEcaptoinfo - convert a termcap description into a terminfo descriptionSYNOPSISn] [filenames]DESCRIPTIONlooks 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 entry, a holdover from Version 6 UNIX, is removed. Any description that is expressed relative to another description (as specified in the tc= field) is reduced to the minimum superset before output. If no filename is given, the environment variable is used for the filename or entry. If is a full pathname to a file, only the terminal whose name is specified in the environment variable is extracted from that file. If the environment variable is not set, the file is read. Options captoinfo recognizes the following options: 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. Print (verbose) tracing information as the program runs. Additional options print more information (for example or Change the output width to n characters.DIAGNOSTICSThe termcap entry is not valid. In particular, check for an invalid 'tc=' entry. The termcap description had an entry for 'cc' whose type was not boolean, numeric or string. The boolean termcap entry 'cc' was entered as a numeric or string capability. An unknown termcap code was specified. The terminal type specified could not be found in the termcap file. The termcap code was specified as a null string. The correct way to cancel an entry is with an as in Giving a null string could cause incorrect assumptions to be made by any software that uses termcap or terminfo. 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. A key that could not be handled was specified in the 'ko' capability. The 'ma' capability specified a function key with a value different from that specified in another setting of the same key. A vi key unknown to captoinfo was specified in the 'ma' capability. assumes that the sg (now xmc) and ug values were the same. The parameterized string being created should be rewritten by hand. The terminal type was null. This occurs when is null or not set. The specified file could not be opened. This termcap capability is no longer supported in terminfo, and therefore cannot be translated.WARNINGSCertain defaults are assumed to be true. For example, the bell character bel) is assumed to be The linefeed capability nl) is assumed to be the same for both and cud1 and ind, respectively). Padding information is assumed to belong at the end of the string. The algorithm used to expand parameterized information for fields such as cm, cup) sometimes produces a string which, though technically correct, may not be optimal. In particular, the rarely used operation 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.AUTHORwas developed by AT&T.SEE ALSOtic(1M), untic(1M), termcap(3X), terminfo(4), infocmp(1M). captoinfo(1M)
Related Man Pages |
---|
captoinfo(1m) - mojave |
captoinfo(1m) - opensolaris |
captoinfo(1) - debian |
captoinfo(1m) - opendarwin |
captoinfo(1) - netbsd |
Similar Topics in the Unix Linux Community |
---|
Help on captoinfo command |
no entry in termcap for 'hp' |
VI Editor issue "E558: Terminal entry not found in terminfo" |