Normally, the tty driver buffers typed characters until a
newline or carriage return is typed. The cbreak routine
disables line buffering and erase/kill character-process-
@@ -135,7 +136,7 @@
Initially, whether the terminal returns 7 or 8 significant
bits on input depends on the control mode of the tty driv-
- er [see termio(7)]. To force 8 bits to be returned, in-
+ er [see termio(7)]. To force 8 bits to be returned, in-
voke meta(win, TRUE); this is equivalent, under POSIX, to
setting the CS8 flag on the terminal. To force 7 bits to
be returned, invoke meta(win, FALSE); this is equivalent,
@@ -168,7 +169,7 @@
When the noqiflush routine is used, normal flush of input
and output queues associated with the INTR, QUIT and SUSP
- characters will not be done [see termio(7)]. When qiflush
+ characters will not be done [see termio(7)]. When qiflush
is called, the queues will be flushed when these control
characters are read. You may want to call noqiflush() in
a signal handler if you want output to continue as though
@@ -185,7 +186,7 @@
additional capability of being able to block for only de-lay milliseconds (where delay is positive).
- The curses library does ``line-breakout optimization'' by
+ The curses library does "line-breakout optimization" by
looking for typeahead periodically while updating the
screen. If input is found, and it is coming from a tty,
the current update is postponed until refresh or doupdate
@@ -199,7 +200,7 @@
All routines that return an integer return ERR upon fail-
ure and OK (SVr4 specifies only "an integer value other
than ERR") upon successful completion, unless otherwise
@@ -216,7 +217,7 @@
These functions are described in the XSI Curses standard,
Issue 4.
@@ -229,33 +230,73 @@
ty, set echo or noecho explicitly just after initializa-
tion, even if your program remains in cooked mode.
+ When keypad is first enabled, ncurses loads the key-defi-
+ nitions for the current terminal description. If the ter-
+ minal description includes extended string capabilities,
+ e.g., from using the -x option of tic, then ncurses also
+ defines keys for the capabilities whose names begin with
+ "k". The corresponding keycodes are generated and (de-
+ pending on previous loads of terminal descriptions) may
+ differ from one execution of a program to the next. The
+ generated keycodes are recognized by the keyname function
+ (which will then return a name beginning with "k" denoting
+ the terminfo capability name rather than "K", used for
+ curses key-names). On the other hand, an application can
+ use define_key to establish a specific keycode for a given
+ string. This makes it possible for an application to
+ check for an extended capability's presence with tigetstr,
+ and reassign the keycode to match its own needs.
+
+ Low-level applications can use tigetstr to obtain the def-
+ inition of any particular string capability. Higher-level
+ applications which use the curses wgetch and similar func-
+ tions to return keycodes rely upon the order in which the
+ strings are loaded. If more than one key definition has
+ the same string value, then wgetch can return only one
+ keycode. Most curses implementations (including ncurses)
+ load key definitions in the order defined by the array of
+ string capability names. The last key to be loaded deter-
+ mines the keycode which will be returned. In ncurses, you
+ may also have extended capabilities interpreted as key
+ definitions. These are loaded after the predefined keys,
+ and if a capability's value is the same as a previously-
+ loaded key definition, the later definition is the one
+ used.
+
-
NOTES
- Note that echo, noecho, halfdelay, intrflush, meta, node-
- lay, notimeout, noqiflush, qiflush, timeout, and wtimeout
+
+ Note that echo, noecho, halfdelay, intrflush, meta, node-
+ lay, notimeout, noqiflush, qiflush, timeout, and wtimeout
may be macros.
The noraw and nocbreak calls follow historical practice in
- that they attempt to restore to normal (`cooked') mode
- from raw and cbreak modes respectively. Mixing raw/noraw
- and cbreak/nocbreak calls leads to tty driver control
- states that are hard to predict or understand; it is not
+ that they attempt to restore to normal (`cooked') mode
+ from raw and cbreak modes respectively. Mixing raw/noraw
+ and cbreak/nocbreak calls leads to tty driver control
+ states that are hard to predict or understand; it is not
recommended.