diff options
Diffstat (limited to 'doc/html/man/terminfo.5.html')
| -rw-r--r-- | doc/html/man/terminfo.5.html | 886 |
1 files changed, 441 insertions, 445 deletions
diff --git a/doc/html/man/terminfo.5.html b/doc/html/man/terminfo.5.html index 67061141faca..0fe01942c9ec 100644 --- a/doc/html/man/terminfo.5.html +++ b/doc/html/man/terminfo.5.html @@ -1,11 +1,14 @@ <!-- * t * DO NOT EDIT THIS FILE BY HAND! - * It is generated from terminfo.head, ./../include/Caps ./../include/Caps-ncurses, and terminfo.tail. - * Note: this must be run through tbl before nroff. - * The magic cookie on the first line triggers this under some man programs. + * man/MKterminfo.sh generated it from: + * terminfo.head, ./../include/Caps, ./../include/Caps-ncurses, + * and terminfo.tail. + * Note: this document must be run through tbl before nroff or troff. + * Some man(1) programs recognize the token in the first-line comment + * as directing them to arrange such a pipeline. **************************************************************************** - * Copyright 2018-2023,2024 Thomas E. Dickey * + * Copyright 2018-2024,2025 Thomas E. Dickey * * Copyright 1998-2016,2017 Free Software Foundation, Inc. * * * * Permission is hereby granted, free of charge, to any person obtaining a * @@ -32,25 +35,23 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: terminfo.head,v 1.65 2024/04/20 21:14:00 tom Exp @ + * @Id: terminfo.head,v 1.69 2025/08/16 21:50:23 tom Exp @ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <HTML> <HEAD> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="generator" content="Manpage converted by man2html - see https://invisible-island.net/scripts/readme.html#others_scripts"> -<TITLE>terminfo 5 2024-04-20 ncurses 6.5 File formats</TITLE> +<TITLE>terminfo 5 2025-08-16 ncurses 6.6 File formats</TITLE> <link rel="author" href="mailto:bug-ncurses@gnu.org"> </HEAD> <BODY> -<H1 class="no-header">terminfo 5 2024-04-20 ncurses 6.5 File formats</H1> +<H1 class="no-header">terminfo 5 2025-08-16 ncurses 6.6 File formats</H1> <PRE> <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> File formats <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> - - </PRE><H2><a name="h2-NAME">NAME</a></H2><PRE> <STRONG>terminfo</STRONG> - terminal capability database @@ -71,7 +72,7 @@ have, by specifying how to perform screen operations, and by specifying padding requirements and initialization sequences. - This document describes <EM>ncurses</EM> version 6.5 (patch 20240427). + This document describes <EM>ncurses</EM> version 6.6 (patch 20251230). </PRE><H3><a name="h3-terminfo-Entry-Syntax"><EM>terminfo</EM> Entry Syntax</a></H3><PRE> @@ -107,10 +108,10 @@ This implementation is not so strict; it allows mixed case in the primary name and aliases. If the last name has no embedded blanks, - it allows that to be both an alias and a verbose name (but will + it allows that to be both an alias and a verbose name (but will warn about this ambiguity). - <STRONG>o</STRONG> Lines beginning with a "#" in the first column are treated as + <STRONG>o</STRONG> Lines beginning with a "#" in the first column are treated as comments. While comment lines are valid at any point, the output of <STRONG>captoinfo</STRONG> @@ -121,8 +122,8 @@ using the following conventions. The particular piece of hardware making up the terminal should have a root name, thus "hp2621". This name should not contain hyphens. Modes that the hardware can be in, or - user preferences, should be indicated by appending a hyphen and a mode - suffix. Thus, a vt100 in 132-column mode would be vt100-w. The + user preferences, should be indicated by appending a hyphen and a mode + suffix. Thus, a vt100 in 132-column mode would be vt100-w. The following suffixes should be used where possible: <STRONG>Suffix</STRONG> <STRONG>Example</STRONG> <STRONG>Meaning</STRONG> @@ -145,51 +146,51 @@ </PRE><H3><a name="h3-terminfo-Capabilities-Syntax"><EM>terminfo</EM> Capabilities Syntax</a></H3><PRE> - The terminfo entry consists of several <EM>capabilities</EM>, i.e., features - that the terminal has, or methods for exercising the terminal's + The terminfo entry consists of several <EM>capabilities</EM>, i.e., features + that the terminal has, or methods for exercising the terminal's features. After the first field (giving the name(s) of the terminal entry), there should be one or more <EM>capability</EM> fields. These are Boolean, numeric or string names with corresponding values: - <STRONG>o</STRONG> Boolean capabilities are true when present, false when absent. + <STRONG>o</STRONG> Boolean capabilities are true when present, false when absent. There is no explicit value for Boolean capabilities. - <STRONG>o</STRONG> Numeric capabilities have a "#" following the name, then an + <STRONG>o</STRONG> Numeric capabilities have a "#" following the name, then an unsigned decimal integer value. - <STRONG>o</STRONG> String capabilities have a "=" following the name, then an string + <STRONG>o</STRONG> String capabilities have a "=" following the name, then an string of characters making up the capability value. - String capabilities can be split into multiple lines, just as the - fields comprising a terminal entry can be split into multiple - lines. While blanks between fields are ignored, blanks embedded - within a string value are retained, except for leading blanks on a + String capabilities can be split into multiple lines, just as the + fields comprising a terminal entry can be split into multiple + lines. While blanks between fields are ignored, blanks embedded + within a string value are retained, except for leading blanks on a line. - Any capability can be <EM>canceled</EM>, i.e., suppressed from the terminal + Any capability can be <EM>canceled</EM>, i.e., suppressed from the terminal entry, by following its name with "@" rather than a capability value. </PRE><H3><a name="h3-Similar-Terminals">Similar Terminals</a></H3><PRE> - If there are two very similar terminals, one (the variant) can be - defined as being just like the other (the base) with certain - exceptions. In the definition of the variant, the string capability + If there are two very similar terminals, one (the variant) can be + defined as being just like the other (the base) with certain + exceptions. In the definition of the variant, the string capability <STRONG>use</STRONG> can be given with the name of the base terminal: - <STRONG>o</STRONG> The capabilities given before <STRONG>use</STRONG> override those in the base type + <STRONG>o</STRONG> The capabilities given before <STRONG>use</STRONG> override those in the base type named by <STRONG>use</STRONG>. - <STRONG>o</STRONG> If there are multiple <STRONG>use</STRONG> capabilities, they are merged in reverse - order. That is, the rightmost <STRONG>use</STRONG> reference is processed first, + <STRONG>o</STRONG> If there are multiple <STRONG>use</STRONG> capabilities, they are merged in reverse + order. That is, the rightmost <STRONG>use</STRONG> reference is processed first, then the one to its left, and so forth. - <STRONG>o</STRONG> Capabilities given explicitly in the entry override those brought + <STRONG>o</STRONG> Capabilities given explicitly in the entry override those brought in by <STRONG>use</STRONG> references. - A capability can be canceled by placing <STRONG>xx@</STRONG> to the left of the use - reference that imports it, where <EM>xx</EM> is the capability. For example, + A capability can be canceled by placing <STRONG>xx@</STRONG> to the left of the use + reference that imports it, where <EM>xx</EM> is the capability. For example, the entry 2621-nl, smkx@, rmkx@, use=2621, @@ -200,15 +201,15 @@ user preferences. An entry included via <STRONG>use</STRONG> can contain canceled capabilities, which have - the same effect as if those cancels were inline in the using terminal + the same effect as if those cancels were inline in the using terminal entry. -</PRE><H3><a name="h3-Predefined-Capabilities">Predefined Capabilities</a></H3><PRE> - Tables of capabilities <EM>ncurses</EM> recognizes in a <EM>terminfo</EM> terminal type +</PRE><H3><a name="h3-Standard-Capabilities">Standard Capabilities</a></H3><PRE> + Tables of capabilities <EM>ncurses</EM> recognizes in a <EM>terminfo</EM> terminal type description and available to <EM>terminfo</EM>-using code follow. - <STRONG>o</STRONG> The capability name identifies the symbol by which the programmer + <STRONG>o</STRONG> The capability name identifies the symbol by which the programmer using the <EM>terminfo</EM> API accesses the capability. <STRONG>o</STRONG> The TI (<EM>terminfo</EM>) code is the short name used by a person composing @@ -219,38 +220,36 @@ uses identical or very similar names). Semantics are also intended to match those of the specification. - <EM>terminfo</EM> codes have no hard length limit, but <EM>ncurses</EM> maintains an - informal one of 5 characters to keep them short and to allow the - tabs in the source file <EM>Caps</EM> to line up nicely. (Some standard + <EM>terminfo</EM> codes have no hard length limit, but <EM>ncurses</EM> maintains an + informal one of 5 characters to keep them short and to allow the + tabs in the source file <EM>Caps</EM> to line up nicely. (Some standard codes exceed this limit regardless.) - <STRONG>o</STRONG> The TC (<EM>termcap</EM>) code is that used by the corresponding API of - <EM>ncurses</EM>. (Some capabilities are new, and have names that BSD + <STRONG>o</STRONG> The TC (<EM>termcap</EM>) code is that used by the corresponding API of + <EM>ncurses</EM>. (Some capabilities are new, and have names that BSD <EM>termcap</EM> did not originate.) - <STRONG>o</STRONG> The description field attempts to convey the capability's + <STRONG>o</STRONG> The description field attempts to convey the capability's semantics. The description field employs a handful of notations. <STRONG>(P)</STRONG> indicates that padding may be specified. - <STRONG>(P*)</STRONG> indicates that padding may vary in proportion to the number of + <STRONG>(P*)</STRONG> indicates that padding may vary in proportion to the number of output lines affected. - <STRONG>#</STRONG><EM>i</EM> indicates the <EM>i</EM>th parameter of a string capability; the - programmer should pass the string to <STRONG><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG> with the + <STRONG>#</STRONG><EM>i</EM> indicates the <EM>i</EM>th parameter of a string capability; the + programmer should pass the string to <STRONG><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG> with the parameters listed. - If the description lists no parameters, passing the string to - <STRONG><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG> may produce unexpected behavior, for instance if the + If the description lists no parameters, passing the string to + <STRONG><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG> may produce unexpected behavior, for instance if the string contains percent signs. <STRONG>Code</STRONG> <STRONG>Boolean</STRONG> <STRONG>Capability</STRONG> <STRONG>Name</STRONG> <STRONG>TI</STRONG> <STRONG>TC</STRONG> <STRONG>Description</STRONG> ------------------------------------------------------------------------ - - <STRONG>auto_left_margin</STRONG> <STRONG>bw</STRONG> <STRONG>bw</STRONG> cub1 wraps from column 0 to last column <STRONG>auto_right_margin</STRONG> <STRONG>am</STRONG> <STRONG>am</STRONG> terminal has automatic margins @@ -316,7 +315,6 @@ resolution <STRONG>Code</STRONG> - <STRONG>Numeric</STRONG> <STRONG>Capability</STRONG> <STRONG>Name</STRONG> <STRONG>TI</STRONG> <STRONG>TC</STRONG> <STRONG>Description</STRONG> ------------------------------------------------------------------------ <STRONG>columns</STRONG> <STRONG>cols</STRONG> <STRONG>co</STRONG> number of columns in a line @@ -382,7 +380,6 @@ <STRONG>wide_char_size</STRONG> <STRONG>widcs</STRONG> <STRONG>Yn</STRONG> character step size when in double wide mode <STRONG>buttons</STRONG> <STRONG>btns</STRONG> <STRONG>BT</STRONG> number of buttons on mouse - <STRONG>bit_image_entwining</STRONG> <STRONG>bitwin</STRONG> <STRONG>Yo</STRONG> number of passes for each bit- image row <STRONG>bit_image_type</STRONG> <STRONG>bitype</STRONG> <STRONG>Yp</STRONG> type of bit-image device @@ -448,7 +445,6 @@ cup <STRONG>exit_delete_mode</STRONG> <STRONG>rmdc</STRONG> <STRONG>ed</STRONG> end delete mode <STRONG>exit_insert_mode</STRONG> <STRONG>rmir</STRONG> <STRONG>ei</STRONG> exit insert mode - <STRONG>exit_standout_mode</STRONG> <STRONG>rmso</STRONG> <STRONG>se</STRONG> exit standout mode <STRONG>exit_underline_mode</STRONG> <STRONG>rmul</STRONG> <STRONG>ue</STRONG> exit underline mode <STRONG>flash_screen</STRONG> <STRONG>flash</STRONG> <STRONG>vb</STRONG> visible bell (may not move @@ -471,7 +467,6 @@ <STRONG>key_dc</STRONG> <STRONG>kdch1</STRONG> <STRONG>kD</STRONG> delete-character key <STRONG>key_dl</STRONG> <STRONG>kdl1</STRONG> <STRONG>kL</STRONG> delete-line key <STRONG>key_down</STRONG> <STRONG>kcud1</STRONG> <STRONG>kd</STRONG> down-arrow key - <STRONG>key_eic</STRONG> <STRONG>krmir</STRONG> <STRONG>kM</STRONG> sent by rmir or smir in insert mode <STRONG>key_eol</STRONG> <STRONG>kel</STRONG> <STRONG>kE</STRONG> clear-to-end-of-line key @@ -499,8 +494,8 @@ <STRONG>key_sr</STRONG> <STRONG>kri</STRONG> <STRONG>kR</STRONG> scroll-backward key <STRONG>key_stab</STRONG> <STRONG>khts</STRONG> <STRONG>kT</STRONG> set-tab key <STRONG>key_up</STRONG> <STRONG>kcuu1</STRONG> <STRONG>ku</STRONG> up-arrow key - <STRONG>keypad_local</STRONG> <STRONG>rmkx</STRONG> <STRONG>ke</STRONG> leave keyboard transmit mode - <STRONG>keypad_xmit</STRONG> <STRONG>smkx</STRONG> <STRONG>ks</STRONG> enter keyboard transmit mode + <STRONG>keypad_local</STRONG> <STRONG>rmkx</STRONG> <STRONG>ke</STRONG> leave keypad transmit mode + <STRONG>keypad_xmit</STRONG> <STRONG>smkx</STRONG> <STRONG>ks</STRONG> enter keypad transmit mode <STRONG>lab_f0</STRONG> <STRONG>lf0</STRONG> <STRONG>l0</STRONG> label on function key f0 if not f0 <STRONG>lab_f1</STRONG> <STRONG>lf1</STRONG> <STRONG>l1</STRONG> label on function key f1 if @@ -513,8 +508,6 @@ not f3 <STRONG>lab_f4</STRONG> <STRONG>lf4</STRONG> <STRONG>l4</STRONG> label on function key f4 if not f4 - - <STRONG>lab_f5</STRONG> <STRONG>lf5</STRONG> <STRONG>l5</STRONG> label on function key f5 if not f5 <STRONG>lab_f6</STRONG> <STRONG>lf6</STRONG> <STRONG>l6</STRONG> label on function key f6 if @@ -525,6 +518,7 @@ not f8 <STRONG>lab_f9</STRONG> <STRONG>lf9</STRONG> <STRONG>l9</STRONG> label on function key f9 if not f9 + <STRONG>meta_off</STRONG> <STRONG>rmm</STRONG> <STRONG>mo</STRONG> turn off meta mode <STRONG>meta_on</STRONG> <STRONG>smm</STRONG> <STRONG>mm</STRONG> turn on meta mode (8th-bit on) <STRONG>newline</STRONG> <STRONG>nel</STRONG> <STRONG>nw</STRONG> newline (behave like cr @@ -554,7 +548,6 @@ <STRONG>repeat_char</STRONG> <STRONG>rep</STRONG> <STRONG>rp</STRONG> repeat char #1 #2 times (P*) <STRONG>reset_1string</STRONG> <STRONG>rs1</STRONG> <STRONG>r1</STRONG> reset string <STRONG>reset_2string</STRONG> <STRONG>rs2</STRONG> <STRONG>r2</STRONG> reset string - <STRONG>reset_3string</STRONG> <STRONG>rs3</STRONG> <STRONG>r3</STRONG> reset string <STRONG>reset_file</STRONG> <STRONG>rf</STRONG> <STRONG>rf</STRONG> name of reset file <STRONG>restore_cursor</STRONG> <STRONG>rc</STRONG> <STRONG>rc</STRONG> restore cursor to position of @@ -580,7 +573,6 @@ <STRONG>init_prog</STRONG> <STRONG>iprog</STRONG> <STRONG>iP</STRONG> path name of program for initialization <STRONG>key_a1</STRONG> <STRONG>ka1</STRONG> <STRONG>K1</STRONG> upper left of keypad - <STRONG>key_a3</STRONG> <STRONG>ka3</STRONG> <STRONG>K3</STRONG> upper right of keypad <STRONG>key_b2</STRONG> <STRONG>kb2</STRONG> <STRONG>K2</STRONG> center of keypad <STRONG>key_c1</STRONG> <STRONG>kc1</STRONG> <STRONG>K4</STRONG> lower left of keypad @@ -630,7 +622,6 @@ <STRONG>key_save</STRONG> <STRONG>ksav</STRONG> <STRONG>&6</STRONG> save key <STRONG>key_suspend</STRONG> <STRONG>kspd</STRONG> <STRONG>&7</STRONG> suspend key <STRONG>key_undo</STRONG> <STRONG>kund</STRONG> <STRONG>&8</STRONG> undo key - <STRONG>key_sbeg</STRONG> <STRONG>kBEG</STRONG> <STRONG>&9</STRONG> shifted begin key <STRONG>key_scancel</STRONG> <STRONG>kCAN</STRONG> <STRONG>&0</STRONG> shifted cancel key <STRONG>key_scommand</STRONG> <STRONG>kCMD</STRONG> <STRONG>*1</STRONG> shifted command key @@ -646,7 +637,6 @@ <STRONG>key_sfind</STRONG> <STRONG>kFND</STRONG> <STRONG>*0</STRONG> shifted find key <STRONG>key_shelp</STRONG> <STRONG>kHLP</STRONG> <STRONG>#1</STRONG> shifted help key <STRONG>key_shome</STRONG> <STRONG>kHOM</STRONG> <STRONG>#2</STRONG> shifted home key - <STRONG>key_sic</STRONG> <STRONG>kIC</STRONG> <STRONG>#3</STRONG> shifted insert-character key <STRONG>key_sleft</STRONG> <STRONG>kLFT</STRONG> <STRONG>#4</STRONG> shifted left-arrow key <STRONG>key_smessage</STRONG> <STRONG>kMSG</STRONG> <STRONG>%a</STRONG> shifted message key @@ -696,7 +686,6 @@ <STRONG>key_f40</STRONG> <STRONG>kf40</STRONG> <STRONG>FU</STRONG> F40 function key <STRONG>key_f41</STRONG> <STRONG>kf41</STRONG> <STRONG>FV</STRONG> F41 function key <STRONG>key_f42</STRONG> <STRONG>kf42</STRONG> <STRONG>FW</STRONG> F42 function key - <STRONG>key_f43</STRONG> <STRONG>kf43</STRONG> <STRONG>FX</STRONG> F43 function key <STRONG>key_f44</STRONG> <STRONG>kf44</STRONG> <STRONG>FY</STRONG> F44 function key <STRONG>key_f45</STRONG> <STRONG>kf45</STRONG> <STRONG>FZ</STRONG> F45 function key @@ -712,7 +701,6 @@ <STRONG>key_f55</STRONG> <STRONG>kf55</STRONG> <STRONG>Fj</STRONG> F55 function key <STRONG>key_f56</STRONG> <STRONG>kf56</STRONG> <STRONG>Fk</STRONG> F56 function key <STRONG>key_f57</STRONG> <STRONG>kf57</STRONG> <STRONG>Fl</STRONG> F57 function key - <STRONG>key_f58</STRONG> <STRONG>kf58</STRONG> <STRONG>Fm</STRONG> F58 function key <STRONG>key_f59</STRONG> <STRONG>kf59</STRONG> <STRONG>Fn</STRONG> F59 function key <STRONG>key_f60</STRONG> <STRONG>kf60</STRONG> <STRONG>Fo</STRONG> F60 function key @@ -776,9 +764,7 @@ <STRONG>define_char</STRONG> <STRONG>defc</STRONG> <STRONG>ZE</STRONG> Define a character #1, #2 dots wide, descender #3 <STRONG>enter_doublewide_mode</STRONG> <STRONG>swidm</STRONG> <STRONG>ZF</STRONG> Enter double-wide mode - <STRONG>enter_draft_quality</STRONG> <STRONG>sdrfq</STRONG> <STRONG>ZG</STRONG> Enter draft-quality mode - <STRONG>enter_italics_mode</STRONG> <STRONG>sitm</STRONG> <STRONG>ZH</STRONG> Enter italic mode <STRONG>enter_leftward_mode</STRONG> <STRONG>slm</STRONG> <STRONG>ZI</STRONG> Start leftward carriage motion <STRONG>enter_micro_mode</STRONG> <STRONG>smicm</STRONG> <STRONG>ZJ</STRONG> Start micro-motion mode @@ -863,6 +849,7 @@ using ANSI escape <STRONG>set_a_background</STRONG> <STRONG>setab</STRONG> <STRONG>AB</STRONG> Set background color to #1, using ANSI escape + <STRONG>pkey_plab</STRONG> <STRONG>pfxl</STRONG> <STRONG>xl</STRONG> Program function key #1 to type string #2 and show string #3 @@ -910,7 +897,6 @@ binary-compatible with System V terminfo entries after SVr4.1; beware! <STRONG>Code</STRONG> - <STRONG>String</STRONG> <STRONG>Capability</STRONG> <STRONG>Name</STRONG> <STRONG>TI</STRONG> <STRONG>TC</STRONG> <STRONG>Description</STRONG> ------------------------------------------------------------------------ <STRONG>enter_horizontal_hl_mode</STRONG> <STRONG>ehhlm</STRONG> <STRONG>Xh</STRONG> Enter horizontal highlight @@ -929,51 +915,54 @@ </PRE><H3><a name="h3-User-Defined-Capabilities">User-Defined Capabilities</a></H3><PRE> - The preceding section listed the <EM>predefined</EM> capabilities. They deal - with some special features for terminals no longer (or possibly never) - produced. Occasionally there are special features of newer terminals - which are awkward or impossible to represent by reusing the predefined - capabilities. - - <EM>ncurses</EM> addresses this limitation by allowing user-defined - capabilities. The <STRONG>tic</STRONG> and <STRONG>infocmp</STRONG> programs provide the <STRONG>-x</STRONG> option for - this purpose. When <STRONG>-x</STRONG> is set, <STRONG>tic</STRONG> treats unknown capabilities as user- - defined. That is, if <STRONG>tic</STRONG> encounters a capability name which it does - not recognize, it infers its type (Boolean, number or string) from the - syntax and makes an extended table entry for that capability. The - <STRONG><A HREF="curs_extend.3x.html">use_extended_names(3x)</A></STRONG> function makes this information conditionally - available to applications. The <EM>ncurses</EM> library provides the data - leaving most of the behavior to applications: - - <STRONG>o</STRONG> User-defined capability strings whose name begins with "k" are - treated as function keys. - - <STRONG>o</STRONG> The types (Boolean, number, string) determined by <STRONG>tic</STRONG> can be - inferred by successful calls on <STRONG>tigetflag</STRONG>, etc. + The preceding section listed the <EM>standard</EM> capabilities. Some are + esoteric, supporting functionality that terminal emulators do not + implement, or may never have been realized in manufactured hardware. + Occasionally, emulators have special features that are awkward or + impossible to represent via standard capabilities. + + <EM>ncurses</EM> addresses this limitation by allowing user-defined + capabilities. The <STRONG>tic</STRONG> and <STRONG>infocmp</STRONG> programs provide an <STRONG>-x</STRONG> option for + this purpose. When <STRONG>-x</STRONG> is used, <STRONG>tic</STRONG> treats unknown capabilities as + user-defined. That is, if <STRONG>tic</STRONG> encounters a capability name that it + does not recognize, the program infers the capability's type (Boolean, + numeric, or string) from the syntax of the capability value and makes + an extended table entry for that capability. <STRONG><A HREF="curs_extend.3x.html">use_extended_names(3x)</A></STRONG> + makes this information conditionally available to applications. + <EM>ncurses</EM> library functions supply callers with capability data, the + interpretation of which is mostly up to the application. + + <STRONG>o</STRONG> <EM>ncurses</EM> treats user-defined string capabilities whose names begin + with "k" as function keys. + + <STRONG>o</STRONG> Capability types (Boolean, numeric, or string) determined by <STRONG>tic</STRONG> + can be inferred by successful <STRONG><A HREF="curs_terminfo.3x.html">tigetflag(3x)</A></STRONG>, <STRONG><A HREF="curs_terminfo.3x.html">tigetnum(3x)</A></STRONG>, and + <STRONG><A HREF="curs_terminfo.3x.html">tigetstr(3x)</A></STRONG> calls. <STRONG>o</STRONG> If the capability name happens to be two characters, the capability is also available through the termcap interface. - While termcap is said to be extensible because it does not use a - predefined set of capabilities, in practice it has been limited to the - capabilities defined by terminfo implementations. As a rule, user- - defined capabilities intended for use by termcap applications should be - limited to Booleans and numbers to avoid running past the 1023 byte - limit assumed by termcap implementations and their applications. In - particular, providing extended sets of function keys (past the 60 - numbered keys and the handful of special named keys) is best done using - the longer names available using terminfo. + While <EM>termcap</EM> is said to be extensible because it mandates no + capabilities, in practice it has been limited to those defined by <EM>term-</EM> + <EM>info</EM> implementations. As a rule, employ only user-defined capabilities + of Boolean and numeric type with <EM>termcap</EM> applications to avoid + overrunning the 1023 byte limit assumed by <EM>termcap</EM> implementations and + their applications. Specifically, support for extended sets of + function keys (past the 60 numbered keys and the handful of special + named keys) is better achieved with longer names available via <EM>term-</EM> + <EM>info</EM>. The <EM>ncurses</EM> library uses a few of these user-defined capabilities, as - described in <STRONG><A HREF="user_caps.5.html">user_caps(5)</A></STRONG>. Other user-defined capabilities (including - function keys) are described in the terminal database, in the section - on <EM>NCURSES</EM> <EM>USER-DEFINABLE</EM> <EM>CAPABILITIES</EM> + described in <STRONG><A HREF="user_caps.5.html">user_caps(5)</A></STRONG>. For other user-defined capabilities, + including function keys, consult the source form of the terminal + database, <EM>terminfo.src</EM>, under the heading "NCURSES USER-DEFINABLE + CAPABILITIES". </PRE><H3><a name="h3-A-Sample-Entry">A Sample Entry</a></H3><PRE> - The following entry, describing an ANSI-standard terminal, is - representative of what a <STRONG>terminfo</STRONG> entry for a modern terminal typically - looks like. + The following entry, describing an ANSI X3.64- (or ECMA-48-) -standard + terminal (henceforth "ANSI-standard" for brevity), is representative of + what a <EM>terminfo</EM> entry for a modern terminal typically looks like. ansi|ansi/pc-term compatible with color, am, mc5i, mir, msgr, @@ -1016,7 +1005,7 @@ <STRONG>o</STRONG> numeric capabilities giving the size of the terminal or the size of particular delays, and - <STRONG>o</STRONG> string capabilities, which give a sequence which can be used to + <STRONG>o</STRONG> string capabilities, which give a sequence which can be used to perform particular terminal operations. @@ -1027,15 +1016,15 @@ <STRONG>am</STRONG>. Hence the description of ansi includes <STRONG>am</STRONG>. Numeric capabilities are followed by the character "#" and then a positive value. Thus <STRONG>cols</STRONG>, which indicates the number of columns the terminal has, gives the - value "80" for ansi. Values for numeric capabilities may be specified - in decimal, octal, or hexadecimal, using the C programming language + value "80" for ansi. Values for numeric capabilities may be specified + in decimal, octal, or hexadecimal, using the C programming language conventions (e.g., 255, 0377 and 0xff or 0xFF). - Finally, string valued capabilities, such as <STRONG>el</STRONG> (clear to end of line - sequence) are given by the two-character code, an "=", and then a + Finally, string valued capabilities, such as <STRONG>el</STRONG> (clear to end of line + sequence) are given by the two-character code, an "=", and then a string ending at the next following ",". - A number of escape sequences are provided in the string valued + A number of escape sequences are provided in the string valued capabilities for easy encoding of characters there: <STRONG>o</STRONG> Both <STRONG>\E</STRONG> and <STRONG>\e</STRONG> map to an ESCAPE character, @@ -1055,8 +1044,8 @@ X/Open Curses does not say what "appropriate <EM>x</EM>" might be. In practice, that is a printable ASCII graphic character. The special case "^?" is interpreted as DEL (127). In all other cases, the character value is - AND'd with 0x1f, mapping to ASCII control codes in the range 0 through - 31. + logically "and"-ed with 0x1f, mapping to ASCII control codes in the + range 0 through 31. Other escapes include @@ -1071,28 +1060,28 @@ <STRONG>o</STRONG> and <STRONG>\0</STRONG> for null. <STRONG>\0</STRONG> will produce \200, which does not terminate a string but behaves - as a null character on most terminals, providing CS7 is specified. + as a null character on most terminals, providing CS7 is specified. See <STRONG>stty(1)</STRONG>. - The reason for this quirk is to maintain binary compatibility of - the compiled terminfo files with other implementations, e.g., the - SVr4 systems, which document this. Compiled terminfo files use - null-terminated strings, with no lengths. Modifying this would - require a new binary format, which would not work with other + The reason for this quirk is to maintain binary compatibility of + the compiled terminfo files with other implementations, e.g., the + SVr4 systems, which document this. Compiled terminfo files use + null-terminated strings, with no lengths. Modifying this would + require a new binary format, which would not work with other implementations. Finally, characters may be given as three octal digits after a <STRONG>\</STRONG>. - A delay in milliseconds may appear anywhere in a string capability, - enclosed in $<..> brackets, as in <STRONG>el</STRONG>=\EK$<5>, and padding characters + A delay in milliseconds may appear anywhere in a string capability, + enclosed in $<..> brackets, as in <STRONG>el</STRONG>=\EK$<5>, and padding characters are supplied by <STRONG><A HREF="curs_terminfo.3x.html">tputs(3x)</A></STRONG> to provide this delay. - <STRONG>o</STRONG> The delay must be a number with at most one decimal place of + <STRONG>o</STRONG> The delay must be a number with at most one decimal place of precision; it may be followed by suffixes "*" or "/" or both. - <STRONG>o</STRONG> A "*" indicates that the padding required is proportional to the - number of lines affected by the operation, and the amount given is - the per-affected-unit padding required. (In the case of insert + <STRONG>o</STRONG> A "*" indicates that the padding required is proportional to the + number of lines affected by the operation, and the amount given is + the per-affected-unit padding required. (In the case of insert character, the factor is still the number of <EM>lines</EM> affected.) Normally, padding is advisory if the device has the <STRONG>xon</STRONG> capability; @@ -1102,37 +1091,37 @@ delay of the given number of milliseconds even on devices for which <STRONG>xon</STRONG> is present to indicate flow control. - Sometimes individual capabilities must be commented out. To do this, - put a period before the capability name. For example, see the second + Sometimes individual capabilities must be commented out. To do this, + put a period before the capability name. For example, see the second <STRONG>ind</STRONG> in the example above. </PRE><H3><a name="h3-Fetching-Compiled-Descriptions">Fetching Compiled Descriptions</a></H3><PRE> - Terminal descriptions in <EM>ncurses</EM> are stored in terminal databases. - These databases, which are found by their pathname, may be configured + Terminal descriptions in <EM>ncurses</EM> are stored in terminal databases. + These databases, which are found by their pathname, may be configured either as directory trees or hashed databases (see <STRONG><A HREF="term.5.html">term(5)</A></STRONG>), - The library uses a compiled-in list of pathnames, which can be + The library uses a compiled-in list of pathnames, which can be overridden by environment variables. Before starting to search, - <EM>ncurses</EM> checks the search list, eliminating duplicates and pathnames - where no terminal database is found. The <EM>ncurses</EM> library reads the + <EM>ncurses</EM> checks the search list, eliminating duplicates and pathnames + where no terminal database is found. The <EM>ncurses</EM> library reads the first description which passes its consistency checks. - <STRONG>o</STRONG> The environment variable <STRONG>TERMINFO</STRONG> is checked first, for a terminal + <STRONG>o</STRONG> The environment variable <STRONG>TERMINFO</STRONG> is checked first, for a terminal database containing the terminal description. <STRONG>o</STRONG> Next, <EM>ncurses</EM> looks in <EM>$HOME/.terminfo</EM> for a compiled description. - This is an optional feature which may be omitted entirely from the + This is an optional feature which may be omitted entirely from the library, or limited to prevent accidental use by privileged applications. - <STRONG>o</STRONG> Next, if the environment variable <EM>TERMINFO</EM><STRONG>_</STRONG><EM>DIRS</EM> is set, <EM>ncurses</EM> - interprets the contents of that variable as a list of colon- + <STRONG>o</STRONG> Next, if the environment variable <EM>TERMINFO</EM><STRONG>_</STRONG><EM>DIRS</EM> is set, <EM>ncurses</EM> + interprets the contents of that variable as a list of colon- separated pathnames of terminal databases to be searched. - An empty pathname (i.e., if the variable begins or ends with a - colon, or contains adjacent colons) is interpreted as the system + An empty pathname (i.e., if the variable begins or ends with a + colon, or contains adjacent colons) is interpreted as the system location <EM>/usr/share/terminfo</EM>. <STRONG>o</STRONG> Finally, <EM>ncurses</EM> searches these compiled-in locations: @@ -1161,8 +1150,8 @@ effective way to prepare a terminal description is by imitating the description of a similar terminal in <EM>terminfo</EM> and to build up a description gradually, using partial descriptions with <EM>vi</EM> or some other - screen-oriented program to check that they are correct. Be aware that - a very unusual terminal may expose deficiencies in the ability of the + screen-oriented program to check that they are correct. Be aware that + a very unusual terminal may expose deficiencies in the ability of the <EM>terminfo</EM> file to describe it or bugs in the screen-handling code of the test program. @@ -1182,13 +1171,13 @@ can clear its screen, leaving the cursor in the home position, then this is given by the <STRONG>clear</STRONG> string capability. If the terminal overstrikes (rather than clearing a position when a character is struck - over) then it should have the <STRONG>os</STRONG> capability. If the terminal is a + over) then it should have the <STRONG>os</STRONG> capability. If the terminal is a printing terminal, with no soft copy unit, give it both <STRONG>hc</STRONG> and <STRONG>os</STRONG>. (<STRONG>os</STRONG> applies to storage scope terminals, such as TEKTRONIX 4010 series, as well as hard copy and APL terminals.) If there is a code to move the - cursor to the left edge of the current row, give this as <STRONG>cr</STRONG>. (Normally - this will be carriage return, control/M.) If there is a code to - produce an audible signal (bell, beep, etc) give this as <STRONG>bel</STRONG>. + cursor to the left edge of the current line, give this as <STRONG>cr</STRONG>. + (Normally this will be carriage return, control/M.) If there is a code + to produce an audible signal (bell, beep, etc) give this as <STRONG>bel</STRONG>. If there is a code to move the cursor one position to the left (such as backspace) that capability should be given as <STRONG>cub1</STRONG>. Similarly, codes @@ -1198,7 +1187,7 @@ space would erase the character moved over. A very important point here is that the local cursor motions encoded in - <EM>terminfo</EM> are undefined at the left and top edges of a CRT terminal. + <EM>terminfo</EM> are undefined at the left and top edges of a CRT terminal. Programs should never attempt to backspace around the left edge, unless <STRONG>bw</STRONG> is given, and never attempt to go up locally off the top. In order to scroll text up, a program will go to the bottom left corner of the @@ -1208,17 +1197,17 @@ screen and sends the <STRONG>ri</STRONG> (reverse index) string. The strings <STRONG>ind</STRONG> and <STRONG>ri</STRONG> are undefined when not on their respective corners of the screen. - Parameterized versions of the scrolling sequences are <STRONG>indn</STRONG> and <STRONG>rin</STRONG> - which have the same semantics as <STRONG>ind</STRONG> and <STRONG>ri</STRONG> except that they take one - parameter, and scroll that many lines. They are also undefined except + Parameterized versions of the scrolling sequences are <STRONG>indn</STRONG> and <STRONG>rin</STRONG> + which have the same semantics as <STRONG>ind</STRONG> and <STRONG>ri</STRONG> except that they take one + parameter, and scroll that many lines. They are also undefined except at the appropriate edge of the screen. - The <STRONG>am</STRONG> capability tells whether the cursor sticks at the right edge of - the screen when text is output, but this does not necessarily apply to - a <STRONG>cuf1</STRONG> from the last column. The only local motion which is defined - from the left edge is if <STRONG>bw</STRONG> is given, then a <STRONG>cub1</STRONG> from the left edge - will move to the right edge of the previous row. If <STRONG>bw</STRONG> is not given, - the effect is undefined. This is useful for drawing a box around the + The <STRONG>am</STRONG> capability tells whether the cursor sticks at the right edge of + the screen when text is output, but this does not necessarily apply to + a <STRONG>cuf1</STRONG> from the last column. The only local motion which is defined + from the left edge is if <STRONG>bw</STRONG> is given, then a <STRONG>cub1</STRONG> from the left edge + will move to the right edge of the previous line. If <STRONG>bw</STRONG> is not given, + the effect is undefined. This is useful for drawing a box around the edge of the screen, for example. If the terminal has switch selectable automatic margins, the <EM>terminfo</EM> file usually assumes that this is on; i.e., <STRONG>am</STRONG>. If the terminal has a command which moves to the first @@ -1244,17 +1233,17 @@ Cursor addressing and other strings requiring parameters in the terminal are described by a parameterized string capability, with <EM>printf</EM>-like escapes such as <EM>%x</EM> in it. For 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 the physical screen visible to the user, not to any unseen - memory.) If the terminal has memory relative cursor addressing, that + cursor, the <STRONG>cup</STRONG> capability is given, using two parameters: the line and + column to address to. (Lines and columns are numbered from zero and + refer to the physical screen visible to the user, not to any unseen + memory.) If the terminal has memory relative cursor addressing, that can be indicated by <STRONG>mrcup</STRONG>. - The parameter mechanism uses a stack and special <STRONG>%</STRONG> codes to manipulate - it. Typically a sequence will push one of the parameters onto the - stack and then print it in some format. Print (e.g., "%d") is a - special case. Other operations, including "%t" pop their operand from - the stack. It is noted that more complex operations are often + The parameter mechanism uses a stack and special <STRONG>%</STRONG> codes to manipulate + it. Typically a sequence will push one of the parameters onto the + stack and then print it in some format. Print (e.g., "%d") is a + special case. Other operations, including "%t" pop their operand from + the stack. It is noted that more complex operations are often necessary, e.g., in the <STRONG>sgr</STRONG> string. The <STRONG>%</STRONG> encodings have the following meanings: @@ -1262,7 +1251,7 @@ <STRONG>%%</STRONG> outputs "%" <STRONG>%</STRONG><EM>[[</EM>:<EM>]flags][width[.precision]][</EM><STRONG>doxXs</STRONG><EM>]</EM> - as in <STRONG>printf(3)</STRONG>, flags are <EM>[-+#]</EM> and <EM>space</EM>. Use a ":" to allow + as in <STRONG>printf(3)</STRONG>, flags are <EM>[-+#]</EM> and <EM>space</EM>. Use a ":" to allow the next character to be a "-" flag, avoiding interpreting "%-" as an operator. @@ -1287,7 +1276,7 @@ The terms "static" and "dynamic" are misleading. Historically, these are simply two different sets of variables, whose values are - not reset between calls to <STRONG><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG>. However, that fact is not + not reset between calls to <STRONG><A HREF="curs_terminfo.3x.html">tparm(3x)</A></STRONG>. However, that fact is not documented in other implementations. Relying on it will adversely impact portability to other implementations: @@ -1332,13 +1321,14 @@ arithmetic (%m is <EM>mod</EM>): <EM>push(pop()</EM> <EM>op</EM> <EM>pop())</EM> <STRONG>%&</STRONG>, <STRONG>%|</STRONG>, <STRONG>%^</STRONG> - bit operations (AND, OR and exclusive-OR): <EM>push(pop()</EM> <EM>op</EM> <EM>pop())</EM> + bit operations ("and", "or" and exclusive "or"): <EM>push(pop()</EM> <EM>op</EM> + <EM>pop())</EM> <STRONG>%=</STRONG>, <STRONG>%></STRONG>, <STRONG>%<</STRONG> logical operations: <EM>push(pop()</EM> <EM>op</EM> <EM>pop())</EM> <STRONG>%A</STRONG>, <STRONG>%O</STRONG> - logical AND and OR operations (for conditionals) + logical "and" and "or" operations (for conditionals) <STRONG>%!</STRONG>, <STRONG>%~</STRONG> unary operations (logical and bit complement): <EM>push(op</EM> <EM>pop())</EM> @@ -1347,8 +1337,8 @@ <STRONG>%?</STRONG> <EM>expr</EM> <STRONG>%t</STRONG> <EM>thenpart</EM> <STRONG>%e</STRONG> <EM>elsepart</EM> <STRONG>%;</STRONG> This forms an if-then-else. The <STRONG>%e</STRONG> <EM>elsepart</EM> is optional. Usually - the <STRONG>%?</STRONG> <EM>expr</EM> part pushes a value onto the stack, and <STRONG>%t</STRONG> pops it - from the stack, testing if it is nonzero (true). If it is zero + the <STRONG>%?</STRONG> <EM>expr</EM> part pushes a value onto the stack, and <STRONG>%t</STRONG> pops it + from the stack, testing if it is nonzero (true). If it is zero (false), control passes to the <STRONG>%e</STRONG> (else) part. It is possible to form else-if's a la Algol 68: @@ -1356,7 +1346,7 @@ where ci are conditions, bi are bodies. - Use the <STRONG>-f</STRONG> option of <STRONG>tic</STRONG> or <STRONG>infocmp</STRONG> to see the structure of if- + Use the <STRONG>-f</STRONG> option of <STRONG>tic</STRONG> or <STRONG>infocmp</STRONG> to see the structure of if- then-else's. Some strings, e.g., <STRONG>sgr</STRONG> can be very complicated when written on one line. The <STRONG>-f</STRONG> option splits the string into lines with the parts indented. @@ -1365,25 +1355,25 @@ order. That is, to get x-5 one would use "%gx%{5}%-". <STRONG>%P</STRONG> and <STRONG>%g</STRONG> variables are persistent across escape-string evaluations. - Consider the HP2645, which, to get to row 3 and column 12, needs to be - sent \E&a12c03Y padded for 6 milliseconds. The order of the rows and - columns is inverted here, and the row and column are printed as two + Consider the HP2645, which, to get to line 3 and column 12, needs to be + sent \E&a12c03Y padded for 6 milliseconds. The order of the lines and + columns is inverted here, and the lines and column are printed as two digits. The corresponding terminal description is expressed thus: cup=\E&a%p2%dc%p1%dY$<6>, - The Microterm ACT-IV needs the current row and column sent preceded by - a <STRONG>^T</STRONG>, with the row and column simply encoded in binary, + The Microterm ACT-IV needs the current line and column sent preceded by + a <STRONG>^T</STRONG>, with the line and column simply encoded in binary, cup=^T%p1%c%p2%c Terminals which use "%c" need to be able to backspace the cursor (<STRONG>cub1</STRONG>), and to move the cursor up one line on the screen (<STRONG>cuu1</STRONG>). This is necessary because it is not always safe to transmit <STRONG>\n</STRONG> <STRONG>^D</STRONG> and <STRONG>\r</STRONG>, as - the system may change or discard them. (The library routines dealing - with terminfo set tty modes so that tabs are never expanded, so \t is + the system may change or discard them. (The library routines dealing + with terminfo set tty modes so that tabs are never expanded, so \t is safe to send. This turns out to be essential for the Ann Arbor 4080.) - A final example is the LSI ADM-3a, which uses row and column offset by - a blank character, thus + A final example is the LSI ADM-3A, which uses line and column offset by + a space, thus cup=\E=%p1%' '%+%c%p2%' '%+%c After sending "\E=", this pushes the first parameter, pushes the ASCII @@ -1404,8 +1394,8 @@ corner of the screen, not of memory. (Thus, the \EH sequence on HP terminals cannot be used for <STRONG>home</STRONG>.) - If the terminal has row or column absolute cursor addressing, these can - be given as single parameter capabilities <STRONG>hpa</STRONG> (horizontal position + If the terminal has line or column absolute cursor addressing, these + can be given as single parameter capabilities <STRONG>hpa</STRONG> (horizontal position absolute) and <STRONG>vpa</STRONG> (vertical position absolute). Sometimes these are shorter than the more general two parameter sequence (as with the hp2645) and can be used in preference to <STRONG>cup</STRONG>. If there are @@ -1416,10 +1406,10 @@ If the terminal needs to be in a special mode when running a program that uses these capabilities, the codes to enter and exit this mode can - be given as <STRONG>smcup</STRONG> and <STRONG>rmcup</STRONG>. This arises, for example, from terminals - like the Concept with more than one page of memory. If the terminal - has only memory relative cursor addressing and not screen relative - cursor addressing, a one screen-sized window must be fixed into the + be given as <STRONG>smcup</STRONG> and <STRONG>rmcup</STRONG>. This arises, for example, from terminals + like the Concept with more than one page of memory. If the terminal + has only memory relative cursor addressing and not screen relative + cursor addressing, a one screen-sized window must be fixed into the terminal for cursor addressing to work properly. This is also used for the TEKTRONIX 4025, where <STRONG>smcup</STRONG> sets the command character to be the one used by terminfo. If the <STRONG>smcup</STRONG> sequence will not restore the @@ -1433,7 +1423,7 @@ were intended for use with printers. <STRONG>o</STRONG> The two terminal capabilities assume that the terminal may have the - capability of setting the left and/or right margin at the current + capability of setting the left and/or right margin at the current cursor column position. <STRONG>o</STRONG> The printer capabilities assume that the printer may have two types @@ -1442,22 +1432,22 @@ <STRONG>o</STRONG> the ability to set a top and/or bottom margin using the current line position, and - <STRONG>o</STRONG> parameterized capabilities for setting the top, bottom, left, - right margins given the number of rows or columns. + <STRONG>o</STRONG> parameterized capabilities for setting the top, bottom, left, + right margins given the number of lines or columns. - In practice, the categorization into "terminal" and "printer" is not + In practice, the categorization into "terminal" and "printer" is not suitable: - <STRONG>o</STRONG> The AT&T SVr4 terminal database uses <STRONG>smgl</STRONG> four times, for AT&T + <STRONG>o</STRONG> The AT&T SVr4 terminal database uses <STRONG>smgl</STRONG> four times, for AT&T hardware. - Three of the four are printers. They lack the ability to set + Three of the four are printers. They lack the ability to set left/right margins by specifying the column. - <STRONG>o</STRONG> Other (non-AT&T) terminals may support margins but using different + <STRONG>o</STRONG> Other (non-AT&T) terminals may support margins but using different assumptions from AT&T. - For instance, the DEC VT420 supports left/right margins, but only + For instance, the DEC VT420 supports left/right margins, but only using a column parameter. As an added complication, the VT420 uses two settings to fully enable left/right margins (left/right margin mode, and origin mode). The former enables the margins, which @@ -1466,7 +1456,7 @@ <STRONG>o</STRONG> Both DEC VT420 left/right margins are set with a single control sequence. If either is omitted, the corresponding margin is set to - the left or right edge of the display (rather than leaving the + the left or right edge of the display (rather than leaving the margin unmodified). These are the margin-related capabilities: @@ -1484,15 +1474,15 @@ <STRONG>smglr</STRONG> Set both left and right margins to <EM>L</EM> and <EM>R</EM> <STRONG>smgtb</STRONG> Set both top and bottom margins to <EM>T</EM> and <EM>B</EM> - When writing an application that uses these string capabilities, the - pairs should be first checked to see if each capability in the pair is + When writing an application that uses these string capabilities, the + pairs should be first checked to see if each capability in the pair is set or only one is set: - <STRONG>o</STRONG> If both <STRONG>smglp</STRONG> and <STRONG>smgrp</STRONG> are set, each is used with a single - argument, <EM>N</EM>, that gives the column number of the left and right + <STRONG>o</STRONG> If both <STRONG>smglp</STRONG> and <STRONG>smgrp</STRONG> are set, each is used with a single + argument, <EM>N</EM>, that gives the column number of the left and right margin, respectively. - <STRONG>o</STRONG> If both <STRONG>smgtp</STRONG> and <STRONG>smgbp</STRONG> are set, each is used to set the top and + <STRONG>o</STRONG> If both <STRONG>smgtp</STRONG> and <STRONG>smgbp</STRONG> are set, each is used to set the top and bottom margin, respectively: <STRONG>o</STRONG> <STRONG>smgtp</STRONG> is used with a single argument, <EM>N</EM>, the line number of the @@ -1500,12 +1490,12 @@ <STRONG>o</STRONG> <STRONG>smgbp</STRONG> is used with two arguments, <EM>N</EM> and <EM>M</EM>, that give the line number of the bottom margin, the first counting from the top of - the page and the second counting from the bottom. This - accommodates the two styles of specifying the bottom margin in + the page and the second counting from the bottom. This + accommodates the two styles of specifying the bottom margin in different manufacturers' printers. - When designing a terminfo entry for a printer that has a settable - bottom margin, only the first or second argument should be used, + When designing a terminfo entry for a printer that has a settable + bottom margin, only the first or second argument should be used, depending on the printer. When developing an application that uses <STRONG>smgbp</STRONG> to set the bottom margin, both arguments must be given. @@ -1515,8 +1505,8 @@ arguments, the column number of the left and right margins, in that order. - <STRONG>o</STRONG> Likewise, if only one of <STRONG>smgtp</STRONG> and <STRONG>smgbp</STRONG> is set, then it is used - with two arguments that give the top and bottom margins, in that + <STRONG>o</STRONG> Likewise, if only one of <STRONG>smgtp</STRONG> and <STRONG>smgbp</STRONG> is set, then it is used + with two arguments that give the top and bottom margins, in that order, counting from the top of the page. When designing a terminfo entry for a printer that requires setting @@ -1527,22 +1517,22 @@ Except for very old terminal descriptions, e.g., those developed for SVr4, the scheme just described should be considered obsolete. An improved set of capabilities was added late in the SVr4 releases (<STRONG>smglr</STRONG> - and <STRONG>smgtb</STRONG>), which explicitly use two parameters for setting the + and <STRONG>smgtb</STRONG>), which explicitly use two parameters for setting the left/right or top/bottom margins. When setting margins, the line- and column-values are zero-based. - The <STRONG>mgc</STRONG> string capability should be defined. Applications such as + The <STRONG>mgc</STRONG> string capability should be defined. Applications such as <STRONG><A HREF="tabs.1.html">tabs(1)</A></STRONG> rely upon this to reset all margins. </PRE><H3><a name="h3-Area-Clears">Area Clears</a></H3><PRE> - If the terminal can clear from the current position to the end of the - line, leaving the cursor where it is, this should be given as <STRONG>el</STRONG>. If - the terminal can clear from the beginning of the line to the current - position inclusive, leaving the cursor where it is, this should be - given as <STRONG>el1</STRONG>. If the terminal can clear from the current position to - the end of the display, then this should be given as <STRONG>ed</STRONG>. <STRONG>Ed</STRONG> is only + If the terminal can clear from the current position to the end of the + line, leaving the cursor where it is, this should be given as <STRONG>el</STRONG>. If + the terminal can clear from the beginning of the line to the current + position inclusive, leaving the cursor where it is, this should be + given as <STRONG>el1</STRONG>. If the terminal can clear from the current position to + the end of the display, then this should be given as <STRONG>ed</STRONG>. <STRONG>Ed</STRONG> is only defined from the first column of a line. (Thus, it can be simulated by a request to delete a large number of lines, if a true <STRONG>ed</STRONG> is not available.) @@ -1563,8 +1553,8 @@ takes two parameters: the top and bottom lines of the scrolling region. The cursor position is, alas, undefined after using this command. - It is possible to get the effect of insert or delete line using <STRONG>csr</STRONG> on - a properly chosen region; the <STRONG>sc</STRONG> and <STRONG>rc</STRONG> (save and restore cursor) + It is possible to get the effect of insert or delete line using <STRONG>csr</STRONG> on + a properly chosen region; the <STRONG>sc</STRONG> and <STRONG>rc</STRONG> (save and restore cursor) commands may be useful for ensuring that your synthesized insert/delete string does not move the cursor. (Note that the <STRONG><A HREF="ncurses.3x.html">ncurses(3x)</A></STRONG> library does this synthesis automatically, so you need not compose @@ -1587,13 +1577,13 @@ off the bottom of the region by the <STRONG>ri</STRONG> re-appears, then scrolling is non-destructive. System V and X/Open Curses expect that <STRONG>ind</STRONG>, <STRONG>ri</STRONG>, <STRONG>indn</STRONG>, and <STRONG>rin</STRONG> will simulate destructive scrolling; their documentation - cautions you not to define <STRONG>csr</STRONG> unless this is true. This <STRONG>curses</STRONG> - implementation is more liberal and will do explicit erases after + cautions you not to define <STRONG>csr</STRONG> unless this is true. This <STRONG>curses</STRONG> + implementation is more liberal and will do explicit erases after scrolling if <STRONG>ndsrc</STRONG> is defined. - If the terminal has the ability to define a window as part of memory, - which all commands affect, it should be given as the parameterized - string <STRONG>wind</STRONG>. The four parameters are the starting and ending lines in + If the terminal has the ability to define a window as part of memory, + which all commands affect, it should be given as the parameterized + string <STRONG>wind</STRONG>. The four parameters are the starting and ending lines in memory and the starting and ending columns in memory, in that order. If the terminal can retain display memory above, then the <STRONG>da</STRONG> capability @@ -1634,49 +1624,49 @@ Terminfo can describe both terminals which have an insert mode, and terminals which send a simple sequence to open a blank position on the current line. Give as <STRONG>smir</STRONG> the sequence to get into insert mode. Give - as <STRONG>rmir</STRONG> the sequence to leave insert mode. Now give as <STRONG>ich1</STRONG> any - sequence needed to be sent just before sending the character to be - inserted. Most terminals with a true insert mode will not give <STRONG>ich1</STRONG>; - terminals which send a sequence to open a screen position should give + as <STRONG>rmir</STRONG> the sequence to leave insert mode. Now give as <STRONG>ich1</STRONG> any + sequence needed to be sent just before sending the character to be + inserted. Most terminals with a true insert mode will not give <STRONG>ich1</STRONG>; + terminals which send a sequence to open a screen position should give it here. - If your terminal has both, insert mode is usually preferable to <STRONG>ich1</STRONG>. - Technically, you should not give both unless the terminal actually - requires both to be used in combination. Accordingly, some non-curses - applications get confused if both are present; the symptom is doubled - characters in an update using insert. This requirement is now rare; - most <STRONG>ich</STRONG> sequences do not require previous smir, and most smir insert - modes do not require <STRONG>ich1</STRONG> before each character. Therefore, the new - <STRONG>curses</STRONG> actually assumes this is the case and uses either <STRONG>rmir</STRONG>/<STRONG>smir</STRONG> or - <STRONG>ich</STRONG>/<STRONG>ich1</STRONG> as appropriate (but not both). If you have to write an entry - to be used under new curses for a terminal old enough to need both, + If your terminal has both, insert mode is usually preferable to <STRONG>ich1</STRONG>. + Technically, you should not give both unless the terminal actually + requires both to be used in combination. Accordingly, some non-curses + applications get confused if both are present; the symptom is doubled + characters in an update using insert. This requirement is now rare; + most <STRONG>ich</STRONG> sequences do not require previous smir, and most smir insert + modes do not require <STRONG>ich1</STRONG> before each character. Therefore, the new + <STRONG>curses</STRONG> actually assumes this is the case and uses either <STRONG>rmir</STRONG>/<STRONG>smir</STRONG> or + <STRONG>ich</STRONG>/<STRONG>ich1</STRONG> as appropriate (but not both). If you have to write an entry + to be used under new curses for a terminal old enough to need both, include the <STRONG>rmir</STRONG>/<STRONG>smir</STRONG> sequences in <STRONG>ich1</STRONG>. If post insert padding is needed, give this as a number of milliseconds in <STRONG>ip</STRONG> (a string option). Any other sequence which may need to be sent after an insert of a single character may also be given in <STRONG>ip</STRONG>. If your - terminal needs both to be placed into an "insert mode" and a special - code to precede each inserted character, then both <STRONG>smir</STRONG>/<STRONG>rmir</STRONG> and <STRONG>ich1</STRONG> - can be given, and both will be used. The <STRONG>ich</STRONG> capability, with one + terminal needs both to be placed into an "insert mode" and a special + code to precede each inserted character, then both <STRONG>smir</STRONG>/<STRONG>rmir</STRONG> and <STRONG>ich1</STRONG> + can be given, and both will be used. The <STRONG>ich</STRONG> capability, with one parameter, <EM>n</EM>, will repeat the effects of <STRONG>ich1</STRONG> <EM>n</EM> times. - If padding is necessary between characters typed while not in insert + If padding is necessary between characters typed while not in insert mode, give this as a number of milliseconds padding in <STRONG>rmp</STRONG>. - It is occasionally necessary to move around while in insert mode to - delete characters on the same line (e.g., if there is a tab after the - insertion position). If your terminal allows motion while in insert - mode you can give the capability <STRONG>mir</STRONG> to speed up inserting in this - case. Omitting <STRONG>mir</STRONG> will affect only speed. Some terminals (notably - Datamedia's) must not have <STRONG>mir</STRONG> because of the way their insert mode + It is occasionally necessary to move around while in insert mode to + delete characters on the same line (e.g., if there is a tab after the + insertion position). If your terminal allows motion while in insert + mode you can give the capability <STRONG>mir</STRONG> to speed up inserting in this + case. Omitting <STRONG>mir</STRONG> will affect only speed. Some terminals (notably + Datamedia's) must not have <STRONG>mir</STRONG> because of the way their insert mode works. - Finally, you can specify <STRONG>dch1</STRONG> to delete a single character, <STRONG>dch</STRONG> with - one parameter, <EM>n</EM>, to delete <EM>n</EM>characters, and delete mode by giving <STRONG>smdc</STRONG> - and <STRONG>rmdc</STRONG> to enter and exit delete mode (any mode the terminal needs to - be placed in for <STRONG>dch1</STRONG> to work). + Finally, you can specify <STRONG>dch1</STRONG> to delete a single character, <STRONG>dch</STRONG> with + one parameter, <EM>n</EM>, to delete <EM>n</EM> characters, and delete mode by giving + <STRONG>smdc</STRONG> and <STRONG>rmdc</STRONG> to enter and exit delete mode (any mode the terminal + needs to be placed in for <STRONG>dch1</STRONG> to work). - A command to erase <EM>n</EM> characters (equivalent to outputting <EM>n</EM> blanks + A command to erase <EM>n</EM> characters (equivalent to outputting <EM>n</EM> blanks without moving the cursor) can be given as <STRONG>ech</STRONG> with one parameter. @@ -1704,8 +1694,8 @@ mode) and <STRONG>rmacs</STRONG> (exit alternate character set mode). Turning on any of these modes singly may or may not turn off other modes. - If there is a sequence to set arbitrary combinations of modes, this - should be given as <STRONG>sgr</STRONG> (set attributes), taking 9 parameters. Each + If there is a sequence to set arbitrary combinations of modes, this + should be given as <STRONG>sgr</STRONG> (set attributes), taking 9 parameters. Each parameter is either zero (0) or nonzero, as the corresponding attribute is on or off. The 9 parameters are, in order: standout, underline, reverse, blink, dim, bold, blank, protect, alternate character set. @@ -1765,30 +1755,30 @@ string. The only drawback to adding an sgr string is that termcap also assumes that sgr0 does not exit alternate character set mode. - Terminals with the "magic cookie" glitch (<STRONG>xmc</STRONG>) deposit special - "cookies" when they receive mode-setting sequences, which affect the - display algorithm rather than having extra bits for each character. - Some terminals, such as the HP 2621, automatically leave standout mode - when they move to a new line or the cursor is addressed. Programs - using standout mode should exit standout mode before moving the cursor - or sending a newline, unless the <STRONG>msgr</STRONG> capability, asserting that it is + Terminals with the "magic cookie" glitch (<STRONG>xmc</STRONG>) deposit special + "cookies" when they receive mode-setting sequences, which affect the + display algorithm rather than having extra bits for each character. + Some terminals, such as the HP 2621, automatically leave standout mode + when they move to a new line or the cursor is addressed. Programs + using standout mode should exit standout mode before moving the cursor + or sending a newline, unless the <STRONG>msgr</STRONG> capability, asserting that it is safe to move in standout mode, is present. - If the terminal has a way of flashing the screen to indicate an error - quietly (a bell replacement) then this can be given as <STRONG>flash</STRONG>; it must + If the terminal has a way of flashing the screen to indicate an error + quietly (a bell replacement) then this can be given as <STRONG>flash</STRONG>; it must not move the cursor. - If the cursor needs to be made more visible than normal when it is not + If the cursor needs to be made more visible than normal when it is not on the bottom line (to make, for example, a non-blinking underline into an easier to find block or blinking underline) give this sequence as <STRONG>cvvis</STRONG>. If there is a way to make the cursor completely invisible, give - that as <STRONG>civis</STRONG>. The capability <STRONG>cnorm</STRONG> should be given which undoes the + that as <STRONG>civis</STRONG>. The capability <STRONG>cnorm</STRONG> should be given which undoes the effects of both of these modes. - If your terminal correctly generates underlined characters (with no - special codes needed) even though it does not overstrike, then you - should give the capability <STRONG>ul</STRONG>. If a character overstriking another - leaves both characters on the screen, specify the capability <STRONG>os</STRONG>. If + If your terminal correctly generates underlined characters (with no + special codes needed) even though it does not overstrike, then you + should give the capability <STRONG>ul</STRONG>. If a character overstriking another + leaves both characters on the screen, specify the capability <STRONG>os</STRONG>. If overstrikes are erasable with a blank, then this should be indicated by giving <STRONG>eo</STRONG>. @@ -1797,12 +1787,12 @@ If the terminal has a keypad that transmits codes when the keys are pressed, this information can be given. Note that it is not possible to handle terminals where the keypad only works in local (this applies, - for example, to the unshifted HP 2621 keys). If the keypad can be set - to transmit or not transmit, give these codes as <STRONG>smkx</STRONG> and <STRONG>rmkx</STRONG>. + for example, to the unshifted HP 2621 keys). If the keypad can be set + to transmit or not transmit, give these codes as <STRONG>smkx</STRONG> and <STRONG>rmkx</STRONG>. Otherwise the keypad is assumed to always transmit. - The codes sent by the left arrow, right arrow, up arrow, down arrow, - and home keys can be given as <STRONG>kcub1,</STRONG> <STRONG>kcuf1,</STRONG> <STRONG>kcuu1,</STRONG> <STRONG>kcud1,</STRONG> and <STRONG>khome</STRONG> + The codes sent by the left arrow, right arrow, up arrow, down arrow, + and home keys can be given as <STRONG>kcub1,</STRONG> <STRONG>kcuf1,</STRONG> <STRONG>kcuu1,</STRONG> <STRONG>kcud1,</STRONG> and <STRONG>khome</STRONG> respectively. If there are function keys such as f0, f1, ..., f10, the codes they send can be given as <STRONG>kf0,</STRONG> <STRONG>kf1,</STRONG> <STRONG>...,</STRONG> <STRONG>kf10</STRONG>. If these keys have labels other than the default f0 through f10, the labels can be @@ -1850,8 +1840,8 @@ directional pad are needed. Strings to program function keys can be given as <STRONG>pfkey</STRONG>, <STRONG>pfloc</STRONG>, and <STRONG>pfx</STRONG>. - A string to program screen labels should be specified as <STRONG>pln</STRONG>. Each of - these strings takes two parameters: the function key number to program + A string to program screen labels should be specified as <STRONG>pln</STRONG>. Each of + these strings takes two parameters: the function key number to program (from 0 to 10) and the string to program it with. Function key numbers out of this range may program undefined keys in a terminal dependent manner. The difference between the capabilities is that <STRONG>pfkey</STRONG> causes @@ -1867,41 +1857,45 @@ </PRE><H3><a name="h3-Tabs-and-Initialization">Tabs and Initialization</a></H3><PRE> - A few capabilities are used only for tabs: + A few capabilities are used only to manage tab stops. - <STRONG>o</STRONG> If the terminal has hardware tabs, the command to advance to the - next tab stop can be given as <STRONG>ht</STRONG> (usually control/I). + <STRONG>o</STRONG> If the terminal has hardware tabs, specify the character sequence + that advances to the next tab stop as the value of the <STRONG>tab</STRONG> (<STRONG>ht</STRONG>) + string capability (usually Control+I). - <STRONG>o</STRONG> A "back-tab" command which moves leftward to the preceding tab stop - can be given as <STRONG>cbt</STRONG>. + <STRONG>o</STRONG> Specify a character sequence that retreats (moves leftward) to the + preceding tab stop as the value of the <STRONG>back_tab</STRONG> (<STRONG>cbt</STRONG>) string + capability. - By convention, if the teletype modes indicate that tabs are being - expanded by the computer rather than being sent to the terminal, - programs should not use <STRONG>ht</STRONG> or <STRONG>cbt</STRONG> even if they are present, since - the user may not have the tab stops properly set. + By convention, if the terminal modes are configured such that tabs + are expanded by the host rather than terminal, applications should + not employ the <STRONG>tab</STRONG> (<STRONG>ht</STRONG>) or <STRONG>back_tab</STRONG> (<STRONG>cbt</STRONG>) capabilities even if they + are present, since the user may not have the tab stops properly + set. - <STRONG>o</STRONG> If the terminal has hardware tabs which are initially set every <EM>n</EM> - spaces when the terminal is powered up, the numeric parameter <STRONG>it</STRONG> is - given, showing the number of spaces the tabs are set to. + <STRONG>o</STRONG> If the terminal has hardware tab stops that are set at every <EM>n</EM> + character cells when the terminal is powered up, specify <EM>n</EM> as the + value of the the numeric capability <STRONG>init_tabs</STRONG> (<STRONG>it</STRONG>). - The <STRONG>it</STRONG> capability is normally used by the <STRONG>tset</STRONG> command to determine - whether to set the mode for hardware tab expansion, and whether to - set the tab stops. If the terminal has tab stops that can be saved - in non-volatile memory, the terminfo description can assume that - they are properly set. + The <STRONG>tset</STRONG> and "<STRONG>tput</STRONG> <STRONG>init</STRONG>" commands interpret the presence of the + <STRONG>init_tabs</STRONG> (<STRONG>it</STRONG>) capability as implying that the terminal is + responsible for tab stop expansion as well as an instruction to set + the tab stops to its value. If the terminal has tab stops that can + be saved in non-volatile memory, its <EM>terminfo</EM> type description can + assume that they are properly set. Other capabilities include <STRONG>o</STRONG> <STRONG>is1</STRONG>, <STRONG>is2</STRONG>, and <STRONG>is3</STRONG>, initialization strings for the terminal, - <STRONG>o</STRONG> <STRONG>iprog</STRONG>, the path name of a program to be run to initialize the + <STRONG>o</STRONG> <STRONG>iprog</STRONG>, the path name of a program to be run to initialize the terminal, <STRONG>o</STRONG> and <STRONG>if</STRONG>, the name of a file containing long initialization strings. - These strings are expected to set the terminal into modes consistent - with the rest of the terminfo description. They are normally sent to - the terminal, by the <EM>init</EM> option of the <STRONG>tput</STRONG> program, each time the + These strings are expected to set the terminal into modes consistent + with the rest of the terminfo description. They are normally sent to + the terminal, by the <EM>init</EM> option of the <STRONG>tput</STRONG> program, each time the user logs in. They will be printed in the following order: run the program @@ -1925,30 +1919,30 @@ and finally output <STRONG>is3</STRONG>. - Most initialization is done with <STRONG>is2</STRONG>. Special terminal modes can be - set up without duplicating strings by putting the common sequences in + Most initialization is done with <STRONG>is2</STRONG>. Special terminal modes can be + set up without duplicating strings by putting the common sequences in <STRONG>is2</STRONG> and special cases in <STRONG>is1</STRONG> and <STRONG>is3</STRONG>. - A set of sequences that does a harder reset from a totally unknown + A set of sequences that does a harder reset from a totally unknown state can be given as <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG>, <STRONG>rf</STRONG> and <STRONG>rs3</STRONG>, analogous to <STRONG>is1</STRONG> <STRONG>,</STRONG> <STRONG>is2</STRONG> <STRONG>,</STRONG> <STRONG>if</STRONG> and <STRONG>is3</STRONG> respectively. These strings are output by <EM>reset</EM> option of <STRONG>tput</STRONG>, or by the <STRONG>reset</STRONG> program (an alias of <STRONG>tset</STRONG>), which is used when the terminal gets into a wedged state. Commands are normally placed in <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG> <STRONG>rs3</STRONG> and <STRONG>rf</STRONG> only if they produce annoying effects on the screen and are not necessary when logging in. For example, the command to set - the vt100 into 80-column mode would normally be part of <STRONG>is2</STRONG>, but it - causes an annoying glitch of the screen and is not normally needed + the vt100 into 80-column mode would normally be part of <STRONG>is2</STRONG>, but it + causes an annoying glitch of the screen and is not normally needed since the terminal is usually already in 80-column mode. - The <STRONG>reset</STRONG> program writes strings including <STRONG>iprog</STRONG>, etc., in the same - order as the <EM>init</EM> program, using <STRONG>rs1</STRONG>, etc., instead of <STRONG>is1</STRONG>, etc. If - any of <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG>, <STRONG>rs3</STRONG>, or <STRONG>rf</STRONG> reset capability strings are missing, the - <STRONG>reset</STRONG> program falls back upon the corresponding initialization + The <STRONG>reset</STRONG> program writes strings including <STRONG>iprog</STRONG>, etc., in the same + order as the <EM>init</EM> program, using <STRONG>rs1</STRONG>, etc., instead of <STRONG>is1</STRONG>, etc. If + any of <STRONG>rs1</STRONG>, <STRONG>rs2</STRONG>, <STRONG>rs3</STRONG>, or <STRONG>rf</STRONG> reset capability strings are missing, the + <STRONG>reset</STRONG> program falls back upon the corresponding initialization capability string. - If there are commands to set and clear tab stops, they can be given as + If there are commands to set and clear tab stops, they can be given as <STRONG>tbc</STRONG> (clear all tab stops) and <STRONG>hts</STRONG> (set a tab stop in the current column - of every row). If a more complex sequence is needed to set the tabs + of every line). If a more complex sequence is needed to set the tabs than can be described by this, the sequence can be placed in <STRONG>is2</STRONG> or <STRONG>if</STRONG>. The <STRONG>tput</STRONG> <STRONG>reset</STRONG> command uses the same capability strings as the <STRONG>reset</STRONG> @@ -1961,11 +1955,11 @@ <STRONG>o</STRONG> Almost all hardware terminals (at least those which supported tabs) initialized those to every <EM>eight</EM> columns: - The only exception was the AT&T 2300 series, which set tabs to + The only exception was the AT&T 2300 series, which set tabs to every <EM>five</EM> columns. - <STRONG>o</STRONG> In particular, developers of the hardware terminals which are - commonly used as models for modern terminal emulators provided + <STRONG>o</STRONG> In particular, developers of the hardware terminals which are + commonly used as models for modern terminal emulators provided documentation demonstrating that <EM>eight</EM> columns were the standard. <STRONG>o</STRONG> Because of this, the terminal initialization programs <STRONG>tput</STRONG> and <STRONG>tset</STRONG> @@ -1981,36 +1975,36 @@ characters after certain cursor motions and screen changes. If the terminal uses xon/xoff handshaking for flow control (that is, it - automatically emits ^S back to the host when its input buffers are - close to full), set <STRONG>xon</STRONG>. This capability suppresses the emission of - padding. You can also set it for memory-mapped console devices + automatically emits ^S back to the host when its input buffers are + close to full), set <STRONG>xon</STRONG>. This capability suppresses the emission of + padding. You can also set it for memory-mapped console devices effectively that do not have a speed limit. Padding information should still be included so that routines can make better decisions about relative costs, but actual pad characters will not be transmitted. If <STRONG>pb</STRONG> (padding baud rate) is given, padding is suppressed at baud rates - below the value of <STRONG>pb</STRONG>. If the entry has no padding baud rate, then + below the value of <STRONG>pb</STRONG>. If the entry has no padding baud rate, then whether padding is emitted or not is completely controlled by <STRONG>xon</STRONG>. - If the terminal requires other than a null (zero) character as a pad, - then this can be given as <STRONG>pad</STRONG>. Only the first character of the <STRONG>pad</STRONG> + If the terminal requires other than a null (zero) character as a pad, + then this can be given as <STRONG>pad</STRONG>. Only the first character of the <STRONG>pad</STRONG> string is used. </PRE><H3><a name="h3-Status-Lines">Status Lines</a></H3><PRE> - Some terminals have an extra "status line" which is not normally used + Some terminals have an extra "status line" which is not normally used by software (and thus not counted in the terminal's <STRONG>lines</STRONG> capability). - The simplest case is a status line which is cursor-addressable but not + The simplest case is a status line which is cursor-addressable but not part of the main scrolling region on the screen; the Heathkit H19 has a status line of this kind, as would a 24-line VT100 with a 23-line scrolling region set up on initialization. This situation is indicated by the <STRONG>hs</STRONG> capability. - Some terminals with status lines need special sequences to access the - status line. These may be expressed as a string with single parameter - <STRONG>tsl</STRONG> which takes the cursor to a given zero-origin column on the status - line. The capability <STRONG>fsl</STRONG> must return to the main-screen cursor + Some terminals with status lines need special sequences to access the + status line. These may be expressed as a string with single parameter + <STRONG>tsl</STRONG> which takes the cursor to a given zero-origin column on the status + line. The capability <STRONG>fsl</STRONG> must return to the main-screen cursor positions before the last <STRONG>tsl</STRONG>. You may need to embed the string values of <STRONG>sc</STRONG> (save cursor) and <STRONG>rc</STRONG> (restore cursor) in <STRONG>tsl</STRONG> and <STRONG>fsl</STRONG> to accomplish this. @@ -2050,7 +2044,6 @@ <STRONG>ACS_BOARD</STRONG> 0x68 h <STRONG>#</STRONG> board of squares <STRONG>ACS_LANTERN</STRONG> 0x69 i <STRONG>#</STRONG> lantern symbol <STRONG>ACS_LRCORNER</STRONG> 0x6a j <STRONG>+</STRONG> lower right corner - <STRONG>ACS_URCORNER</STRONG> 0x6b k <STRONG>+</STRONG> upper right corner <STRONG>ACS_ULCORNER</STRONG> 0x6c l <STRONG>+</STRONG> upper left corner <STRONG>ACS_LLCORNER</STRONG> 0x6d m <STRONG>+</STRONG> lower left corner @@ -2089,43 +2082,48 @@ presumably they were used in the AT&T terminal: <EM>board</EM> <EM>of</EM> <EM>squares</EM> replaces the VT100 <EM>newline</EM> symbol, while <EM>lantern</EM> <EM>symbol</EM> replaces the VT100 <EM>vertical</EM> <EM>tab</EM> symbol. The other VT100 symbols for control - characters (<EM>horizontal</EM> <EM>tab</EM>, <EM>carriage</EM> <EM>return</EM> and <EM>line-feed</EM>) are not + characters (<EM>horizontal</EM> <EM>tab</EM>, <EM>carriage</EM> <EM>return</EM> and <EM>line-feed</EM>) are not (re)used in curses. - The best way to define a new device's graphics set is to add a column - to a copy of this table for your terminal, giving the character which - (when emitted between <STRONG>smacs</STRONG>/<STRONG>rmacs</STRONG> switches) will be rendered as the + The best way to define a new device's graphics set is to add a column + to a copy of this table for your terminal, giving the character which + (when emitted between <STRONG>smacs</STRONG>/<STRONG>rmacs</STRONG> switches) will be rendered as the corresponding graphic. Then read off the VT100/your terminal character pairs right to left in sequence; these become the ACSC string. </PRE><H3><a name="h3-Color-Handling">Color Handling</a></H3><PRE> - The curses library functions <STRONG>init_pair</STRONG> and <STRONG>init_color</STRONG> manipulate the - <EM>color</EM> <EM>pairs</EM> and <EM>color</EM> <EM>values</EM> discussed in this section (see - <STRONG><A HREF="curs_color.3x.html">curs_color(3x)</A></STRONG> for details on these and related functions). - - Most color terminals are either "Tektronix-like" or "HP-like": - - <STRONG>o</STRONG> Tektronix-like terminals have a predefined set of <EM>N</EM> colors (where <EM>N</EM> - is usually 8), and can set character-cell foreground and background - characters independently, mixing them into <EM>N</EM> * <EM>N</EM> color pairs. - - <STRONG>o</STRONG> On HP-like terminals, the user must set each color pair up - separately (foreground and background are not independently - settable). Up to <EM>M</EM> color pairs may be set up from 2*<EM>M</EM> different - colors. ANSI-compatible terminals are Tektronix-like. - - Some basic color capabilities are independent of the color method. The - numeric capabilities <STRONG>colors</STRONG> and <STRONG>pairs</STRONG> specify the maximum numbers of - colors and color pairs that can be displayed simultaneously. The <STRONG>op</STRONG> - (original pair) string resets foreground and background colors to their - default values for the terminal. The <STRONG>oc</STRONG> string resets all colors or - color pairs to their default values for the terminal. Some terminals + The <EM>curses</EM> library functions <STRONG>init_pair</STRONG> and <STRONG>init_color</STRONG> manipulate the + <EM>color</EM> <EM>pairs</EM> and <EM>colors</EM> (color values or indices, such as "1=red") + discussed in this section (see <STRONG><A HREF="curs_color.3x.html">curs_color(3x)</A></STRONG> for details on these and + related functions). + + Most color terminals are either "Tektronix-like" or "HP-like" in their + approach to color management. + + <STRONG>o</STRONG> <EM>Tektronix-like</EM> terminals define a set of <EM>n</EM> colors (where <EM>n</EM> is + usually 8), and can alter character-cell foreground and background + colors independently, mixing them into <EM>n</EM>x<EM>n</EM> color pairs. ANSI- + standard terminals are Tektronix-like. + + <STRONG>o</STRONG> On <EM>HP-like</EM> terminals, the user must set up each color pair + separately; foreground and background are not independently + alterable. Up to <EM>m</EM> color pairs may be configured from 2x<EM>m</EM> + different colors. + + Some basic color management capabilities are independent of the color + encoding method. The numeric capabilities <STRONG>max_colors</STRONG> (<STRONG>colors</STRONG>) and + <STRONG>max_pairs</STRONG> (<STRONG>pairs</STRONG>) specify the maximum numbers of colors and color pairs + that the device can display simultaneously. The <STRONG>orig_pair</STRONG> (<STRONG>op</STRONG>) + ("original pair") string capability resets foreground and background + colors to their default values for the terminal. The <STRONG>orig_colors</STRONG> (<STRONG>oc</STRONG>) + ("original colors") string capability resets all colors or color pairs + to their default values for the terminal. Some terminal types (including many PC terminal emulators) erase screen areas with the current background color rather than the power-up default background; - these should have the Boolean capability <STRONG>bce</STRONG>. + these should declare the Boolean capability <STRONG>back_color_erase</STRONG> (<STRONG>bce</STRONG>). - While the curses library works with <EM>color</EM> <EM>pairs</EM> (reflecting the + While the <EM>curses</EM> library works with <EM>color</EM> <EM>pairs</EM> (reflecting the inability of some devices to set foreground and background colors independently), there are separate capabilities for setting these features: @@ -2134,17 +2132,17 @@ Tektronix-type terminal, use <STRONG>setaf</STRONG> (set ANSI foreground) and <STRONG>setab</STRONG> (set ANSI background) or <STRONG>setf</STRONG> (set foreground) and <STRONG>setb</STRONG> (set background). These take one parameter, the color number. The SVr4 - documentation describes only <STRONG>setaf</STRONG>/<STRONG>setab</STRONG>; the XPG4 draft says that - "If the terminal supports ANSI escape sequences to set background - and foreground, they should be coded as <STRONG>setaf</STRONG> and <STRONG>setab</STRONG>, + documentation describes only <STRONG>setaf</STRONG>/<STRONG>setab</STRONG>; the XPG4 draft says that + "If the terminal supports ANSI escape sequences to set background + and foreground, they should be coded as <STRONG>setaf</STRONG> and <STRONG>setab</STRONG>, respectively. - <STRONG>o</STRONG> If the terminal supports other escape sequences to set background - and foreground, they should be coded as <STRONG>setf</STRONG> and <STRONG>setb</STRONG>, - respectively. The <STRONG>vidputs</STRONG> and the <STRONG><A HREF="curs_refresh.3x.html">refresh(3x)</A></STRONG> functions use the + <STRONG>o</STRONG> If the terminal supports other escape sequences to set background + and foreground, they should be coded as <STRONG>setf</STRONG> and <STRONG>setb</STRONG>, + respectively. The <STRONG>vidputs</STRONG> and the <STRONG><A HREF="curs_refresh.3x.html">refresh(3x)</A></STRONG> functions use the <STRONG>setaf</STRONG> and <STRONG>setab</STRONG> capabilities if they are defined. - The <STRONG>setaf</STRONG>/<STRONG>setab</STRONG> and <STRONG>setf</STRONG>/<STRONG>setb</STRONG> capabilities take a single numeric + The <STRONG>setaf</STRONG>/<STRONG>setab</STRONG> and <STRONG>setf</STRONG>/<STRONG>setb</STRONG> capabilities take a single numeric argument each. Argument values 0-7 of <STRONG>setaf</STRONG>/<STRONG>setab</STRONG> are portably defined as follows (the middle column is the symbolic #define available in the header for the <STRONG>curses</STRONG> or <EM>ncurses</EM> libraries). The terminal hardware is @@ -2176,32 +2174,32 @@ yellow <STRONG>COLOR_YELLOW</STRONG> 6 max, max, 0 white <STRONG>COLOR_WHITE</STRONG> 7 max, max, max - It is important to not confuse the two sets of color capabilities; + It is important to not confuse the two sets of color capabilities; otherwise red/blue will be interchanged on the display. - On an HP-like terminal, use <STRONG>scp</STRONG> with a color pair number parameter to + On an HP-like terminal, use <STRONG>scp</STRONG> with a color pair number parameter to set which color pair is current. Some terminals allow the <EM>color</EM> <EM>values</EM> to be modified: - <STRONG>o</STRONG> On a Tektronix-like terminal, the capability <STRONG>ccc</STRONG> may be present to - indicate that colors can be modified. If so, the <STRONG>initc</STRONG> capability + <STRONG>o</STRONG> On a Tektronix-like terminal, the capability <STRONG>ccc</STRONG> may be present to + indicate that colors can be modified. If so, the <STRONG>initc</STRONG> capability will take a color number (0 to <STRONG>colors</STRONG> - 1)and three more parameters which describe the color. These three parameters default to being interpreted as RGB (Red, Green, Blue) values. If the Boolean capability <STRONG>hls</STRONG> is present, they are instead as HLS (Hue, Lightness, Saturation) indices. The ranges are terminal-dependent. - <STRONG>o</STRONG> On an HP-like terminal, <STRONG>initp</STRONG> may give a capability for changing a - color pair value. It will take seven parameters; a color pair - number (0 to <STRONG>max_pairs</STRONG> - 1), and two triples describing first - background and then foreground colors. These parameters must be - (Red, Green, Blue) or (Hue, Lightness, Saturation) depending on + <STRONG>o</STRONG> On an HP-like terminal, <STRONG>initp</STRONG> may give a capability for changing a + color pair value. It will take seven parameters; a color pair + number (0 to <STRONG>max_pairs</STRONG> - 1), and two triples describing first + background and then foreground colors. These parameters must be + (Red, Green, Blue) or (Hue, Lightness, Saturation) depending on <STRONG>hls</STRONG>. - On some color terminals, colors collide with highlights. You can - register these collisions with the <STRONG>ncv</STRONG> capability. This is a bit mask - of attributes not to be used when colors are enabled. The + On some color terminals, colors collide with highlights. You can + register these collisions with the <STRONG>ncv</STRONG> capability. This is a bit mask + of attributes not to be used when colors are enabled. The correspondence with the attributes understood by <STRONG>curses</STRONG> is as follows: <STRONG>Attribute</STRONG> <STRONG>Bit</STRONG> <STRONG>Decimal</STRONG> <STRONG>Set</STRONG> <STRONG>by</STRONG> @@ -2223,17 +2221,17 @@ <STRONG>A_VERTICAL</STRONG> 14 16384 <STRONG>sgr1</STRONG> <STRONG>A_ITALIC</STRONG> 15 32768 <STRONG>sitm</STRONG> - For example, on many IBM PC consoles, the underline attribute collides - with the foreground color blue and is not available in color mode. + For example, on many IBM PC consoles, the underline attribute collides + with the foreground color blue and is not available in color mode. These should have an <STRONG>ncv</STRONG> capability of 2. - SVr4 curses does nothing with <STRONG>ncv</STRONG>, <EM>ncurses</EM> recognizes it and optimizes + SVr4 curses does nothing with <STRONG>ncv</STRONG>, <EM>ncurses</EM> recognizes it and optimizes the output in favor of colors. </PRE><H3><a name="h3-Miscellaneous">Miscellaneous</a></H3><PRE> - If the terminal requires other than a null (zero) character as a pad, - then this can be given as pad. Only the first character of the pad + If the terminal requires other than a null (zero) character as a pad, + then this can be given as pad. Only the first character of the pad string is used. If the terminal does not have a pad character, specify npc. Note that <EM>ncurses</EM> implements the termcap-compatible <STRONG>PC</STRONG> variable; though the application may set this value to something other than a @@ -2246,17 +2244,17 @@ hard-copy terminal can eject to the next page (form feed), give this as <STRONG>ff</STRONG> (usually control/L). - If there is a command to repeat a given character a given number of - times (to save time transmitting a large number of identical - characters) this can be indicated with the parameterized string <STRONG>rep</STRONG>. - The first parameter is the character to be repeated and the second is + If there is a command to repeat a given character a given number of + times (to save time transmitting a large number of identical + characters) this can be indicated with the parameterized string <STRONG>rep</STRONG>. + The first parameter is the character to be repeated and the second is the number of times to repeat it. Thus, tparm(repeat_char, 'x', 10) is the same as "xxxxxxxxxx". If the terminal has a settable command character, such as the TEKTRONIX - 4025, this can be indicated with <STRONG>cmdch</STRONG>. A prototype command character - is chosen which is used in all capabilities. This character is given - in the <STRONG>cmdch</STRONG> capability to identify it. The following convention is + 4025, this can be indicated with <STRONG>cmdch</STRONG>. A prototype command character + is chosen which is used in all capabilities. This character is given + in the <STRONG>cmdch</STRONG> capability to identify it. The following convention is supported on some Unix systems: The environment is to be searched for a <STRONG>CC</STRONG> variable, and if found, all occurrences of the prototype character are replaced with the character in the environment variable. @@ -2269,9 +2267,9 @@ known.) If the terminal has a "meta key" which acts as a shift key, setting the - 8th bit of any character transmitted, this fact can be indicated with - <STRONG>km</STRONG>. Otherwise, software will assume that the 8th bit is parity and it - will usually be cleared. If strings exist to turn this "meta mode" on + 8th bit of any character transmitted, this fact can be indicated with + <STRONG>km</STRONG>. Otherwise, software will assume that the 8th bit is parity and it + will usually be cleared. If strings exist to turn this "meta mode" on and off, they can be given as <STRONG>smm</STRONG> and <STRONG>rmm</STRONG>. If the terminal has more lines of memory than will fit on the screen at @@ -2279,16 +2277,16 @@ of <STRONG>lm</STRONG>#0 indicates that the number of lines is not fixed, but that there is still more memory than fits on the screen. - If the terminal is one of those supported by the Unix virtual terminal + If the terminal is one of those supported by the Unix virtual terminal protocol, the terminal number can be given as <STRONG>vt</STRONG>. - Media copy strings which control an auxiliary printer connected to the - terminal can be given as <STRONG>mc0</STRONG>: print the contents of the screen, <STRONG>mc4</STRONG>: - turn off the printer, and <STRONG>mc5</STRONG>: turn on the printer. When the printer - is on, all text sent to the terminal will be sent to the printer. It - is undefined whether the text is also displayed on the terminal screen - when the printer is on. A variation <STRONG>mc5p</STRONG> takes one parameter, and - leaves the printer on for as many characters as the value of the + Media copy strings which control an auxiliary printer connected to the + terminal can be given as <STRONG>mc0</STRONG>: print the contents of the screen, <STRONG>mc4</STRONG>: + turn off the printer, and <STRONG>mc5</STRONG>: turn on the printer. When the printer + is on, all text sent to the terminal will be sent to the printer. It + is undefined whether the text is also displayed on the terminal screen + when the printer is on. A variation <STRONG>mc5p</STRONG> takes one parameter, and + leaves the printer on for as many characters as the value of the parameter, then turns the printer off. The parameter should not exceed 255. All text, including <STRONG>mc4</STRONG>, is transparently passed to the printer while an <STRONG>mc5p</STRONG> is in effect. @@ -2305,27 +2303,27 @@ normal text on top of it), <STRONG>xhp</STRONG> should be given. Teleray terminals, where tabs turn all characters moved over to blanks, - should indicate <STRONG>xt</STRONG> (destructive tabs). Note: the variable indicating - this is now "dest_tabs_magic_smso"; in older versions, it was - teleray_glitch. This glitch is also taken to mean that it is not - possible to position the cursor on top of a "magic cookie", that to - erase standout mode it is instead necessary to use delete and insert + should indicate <STRONG>xt</STRONG> (destructive tabs). Note: the variable indicating + this is now "dest_tabs_magic_smso"; in older versions, it was + teleray_glitch. This glitch is also taken to mean that it is not + possible to position the cursor on top of a "magic cookie", that to + erase standout mode it is instead necessary to use delete and insert line. The <EM>ncurses</EM> implementation ignores this glitch. - The Beehive Superbee, which is unable to correctly transmit the escape - or control/C characters, has <STRONG>xsb</STRONG>, indicating that the f1 key is used - for escape and f2 for control/C. (Only certain Superbees have this - problem, depending on the ROM.) Note that in older terminfo versions, + The Beehive Superbee, which is unable to correctly transmit the escape + or control/C characters, has <STRONG>xsb</STRONG>, indicating that the f1 key is used + for escape and f2 for control/C. (Only certain Superbees have this + problem, depending on the ROM.) Note that in older terminfo versions, this capability was called "beehive_glitch"; it is now "no_esc_ctl_c". - Other specific terminal problems may be corrected by adding more + Other specific terminal problems may be corrected by adding more capabilities of the form <STRONG>x</STRONG><EM>x</EM>. </PRE><H3><a name="h3-Pitfalls-of-Long-Entries">Pitfalls of Long Entries</a></H3><PRE> - Long terminfo entries are unlikely to be a problem; to date, no entry - has even approached terminfo's 4096-byte string-table maximum. - Unfortunately, the termcap translations are much more strictly limited + Long terminfo entries are unlikely to be a problem; to date, no entry + has even approached terminfo's 4096-byte string-table maximum. + Unfortunately, the termcap translations are much more strictly limited (to 1023 bytes), thus termcap translations of long terminfo entries can cause problems. @@ -2348,15 +2346,15 @@ Some application programs allocate more than the recommended 1K for the termcap entry; others do not. - Each termcap entry has two important sizes associated with it: before - "tc" expansion, and after "tc" expansion. "tc" is the capability that + Each termcap entry has two important sizes associated with it: before + "tc" expansion, and after "tc" expansion. "tc" is the capability that tacks on another termcap entry to the end of the current one, to add on its capabilities. If a termcap entry does not use the "tc" capability, then of course the two lengths are the same. - The "before tc expansion" length is the most important one, because it - affects more than just users of that particular terminal. This is the - length of the entry as it exists in /etc/termcap, minus the backslash- + The "before tc expansion" length is the most important one, because it + affects more than just users of that particular terminal. This is the + length of the entry as it exists in /etc/termcap, minus the backslash- newline pairs, which <STRONG>tgetent</STRONG> strips out while reading it. Some termcap libraries strip off the final newline, too (GNU termcap does not). Now suppose: @@ -2365,25 +2363,25 @@ <STRONG>o</STRONG> and the application has only allocated a 1k buffer, - <STRONG>o</STRONG> and the termcap library (like the one in BSD/OS 1.1 and GNU) reads - the whole entry into the buffer, no matter what its length, to see + <STRONG>o</STRONG> and the termcap library (like the one in BSD/OS 1.1 and GNU) reads + the whole entry into the buffer, no matter what its length, to see if it is the entry it wants, - <STRONG>o</STRONG> and <STRONG>tgetent</STRONG> is searching for a terminal type that either is the - long entry, appears in the termcap file after the long entry, or - does not appear in the file at all (so that <STRONG>tgetent</STRONG> has to search + <STRONG>o</STRONG> and <STRONG>tgetent</STRONG> is searching for a terminal type that either is the + long entry, appears in the termcap file after the long entry, or + does not appear in the file at all (so that <STRONG>tgetent</STRONG> has to search the whole termcap file). - Then <STRONG>tgetent</STRONG> will overwrite memory, perhaps its stack, and probably - core dump the program. Programs like telnet are particularly - vulnerable; modern telnets pass along values like the terminal type - automatically. The results are almost as undesirable with a termcap - library, like SunOS 4.1.3 and Ultrix 4.4, that prints warning messages - when it reads an overly long termcap entry. If a termcap library - truncates long entries, like OSF/1 3.0, it is immune to dying here but + Then <STRONG>tgetent</STRONG> will overwrite memory, perhaps its stack, and probably + core dump the program. Programs like telnet are particularly + vulnerable; modern telnets pass along values like the terminal type + automatically. The results are almost as undesirable with a termcap + library, like SunOS 4.1.3 and Ultrix 4.4, that prints warning messages + when it reads an overly long termcap entry. If a termcap library + truncates long entries, like OSF/1 3.0, it is immune to dying here but will return incorrect data for the terminal. - The "after tc expansion" length will have a similar effect to the + The "after tc expansion" length will have a similar effect to the above, but only for people who actually set <EM>TERM</EM> to that terminal type, since <STRONG>tgetent</STRONG> only does "tc" expansion once it is found the terminal type it was looking for, not while searching. @@ -2422,53 +2420,53 @@ turned off. The <EM>ncurses</EM> library handles insert-character and insert-character modes - in a slightly non-standard way to get better update efficiency. See + in a slightly non-standard way to get better update efficiency. See the <STRONG>Insert/Delete</STRONG> <STRONG>Character</STRONG> subsection above. - The parameter substitutions for <STRONG>set_clock</STRONG> and <STRONG>display_clock</STRONG> are not - documented in SVr4 or X/Open Curses. They are deduced from the + The parameter substitutions for <STRONG>set_clock</STRONG> and <STRONG>display_clock</STRONG> are not + documented in SVr4 or X/Open Curses. They are deduced from the documentation for the AT&T 505 terminal. - Be careful assigning the <STRONG>kmous</STRONG> capability. The <EM>ncurses</EM> library wants - to interpret it as <STRONG>KEY_MOUSE</STRONG>, for use by terminals and emulators like - xterm that can return mouse-tracking information in the keyboard-input + Be careful assigning the <STRONG>kmous</STRONG> capability. The <EM>ncurses</EM> library wants + to interpret it as <STRONG>KEY_MOUSE</STRONG>, for use by terminals and emulators like + xterm that can return mouse-tracking information in the keyboard-input stream. - X/Open Curses does not mention italics. Portable applications must - assume that numeric capabilities are signed 16-bit values. This - includes the <EM>no</EM><STRONG>_</STRONG><EM>color</EM><STRONG>_</STRONG><EM>video</EM> (<STRONG>ncv</STRONG>) capability. The 32768 mask value - used for italics with <STRONG>ncv</STRONG> can be confused with an absent or cancelled - <STRONG>ncv</STRONG>. If italics should work with colors, then the <STRONG>ncv</STRONG> value must be + X/Open Curses does not mention italics. Portable applications must + assume that numeric capabilities are signed 16-bit values. This + includes the <EM>no</EM><STRONG>_</STRONG><EM>color</EM><STRONG>_</STRONG><EM>video</EM> (<STRONG>ncv</STRONG>) capability. The 32768 mask value + used for italics with <STRONG>ncv</STRONG> can be confused with an absent or canceled + <STRONG>ncv</STRONG>. If italics should work with colors, then the <STRONG>ncv</STRONG> value must be specified, even if it is zero. - Different commercial ports of <EM>terminfo</EM> and <EM>curses</EM> support different - subsets of X/Open Curses and (in some cases) different extensions. - Here is a summary, accurate as of October 1995, after which the + Different commercial ports of <EM>terminfo</EM> and <EM>curses</EM> support different + subsets of X/Open Curses and (in some cases) different extensions. + Here is a summary, accurate as of October 1995, after which the commercial Unix market contracted and lost diversity. <STRONG>o</STRONG> SVr4, Solaris, and <EM>ncurses</EM> support all SVr4 capabilities. - <STRONG>o</STRONG> IRIX supports the SVr4 set and adds one undocumented extended + <STRONG>o</STRONG> IRIX supports the SVr4 set and adds one undocumented extended string capability (<STRONG>set_pglen</STRONG>). - <STRONG>o</STRONG> SVr1 and Ultrix support a restricted subset of <EM>terminfo</EM> - capabilities. The Booleans end with <STRONG>xon_xoff</STRONG>; the numerics with + <STRONG>o</STRONG> SVr1 and Ultrix support a restricted subset of <EM>terminfo</EM> + capabilities. The Booleans end with <STRONG>xon_xoff</STRONG>; the numerics with <STRONG>width_status_line</STRONG>; and the strings with <STRONG>prtr_non</STRONG>. - <STRONG>o</STRONG> HP/UX supports the SVr1 subset, plus the SVr[234] numerics - <STRONG>num_labels</STRONG>, <STRONG>label_height</STRONG>, <STRONG>label_width</STRONG>, plus function keys 11 - through 63, plus <STRONG>plab_norm</STRONG>, <STRONG>label_on</STRONG>, and <STRONG>label_off</STRONG>, plus a number + <STRONG>o</STRONG> HP/UX supports the SVr1 subset, plus the SVr[234] numerics + <STRONG>num_labels</STRONG>, <STRONG>label_height</STRONG>, <STRONG>label_width</STRONG>, plus function keys 11 + through 63, plus <STRONG>plab_norm</STRONG>, <STRONG>label_on</STRONG>, and <STRONG>label_off</STRONG>, plus a number of incompatible string table extensions. - <STRONG>o</STRONG> AIX supports the SVr1 subset, plus function keys 11 through 63, + <STRONG>o</STRONG> AIX supports the SVr1 subset, plus function keys 11 through 63, plus a number of incompatible string table extensions. <STRONG>o</STRONG> OSF/1 supports both the SVr4 set and the AIX extensions. </PRE><H2><a name="h2-PORTABILITY">PORTABILITY</a></H2><PRE> - Do not count on compiled (binary) <EM>terminfo</EM> entries being portable - between commercial Unix systems. At least two implementations of + Do not count on compiled (binary) <EM>terminfo</EM> entries being portable + between commercial Unix systems. At least two implementations of <EM>terminfo</EM> (those of HP-UX and AIX) diverged from those of other System V Unices after SVr1, adding extension capabilities to the string table that (in the binary format) collide with subsequent System V and X/Open @@ -2485,9 +2483,7 @@ <STRONG><A HREF="curs_terminfo.3x.html">curs_terminfo(3x)</A></STRONG>, <STRONG><A HREF="curs_variables.3x.html">curs_variables(3x)</A></STRONG>, <STRONG>printf(3)</STRONG>, <STRONG><A HREF="term_variables.3x.html">term_variables(3x)</A></STRONG>, <STRONG><A HREF="term.5.html">term(5)</A></STRONG>, <STRONG><A HREF="user_caps.5.html">user_caps(5)</A></STRONG> - - -ncurses 6.5 2024-04-20 <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> +ncurses 6.6 2025-08-16 <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> </PRE> <div class="nav"> <ul> @@ -2498,7 +2494,7 @@ ncurses 6.5 2024-04-20 <STRONG><A HR <li><a href="#h3-terminfo-Entry-Syntax">terminfo Entry Syntax</a></li> <li><a href="#h3-terminfo-Capabilities-Syntax">terminfo Capabilities Syntax</a></li> <li><a href="#h3-Similar-Terminals">Similar Terminals</a></li> -<li><a href="#h3-Predefined-Capabilities">Predefined Capabilities</a></li> +<li><a href="#h3-Standard-Capabilities">Standard Capabilities</a></li> <li><a href="#h3-User-Defined-Capabilities">User-Defined Capabilities</a></li> <li><a href="#h3-A-Sample-Entry">A Sample Entry</a></li> <li><a href="#h3-Types-of-Capabilities">Types of Capabilities</a></li> |