* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
* Beginning of terminfo.tail file
* This file is part of ncurses.
* See "terminfo.head" for copyright.
* Beginning of terminfo.tail file
* This file is part of ncurses.
* See "terminfo.head" for copyright.
nals by giving a set of capabilities which they have, by
specifying how to perform screen operations, and by speci-
fying padding requirements and initialization sequences.
nals by giving a set of capabilities which they have, by
specifying how to perform screen operations, and by speci-
fying padding requirements and initialization sequences.
Entries in <EM>terminfo</EM> consist of a sequence of `,' separated
fields (embedded commas may be escaped with a backslash or
Entries in <EM>terminfo</EM> consist of a sequence of `,' separated
fields (embedded commas may be escaped with a backslash or
Lines beginning with a `#' in the first column are treated
as comments. While comment lines are legal at any point,
Lines beginning with a `#' in the first column are treated
as comments. While comment lines are legal at any point,
will move comments so they occur only between entries.
Newlines and leading tabs may be used for formatting
entries for readability. These are removed from parsed
will move comments so they occur only between entries.
Newlines and leading tabs may be used for formatting
entries for readability. These are removed from parsed
- entries. The <EM>infocmp</EM> <EM>-f</EM> option relies on this to format
- if-then-else expressions: the result can be read by <EM>tic</EM>.
+ entries. The <STRONG>infocmp</STRONG> <STRONG>-f</STRONG> option relies on this to format
+ if-then-else expressions: the result can be read by <STRONG>tic</STRONG>.
Terminal names (except for the last, verbose entry) should
be chosen using the following conventions. The particular
Terminal names (except for the last, verbose entry) should
be chosen using the following conventions. The particular
<STRONG>Parameterized</STRONG> <STRONG>Strings</STRONG>
Cursor addressing and other strings requiring parameters
in the terminal are described by a parameterized string
<STRONG>Parameterized</STRONG> <STRONG>Strings</STRONG>
Cursor addressing and other strings requiring parameters
in the terminal are described by a parameterized string
example, to address the cursor, the <STRONG>cup</STRONG> capability is
given, using two parameters: the row and column to address
to. (Rows and columns are numbered from zero and refer to
example, to address the cursor, the <STRONG>cup</STRONG> capability is
given, using two parameters: the row and column to address
to. (Rows and columns are numbered from zero and refer to
- <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="printf.3S.html">printf(3S)</A></STRONG>, <STRONG><A HREF="term.5.html">term(5)</A></STRONG>.
+ <STRONG><A HREF="tic.1m.html">tic(1m)</A></STRONG>, <STRONG><A HREF="infocmp.1m.html">infocmp(1m)</A></STRONG>, <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="printf.3.html">printf(3)</A></STRONG>, <STRONG><A HREF="term.5.html">term(5)</A></STRONG>.