{
    "mode": "man",
    "parameter": "tic",
    "section": "1",
    "url": "https://www.chedong.com/phpMan.php/man/tic/1/json",
    "generated": "2026-11-09T19:01:49Z",
    "synopsis": "tic  [-01acCDfgGIKLNqrstTUVWx]  [-e  terminal-type-list] [-o dir] [-Q[n]] [-R subset] [-v[n]]\n[-w[n]] file",
    "sections": {
        "NAME": {
            "content": "tic - compile terminal descriptions for terminfo or termcap\n",
            "subsections": []
        },
        "SYNOPSIS": {
            "content": "tic  [-01acCDfgGIKLNqrstTUVWx]  [-e  terminal-type-list] [-o dir] [-Q[n]] [-R subset] [-v[n]]\n[-w[n]] file\n",
            "subsections": []
        },
        "DESCRIPTION": {
            "content": "The tic command translates a terminfo file from source format into compiled format.  The com‐\npiled format is necessary for use with the library routines in ncurses(3NCURSES).\n\nAs described in term(5), the database may be either a directory tree (one file  per  terminal\nentry)  or a hashed database (one record per entry).  The tic command writes only one type of\nentry, depending on how it was built:\n\n•   For directory trees, the top-level directory, e.g.,  /usr/share/terminfo,  specifies  the\nlocation of the database.\n\n•   For hashed databases, a filename is needed.  If the given file is not found by that name,\nbut can be found by adding the suffix \".db\", then that is used.\n\nThe  default name for the hashed database is the same as the default directory name (only\nadding a \".db\" suffix).\n\nIn either case (directory or hashed database), tic will create the container if it  does  not\nexist.  For a directory, this would be the “terminfo” leaf, versus a \"terminfo.db\" file.\n\nThe  results are normally placed in the system terminfo database /etc/terminfo.  The compiled\nterminal description can be placed in a different terminfo database.  There are two  ways  to\nachieve this:\n\n•   First,  you  may override the system default either by using the -o option, or by setting\nthe variable TERMINFO in your shell environment to a valid database location.\n\n•   Secondly, if tic cannot write in /etc/terminfo  or  the  location  specified  using  your\nTERMINFO  variable,  it  looks  for  the  directory  $HOME/.terminfo  (or hashed database\n$HOME/.terminfo.db); if that location exists, the entry is placed there.\n\nLibraries that read terminfo entries are expected to check in succession\n\n•   a location specified with the TERMINFO environment variable,\n\n•   $HOME/.terminfo,\n\n•   directories listed in the TERMINFODIRS environment variable,\n\n•   a compiled-in list of directories (/etc/terminfo:/lib/terminfo:/usr/share/terminfo), and\n\n•   the system terminfo database (/etc/terminfo).\n\nThe Fetching Compiled Descriptions section in the terminfo(5) manual goes  into  further  de‐\ntail.\n",
            "subsections": [
                {
                    "name": "Aliases",
                    "content": "This  is  the same program as infotocap and captoinfo; usually those are linked to, or copied\nfrom this program:\n\n•   When invoked as infotocap, tic sets the -I option.\n\n•   When invoked as captoinfo, tic sets the -C option.\n"
                }
            ]
        },
        "OPTIONS": {
            "content": "",
            "subsections": [
                {
                    "name": "-0",
                    "content": "",
                    "flag": "-0"
                },
                {
                    "name": "-1",
                    "content": "",
                    "flag": "-1"
                },
                {
                    "name": "-a",
                    "content": "ties are commented by prefixing them with a period.  This sets the -x option,  because\nit  treats the commented-out entries as user-defined names.  If the source is termcap,\naccept the 2-character names required by version 6.  Otherwise these are ignored.\n",
                    "flag": "-a"
                },
                {
                    "name": "-C      -C",
                    "content": "infocmp(1)  in that it does not merely translate capability names, but also translates\nterminfo strings to termcap format.  Capabilities that are not translatable  are  left\nin  the  entry  under  their terminfo names but commented out with two preceding dots.\nThe actual format used incorporates some improvements for escaped characters from ter‐\nminfo format.  For a stricter BSD-compatible translation, add the -K option.\n\nIf this is combined with -c, tic makes additional checks to  report  cases  where  the\nterminfo values do not have an exact equivalent in termcap form.  For example:\n\n•   sgr  usually will not convert, because termcap lacks the ability to work with more\nthan two parameters, and because termcap lacks many of the arithmetic/logical  op‐\nerators used in terminfo.\n\n•   capabilities  with more than one delay or with delays before the end of the string\nwill not convert completely.\n",
                    "flag": "-C"
                },
                {
                    "name": "-c",
                    "content": "If  you  specify  -C (-I) with this option, the code will print warnings about entries\nwhich, after use resolution, are more than 1023 (4096) bytes long.   Due  to  a  fixed\nbuffer  length  in  older  termcap libraries, as well as buggy checking for the buffer\nlength (and a documented limit in terminfo), these entries may cause core  dumps  with\nother implementations.\n\ntic  checks string capabilities to ensure that those with parameters will be valid ex‐\npressions.  It does this check only for  the  predefined  string  capabilities;  those\nwhich are defined with the -x option are ignored.\n",
                    "flag": "-c"
                },
                {
                    "name": "-D",
                    "content": "location shown is the one to which it would write compiled terminal descriptions.   If\ntic is not able to find a writable database location according to the rules summarized\nabove,  it  will print a diagnostic and exit with an error rather than printing a list\nof database locations.\n",
                    "flag": "-D"
                },
                {
                    "name": "-e",
                    "content": "Limit writes and translations to the comma-separated list of terminal types.   If  any\nname  or  alias  of a terminal matches one of the names in the list, the entry will be\nwritten or translated as normal.  Otherwise no output will be generated for  it.   The\noption  value  is  interpreted  as  a  file  containing the list if it contains a '/'.\n(Note: depending on how tic was compiled, this option may require -I or -C.)\n",
                    "flag": "-e"
                },
                {
                    "name": "-f",
                    "content": "for readability.\n",
                    "flag": "-f"
                },
                {
                    "name": "-G",
                    "content": "",
                    "flag": "-G"
                },
                {
                    "name": "-g",
                    "content": "lents.\n",
                    "flag": "-g"
                },
                {
                    "name": "-I",
                    "content": "",
                    "flag": "-I"
                },
                {
                    "name": "-K",
                    "content": "",
                    "flag": "-K"
                },
                {
                    "name": "-L",
                    "content": "<term.h>\n",
                    "flag": "-L"
                },
                {
                    "name": "-N",
                    "content": "piler makes a number of assumptions about the  defaults  of  string  capabilities  re‐\nset1string,  carriagereturn, cursorleft, cursordown, scrollforward, tab, newline,\nkeybackspace, keyleft, and keydown, then attempts to use obsolete termcap capabili‐\nties to deduce correct values.  It also normally suppresses output of obsolete termcap\ncapabilities such as bs.  This option forces a more literal translation that also pre‐\nserves the obsolete capabilities.\n",
                    "flag": "-N"
                },
                {
                    "name": "-o",
                    "content": "variable.\n",
                    "flag": "-o"
                },
                {
                    "name": "-Q",
                    "content": "in hexadecimal or base64 form, depending on the option's value:\n\n1  hexadecimal\n\n2  base64\n\n3  hexadecimal and base64\n",
                    "flag": "-Q"
                },
                {
                    "name": "-q",
                    "content": "",
                    "flag": "-q"
                },
                {
                    "name": "-R",
                    "content": "Restrict  output  to  a given subset.  This option is for use with archaic versions of\nterminfo like those on SVr1, Ultrix, or HP-UX that do not  support  the  full  set  of\nSVR4/XSI  Curses  terminfo; and outright broken ports like AIX 3.x that have their own\nextensions incompatible with SVr4/XSI.\n\nAvailable subsets are\n“SVr1”, “Ultrix”, “HP”, “BSD”, and “AIX”\n\nSee terminfo(5) for details.\n",
                    "flag": "-R"
                },
                {
                    "name": "-r",
                    "content": "translation to termcap format.  This may be needed if you are preparing a termcap file\nfor  a termcap library (such as GNU termcap through version 1.3 or BSD termcap through\n4.3BSD) that does not handle multiple tc capabilities per entry.\n",
                    "flag": "-r"
                },
                {
                    "name": "-s",
                    "content": "and the number of entries which are compiled.\n",
                    "flag": "-s"
                },
                {
                    "name": "-T",
                    "content": "and analysis, since the compiled descriptions are limited  (e.g.,  1023  for  termcap,\n4096 for terminfo).\n",
                    "flag": "-T"
                },
                {
                    "name": "-t",
                    "content": "minfo to termcap, untranslatable capabilities are commented-out.\n",
                    "flag": "-t"
                },
                {
                    "name": "-U",
                    "content": "fers data which is commonly missing in older terminfo data, or in termcaps.\n",
                    "flag": "-U"
                },
                {
                    "name": "-V",
                    "content": "",
                    "flag": "-V"
                },
                {
                    "name": "-v",
                    "content": "tic's progress.\n\nThe optional parameter n is a number from 1 to  9,  inclusive,  indicating  the  desired\nlevel of detail of information.\n\n•   If ncurses is built without tracing support, the optional parameter is ignored.\n\n•   If n is omitted, the default level is 1.\n\n•   If n is specified and greater than 1, the level of detail is increased, and the out‐\nput is written (with tracing information) to the “trace” file.\n\nThe debug flag levels are as follows:\n\n1   Names of files created and linked\n\n2   Information related to the “use” facility\n\n3   Statistics from the hashing algorithm\n\n4   Details of extended capabilities\n\n5   (unused)\n\n6   (unused)\n\n7   Entries into the string-table\n\n8   List of tokens encountered by scanner\n\n9   All values computed in construction of the hash table\n",
                    "flag": "-v"
                },
                {
                    "name": "-W    -w  -W",
                    "content": "to do this.\n\nIf you specify both -f and -W options, the latter is ignored when -f has  already  split\nthe line.\n",
                    "flag": "-W"
                },
                {
                    "name": "-w",
                    "content": "faults to 60.\n",
                    "flag": "-w"
                },
                {
                    "name": "-x",
                    "content": "capability name which tic does not recognize, it will infer its type (Boolean, number or\nstring)  from  the syntax and make an extended table entry for that.  User-defined capa‐\nbility strings whose name begins with “k” are treated as function keys.\n",
                    "flag": "-x"
                },
                {
                    "name": "Parameters",
                    "content": "file   contains  one  or  more  terminfo  terminal  descriptions  in   source   format   [see\nterminfo(5)].  Each description in the file describes the capabilities of a particular\nterminal.\n\nIf file is “-”, then the data is read from the standard input.  The file parameter may\nalso be the path of a character-device.\n"
                },
                {
                    "name": "Processing",
                    "content": "All  but one of the capabilities recognized by tic are documented in terminfo(5).  The excep‐\ntion is the use capability.\n\nWhen a use=entry-name field is discovered in a terminal entry currently being  compiled,  tic\nreads  in  the  binary  from /etc/terminfo to complete the entry.  (Entries created from file\nwill be used first.  tic duplicates the capabilities in entry-name  for  the  current  entry,\nwith the exception of those capabilities that explicitly are defined in the current entry.\n\nWhen  an entry, e.g., entryname1, contains a use=entryname2 field, any canceled capabili‐\nties in entryname2 must also appear in entryname1 before use= for these  capabilities  to\nbe canceled in entryname1.\n\nTotal  compiled entries cannot exceed 4096 bytes in the legacy storage format, or 32768 using\nthe extended number format.  The name field cannot exceed 512 bytes.  Terminal names  exceed‐\ning  the  maximum  alias  length (32 characters on systems with long filenames, 14 characters\notherwise) will be truncated to the maximum alias  length  and  a  warning  message  will  be\nprinted.\n"
                }
            ]
        },
        "FILES": {
            "content": "/etc/terminfo\ncompiled terminal description database\n",
            "subsections": []
        },
        "NOTES": {
            "content": "There  is  some evidence that historic tic implementations treated description fields with no\nwhitespace in them as additional aliases or short names.  This tic does not do that,  but  it\ndoes  warn when description fields may be treated that way and check them for dangerous char‐\nacters.\n",
            "subsections": []
        },
        "EXTENSIONS": {
            "content": "Unlike the SVr4 tic command, this implementation can actually compile  termcap  sources.   In\nfact,  entries  in  terminfo  and  termcap  syntax can be mixed in a single source file.  See\nterminfo(5) for the list of termcap names taken to be equivalent to terminfo names.\n\nThe SVr4 manual pages are not clear on the resolution rules for use capabilities.   This  im‐\nplementation  of  tic  will  find use targets anywhere in the source file, or anywhere in the\nfile tree rooted at TERMINFO (if TERMINFO is defined), or in the user's $HOME/.terminfo data‐\nbase (if it exists), or (finally) anywhere in the system's file tree of compiled entries.\n\nThe error messages from this tic have the same format as GNU C error  messages,  and  can  be\nparsed by GNU Emacs's compile facility.\n\nAside from -c and -v, options are not portable:\n\n•   Most of tic's options are not supported by SVr4 tic:\n\n-0 -1 -C -G -I -N -R -T -V -a -e -f -g -o -r -s -t -x\n\n•   The NetBSD tic supports a few of the ncurses options\n\n-a -o -x\n\nand adds -S (a feature which does the same thing as infocmp's -e and -E options).\n\nThe SVr4 -c mode does not report bad “use=” links.\n\nSystem  V  does not compile entries to or read entries from your $HOME/.terminfo database un‐\nless TERMINFO is explicitly set to it.\n",
            "subsections": []
        },
        "PORTABILITY": {
            "content": "X/Open Curses, Issue 7 (2009) provides a brief description of tic.  It lists one option:  -c.\nThe  omission of -v is unexpected.  The change history states that the description is derived\nfrom Tru64.  According to its manual pages, that system also supported the -v option.\n\nShortly after Issue 7 was released, Tru64 was discontinued.  As of 2019, the surviving imple‐\nmentations of tic are SVr4 (AIX, HP-UX and Solaris), ncurses and NetBSD curses.  The SVr4 tic\nprograms all support the -v option.  The NetBSD tic program follows  X/Open's  documentation,\nomitting the -v option.\n\nThe  X/Open rationale states that some implementations of tic read terminal descriptions from\nthe standard input if the file parameter is omitted.  None of these implementations do  that.\nFurther,  it comments that some may choose to read from ”./terminfo.src” but that is obsoles‐\ncent behavior from SVr2, and is not (for example) a documented feature of SVr3.\n",
            "subsections": []
        },
        "HISTORY": {
            "content": "System V Release 2 provided a tic utility.  It accepted a single option: -v (optionally  fol‐\nlowed  by  a  number).  According to Ross Ridge's comment in mytinfo, this version of tic was\nunable to represent cancelled capabilities.\n\nSystem V Release 3 provided a different tic utility, written  by  Pavel  Curtis,  (originally\nnamed  “compile” in pcurses).  This added an option -c to check the file for errors, with the\ncaveat that errors in “use=” links would not be reported.  System V Release  3  documented  a\nfew  warning  messages which did not appear in pcurses.  While the program itself was changed\nlittle as development continued with System V Release 4, the table of capabilities grew  from\n180 (pcurses) to 464 (Solaris).\n\nIn  early development of ncurses (1993), Zeyd Ben-Halim used the table from mytinfo to extend\nthe pcurses table to 469 capabilities (456 matched SVr4, 8 were only in SVr4, 13 were not  in\nSVr4).   Of  those  13,  11  were  ultimately discarded (perhaps to match the draft of X/Open\nCurses).  The exceptions were memorylockabove and memoryunlock (see usercaps(5)).\n\nEric Raymond incorporated parts of mytinfo into ncurses to implement the  termcap-to-terminfo\nsource  conversion,  and extended that to begin development of the corresponding terminfo-to-\ntermcap source conversion, Thomas Dickey completed that development over the course  of  sev‐\neral years.\n\nIn 1999, Thomas Dickey added the -x option to support user-defined capabilities.\n\nIn  2010, Roy Marples provided a tic program and terminfo library for NetBSD.  That implemen‐\ntation adapts several features from ncurses, including tic's -x option.\n\nThe -c option tells tic to check for problems in the terminfo source file.  Continued  devel‐\nopment provides additional checks:\n\n•   pcurses had 8 warnings\n\n•   ncurses in 1996 had 16 warnings\n\n•   Solaris (SVr4) curses has 28 warnings\n\n•   NetBSD tic in 2019 has 19 warnings.\n\n•   ncurses in 2019 has 96 warnings\n\nThe  checking  done in ncurses' tic helps with the conversion to termcap, as well as pointing\nout errors and inconsistencies.  It is also used to ensure consistency with the  user-defined\ncapabilities.   There  are  527  distinct  capabilities in ncurses' terminal database; 128 of\nthose are user-defined.\n",
            "subsections": []
        },
        "AUTHORS": {
            "content": "Eric S. Raymond <esr@snark.thyrsus.com> and\nThomas E. Dickey <dickey@invisible-island.net>\n",
            "subsections": []
        },
        "SEE ALSO": {
            "content": "captoinfo(1), infocmp(1),  infotocap(1),  toe(1),  ncurses(3NCURSES),  term(5),  terminfo(5),\nusercaps(5)\n\nncurses 6.4                                  2023-12-30                                       tic(1)",
            "subsections": []
        }
    },
    "summary": "tic - compile terminal descriptions for terminfo or termcap",
    "flags": [
        {
            "flag": "-0",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-1",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-a",
            "long": null,
            "arg": null,
            "description": "ties are commented by prefixing them with a period. This sets the -x option, because it treats the commented-out entries as user-defined names. If the source is termcap, accept the 2-character names required by version 6. Otherwise these are ignored."
        },
        {
            "flag": "-C",
            "long": null,
            "arg": null,
            "description": "infocmp(1) in that it does not merely translate capability names, but also translates terminfo strings to termcap format. Capabilities that are not translatable are left in the entry under their terminfo names but commented out with two preceding dots. The actual format used incorporates some improvements for escaped characters from ter‐ minfo format. For a stricter BSD-compatible translation, add the -K option. If this is combined with -c, tic makes additional checks to report cases where the terminfo values do not have an exact equivalent in termcap form. For example: • sgr usually will not convert, because termcap lacks the ability to work with more than two parameters, and because termcap lacks many of the arithmetic/logical op‐ erators used in terminfo. • capabilities with more than one delay or with delays before the end of the string will not convert completely."
        },
        {
            "flag": "-c",
            "long": null,
            "arg": null,
            "description": "If you specify -C (-I) with this option, the code will print warnings about entries which, after use resolution, are more than 1023 (4096) bytes long. Due to a fixed buffer length in older termcap libraries, as well as buggy checking for the buffer length (and a documented limit in terminfo), these entries may cause core dumps with other implementations. tic checks string capabilities to ensure that those with parameters will be valid ex‐ pressions. It does this check only for the predefined string capabilities; those which are defined with the -x option are ignored."
        },
        {
            "flag": "-D",
            "long": null,
            "arg": null,
            "description": "location shown is the one to which it would write compiled terminal descriptions. If tic is not able to find a writable database location according to the rules summarized above, it will print a diagnostic and exit with an error rather than printing a list of database locations."
        },
        {
            "flag": "-e",
            "long": null,
            "arg": null,
            "description": "Limit writes and translations to the comma-separated list of terminal types. If any name or alias of a terminal matches one of the names in the list, the entry will be written or translated as normal. Otherwise no output will be generated for it. The option value is interpreted as a file containing the list if it contains a '/'. (Note: depending on how tic was compiled, this option may require -I or -C.)"
        },
        {
            "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": ""
        },
        {
            "flag": "-K",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-L",
            "long": null,
            "arg": null,
            "description": "<term.h>"
        },
        {
            "flag": "-N",
            "long": null,
            "arg": null,
            "description": "piler makes a number of assumptions about the defaults of string capabilities re‐ set1string, carriagereturn, cursorleft, cursordown, scrollforward, tab, newline, keybackspace, keyleft, and keydown, then attempts to use obsolete termcap capabili‐ ties to deduce correct values. It also normally suppresses output of obsolete termcap capabilities such as bs. This option forces a more literal translation that also pre‐ serves the obsolete capabilities."
        },
        {
            "flag": "-o",
            "long": null,
            "arg": null,
            "description": "variable."
        },
        {
            "flag": "-Q",
            "long": null,
            "arg": null,
            "description": "in hexadecimal or base64 form, depending on the option's value: 1 hexadecimal 2 base64 3 hexadecimal and base64"
        },
        {
            "flag": "-q",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-R",
            "long": null,
            "arg": null,
            "description": "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 outright broken ports like AIX 3.x that have their own extensions incompatible with SVr4/XSI. Available subsets are “SVr1”, “Ultrix”, “HP”, “BSD”, and “AIX” See terminfo(5) for details."
        },
        {
            "flag": "-r",
            "long": null,
            "arg": null,
            "description": "translation to termcap format. This may be needed if you are preparing a termcap file for a termcap library (such as GNU termcap through version 1.3 or BSD termcap through 4.3BSD) that does not handle multiple tc capabilities per entry."
        },
        {
            "flag": "-s",
            "long": null,
            "arg": null,
            "description": "and the number of entries which are compiled."
        },
        {
            "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": "fers data which is commonly missing in older terminfo data, or in termcaps."
        },
        {
            "flag": "-V",
            "long": null,
            "arg": null,
            "description": ""
        },
        {
            "flag": "-v",
            "long": null,
            "arg": null,
            "description": "tic's progress. The optional parameter n is a number from 1 to 9, inclusive, indicating the desired level of detail of information. • If ncurses is built without tracing support, the optional parameter is ignored. • If n is omitted, the default level is 1. • If n is specified and greater than 1, the level of detail is increased, and the out‐ put is written (with tracing information) to the “trace” file. The debug flag levels are as follows: 1 Names of files created and linked 2 Information related to the “use” facility 3 Statistics from the hashing algorithm 4 Details of extended capabilities 5 (unused) 6 (unused) 7 Entries into the string-table 8 List of tokens encountered by scanner 9 All values computed in construction of the hash table"
        },
        {
            "flag": "-W",
            "long": null,
            "arg": null,
            "description": "to do this. If you specify both -f and -W options, the latter is ignored when -f has already split the line."
        },
        {
            "flag": "-w",
            "long": null,
            "arg": null,
            "description": "faults to 60."
        },
        {
            "flag": "-x",
            "long": null,
            "arg": null,
            "description": "capability name which tic does not recognize, it will infer its type (Boolean, number or string) from the syntax and make an extended table entry for that. User-defined capa‐ bility strings whose name begins with “k” are treated as function keys."
        }
    ],
    "examples": [],
    "see_also": [
        {
            "name": "captoinfo",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/captoinfo/1/json"
        },
        {
            "name": "infocmp",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/infocmp/1/json"
        },
        {
            "name": "infotocap",
            "section": "1",
            "url": "https://www.chedong.com/phpMan.php/man/infotocap/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": "term",
            "section": "5",
            "url": "https://www.chedong.com/phpMan.php/man/term/5/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"
        }
    ],
    "tldr": {
        "source": "official",
        "description": "Compile terminfo and install for ncurses.",
        "examples": [
            {
                "description": "Compile and install terminfo for a terminal",
                "command": "tic -xe {{terminal}} {{path/to/terminal.info}}"
            },
            {
                "description": "Check terminfo file for errors",
                "command": "tic -c {{path/to/terminal.info}}"
            },
            {
                "description": "Print database locations",
                "command": "tic -D"
            }
        ]
    }
}