{
    "mode": "man",
    "parameter": "infocmp",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/infocmp/1/json",
    "generated": "2026-06-12T13:13:15Z",
    "synopsis": "infocmp [-1CDEFGIKLTUVWcdegilnpqrtux]\n[-v n] [-s d| i| l| c] [-Q n] [-R subset]\n[-w width] [-A directory] [-B directory]\n[termname...]",
    "sections": {
        "NAME": {
            "content": "infocmp - compare or print out terminfo descriptions\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "infocmp [-1CDEFGIKLTUVWcdegilnpqrtux]\n[-v n] [-s d| i| l| c] [-Q n] [-R subset]\n[-w width] [-A directory] [-B directory]\n[termname...]\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "infocmp can be used to compare a binary terminfo entry with other terminfo entries, rewrite a\nterminfo description to take advantage of the use= terminfo field, or print  out  a  terminfo\ndescription  from  the binary file (term) in a variety of formats.  In all cases, the boolean\nfields will be printed first, followed by the numeric fields, followed by the string fields.\n",
            "subsections": [
                {
                    "name": "Default Options",
                    "content": "If no options are specified and zero or one termnames are specified, the -I  option  will  be\nassumed.  If more than one termname is specified, the -d option will be assumed.\n"
                },
                {
                    "name": "Comparison Options [-d] [-c] [-n]",
                    "content": "infocmp compares the terminfo description of the first terminal termname with each of the de‐\nscriptions given by the entries for the other terminal's termnames.  If a capability  is  de‐\nfined  for  only one of the terminals, the value returned depends on the type of the capabil‐\nity:\n\n•   F for missing boolean variables\n\n•   NULL for missing integer or string variables\n\nUse the -q option to show the distinction between absent and cancelled capabilities.\n\nThese options produce a list which you can use to compare two or more terminal descriptions:\n"
                },
                {
                    "name": "-d",
                    "content": "the  list  shows “:” after the capability name, followed by the capability values, sepa‐\nrated by a comma.\n",
                    "flag": "-d"
                },
                {
                    "name": "-c",
                    "content": "capabilities  are  ignored.   Each item in the list shows “=” after the capability name,\nfollowed by the capability value.\n\nThe -u option provides a related output, showing the first terminal description  rewrit‐\nten to use the second as a building block via the “use=” clause.\n",
                    "flag": "-c"
                },
                {
                    "name": "-n",
                    "content": "the list shows “!” before the capability name.\n\nNormally only the conventional capabilities are shown.  Use the -x  option  to  add  the\nBSD-compatibility capabilities (names prefixed with “OT”).\n\nIf  no  termnames  are given, infocmp uses the environment variable TERM for each of the\ntermnames.\n",
                    "flag": "-n"
                },
                {
                    "name": "Source Listing Options [-I] [-L] [-C] [-r]",
                    "content": "The -I, -L, and -C options will produce a source listing for each terminal named.\n\n-I   use the terminfo names\n-L   use the long C variable name listed in <term.h>\n-C   use the termcap names\n-r   when using -C, put out all capabilities in termcap form\n-K   modifies the -C option, improving BSD-compatibility.\n\nIf no termnames are given, the environment variable TERM will be used for the terminal name.\n\nThe source produced by the -C option may be used directly as a termcap entry, but not all pa‐\nrameterized  strings  can  be changed to the termcap format.  infocmp will attempt to convert\nmost of the parameterized information, and anything not converted will be plainly  marked  in\nthe output and commented out.  These should be edited by hand.\n\nFor  best results when converting to termcap format, you should use both -C and -r.  Normally\na termcap description is limited to 1023 bytes.  infocmp trims away less essential  parts  to\nmake it fit.  If you are converting to one of the (rare) termcap implementations which accept\nan unlimited size of termcap, you may want to add the -T option.   More  often  however,  you\nmust  help  the  termcap  implementation,  and  trim excess whitespace (use the -0 option for\nthat).\n\nAll padding information for strings will be collected together and placed at the beginning of\nthe  string where termcap expects it.  Mandatory padding (padding information with a trailing\n“/”) will become optional.\n\nAll termcap variables no longer supported by terminfo, but which  are  derivable  from  other\nterminfo  variables,  will be output.  Not all terminfo capabilities will be translated; only\nthose variables which were part of termcap will normally be output.  Specifying the -r option\nwill take off this restriction, allowing all capabilities to be output in termcap form.  Nor‐\nmally you would use both the -C and -r options.  The actual format used incorporates some im‐\nprovements for escaped characters from terminfo format.  For a stricter BSD-compatible trans‐\nlation, use the -K option rather than -C.\n\nNote that because padding is collected to the beginning of the capability, not all  capabili‐\nties  are  output.   Mandatory  padding is not supported.  Because termcap strings are not as\nflexible, it is not always possible to convert a terminfo string capability into  an  equiva‐\nlent  termcap  format.  A subsequent conversion of the termcap file back into terminfo format\nwill not necessarily reproduce the original terminfo source.\n\nSome common terminfo parameter sequences, their termcap equivalents, and some terminal  types\nwhich commonly have such sequences, are:\n\nterminfo                    termcap   Representative Terminals\n───────────────────────────────────────────────────────────────\n%p1%c                       %.        adm\n%p1%d                       %d        hp, ANSI standard, vt100\n%p1%'x'%+%c                 %+x       concept\n%i                          %iq       ANSI standard, vt100\n%p1%?%'x'%>%t%p1%'y'%+%;    %>xy      concept\n%p2 is printed before %p1   %r        hp\n"
                },
                {
                    "name": "Use= Option [-u]",
                    "content": "The  -u option produces a terminfo source description of the first terminal termname which is\nrelative to the sum of the  descriptions  given  by  the  entries  for  the  other  terminals\ntermnames.   It  does  this  by  analyzing the differences between the first termname and the\nother termnames and producing a description with use= fields for  the  other  terminals.   In\nthis  manner,  it is possible to retrofit generic terminfo entries into a terminal's descrip‐\ntion.  Or, if two similar terminals exist, but were coded at different times or by  different\npeople  so  that  each description is a full description, using infocmp will show what can be\ndone to change one description to be relative to the other.\n\nA capability will be printed with an at-sign  (@)  if  it  no  longer  exists  in  the  first\ntermname,  but  one  of  the  other termname entries contains a value for it.  A capability's\nvalue will be printed if the value in the first termname is not found in  any  of  the  other\ntermname  entries,  or  if  the  first of the other termname entries that has this capability\ngives a different value for the capability than that in the first termname.\n\nThe order of the other termname entries is significant.  Since the terminfo compiler tic does\na  left-to-right scan of the capabilities, specifying two use= entries that contain differing\nentries for the same capabilities will produce different results depending on the order  that\nthe  entries  are  given  in.   infocmp  will flag any such inconsistencies between the other\ntermname entries as they are found.\n\nAlternatively, specifying a capability after a use= entry that contains that capability  will\ncause the second specification to be ignored.  Using infocmp to recreate a description can be\na useful check to make sure that everything was specified correctly in  the  original  source\ndescription.\n\nAnother  error  that does not cause incorrect compiled files, but will slow down the compila‐\ntion time, is specifying extra use= fields that are superfluous.  infocmp will flag any other\ntermname use= fields that were not needed.\n\nChanging Databases [-A directory] [-B directory]\nLike  other ncurses utilities, infocmp looks for the terminal descriptions in several places.\nYou can use the TERMINFO and TERMINFODIRS environment variables to override the  compiled-in\ndefault list of places to search (see curses(3X) for details).\n\nYou  can also use the options -A and -B to override the list of places to search when compar‐\ning terminal descriptions:\n\n•   The -A option sets the location for the first termname\n\n•   The -B option sets the location for the other termnames.\n\nUsing these options, it is possible to compare descriptions for a terminal with the same name\nlocated in two different databases.  For instance, you can use this feature for comparing de‐\nscriptions for the same terminal created by different people.\n"
                },
                {
                    "name": "Other Options",
                    "content": ""
                },
                {
                    "name": "-0",
                    "content": "",
                    "flag": "-0"
                },
                {
                    "name": "-1",
                    "content": "printed several to a line to a maximum width of 60 characters.\n",
                    "flag": "-1"
                },
                {
                    "name": "-a",
                    "content": "bilities are commented by prefixing them with a period.\n",
                    "flag": "-a"
                },
                {
                    "name": "-D",
                    "content": "",
                    "flag": "-D"
                },
                {
                    "name": "-E",
                    "content": "TERMTYPE  structure (the terminal capability structure in the <term.h>).  This option is\nuseful for preparing versions of the curses library hardwired for a given terminal type.\nThe  tables are all declared static, and are named according to the type and the name of\nthe corresponding terminal entry.\n\nBefore ncurses 5.0, the split between the -e and -E options was not needed; but  support\nfor extended names required making the arrays of terminal capabilities separate from the\nTERMTYPE structure.\n",
                    "flag": "-E"
                },
                {
                    "name": "-e",
                    "content": "(the  terminal capability structure in the <term.h>).  This option is useful for prepar‐\ning versions of the curses library hardwired for a given terminal type.\n",
                    "flag": "-e"
                },
                {
                    "name": "-F",
                    "content": "files  are searched for pairwise matches between entries, with two entries considered to\nmatch if any of their names do.  The report printed to  standard  output  lists  entries\nwith  no  matches  in the other file, and entries with more than one match.  For entries\nwith exactly one match it includes a difference report.  Normally, to reduce the  volume\nof the report, use references are not resolved before looking for differences, but reso‐\nlution can be forced by also specifying -r.\n",
                    "flag": "-F"
                },
                {
                    "name": "-f",
                    "content": "for readability.\n",
                    "flag": "-f"
                },
                {
                    "name": "-G",
                    "content": "",
                    "flag": "-G"
                },
                {
                    "name": "-g",
                    "content": "lents.\n",
                    "flag": "-g"
                },
                {
                    "name": "-i",
                    "content": "entry,  as  well as those used for starting/stopping cursor-positioning mode (smcup, rm‐‐\ncup) as well as starting/stopping keymap mode (smkx, rmkx).\n\nFor each string, the code tries to analyze it into actions in terms of the  other  capa‐\nbilities  in the entry, certain X3.64/ISO 6429/ECMA-48 capabilities, and certain DEC VT-\nseries private modes (the set of recognized special sequences has been selected for com‐\npleteness  over the existing terminfo database).  Each report line consists of the capa‐\nbility name, followed by a colon and space, followed by a printable expansion of the ca‐\npability  string  with sections matching recognized actions translated into {}-bracketed\ndescriptions.\n\nHere is a list of the DEC/ANSI special sequences recognized:\n\nAction        Meaning\n─────────────────────────────────────────\nRIS           full reset\nSC            save cursor\nRC            restore cursor\nLL            home-down\nRSR           reset scroll region\n─────────────────────────────────────────\nDECSTR        soft reset (VT320)\nS7C1T         7-bit controls (VT220)\n─────────────────────────────────────────\nISO DEC G0    enable DEC graphics for G0\nISO UK G0     enable UK chars for G0\nISO US G0     enable US chars for G0\nISO DEC G1    enable DEC graphics for G1\nISO UK G1     enable UK chars for G1\nISO US G1     enable US chars for G1\n─────────────────────────────────────────\nDECPAM        application keypad mode\nDECPNM        normal keypad mode\nDECANSI       enter ANSI mode\n─────────────────────────────────────────\nECMA[+-]AM    keyboard action mode\nECMA[+-]IRM   insert replace mode\nECMA[+-]SRM   send receive mode\nECMA[+-]LNM   linefeed mode\n─────────────────────────────────────────\nDEC[+-]CKM    application cursor keys\nDEC[+-]ANM    set VT52 mode\nDEC[+-]COLM   132-column mode\nDEC[+-]SCLM   smooth scroll\nDEC[+-]SCNM   reverse video mode\nDEC[+-]OM     origin mode\nDEC[+-]AWM    wraparound mode\nDEC[+-]ARM    auto-repeat mode\n\nIt also recognizes a SGR action corresponding to ANSI/ISO 6429/ECMA Set Graphics  Rendi‐\ntion,  with  the values NORMAL, BOLD, UNDERLINE, BLINK, and REVERSE.  All but NORMAL may\nbe prefixed with\n\n•   “+” (turn on) or\n\n•   “-” (turn off).\n\nAn SGR0 designates an empty highlight sequence (equivalent to {SGR:NORMAL}).\n",
                    "flag": "-i"
                },
                {
                    "name": "-l",
                    "content": "",
                    "flag": "-l"
                },
                {
                    "name": "-p",
                    "content": "",
                    "flag": "-p"
                },
                {
                    "name": "-Q",
                    "content": "hexadecimal or base64 form, depending on the option's value:\n\n1  hexadecimal\n\n2  base64\n\n3  hexadecimal and base64\n\nFor example, this prints the compiled terminfo value as a string which could be assigned\nto the TERMINFO environment variable:\n\ninfocmp -0 -q -Q2\n",
                    "flag": "-Q"
                },
                {
                    "name": "-q",
                    "content": "•   Make the comparison listing shorter by omitting subheadings, and using “-”  for  ab‐\nsent capabilities, “@” for canceled rather than “NULL”.\n\n•   However, show differences between absent and cancelled capabilities.\n\n•   Omit the “Reconstructed from” comment for source listings.\n",
                    "flag": "-q"
                },
                {
                    "name": "-R",
                    "content": "Restrict output to a given subset.  This option is for use with archaic versions of ter‐\nminfo like those on SVr1, Ultrix, or HP-UX that do not support the full set of  SVR4/XSI\nCurses  terminfo;  and  variants such as AIX that have their own extensions incompatible\nwith SVr4/XSI.\n\n•   Available terminfo subsets are “SVr1”, “Ultrix”, “HP”, and  “AIX”;  see  terminfo(5)\nfor details.\n\n•   You  can  also  choose the subset “BSD” which selects only capabilities with termcap\nequivalents recognized by 4.4BSD.  The -C option sets the “BSD” subset as a side-ef‐\nfect.\n\n•   If  you  select any other value for -R, it is the same as no subset, i.e., all capa‐\nbilities are used.  The -I option likewise selects no subset as a side-effect.\n",
                    "flag": "-R"
                },
                {
                    "name": "-s",
                    "content": "The -s option sorts the fields within each type according to the argument below:\n\nd    leave fields in the order that they are stored in the terminfo database.\n\ni    sort by terminfo name.\n\nl    sort by the long C variable name.\n\nc    sort by the termcap name.\n\nIf the -s option is not given, the fields printed out will be sorted  alphabetically  by\nthe  terminfo  name  within  each  type, except in the case of the -C or the -L options,\nwhich cause the sorting to be done by the termcap name or the long C variable name,  re‐\nspectively.\n",
                    "flag": "-s"
                },
                {
                    "name": "-T",
                    "content": "and analysis, since the compiled descriptions are limited (e.g., 1023 for termcap,  4096\nfor terminfo).\n",
                    "flag": "-T"
                },
                {
                    "name": "-t",
                    "content": "minfo to termcap, untranslatable capabilities are commented-out.\n",
                    "flag": "-t"
                },
                {
                    "name": "-U",
                    "content": "helps  when comparing the actual contents of two source files, since it excludes the in‐\nferences that infocmp makes to fill in missing data.\n",
                    "flag": "-U"
                },
                {
                    "name": "-V",
                    "content": "",
                    "flag": "-V"
                },
                {
                    "name": "-v",
                    "content": "The optional parameter n is a number from 1 to 10,  inclusive,  indicating  the  desired\nlevel  of  detail  of information.  If ncurses is built without tracing support, the op‐\ntional parameter is ignored.\n",
                    "flag": "-v"
                },
                {
                    "name": "-W -w -W",
                    "content": "to do this.\n",
                    "flag": "-W"
                },
                {
                    "name": "-w",
                    "content": "changes the output to width characters.\n",
                    "flag": "-w"
                },
                {
                    "name": "-x",
                    "content": "to the terminfo repertoire which can be loaded using the -x option of tic.\n",
                    "flag": "-x"
                }
            ]
        },
        "FILES": {
            "content": "/etc/terminfo       Compiled terminal description database.\n",
            "subsections": []
        },
        "HISTORY": {
            "content": "Although System V Release 2 provided a terminfo library, it had no documented tool for decom‐\npiling  the terminal descriptions.  Tony Hansen (AT&T) wrote the first infocmp in early 1984,\nfor System V Release 3.\n\nEric Raymond used the AT&T documentation  in  1995  to  provide  an  equivalent  infocmp  for\nncurses.  In addition, he added a few new features such as:\n\n•   the -e option, to support fallback (compiled-in) terminal descriptions\n\n•   the -i option, to help with analysis\n\nLater,  Thomas  Dickey  added the -x (user-defined capabilities) option, and the -E option to\nsupport fallback entries with user-defined capabilities.\n\nFor a complete list, see the EXTENSIONS section.\n\nIn 2010, Roy Marples provided an infocmp program for NetBSD.  It is  less  capable  than  the\nSVr4  or ncurses versions (e.g., it lacks the sorting options documented in X/Open), but does\ninclude the -x option adapted from ncurses.\n",
            "subsections": []
        },
        "PORTABILITY": {
            "content": "X/Open Curses, Issue 7 (2009) provides a description of infocmp.  It does not mention the op‐\ntions used for converting to termcap format.\n",
            "subsections": []
        },
        "EXTENSIONS": {
            "content": "The -0, -1, -E, -F, -G, -Q, -R, -T, -V, -a, -e, -f, -g, -i, -l, -p, -q and -t options are not\nsupported in SVr4 curses.\n\nSVr4 infocmp does not distinguish between absent and cancelled capabilities.  Also, it  shows\nmissing  integer  capabilities as -1 (the internal value used to represent missing integers).\nThis implementation shows those as “NULL”, for consistency with missing strings.\n\nThe -r option's notion of “termcap” capabilities is System V Release 4's.  Actual BSD  curses\nversions will have a more restricted set.  To see only the 4.4BSD set, use -r -RBSD.\n",
            "subsections": []
        },
        "BUGS": {
            "content": "The -F option of infocmp(1) should be a toe(1) mode.\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "captoinfo(1), infotocap(1), tic(1), toe(1), ncurses(3NCURSES), terminfo(5).  usercaps(5).\n\nhttps://invisible-island.net/ncurses/tctest.html\n\nThis describes ncurses version 6.3 (patch 20211021).\n",
            "subsections": []
        },
        "AUTHOR": {
            "content": "Eric S. Raymond <esr@snark.thyrsus.com> and\nThomas E. Dickey <dickey@invisible-island.net>\n\n\n\ninfocmp(1)",
            "subsections": []
        }
    },
    "summary": "infocmp - compare or print out terminfo descriptions",
    "flags": [
        {
            "flag": "-d",
            "long": null,
            "arg": null,
            "description": "the list shows “:” after the capability name, followed by the capability values, sepa‐ rated by a comma."
        },
        {
            "flag": "-c",
            "long": null,
            "arg": null,
            "description": "capabilities are ignored. Each item in the list shows “=” after the capability name, followed by the capability value. The -u option provides a related output, showing the first terminal description rewrit‐ ten to use the second as a building block via the “use=” clause."
        },
        {
            "flag": "-n",
            "long": null,
            "arg": null,
            "description": "the list shows “!” before the capability name. Normally only the conventional capabilities are shown. Use the -x 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."
        },
        {
            "flag": "-0",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-1",
            "long": null,
            "arg": null,
            "description": "printed several to a line to a maximum width of 60 characters."
        },
        {
            "flag": "-a",
            "long": null,
            "arg": null,
            "description": "bilities are commented by prefixing them with a period."
        },
        {
            "flag": "-D",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-E",
            "long": null,
            "arg": null,
            "description": "TERMTYPE structure (the terminal capability structure in the <term.h>). 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."
        },
        {
            "flag": "-e",
            "long": null,
            "arg": null,
            "description": "(the terminal capability structure in the <term.h>). This option is useful for prepar‐ ing versions of the curses library hardwired for a given terminal type."
        },
        {
            "flag": "-F",
            "long": null,
            "arg": null,
            "description": "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 reso‐ lution can be forced by also specifying -r."
        },
        {
            "flag": "-f",
            "long": null,
            "arg": null,
            "description": "for readability."
        },
        {
            "flag": "-G",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-g",
            "long": null,
            "arg": null,
            "description": "lents."
        },
        {
            "flag": "-i",
            "long": null,
            "arg": null,
            "description": "entry, as well as those used for starting/stopping cursor-positioning mode (smcup, rm‐‐ cup) as well as starting/stopping keymap mode (smkx, rmkx). For each string, the code tries to analyze it into actions in terms of the other capa‐ bilities 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 com‐ pleteness over the existing terminfo database). Each report line consists of the capa‐ bility name, followed by a colon and space, followed by a printable expansion of the ca‐ pability string with sections matching recognized actions translated into {}-bracketed descriptions. Here is a list of the DEC/ANSI special sequences recognized: 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 Rendi‐ tion, 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})."
        },
        {
            "flag": "-l",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-p",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-Q",
            "long": null,
            "arg": null,
            "description": "hexadecimal or base64 form, depending on the option's value: 1 hexadecimal 2 base64 3 hexadecimal and base64 For example, this prints the compiled terminfo value as a string which could be assigned to the TERMINFO environment variable: infocmp -0 -q -Q2"
        },
        {
            "flag": "-q",
            "long": null,
            "arg": null,
            "description": "• Make the comparison listing shorter by omitting subheadings, and using “-” for ab‐ sent capabilities, “@” for canceled rather than “NULL”. • However, show differences between absent and cancelled capabilities. • Omit the “Reconstructed from” comment for source listings."
        },
        {
            "flag": "-R",
            "long": null,
            "arg": null,
            "description": "Restrict output to a given subset. This option is for use with archaic versions of ter‐ minfo 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 “SVr1”, “Ultrix”, “HP”, and “AIX”; see terminfo(5) for details. • You can also choose the subset “BSD” which selects only capabilities with termcap equivalents recognized by 4.4BSD. The -C option sets the “BSD” subset as a side-ef‐ fect. • If you select any other value for -R, it is the same as no subset, i.e., all capa‐ bilities are used. The -I option likewise selects no subset as a side-effect."
        },
        {
            "flag": "-s",
            "long": null,
            "arg": null,
            "description": "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, re‐ spectively."
        },
        {
            "flag": "-T",
            "long": null,
            "arg": null,
            "description": "and analysis, since the compiled descriptions are limited (e.g., 1023 for termcap, 4096 for terminfo)."
        },
        {
            "flag": "-t",
            "long": null,
            "arg": null,
            "description": "minfo to termcap, untranslatable capabilities are commented-out."
        },
        {
            "flag": "-U",
            "long": null,
            "arg": null,
            "description": "helps when comparing the actual contents of two source files, since it excludes the in‐ ferences that infocmp makes to fill in missing data."
        },
        {
            "flag": "-V",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-v",
            "long": null,
            "arg": null,
            "description": "The optional parameter n is a number from 1 to 10, inclusive, indicating the desired level of detail of information. If ncurses is built without tracing support, the op‐ tional parameter is ignored."
        },
        {
            "flag": "-W",
            "long": null,
            "arg": null,
            "description": "to do this."
        },
        {
            "flag": "-w",
            "long": null,
            "arg": null,
            "description": "changes the output to width characters."
        },
        {
            "flag": "-x",
            "long": null,
            "arg": null,
            "description": "to the terminfo repertoire which can be loaded using the -x option of tic."
        }
    ],
    "examples": [],
    "see_also": [
        {
            "name": "captoinfo",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/captoinfo/1/json"
        },
        {
            "name": "infotocap",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/infotocap/1/json"
        },
        {
            "name": "tic",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/tic/1/json"
        },
        {
            "name": "toe",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/toe/1/json"
        },
        {
            "name": "ncurses",
            "section": "3NCURSES",
            "url": "https://www.chedong.com/phpMan.php/man/ncurses/3NCURSES/json"
        },
        {
            "name": "terminfo",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/terminfo/5/json"
        },
        {
            "name": "usercaps",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/usercaps/5/json"
        }
    ]
}