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
+ 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 termnames are specified,
- the -I option will be assumed. If more than one termname is specified,
- the -d option will be assumed.
+ 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.
-
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 depends on the type of the
- capability:
+ 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:
- oF for missing boolean variables
+ oF for missing Boolean variables
oNULL for missing integer or string variables
@@ -111,22 +111,22 @@
option to add the BSD-compatibility capabilities (names prefixed
with "OT").
- If no termnames are given, infocmp uses the environment variable
- TERM for each of the termnames.
+ If no terminal-types are given, infocmp uses the environment
+ variable TERM for each of the terminal-types.
-
The -I, -L, and -C options will produce a source listing for each
terminal named.
- -I use the terminfo names
- -L use the long C variable name listed in <term.h>
- -C use the termcap names
- -r when using -C, put out all capabilities in termcap form
- -K modifies the -C option, improving BSD-compatibility.
+ -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 termnames are given, the environment variable TERM will be used
- for the terminal name.
+ 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
@@ -168,41 +168,43 @@
Some common terminfo parameter sequences, their termcap equivalents,
and some terminal types which commonly have such sequences, are:
- terminfotermcap Representative Terminals
- ---------------------------------------------------------------
- %p1%c%. adm
- %p1%d%d hp, ANSI standard, vt100
- %p1%'x'%+%c%+x concept
- %i%iq ANSI standard, vt100
- %p1%?%'x'%>%t%p1%'y'%+%;%>xy concept
- %p2 is printed before %p1%r hp
+ terminfotermcap 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 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.
+ 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
+ infocmp 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 termname, but one of the other termname entries contains a
- value for it. A capability's value will be 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
+ 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 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.
+ 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.
@@ -212,22 +214,22 @@
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 termnameuse= fields that
- were not needed.
+ are superfluous. infocmp will flag any other terminal-typeuse= fields
+ that were not needed.
ChangingDatabases[-Adirectory] [-B directory]
- Like other ncurses utilities, infocmp looks for the terminal
- descriptions in several places. You can use the TERMINFO and
- TERMINFO_DIRS environment variables to override the compiled-in default
+ Like other ncurses utilities, infocmp 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 FetchingCompiledDescriptions 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:
- o The -A option sets the location for the first termname
+ o The -A option sets the location for the first terminal-type
- o The -B option sets the location for the other termnames.
+ o The -B option sets the location for the other terminal-types.
Using these options, it is possible to compare descriptions for a
terminal with the same name located in two different databases. For
@@ -257,7 +259,7 @@
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
+ 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.
@@ -311,9 +313,8 @@
LL home-down
RSR reset scroll region
-----------------------------------------
- DECSTR soft reset (VT320)
-
+ DECSTR soft reset (VT320)
S7C1T 7-bit controls (VT220)
-----------------------------------------
ISO DEC G0 enable DEC graphics for G0
@@ -367,7 +368,7 @@
3 hexadecimal and base64
For example, this prints the compiled terminfo value as a string
- which could be assigned to the TERMINFO environment variable:
+ which could be assigned to the TERMINFO environment variable:
infocmp -0 -q -Q2
@@ -440,14 +441,14 @@
contents of two source files, since it excludes the inferences
that infocmp makes to fill in missing data.
- -V reports the version of ncurses which was used in this program, and
+ -V reports the version of ncurses which was used in this program, and
exits.
-vn prints out tracing information on standard error as the program
runs.
The optional parameter n is a number from 1 to 10, inclusive,
- indicating the desired level of detail of information. If ncurses
+ indicating the desired level of detail of information. If ncurses
is built without tracing support, the optional parameter is
ignored.
@@ -457,13 +458,34 @@
-wwidth
changes the output to width characters.
- -x print information for user-defined capabilities (see user_caps(5).
+ -x print information for user-defined capabilities (see user_caps(5).
These are extensions to the terminfo repertoire which can be
loaded using the -x option of tic.
+ 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.
+
+
+
@@ -472,7 +494,7 @@
(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 infocmp for ncurses. In addition, he added a few new
+ equivalent infocmp for ncurses. In addition, he added a few new
features such as:
o the -e option, to support fallback (compiled-in) terminal
@@ -487,51 +509,29 @@
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
+ 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 -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.
+ adapted from ncurses.
- Eric S. Raymond <esr@snark.thyrsus.com> and
- Thomas E. Dickey <dickey@invisible-island.net>
-
-ncurses 6.4 2023-09-16 infocmp(1m)
+ncurses 6.5 2024-05-11 infocmp(1m)