2 ****************************************************************************
3 * Copyright 2018-2021,2022 Thomas E. Dickey *
4 * Copyright 1998-2016,2017 Free Software Foundation, Inc. *
6 * Permission is hereby granted, free of charge, to any person obtaining a *
7 * copy of this software and associated documentation files (the *
8 * "Software"), to deal in the Software without restriction, including *
9 * without limitation the rights to use, copy, modify, merge, publish, *
10 * distribute, distribute with modifications, sublicense, and/or sell *
11 * copies of the Software, and to permit persons to whom the Software is *
12 * furnished to do so, subject to the following conditions: *
14 * The above copyright notice and this permission notice shall be included *
15 * in all copies or substantial portions of the Software. *
17 * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS *
18 * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF *
19 * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. *
20 * IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, *
21 * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR *
22 * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR *
23 * THE USE OR OTHER DEALINGS IN THE SOFTWARE. *
25 * Except as contained in this notice, the name(s) of the above copyright *
26 * holders shall not be used in advertising or otherwise to promote the *
27 * sale, use or other dealings in this Software without prior written *
29 ****************************************************************************
30 * @Id: tic.1m,v 1.84 2022/09/17 19:01:24 tom Exp @
32 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
35 <meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
36 <meta name="generator" content="Manpage converted by man2html - see https://invisible-island.net/scripts/readme.html#others_scripts">
38 <link rel="author" href="mailto:bug-ncurses@gnu.org">
42 <H1 class="no-header">tic 1m</H1>
44 <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG> <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>
49 </PRE><H2><a name="h2-NAME">NAME</a></H2><PRE>
50 <STRONG>tic</STRONG> - the <EM>terminfo</EM> entry-description compiler
53 </PRE><H2><a name="h2-SYNOPSIS">SYNOPSIS</a></H2><PRE>
54 <STRONG>tic</STRONG> [<STRONG>-01CDGIKLNTUVWacfgqrstx</STRONG>] [<STRONG>-e</STRONG> <EM>names</EM>] [<STRONG>-o</STRONG> <EM>dir</EM>] [<STRONG>-Q</STRONG>[<EM>n</EM>]] [<STRONG>-R</STRONG> <EM>subset</EM>]
55 [<STRONG>-v</STRONG>[<EM>n</EM>]] [<STRONG>-w</STRONG>[<EM>n</EM>]] <EM>file</EM>
58 </PRE><H2><a name="h2-DESCRIPTION">DESCRIPTION</a></H2><PRE>
59 The <STRONG>tic</STRONG> command translates a <STRONG>terminfo</STRONG> file from source format into
60 compiled format. The compiled format is necessary for use with the
61 library routines in <STRONG><A HREF="ncurses.3x.html">ncurses(3x)</A></STRONG>.
63 As described in <STRONG><A HREF="term.5.html">term(5)</A></STRONG>, the database may be either a directory tree
64 (one file per terminal entry) or a hashed database (one record per
65 entry). The <STRONG>tic</STRONG> command writes only one type of entry, depending on
68 <STRONG>o</STRONG> For directory trees, the top-level directory, e.g.,
69 /usr/share/terminfo, specifies the location of the database.
71 <STRONG>o</STRONG> For hashed databases, a filename is needed. If the given file is
72 not found by that name, but can be found by adding the suffix
73 ".db", then that is used.
75 The default name for the hashed database is the same as the default
76 directory name (only adding a ".db" suffix).
78 In either case (directory or hashed database), <STRONG>tic</STRONG> will create the
79 container if it does not exist. For a directory, this would be the
80 "terminfo" leaf, versus a "terminfo.db" file.
82 The results are normally placed in the system terminfo database
83 <STRONG>/usr/share/terminfo</STRONG>. The compiled terminal description can be placed
84 in a different terminfo database. There are two ways to achieve this:
86 <STRONG>o</STRONG> First, you may override the system default either by using the <STRONG>-o</STRONG>
87 option, or by setting the variable <STRONG>TERMINFO</STRONG> in your shell
88 environment to a valid database location.
90 <STRONG>o</STRONG> Secondly, if <STRONG>tic</STRONG> cannot write in <EM>/usr/share/terminfo</EM> or the
91 location specified using your TERMINFO variable, it looks for the
92 directory <EM>$HOME/.terminfo</EM> (or hashed database <EM>$HOME/.terminfo.db)</EM>;
93 if that location exists, the entry is placed there.
95 Libraries that read terminfo entries are expected to check in
98 <STRONG>o</STRONG> a location specified with the TERMINFO environment variable,
100 <STRONG>o</STRONG> <EM>$HOME/.terminfo</EM>,
102 <STRONG>o</STRONG> directories listed in the TERMINFO_DIRS environment variable,
104 <STRONG>o</STRONG> a compiled-in list of directories (no default value), and
106 <STRONG>o</STRONG> the system terminfo database (<EM>/usr/share/terminfo</EM>).
109 </PRE><H3><a name="h3-ALIASES">ALIASES</a></H3><PRE>
110 This is the same program as infotocap and captoinfo; usually those are
111 linked to, or copied from this program:
113 <STRONG>o</STRONG> When invoked as infotocap, tic sets the <STRONG>-I</STRONG> option.
115 <STRONG>o</STRONG> When invoked as captoinfo, tic sets the <STRONG>-C</STRONG> option.
118 </PRE><H3><a name="h3-OPTIONS">OPTIONS</a></H3><PRE>
119 <STRONG>-0</STRONG> restricts the output to a single line
121 <STRONG>-1</STRONG> restricts the output to a single column
123 <STRONG>-a</STRONG> tells <STRONG>tic</STRONG> to retain commented-out capabilities rather than
124 discarding them. Capabilities are commented by prefixing them
125 with a period. This sets the <STRONG>-x</STRONG> option, because it treats the
126 commented-out entries as user-defined names. If the source is
127 termcap, accept the 2-character names required by version 6.
128 Otherwise these are ignored.
130 <STRONG>-C</STRONG> Force source translation to termcap format. Note: this differs
131 from the <STRONG>-C</STRONG> option of <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG> in that it does not merely
132 translate capability names, but also translates terminfo strings
133 to termcap format. Capabilities that are not translatable are
134 left in the entry under their terminfo names but commented out
135 with two preceding dots. The actual format used incorporates
136 some improvements for escaped characters from terminfo format.
137 For a stricter BSD-compatible translation, add the <STRONG>-K</STRONG> option.
139 If this is combined with <STRONG>-c</STRONG>, <STRONG>tic</STRONG> makes additional checks to
140 report cases where the terminfo values do not have an exact
141 equivalent in termcap form. For example:
143 <STRONG>o</STRONG> <STRONG>sgr</STRONG> usually will not convert, because termcap lacks the
144 ability to work with more than two parameters, and because
145 termcap lacks many of the arithmetic/logical operators used
148 <STRONG>o</STRONG> capabilities with more than one delay or with delays before
149 the end of the string will not convert completely.
151 <STRONG>-c</STRONG> tells <STRONG>tic</STRONG> to only check <EM>file</EM> for errors, including syntax
152 problems and bad use-links. If you specify <STRONG>-C</STRONG> (<STRONG>-I</STRONG>) with this
153 option, the code will print warnings about entries which, after
154 use resolution, are more than 1023 (4096) bytes long. Due to a
155 fixed buffer length in older termcap libraries, as well as buggy
156 checking for the buffer length (and a documented limit in
157 terminfo), these entries may cause core dumps with other
160 <STRONG>tic</STRONG> checks string capabilities to ensure that those with
161 parameters will be valid expressions. It does this check only
162 for the predefined string capabilities; those which are defined
163 with the <STRONG>-x</STRONG> option are ignored.
165 <STRONG>-D</STRONG> tells <STRONG>tic</STRONG> to print the database locations that it knows about,
166 and exit. The first location shown is the one to which it would
167 write compiled terminal descriptions. If <STRONG>tic</STRONG> is not able to
168 find a writable database location according to the rules
169 summarized above, it will print a diagnostic and exit with an
170 error rather than printing a list of database locations.
172 <STRONG>-e</STRONG> <EM>names</EM>
173 Limit writes and translations to the following comma-separated
174 list of terminals. If any name or alias of a terminal matches
175 one of the names in the list, the entry will be written or
176 translated as normal. Otherwise no output will be generated for
177 it. The option value is interpreted as a file containing the
178 list if it contains a '/'. (Note: depending on how tic was
179 compiled, this option may require <STRONG>-I</STRONG> or <STRONG>-C</STRONG>.)
181 <STRONG>-f</STRONG> Display complex terminfo strings which contain
182 if/then/else/endif expressions indented for readability.
184 <STRONG>-G</STRONG> Display constant literals in decimal form rather than their
185 character equivalents.
187 <STRONG>-g</STRONG> Display constant character literals in quoted form rather than
188 their decimal equivalents.
190 <STRONG>-I</STRONG> Force source translation to terminfo format.
192 <STRONG>-K</STRONG> Suppress some longstanding ncurses extensions to termcap format,
193 e.g., "\s" for space.
195 <STRONG>-L</STRONG> Force source translation to terminfo format using the long C
196 variable names listed in <<STRONG>term.h</STRONG>>
198 <STRONG>-N</STRONG> Disable smart defaults. Normally, when translating from termcap
199 to terminfo, the compiler makes a number of assumptions about
200 the defaults of string capabilities <STRONG>reset1_string</STRONG>,
201 <STRONG>carriage_return</STRONG>, <STRONG>cursor_left</STRONG>, <STRONG>cursor_down</STRONG>, <STRONG>scroll_forward</STRONG>, <STRONG>tab</STRONG>,
202 <STRONG>newline</STRONG>, <STRONG>key_backspace</STRONG>, <STRONG>key_left</STRONG>, and <STRONG>key_down</STRONG>, then attempts to
203 use obsolete termcap capabilities to deduce correct values. It
204 also normally suppresses output of obsolete termcap capabilities
205 such as <STRONG>bs</STRONG>. This option forces a more literal translation that
206 also preserves the obsolete capabilities.
208 <STRONG>-o</STRONG><EM>dir</EM> Write compiled entries to given database location. Overrides
209 the TERMINFO environment variable.
211 <STRONG>-Q</STRONG><EM>n</EM> Rather than show source in terminfo (text) format, print the
212 compiled (binary) format in hexadecimal or base64 form,
213 depending on the option's value:
219 3 hexadecimal and base64
221 <STRONG>-q</STRONG> Suppress comments and blank lines when showing translated
224 <STRONG>-R</STRONG><EM>subset</EM>
225 Restrict output to a given subset. This option is for use with
226 archaic versions of terminfo like those on SVr1, Ultrix, or HP-
227 UX that do not support the full set of SVR4/XSI Curses terminfo;
228 and outright broken ports like AIX 3.x that have their own
229 extensions incompatible with SVr4/XSI. Available subsets are
230 "SVr1", "Ultrix", "HP", "BSD" and "AIX"; see <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> for
233 <STRONG>-r</STRONG> Force entry resolution (so there are no remaining tc
234 capabilities) even when doing translation to termcap format.
235 This may be needed if you are preparing a termcap file for a
236 termcap library (such as GNU termcap through version 1.3 or BSD
237 termcap through 4.3BSD) that does not handle multiple tc
238 capabilities per entry.
240 <STRONG>-s</STRONG> Summarize the compile by showing the database location into
241 which entries are written, and the number of entries which are
244 <STRONG>-T</STRONG> eliminates size-restrictions on the generated text. This is
245 mainly useful for testing and analysis, since the compiled
246 descriptions are limited (e.g., 1023 for termcap, 4096 for
249 <STRONG>-t</STRONG> tells <STRONG>tic</STRONG> to discard commented-out capabilities. Normally when
250 translating from terminfo to termcap, untranslatable
251 capabilities are commented-out.
253 <STRONG>-U</STRONG> tells <STRONG>tic</STRONG> to not post-process the data after parsing the source
254 file. Normally, it infers data which is commonly missing in older
255 terminfo data, or in termcaps.
257 <STRONG>-V</STRONG> reports the version of ncurses which was used in this program, and
260 <STRONG>-v</STRONG><EM>n</EM> specifies that (verbose) output be written to standard error trace
261 information showing <STRONG>tic</STRONG>'s progress.
263 The optional parameter <EM>n</EM> is a number from 1 to 9, inclusive,
264 indicating the desired level of detail of information.
266 <STRONG>o</STRONG> If ncurses is built without tracing support, the optional
267 parameter is ignored.
269 <STRONG>o</STRONG> If <EM>n</EM> is omitted, the default level is 1.
271 <STRONG>o</STRONG> If <EM>n</EM> is specified and greater than 1, the level of detail is
272 increased, and the output is written (with tracing
273 information) to the "trace" file.
275 The debug flag levels are as follows:
277 1 Names of files created and linked
279 2 Information related to the "use" facility
281 3 Statistics from the hashing algorithm
283 4 Details of extended capabilities
289 7 Entries into the string-table
291 8 List of tokens encountered by scanner
293 9 All values computed in construction of the hash table
295 <STRONG>-W</STRONG> By itself, the <STRONG>-w</STRONG> option will not force long strings to be
296 wrapped. Use the <STRONG>-W</STRONG> option to do this.
298 If you specify both <STRONG>-f</STRONG> and <STRONG>-W</STRONG> options, the latter is ignored when
299 <STRONG>-f</STRONG> has already split the line.
301 <STRONG>-w</STRONG><EM>n</EM> specifies the width of the output. The parameter is optional. If
302 it is omitted, it defaults to 60.
304 <STRONG>-x</STRONG> Treat unknown capabilities as user-defined (see <STRONG>user_caps(5)</STRONG>).
305 That is, if you supply a capability name which <STRONG>tic</STRONG> does not
306 recognize, it will infer its type (boolean, number or string) from
307 the syntax and make an extended table entry for that. User-
308 defined capability strings whose name begins with "k" are treated
312 </PRE><H3><a name="h3-PARAMETERS">PARAMETERS</a></H3><PRE>
313 <EM>file</EM> contains one or more <STRONG>terminfo</STRONG> terminal descriptions in source
314 format [see <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>]. Each description in the file
315 describes the capabilities of a particular terminal.
317 If <EM>file</EM> is "-", then the data is read from the standard input.
318 The <EM>file</EM> parameter may also be the path of a character-device.
321 </PRE><H3><a name="h3-PROCESSING">PROCESSING</a></H3><PRE>
322 All but one of the capabilities recognized by <STRONG>tic</STRONG> are documented in
323 <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>. The exception is the <STRONG>use</STRONG> capability.
325 When a <STRONG>use</STRONG>=<EM>entry</EM>-<EM>name</EM> field is discovered in a terminal entry currently
326 being compiled, <STRONG>tic</STRONG> reads in the binary from <STRONG>/usr/share/terminfo</STRONG> to
327 complete the entry. (Entries created from <EM>file</EM> will be used first.
328 <STRONG>tic</STRONG> duplicates the capabilities in <EM>entry</EM>-<EM>name</EM> for the current entry,
329 with the exception of those capabilities that explicitly are defined in
332 When an entry, e.g., <STRONG>entry_name_1</STRONG>, contains a <STRONG>use=</STRONG><EM>entry</EM>_<EM>name</EM>_<EM>2</EM> field,
333 any canceled capabilities in <EM>entry</EM>_<EM>name</EM>_<EM>2</EM> must also appear in
334 <STRONG>entry_name_1</STRONG> before <STRONG>use=</STRONG> for these capabilities to be canceled in
335 <STRONG>entry_name_1</STRONG>.
337 Total compiled entries cannot exceed 4096 bytes. The name field cannot
338 exceed 512 bytes. Terminal names exceeding the maximum alias length
339 (32 characters on systems with long filenames, 14 characters otherwise)
340 will be truncated to the maximum alias length and a warning message
344 </PRE><H2><a name="h2-HISTORY">HISTORY</a></H2><PRE>
345 System V Release 2 provided a <STRONG>tic</STRONG> utility. It accepted a single
346 option: <STRONG>-v</STRONG> (optionally followed by a number). According to Ross
347 Ridge's comment in <EM>mytinfo</EM>, this version of <STRONG>tic</STRONG> was unable to represent
348 cancelled capabilities.
350 System V Release 3 provided a different <STRONG>tic</STRONG> utility, written by Pavel
351 Curtis, (originally named "compile" in <EM>pcurses</EM>). This added an option
352 <STRONG>-c</STRONG> to check the file for errors, with the caveat that errors in "use="
353 links would not be reported. System V Release 3 documented a few
354 warning messages which did not appear in <EM>pcurses</EM>. While the program
355 itself was changed little as development continued with System V
356 Release 4, the table of capabilities grew from 180 (<EM>pcurses</EM>) to 464
359 In early development of ncurses (1993), Zeyd Ben-Halim used the table
360 from <EM>mytinfo</EM> to extend the <EM>pcurses</EM> table to 469 capabilities (456
361 matched SVr4, 8 were only in SVr4, 13 were not in SVr4). Of those 13,
362 11 were ultimately discarded (perhaps to match the draft of X/Open
363 Curses). The exceptions were <STRONG>memory_lock_above</STRONG> and <STRONG>memory_unlock</STRONG> (see
364 <STRONG><A HREF="user_caps.5.html">user_caps(5)</A></STRONG>).
366 Eric Raymond incorporated parts of <EM>mytinfo</EM> into ncurses to implement
367 the termcap-to-terminfo source conversion, and extended that to begin
368 development of the corresponding terminfo-to-termcap source conversion,
369 Thomas Dickey completed that development over the course of several
372 In 1999, Thomas Dickey added the <STRONG>-x</STRONG> option to support user-defined
375 In 2010, Roy Marples provided a <STRONG>tic</STRONG> program and terminfo library for
376 NetBSD. That implementation adapts several features from ncurses,
377 including <STRONG>tic</STRONG>'s <STRONG>-x</STRONG> option.
379 The <STRONG>-c</STRONG> option tells <STRONG>tic</STRONG> to check for problems in the terminfo source
380 file. Continued development provides additional checks:
382 <STRONG>o</STRONG> <EM>pcurses</EM> had 8 warnings
384 <STRONG>o</STRONG> ncurses in 1996 had 16 warnings
386 <STRONG>o</STRONG> Solaris (SVr4) curses has 28 warnings
388 <STRONG>o</STRONG> NetBSD tic in 2019 has 19 warnings.
390 <STRONG>o</STRONG> ncurses in 2019 has 96 warnings
392 The checking done in ncurses' <STRONG>tic</STRONG> helps with the conversion to termcap,
393 as well as pointing out errors and inconsistencies. It is also used to
394 ensure consistency with the user-defined capabilities. There are 527
395 distinct capabilities in ncurses' terminal database; 128 of those are
399 </PRE><H2><a name="h2-PORTABILITY">PORTABILITY</a></H2><PRE>
400 X/Open Curses, Issue 7 (2009) provides a brief description of <STRONG>tic</STRONG>. It
401 lists one option: <STRONG>-c</STRONG>. The omission of <STRONG>-v</STRONG> is unexpected. The change
402 history states that the description is derived from True64 UNIX.
403 According to its manual pages, that system also supported the <STRONG>-v</STRONG>
406 Shortly after Issue 7 was released, Tru64 was discontinued. As of
407 2019, the surviving implementations of <STRONG>tic</STRONG> are SVr4 (AIX, HP-UX and
408 Solaris), ncurses and NetBSD curses. The SVr4 <STRONG>tic</STRONG> programs all support
409 the <STRONG>-v</STRONG> option. The NetBSD <STRONG>tic</STRONG> program follows X/Open's documentation,
410 omitting the <STRONG>-v</STRONG> option.
412 The X/Open rationale states that some implementations of <STRONG>tic</STRONG> read
413 terminal descriptions from the standard input if the <EM>file</EM> parameter is
414 omitted. None of these implementations do that. Further, it comments
415 that some may choose to read from "./terminfo.src" but that is
416 obsolescent behavior from SVr2, and is not (for example) a documented
420 </PRE><H3><a name="h3-COMPATIBILITY">COMPATIBILITY</a></H3><PRE>
421 There is some evidence that historic <STRONG>tic</STRONG> implementations treated
422 description fields with no whitespace in them as additional aliases or
423 short names. This <STRONG>tic</STRONG> does not do that, but it does warn when
424 description fields may be treated that way and check them for dangerous
428 </PRE><H3><a name="h3-EXTENSIONS">EXTENSIONS</a></H3><PRE>
429 Unlike the SVr4 <STRONG>tic</STRONG> command, this implementation can actually compile
430 termcap sources. In fact, entries in terminfo and termcap syntax can
431 be mixed in a single source file. See <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> for the list of
432 termcap names taken to be equivalent to terminfo names.
434 The SVr4 manual pages are not clear on the resolution rules for <STRONG>use</STRONG>
435 capabilities. This implementation of <STRONG>tic</STRONG> will find <STRONG>use</STRONG> targets
436 anywhere in the source file, or anywhere in the file tree rooted at
437 <STRONG>TERMINFO</STRONG> (if <STRONG>TERMINFO</STRONG> is defined), or in the user's <EM>$HOME/.terminfo</EM>
438 database (if it exists), or (finally) anywhere in the system's file
439 tree of compiled entries.
441 The error messages from this <STRONG>tic</STRONG> have the same format as GNU C error
442 messages, and can be parsed by GNU Emacs's compile facility.
444 Aside from <STRONG>-c</STRONG> and <STRONG>-v</STRONG>, options are not portable:
446 <STRONG>o</STRONG> Most of tic's options are not supported by SVr4 <STRONG>tic</STRONG>:
448 <STRONG>-0</STRONG> <STRONG>-1</STRONG> <STRONG>-C</STRONG> <STRONG>-G</STRONG> <STRONG>-I</STRONG> <STRONG>-N</STRONG> <STRONG>-R</STRONG> <STRONG>-T</STRONG> <STRONG>-V</STRONG> <STRONG>-a</STRONG> <STRONG>-e</STRONG> <STRONG>-f</STRONG> <STRONG>-g</STRONG> <STRONG>-o</STRONG> <STRONG>-r</STRONG> <STRONG>-s</STRONG> <STRONG>-t</STRONG> <STRONG>-x</STRONG>
450 <STRONG>o</STRONG> The NetBSD <STRONG>tic</STRONG> supports a few of the ncurses options
452 <STRONG>-a</STRONG> <STRONG>-o</STRONG> <STRONG>-x</STRONG>
454 and adds <STRONG>-S</STRONG> (a feature which does the same thing as infocmp's <STRONG>-e</STRONG>
455 and <STRONG>-E</STRONG> options).
457 The SVr4 <STRONG>-c</STRONG> mode does not report bad "use=" links.
459 System V does not compile entries to or read entries from your
460 <EM>$HOME/.terminfo</EM> database unless TERMINFO is explicitly set to it.
463 </PRE><H2><a name="h2-FILES">FILES</a></H2><PRE>
464 <STRONG>/usr/share/terminfo/?/*</STRONG>
465 Compiled terminal description database.
468 </PRE><H2><a name="h2-SEE-ALSO">SEE ALSO</a></H2><PRE>
469 <STRONG><A HREF="captoinfo.1m.html">captoinfo(1m)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="infotocap.1m.html">infotocap(1m)</A></STRONG>, <STRONG><A HREF="toe.1m.html">toe(1m)</A></STRONG>, <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>,
470 <STRONG><A HREF="term.5.html">term(5)</A></STRONG>. <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>. <STRONG><A HREF="user_caps.5.html">user_caps(5)</A></STRONG>.
472 This describes <STRONG>ncurses</STRONG> version 6.3 (patch 20220917).
475 </PRE><H2><a name="h2-AUTHOR">AUTHOR</a></H2><PRE>
476 Eric S. Raymond <esr@snark.thyrsus.com> and
477 Thomas E. Dickey <dickey@invisible-island.net>
481 <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>
485 <li><a href="#h2-NAME">NAME</a></li>
486 <li><a href="#h2-SYNOPSIS">SYNOPSIS</a></li>
487 <li><a href="#h2-DESCRIPTION">DESCRIPTION</a>
489 <li><a href="#h3-ALIASES">ALIASES</a></li>
490 <li><a href="#h3-OPTIONS">OPTIONS</a></li>
491 <li><a href="#h3-PARAMETERS">PARAMETERS</a></li>
492 <li><a href="#h3-PROCESSING">PROCESSING</a></li>
495 <li><a href="#h2-HISTORY">HISTORY</a></li>
496 <li><a href="#h2-PORTABILITY">PORTABILITY</a>
498 <li><a href="#h3-COMPATIBILITY">COMPATIBILITY</a></li>
499 <li><a href="#h3-EXTENSIONS">EXTENSIONS</a></li>
502 <li><a href="#h2-FILES">FILES</a></li>
503 <li><a href="#h2-SEE-ALSO">SEE ALSO</a></li>
504 <li><a href="#h2-AUTHOR">AUTHOR</a></li>