X-Git-Url: https://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fterm_variables.3x.html;h=a61911be72ba23b8fe8b71c7f3d3b6499de45b1b;hb=a816c8dae437106bbf1661304240ff568ae3efef;hp=647a0142037e765aba1ae0845ef40d8f3570c634;hpb=c6cfd97b8beaf0f6deafbf8aac7281cf6aa7f012;p=ncurses.git diff --git a/doc/html/man/term_variables.3x.html b/doc/html/man/term_variables.3x.html index 647a0142..a61911be 100644 --- a/doc/html/man/term_variables.3x.html +++ b/doc/html/man/term_variables.3x.html @@ -1,6 +1,7 @@ -
- +-term_variables(3x) term_variables(3x) +term_variables(3x) term_variables(3x) --
- SP, acs_map, boolcodes, boolfnames, boolnames, cur_term, - numcodes, numfnames, numnames, strcodes, strfnames, - strnames, ttytype - curses terminfo global variables +
+ SP, acs_map, boolcodes, boolfnames, boolnames, cur_term, numcodes, + numfnames, numnames, strcodes, strfnames, strnames, ttytype - curses + terminfo global variables --
+
#include <curses.h> #include <term.h> chtype acs_map[]; - NCURSES_CONST char * const * boolcodes; - NCURSES_CONST char * const * boolfnames; - NCURSES_CONST char * const * boolnames; + + SCREEN * SP; + TERMINAL * cur_term; - NCURSES_CONST char * const * numcodes; - NCURSES_CONST char * const * numfnames; - NCURSES_CONST char * const * numnames; - NCURSES_CONST char * const * strcodes; - NCURSES_CONST char * const * strfnames; - NCURSES_CONST char * const * strnames; + char ttytype[]; + NCURSES_CONST char * const boolcodes[]; + NCURSES_CONST char * const boolfnames[]; + NCURSES_CONST char * const boolnames[]; --
- This page summarizes variables provided by the curses li- - brary's low-level terminfo interface. A more complete de- - scription is given in the curs_terminfo(3x) manual page. + NCURSES_CONST char * const numcodes[]; + NCURSES_CONST char * const numfnames[]; + NCURSES_CONST char * const numnames[]; - Depending on the configuration, these may be actual vari- - ables, or macros (see curs_threads(3x)) which provide - read-only access to curses's state. In either case, ap- - plications should treat them as read-only to avoid confus- - ing the library. + NCURSES_CONST char * const strcodes[]; + NCURSES_CONST char * const strfnames[]; + NCURSES_CONST char * const strnames[]; --
- After initializing the curses or terminfo interfaces, the - acs_map array holds information used to translate cells - with the A_ALTCHARSET video attribute into line-drawing - characters. +
+ This page summarizes variables provided by the curses library's low- + level terminfo interface. A more complete description is given in the + curs_terminfo(3x) manual page. - The encoding of the information in this array has changed - periodically. Application developers need only know that - it is used for the "ACS_" constants in <curses.h>. + Depending on the configuration, these may be actual variables, or + macros (see curs_threads(3x)) which provide read-only access to curs- + es's state. In either case, applications should treat them as read-on- + ly to avoid confusing the library. - The comparable data for the wide-character library is a - private variable. +
+ After initializing the curses or terminfo interfaces, the acs_map array + holds information used to translate cells with the A_ALTCHARSET video + attribute into line-drawing characters. --
- After initializing the curses or terminfo interfaces, the - cur_term contains data describing the current terminal. - This variable is also set as a side-effect of curs_initscr(3x) - and curs_initscr(3x). + The encoding of the information in this array has changed periodically. + Application developers need only know that it is used for the "ACS_" + constants in <curses.h>. - It is possible to save a value of cur_term for subsequent - use as a parameter to set_term, for switching between - screens. Alternatively, one can save the return value - from newterm or setupterm to reuse in set_term. + The comparable data for the wide-character library is a private vari- + able. --
- The tic(1m) and infocmp(1m) programs use lookup tables for - the long and short names of terminfo capabilities, as well - as the corresponding names for termcap capabilities. - These are available to other applications, though the - hash-tables are not available. +
+ After initializing the curses or terminfo interfaces, the cur_term con- + tains data describing the current terminal. This variable is also set + as a side-effect of set_term(3x) and delscreen(3x). - The long terminfo capability names use a "l" (ell) in - their names: boolfnames numfnames strfnames + It is possible to save a value of cur_term for subsequent use as a pa- + rameter to set_term, for switching between screens. Alternatively, one + can save the return value from newterm or setupterm(3x) to reuse in + set_term. - These are the short names for terminfo capabilities: bool- - names, numnames, and strnames. - These are the corresponding names used for termcap de- - scriptions: boolcodes, numcodes, and strcodes. +
+ The tic(1) and infocmp(1) programs use lookup tables for the long and + short names of terminfo capabilities, as well as the corresponding + names for termcap capabilities. These are available to other applica- + tions, although the hash-tables used by the terminfo and termcap func- + tions are not available. + The long terminfo capability names use a "l" (ell) in their names: + boolfnames, numfnames, and strfnames. --
- On initialization of the curses or terminfo interfaces, - setupterm copies the terminal name to the array ttytype. + These are the short names for terminfo capabilities: boolnames, num- + names, and strnames. + These are the corresponding names used for termcap descriptions: bool- + codes, numcodes, and strcodes. --
- The low-level terminfo interface is initialized using - curs_terminfo(3x). The upper-level curses interface uses the - low-level terminfo interface, internally. +
+ A terminal description begins with one or more terminal names separated + by "|" (vertical bars). On initialization of the curses or terminfo + interfaces, setupterm(3x) copies the terminal names to the array tty- + type. --
- X/Open Curses does not describe any of these except for - cur_term. (The inclusion of cur_term appears to be an - oversight, since other comparable low-level information is - omitted by X/Open). - Other implementations may have comparable variables. Some - implementations provide the variables in their libraries, - but omit them from the header files. +
+ In addition to the variables, <term.h> also defines a symbol for each + terminfo capability long name. These are in terms of the symbol CUR, + which is defined + #define CUR ((TERMTYPE *)(cur_term))-> --
- curses(3x), curs_terminfo(3x), curs_threads(3x), - terminfo(5). + These symbols provide a faster method of accessing terminfo capabili- + ties than using tigetstr(3x), etc. + + The actual definition of CUR depends upon the implementation, but each + terminfo library provides these long names defined to point into the + current terminal description loaded into memory. + + +
+ The low-level terminfo interface is initialized using setupterm(3x). + The upper-level curses interface uses the low-level terminfo interface, + internally. + + +
+ X/Open Curses does not describe any of these except for cur_term. (The + inclusion of cur_term appears to be an oversight, since other compara- + ble low-level information is omitted by X/Open). + Other implementations may have comparable variables. Some implementa- + tions provide the variables in their libraries, but omit them from the + header files. + All implementations which provide terminfo interfaces add definitions + as described in the Terminfo Names section. Most, but not all, base + the definition upon the cur_term variable. - term_variables(3x) + +
+ curses(3x), curs_terminfo(3x), curs_threads(3x), terminfo(5). + + + + term_variables(3x)