Home
Main website
Display Sidebar
Hide Ads
Recent Changes
View Source:
infocmp(1)
Edit
PageHistory
Diff
Info
LikePages
infocmp !!!infocmp NAME SYNOPSIS DESCRIPTION FILES EXTENSIONS BUGS SEE ALSO AUTHOR ---- !!NAME __infocmp__ - compare or print out ''terminfo'' descriptions !!SYNOPSIS __infocmp__ [[__-dceEGgnpqrILCuV1__] [[__-v__ ''n''] [[__-s d__| __i__| __l__| __c__] [[__-w__ ''width''] [[__-A__ ''directory''] [[__-B__ ''directory''] [[''termname''...] !!DESCRIPTION __infocmp__ can be used to compare a binary __terminfo__ entry with other terminfo entries, rewrite a __terminfo__ 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, followed 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 descriptions 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. The __-d__ option 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. The __-c__ option 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. The __-n__ option 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 anything 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. 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 parameterized strings can be changed to the __termcap__ format. __infocmp__ will attempt to convert most of the parameterized information, and anything not converted will be plainly marked in the output and commented 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 __terminfo__ 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 restriction, allowing all capabilities to 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 possible to convert a __terminfo__ string capability into an equivalent __termcap__ format. A subsequent conversion of the __termcap__ file back into __terminfo__ format will not necessarily reproduce the original __terminfo__ source. Some common __terminfo__ parameter sequences, their __termcap__ equivalents, and some terminal types which commonly have such sequences, are: __Use= Option [[-u]__ The __-u__ option 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 relative 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. __Changing Databases [[-A__ ''directory''] [[-B ''directory''] 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, in __/usr/share/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. __Other Options [[-s d|i|l|c] [[-1FTVefip] [[-Rsubset] [[-v__ ''n''] [[-w ''width''] The __-s__ option 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. __-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. __-F__ compare terminfo files. This assumes that two following arguments are filenames. The files are searched for pairwise matches between entries, with two entries considered to match if any of their names do. The report printed to standard output lists entries with no matches in the other file, and entries with more than one match. For entries with exactly one match it includes a difference report. Normally, to reduce the volume of the report, use references are not resolved before looking for differences, but resolution can be forced by also specifying __-r__. __-G__ Display constant literals in decimal form rather than their character equivalents. __-a__ tells __infocmp__ to retain commented-out capabilities rather than discarding them. Capabilities are commented by prefixing them with a period. __-q__ Make the comparison listing shorter by omitting subheadings, and using __-R__''subset'' Restrict output to a given subset. This option is for use with archaic versions of terminfo like those on SVr1, Ultrix, or HP/UX that do not support the full set of SVR4/XSI Curses terminfo; and variants such as AIX that have their own extensions incompatible with SVr4/XSI. Available terminfo subsets are terminfo__(5) for details. You can also choose the subset __ __-T__ eliminates size-restrictions on the generated text. This is mainly useful for testing and analysis, since the compiled descriptions are limited (e.g., 1023 for termcap, 4096 for terminfo). __-V__ reports the version of ncurses which was used in this program, and exits. __-e__ Dump the capabilities of the given terminal as a C initializer for a TERMTYPE structure (the terminal capability structure in the ____). This option is useful for preparing versions of the curses library hardwired for a given terminal type. __-E__ Dump the capabilities of the given terminal as tables, needed in the C initializer for a TERMTYPE structure (the terminal capability structure in the ____). This option is useful for preparing versions of the curses library hardwired for a given terminal type. The tables are all declared static, and are named according to the type and the name of the corresponding terminal entry. Before ncurses 5.0, the split between the __-e__ and __-E__ options was not needed; but support for extended names required making the arrays of terminal capabilities separate from the TERMTYPE structure. __-f__ Display complex terminfo strings which contain if/then/else/endif expressions indented for readability. __-g__ Display constant character literals in quoted form rather than their decimal equivalents. __-i__ Analyze the initialization (__is1__, __is2__, __is3__), and reset (__rs1__, __rs2__, __rs3__), strings in the entry. For each string, the code tries to analyze it into actions in terms of the other capabilities in the entry, certain X3.64/ISO 6429/ECMA-48 capabilities, and certain DEC VT-series private modes (the set of recognized special sequences has been selected for completeness over the existing terminfo database). Each report line consists of the capability name, followed by a colon and space, followed by a printable expansion of the capability string with sections matching recognized actions translated into {}-bracketed descriptions. Here is a list of the DEC/ANSI special sequences recognized: It also recognizes a SGR action corresponding to ANSI/ISO 6429/ECMA Set Graphics Rendition, with the values NORMAL, BOLD, UNDERLINE, BLINK, and REVERSE. All but NORMAL may be prefixed with `+' (turn on) or `-' (turn off). An SGR0 designates an empty highlight sequence (equivalent to {SGR:NORMAL}). __-p__ Ignore padding specifications when comparing strings. __-v__ ''n'' prints out tracing information on standard error as the program runs. Higher values of n induce greater verbosity. __-w__ ''width'' changes the output to ''width'' characters. !!FILES /usr/share/terminfo Compiled terminal description database. !!EXTENSIONS The __-E__, __-F__, __-G__, __-R__, __-T__, __-V__, __-a__, __-e__, __-f__, __-g__, __-i__, __-p__, and __-q__ options are not supported in SVr4 curses. The __-r__ option's notion of `termcap' capabilities is System V Release 4's. Actual BSD curses versions will have a more restricted set. To see only the 4.4BSD set, use -r -RBSD. !!BUGS The -F option of __infocmp__(1M) should be a __toe__(1M) mode. !!SEE ALSO __infocmp__(1M), __captoinfo__(1M), __infotocap__(1M), __tic__(1M), __toe__(1M), __curses__(3X), terminfo(5). !!AUTHOR Eric S. Raymond ----
2 pages link to
infocmp(1)
:
term(7)
Man1i
This page is a man page (or other imported legacy content). We are unable to automatically determine the license status of this page.
