ginfocmp(1M) | User commands | ginfocmp(1M) |
ginfocmp - compare or print out terminfo descriptions
ginfocmp [-1cCdDeEFgGiIKlLnpqrtTuUVWx]
[-v n] [-s d| i| l| c] [-Q
n] [-R subset]
[-w width] [-A directory]
[-B directory]
[terminal-type ...]
ginfocmp 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.
If no options are specified and zero or one terminal-types are specified, the -I option will be assumed. If more than one terminal-type is specified, the -d option will be assumed.
ginfocmp compares the terminfo description of the first terminal terminal-type with each of the descriptions given by the entries for the other terminal's terminal-types. If a capability is defined for only one of the terminals, the value returned depends on the type of the capability:
Use the -q option to show the distinction between absent and cancelled capabilities.
These options produce a list which you can use to compare two or more terminal descriptions:
The -I, -L, and -C options will produce a source listing for each terminal named.
-I | use terminfo capability codes |
-L | use “long” capability names |
-C | use termcap capability codes |
-r | with -C, include nonstandard capabilities |
-K | with -C, improve BSD compatibility |
If no terminal-types 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. ginfocmp 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.
For best results when converting to termcap format, you should use both -C and -r. Normally a termcap description is limited to 1023 bytes. ginfocmp trims away less essential parts to make it fit. If you are converting to one of the (rare) termcap implementations which accept an unlimited size of termcap, you may want to add the -T option. More often however, you must help the termcap implementation, and trim excess whitespace (use the -0 option for that).
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. Normally you would use both the -C and -r options. The actual format used incorporates some improvements for escaped characters from terminfo format. For a stricter BSD-compatible translation, use the -K option rather than -C.
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:
terminfo | termcap | Terminal Types |
%p1%c | %. | ansi-m |
%p1%d | %d | ansi, vt100 |
%p1%' '%+%c | %+x | vt52 |
%i | %iq | ansi, vt100 |
%p1%?%'x'%>%t%p1%'y'%+%; | %>xy | annarbor4080 |
%p2...%p1 | %r | hpgeneric |
The -u option produces a terminfo source description of the first terminal terminal-type which is relative to the sum of the descriptions given by the entries for the other terminal-types. It does this by analyzing the differences between the first terminal-types and the other terminal-types 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 ginfocmp will show what can be done to change one description to be relative to the other.
A capability will be printed with an at-sign (@) if it no longer exists in the first terminal-type, but one of the other terminal-type entries contains a value for it. A capability's value will be printed if the value in the first terminal-type is not found in any of the other terminal-type entries, or if the first of the other terminal-type entries that has this capability gives a different value for the capability than that in the first terminal-type.
The order of the other terminal-type entries is significant. Since the terminfo compiler gtic 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. ginfocmp will flag any such inconsistencies between the other terminal-type 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 ginfocmp 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. ginfocmp will flag any other terminal-type use= fields that were not needed.
Like other ncurses utilities, ginfocmp looks for the terminal descriptions in several places. You can use the TERMINFO and TERMINFO_DIRS environment variables to override the compiled-in default list of places to search. See curses(3X), as well as the Fetching Compiled Descriptions section in terminfo(5).
You can also use the options -A and -B to override the list of places to search when comparing terminal descriptions:
Using these options, it is possible to compare descriptions for a terminal with the same name located in two different databases. For instance, you can use this feature for comparing descriptions for the same terminal created by different people.
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.
Action | Meaning |
RIS | full reset |
SC | save cursor |
RC | restore cursor |
LL | home-down |
RSR | reset scroll region |
DECSTR | soft reset (VT320) |
S7C1T | 7-bit controls (VT220) |
ISO DEC G0 | enable DEC graphics for G0 |
ISO UK G0 | enable UK chars for G0 |
ISO US G0 | enable US chars for G0 |
ISO DEC G1 | enable DEC graphics for G1 |
ISO UK G1 | enable UK chars for G1 |
ISO US G1 | enable US chars for G1 |
DECPAM | application keypad mode |
DECPNM | normal keypad mode |
DECANSI | enter ANSI mode |
ECMA[+-]AM | keyboard action mode |
ECMA[+-]IRM | insert replace mode |
ECMA[+-]SRM | send receive mode |
ECMA[+-]LNM | linefeed mode |
DEC[+-]CKM | application cursor keys |
DEC[+-]ANM | set VT52 mode |
DEC[+-]COLM | 132-column mode |
DEC[+-]SCLM | smooth scroll |
DEC[+-]SCNM | reverse video mode |
DEC[+-]OM | origin mode |
DEC[+-]AWM | wraparound mode |
DEC[+-]ARM | auto-repeat mode |
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
ginfocmp -0 -q -Q2
The -0, -1, -E, -F, -G, -Q, -R, -T, -V, -a, -e, -f, -g, -i, -l, -p, -q and -t options are not supported in SVr4 curses.
SVr4 infocmp does not distinguish between absent and cancelled capabilities. Also, it shows missing integer capabilities as -1 (the internal value used to represent missing integers). This implementation shows those as “NULL”, for consistency with missing strings.
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.
X/Open Curses, Issue 7 (2009) provides a description of infocmp. It does not mention the options used for converting to termcap format.
Although System V Release 2 provided a terminfo library, it had no documented tool for decompiling the terminal descriptions. Tony Hansen (AT&T) wrote the first infocmp in early 1984, for System V Release 3.
Eric Raymond used the AT&T documentation in 1995 to provide an equivalent ginfocmp for ncurses. In addition, he added a few new features such as:
Later, Thomas Dickey added the -x (user-defined capabilities) option, and the -E option to support fallback entries with user-defined capabilities.
For a complete list, see the EXTENSIONS section.
In 2010, Roy Marples provided an infocmp program for NetBSD. It is less capable than the SVr4 or ncurses versions (e.g., it lacks the sorting options documented in X/Open), but does include the -x option adapted from ncurses.
The -F option of ginfocmp(1M) should be a gtoe(1M) mode.
Eric S. Raymond <esr@snark.thyrsus.com> and
Thomas E. Dickey <dickey@invisible-island.net>
gcaptoinfo(1M), ginfotocap(1M), gtic(1M), gtoe(1M), curses(3X), terminfo(5), user_caps(5)
https://invisible-island.net/ncurses/tctest.html
2024-05-11 | ncurses 6.5 |