{ "content": [ { "type": "text", "text": "# tic(1) (man)\n\n**Summary:** tic - the terminfo entry-description compiler\n\n**Synopsis:** tic [-01CDGIKLNTUVWacfgqrstx] [-e names] [-o dir] [-Q[n]] [-R subset] [-v[n]] [-w[n]] file\n\n## Flags\n\n| Flag | Long | Arg | Description |\n|------|------|-----|-------------|\n| -0 | — | — | |\n| -1 | — | — | |\n| -a | — | — | ties are commented by prefixing them with a period. This sets the -x option, because it treats the commented-out entries |\n| -C | — | — | infocmp(1) in that it does not merely translate capability names, but also translates terminfo strings to termcap format |\n| -c | — | — | If you specify -C (-I) with this option, the code will print warnings about entries which, after use resolution, are mor |\n| -D | — | — | location shown is the one to which it would write compiled terminal descriptions. If tic is not able to find a writable |\n| -e | — | — | Limit writes and translations to the following comma-separated list of terminals. If any name or alias of a terminal mat |\n| -f | — | — | for readability. |\n| -G | — | — | |\n| -g | — | — | lents. |\n| -I | — | — | |\n| -K | — | — | |\n| -L | — | — | |\n| -N | — | — | piler makes a number of assumptions about the defaults of string capabilities re‐‐ set1string, carriagereturn, cursorlef |\n| -o | — | — | variable. |\n| -Q | — | — | in hexadecimal or base64 form, depending on the option's value: 1 hexadecimal 2 base64 3 hexadecimal and base64 |\n| -q | — | — | |\n| -R | — | — | Restrict output to a given subset. This option is for use with archaic versions of terminfo like those on SVr1, Ultrix, |\n| -r | — | — | translation to termcap format. This may be needed if you are preparing a termcap file for a termcap library (such as GNU |\n| -s | — | — | and the number of entries which are compiled. |\n| -T | — | — | and analysis, since the compiled descriptions are limited (e.g., 1023 for termcap, 4096 for terminfo). |\n| -t | — | — | minfo to termcap, untranslatable capabilities are commented-out. |\n| -U | — | — | fers data which is commonly missing in older terminfo data, or in termcaps. |\n| -V | — | — | |\n| -v | — | — | tic's progress. The optional parameter n is a number from 1 to 10, inclusive, indicating the desired level of detail of |\n| -W | — | — | to do this. If you specify both -f and -W options, the latter is ignored when -f has already split the line. |\n| -w | — | — | faults to 60. |\n| -x | — | — | capability name which tic does not recognize, it will infer its type (boolean, number or string) from the syntax and mak |\n\n## See Also\n\n- captoinfo(1)\n- infocmp(1)\n- infotocap(1)\n- toe(1)\n- ncurses(3NCURSES)\n- term(5)\n- terminfo(5)\n- usercaps(5)\n\n## Section Outline\n\n- **NAME** (2 lines)\n- **SYNOPSIS** (2 lines)\n- **DESCRIPTION** (51 lines) — 28 subsections\n - -0 (1 lines)\n - -1 (1 lines)\n - -a (4 lines)\n - -C -C (16 lines)\n - -c (10 lines)\n - -D (5 lines)\n - -e (6 lines)\n - -f (2 lines)\n - -G (1 lines)\n - -g (2 lines)\n - -I (1 lines)\n - -K (1 lines)\n - -L (2 lines)\n - -N (7 lines)\n - -o (2 lines)\n - -Q (8 lines)\n - -q (1 lines)\n - -R (6 lines)\n - -r (4 lines)\n - -s (2 lines)\n - -T (3 lines)\n - -t (2 lines)\n - -U (2 lines)\n - -V (1 lines)\n - -v (25 lines)\n - -W -w -W (5 lines)\n - -w (2 lines)\n - -x (30 lines)\n- **HISTORY** (44 lines)\n- **PORTABILITY** (50 lines)\n- **FILES** (3 lines)\n- **SEE ALSO** (5 lines)\n- **AUTHOR** (6 lines)\n\n## Full Content\n\n### NAME\n\ntic - the terminfo entry-description compiler\n\n### SYNOPSIS\n\ntic [-01CDGIKLNTUVWacfgqrstx] [-e names] [-o dir] [-Q[n]] [-R subset] [-v[n]] [-w[n]] file\n\n### DESCRIPTION\n\nThe 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 TER‐\nMINFO 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 (no default value), and\n\n• the system terminfo database (/etc/terminfo).\n\nALIASES\nThis 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\nOPTIONS\n\n#### -0\n\n#### -1\n\n#### -a\n\nties 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\n#### -C -C\n\ninfocmp(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\n#### -c\n\nIf 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\n#### -D\n\nlocation 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\n#### -e\n\nLimit writes and translations to the following comma-separated list of terminals. If\nany name or alias of a terminal matches one of the names in the list, the entry will\nbe written or translated as normal. Otherwise no output will be generated for it.\nThe option 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\n#### -f\n\nfor readability.\n\n#### -G\n\n#### -g\n\nlents.\n\n#### -I\n\n#### -K\n\n#### -L\n\n\n\n#### -N\n\npiler 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\n#### -o\n\nvariable.\n\n#### -Q\n\nin hexadecimal or base64 form, depending on the option's value:\n\n1 hexadecimal\n\n2 base64\n\n3 hexadecimal and base64\n\n#### -q\n\n#### -R\n\nRestrict 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. Available subsets are “SVr1”, “Ultrix”, “HP”,\n“BSD” and “AIX”; see terminfo(5) for details.\n\n#### -r\n\ntranslation 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\n#### -s\n\nand the number of entries which are compiled.\n\n#### -T\n\nand analysis, since the compiled descriptions are limited (e.g., 1023 for termcap,\n4096 for terminfo).\n\n#### -t\n\nminfo to termcap, untranslatable capabilities are commented-out.\n\n#### -U\n\nfers data which is commonly missing in older terminfo data, or in termcaps.\n\n#### -V\n\n#### -v\n\ntic's progress.\n\nThe 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. If n is omitted, the default level is 1. If n is speci‐\nfied and greater than 1, the level of detail is increased.\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\n5 String-table memory allocations\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\nIf the debug level n is not given, it is taken to be one.\n\n#### -W -w -W\n\nto do this.\n\nIf you specify both -f and -W options, the latter is ignored when -f has already split\nthe line.\n\n#### -w\n\nfaults to 60.\n\n#### -x\n\ncapability 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\nPARAMETERS\nfile contains one or more terminfo terminal descriptions in source format [see ter‐‐\nminfo(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\nPROCESSING\nAll 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. The name field cannot exceed 512 bytes.\nTerminal names exceeding the maximum alias length (32 characters on systems with long file‐\nnames, 14 characters otherwise) will be truncated to the maximum alias length and a warning\nmessage will be printed.\n\n### HISTORY\n\nSystem 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\n### PORTABILITY\n\nX/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 True64 UNIX. 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\nCOMPATIBILITY\nThere 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\nEXTENSIONS\nUnlike 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 ter‐‐\nminfo(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\n### FILES\n\n/etc/terminfo/?/*\nCompiled terminal description database.\n\n### SEE ALSO\n\ncaptoinfo(1), infocmp(1), infotocap(1), toe(1), ncurses(3NCURSES), term(5). terminfo(5).\nusercaps(5).\n\nThis describes ncurses version 6.3 (patch 20211021).\n\n### AUTHOR\n\nEric S. Raymond and\nThomas E. Dickey \n\n\n\ntic(1)\n\n" } ], "structuredContent": { "command": "tic", "section": "1", "mode": "man", "summary": "tic - the terminfo entry-description compiler", "synopsis": "tic [-01CDGIKLNTUVWacfgqrstx] [-e names] [-o dir] [-Q[n]] [-R subset] [-v[n]] [-w[n]] file", "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 following comma-separated list of terminals. 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": "" }, { "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 10, inclusive, indicating the desired level of detail of information. If ncurses is built without tracing support, the op‐ tional parameter is ignored. If n is omitted, the default level is 1. If n is speci‐ fied and greater than 1, the level of detail is increased. 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 5 String-table memory allocations 7 Entries into the string-table 8 List of tokens encountered by scanner 9 All values computed in construction of the hash table If the debug level n is not given, it is taken to be one." }, { "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. PARAMETERS file contains one or more terminfo terminal descriptions in source format [see ter‐‐ minfo(5)]. Each description in the file describes the capabilities of a particular terminal. If file is “-”, then the data is read from the standard input. The file parameter may also be the path of a character-device. PROCESSING All but one of the capabilities recognized by tic are documented in terminfo(5). The excep‐ tion is the use capability. When a use=entry-name field is discovered in a terminal entry currently being compiled, tic reads in the binary from /etc/terminfo to complete the entry. (Entries created from file will be used first. tic duplicates the capabilities in entry-name for the current entry, with the exception of those capabilities that explicitly are defined in the current entry. When an entry, e.g., entryname1, contains a use=entryname2 field, any canceled capabili‐ ties in entryname2 must also appear in entryname1 before use= for these capabilities to be canceled in entryname1. Total compiled entries cannot exceed 4096 bytes. The name field cannot exceed 512 bytes. Terminal names exceeding the maximum alias length (32 characters on systems with long file‐ names, 14 characters otherwise) will be truncated to the maximum alias length and a warning message will be printed." } ], "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" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 51, "subsections": [ { "name": "-0", "lines": 1, "flag": "-0" }, { "name": "-1", "lines": 1, "flag": "-1" }, { "name": "-a", "lines": 4, "flag": "-a" }, { "name": "-C -C", "lines": 16, "flag": "-C" }, { "name": "-c", "lines": 10, "flag": "-c" }, { "name": "-D", "lines": 5, "flag": "-D" }, { "name": "-e", "lines": 6, "flag": "-e" }, { "name": "-f", "lines": 2, "flag": "-f" }, { "name": "-G", "lines": 1, "flag": "-G" }, { "name": "-g", "lines": 2, "flag": "-g" }, { "name": "-I", "lines": 1, "flag": "-I" }, { "name": "-K", "lines": 1, "flag": "-K" }, { "name": "-L", "lines": 2, "flag": "-L" }, { "name": "-N", "lines": 7, "flag": "-N" }, { "name": "-o", "lines": 2, "flag": "-o" }, { "name": "-Q", "lines": 8, "flag": "-Q" }, { "name": "-q", "lines": 1, "flag": "-q" }, { "name": "-R", "lines": 6, "flag": "-R" }, { "name": "-r", "lines": 4, "flag": "-r" }, { "name": "-s", "lines": 2, "flag": "-s" }, { "name": "-T", "lines": 3, "flag": "-T" }, { "name": "-t", "lines": 2, "flag": "-t" }, { "name": "-U", "lines": 2, "flag": "-U" }, { "name": "-V", "lines": 1, "flag": "-V" }, { "name": "-v", "lines": 25, "flag": "-v" }, { "name": "-W -w -W", "lines": 5, "flag": "-W" }, { "name": "-w", "lines": 2, "flag": "-w" }, { "name": "-x", "lines": 30, "flag": "-x" } ] }, { "name": "HISTORY", "lines": 44, "subsections": [] }, { "name": "PORTABILITY", "lines": 50, "subsections": [] }, { "name": "FILES", "lines": 3, "subsections": [] }, { "name": "SEE ALSO", "lines": 5, "subsections": [] }, { "name": "AUTHOR", "lines": 6, "subsections": [] } ] } }