- The unctrl routine returns a character string which is a printable
+ The unctrl routine returns a character string as a printable
representation of the character ch:
o Printable characters are displayed as themselves, e.g., a one-
@@ -186,7 +186,7 @@
from the terminal database.
oncurses re-fetches the value of the environment variables so that
- it is still the environment variables which set the screen size.
+ it is still the environment variables that set the screen size.
The use_env and use_tioctl routines combine as follows.
@@ -221,7 +221,7 @@
o the window's character cells contain the color pair value, but not
the actual color numbers. If cells in the retrieved window use
- color pairs which have not been created in the application using
+ color pairs that have not been created in the application using
init_pair, they will not be colored when the window is refreshed.
@@ -260,7 +260,7 @@
returns ERR if the terminal was not initialized.
putwin
- returns ERR if the associated fwrite calls return ERR.
+ returns ERR if the associated write(2) calls return ERR.
The keyname function may return the names of user-defined string
- capabilities which are defined in the terminfo entry via the -x option
+ capabilities that are defined in the terminfo entry via the -x option
of tic. This implementation automatically assigns at run-time key
- codes to user-defined strings which begin with "k". The key codes
- start at KEY_MAX, but are not guaranteed to be the same value for
- different runs because user-defined codes are merged from all terminal
- descriptions which have been loaded. The use_extended_names(3x)
+ codes to user-defined strings that begin with "k". The key codes start
+ at KEY_MAX, but are not guaranteed to be the same value for different
+ runs because user-defined codes are merged from all terminal
+ descriptions that have been loaded. The use_extended_names(3x)
function controls whether this data is loaded when the terminal
description is read by the library.
@@ -321,13 +321,13 @@
older ncurses versions. This implementation (as well as the X/Open
variant of Solaris curses, dated 1995) uses textual dumps.
- The implementations which use binary dumps use block-I/O (the
- fwrite and fread functions). Those that use textual dumps use
- buffered-I/O. A few applications may happen to write extra data in
- the file using these functions. Doing that can run into problems
- mixing block- and buffered-I/O. This implementation reduces the
- problem on writes by flushing the output. However, reading from a
- file written using mixed schemes may not be successful.
+ The implementations that use binary dumps use block-I/O (write(2)
+ and read(2) functions). Those that use textual dumps use buffered-
+ I/O. A few applications may happen to write extra data in the file
+ using these functions. Doing that can run into problems mixing
+ block- and buffered-I/O. This implementation reduces the problem
+ on writes by flushing the output. However, reading from a file
+ written using mixed schemes may not be successful.