1term_variables(3X) term_variables(3X)
2
3
4
6 SP, acs_map, boolcodes, boolfnames, boolnames, cur_term, numcodes,
7 numfnames, numnames, strcodes, strfnames, strnames, ttytype - curses
8 terminfo global variables
9
11 #include <curses.h>
12 #include <term.h>
13
14 chtype acs_map[];
15 NCURSES_CONST char * const * boolcodes;
16 NCURSES_CONST char * const * boolfnames;
17 NCURSES_CONST char * const * boolnames;
18 TERMINAL * cur_term;
19 NCURSES_CONST char * const * numcodes;
20 NCURSES_CONST char * const * numfnames;
21 NCURSES_CONST char * const * numnames;
22 NCURSES_CONST char * const * strcodes;
23 NCURSES_CONST char * const * strfnames;
24 NCURSES_CONST char * const * strnames;
25 char ttytype[];
26
28 This page summarizes variables provided by the curses library's low-
29 level terminfo interface. A more complete description is given in the
30 curs_terminfo(3X) manual page.
31
32 Depending on the configuration, these may be actual variables, or
33 macros (see curs_threads(3X)) which provide read-only access to curs‐
34 es's state. In either case, applications should treat them as read-on‐
35 ly to avoid confusing the library.
36
37 Alternate Character Set Mapping
38 After initializing the curses or terminfo interfaces, the acs_map array
39 holds information used to translate cells with the A_ALTCHARSET video
40 attribute into line-drawing characters.
41
42 The encoding of the information in this array has changed periodically.
43 Application developers need only know that it is used for the "ACS_"
44 constants in <curses.h>.
45
46 The comparable data for the wide-character library is a private vari‐
47 able.
48
49 Current Terminal Data
50 After initializing the curses or terminfo interfaces, the cur_term con‐
51 tains data describing the current terminal. This variable is also set
52 as a side-effect of set_term(3X) and delscreen(3X).
53
54 It is possible to save a value of cur_term for subsequent use as a pa‐
55 rameter to set_term, for switching between screens. Alternatively, one
56 can save the return value from newterm or setupterm to reuse in
57 set_term.
58
59 Terminfo Names
60 The tic(1) and infocmp(1) programs use lookup tables for the long and
61 short names of terminfo capabilities, as well as the corresponding
62 names for termcap capabilities. These are available to other applica‐
63 tions, though the hash-tables are not available.
64
65 The long terminfo capability names use a "l" (ell) in their names:
66 boolfnames numfnames strfnames
67
68 These are the short names for terminfo capabilities: boolnames, num‐
69 names, and strnames.
70
71 These are the corresponding names used for termcap descriptions: bool‐
72 codes, numcodes, and strcodes.
73
74 Terminal Type
75 On initialization of the curses or terminfo interfaces, setupterm
76 copies the terminal name to the array ttytype.
77
79 The low-level terminfo interface is initialized using setupterm(3X).
80 The upper-level curses interface uses the low-level terminfo interface,
81 internally.
82
84 X/Open Curses does not describe any of these except for cur_term. (The
85 inclusion of cur_term appears to be an oversight, since other compara‐
86 ble low-level information is omitted by X/Open).
87
88 Other implementations may have comparable variables. Some implementa‐
89 tions provide the variables in their libraries, but omit them from the
90 header files.
91
93 curses(3X), curs_terminfo(3X), curs_threads(3X), terminfo(3X), termin‐
94 fo(5).
95
96
97
98 term_variables(3X)