[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v2 06/18] Style {n,}curses, termcap, terminfo as elsewhere.
|
From: |
G. Branden Robinson |
|
Subject: |
[PATCH v2 06/18] Style {n,}curses, termcap, terminfo as elsewhere. |
|
Date: |
Sat, 23 Sep 2023 06:57:20 -0500 |
That is, not capitalized; in italics (not bold); and not (repeatedly) as
a man page cross reference.
* man/curs_color.3x:
* man/curs_getyx.3x:
* man/curs_inopts.3x:
* man/curs_legacy.3x:
* man/curs_mouse.3x:
* man/curs_opaque.3x:
* man/curs_pad.3x:
* man/curs_print.3x:
* man/curs_slk.3x:
* man/curs_terminfo.3x:
* man/curs_touch.3x:
* man/curs_util.3x:
* man/define_key.3x:
* man/key_defined.3x:
* man/keybound.3x:
* man/keyok.3x:
* man/new_pair.3x:
* man/resizeterm.3x: Do it.
---
man/curs_color.3x | 22 ++++----
man/curs_getyx.3x | 4 +-
man/curs_inopts.3x | 38 +++++++-------
man/curs_legacy.3x | 2 +-
man/curs_mouse.3x | 22 ++++----
man/curs_opaque.3x | 4 +-
man/curs_pad.3x | 8 +--
man/curs_print.3x | 4 +-
man/curs_slk.3x | 26 +++++-----
man/curs_terminfo.3x | 121 ++++++++++++++++++++++---------------------
man/curs_touch.3x | 4 +-
man/curs_util.3x | 50 +++++++++---------
man/define_key.3x | 6 +--
man/key_defined.3x | 4 +-
man/keybound.3x | 4 +-
man/keyok.3x | 4 +-
man/new_pair.3x | 8 +--
man/resizeterm.3x | 28 +++++-----
18 files changed, 180 insertions(+), 179 deletions(-)
diff --git a/man/curs_color.3x b/man/curs_color.3x
index 7519ed59..7df9c45e 100644
--- a/man/curs_color.3x
+++ b/man/curs_color.3x
@@ -83,7 +83,7 @@ .SH SYNOPSIS
.fi
.SH DESCRIPTION
.SS Overview
-\fBcurses\fP supports color attributes on terminals with that capability.
+\fIcurses\fP supports color attributes on terminals with that capability.
To use these routines \fB\%start_color\fP must be called, usually right after
\fB\%initscr\fP.
Colors are always used in pairs (referred to as color-pairs).
@@ -105,7 +105,7 @@ .SS Overview
The routine \fB\%pair_content\fP allows a programmer to find
out how a given color-pair is currently defined.
.SS Color Rendering
-The \fBcurses\fP library combines these inputs to produce the
+The \fIcurses\fP library combines these inputs to produce the
actual foreground and background colors shown on the screen:
.bP
per-character video attributes (e.g., via \fB\%waddch\fP),
@@ -122,36 +122,36 @@ .SS Color Rendering
The background character is a special case: it includes a character value,
just as if it were passed to \fB\%waddch\fP.
.PP
-The \fBcurses\fP library does the actual work of combining these color
+The \fIcurses\fP library does the actual work of combining these color
pairs in an internal function called from \fB\%waddch\fP:
.bP
If the parameter passed to \fB\%waddch\fP is \fIblank\fP,
and it uses the special color pair 0,
.RS
.bP
-\fBcurses\fP next checks the window attribute.
+\fIcurses\fP next checks the window attribute.
.bP
If the window attribute does not use color pair 0,
-\fBcurses\fP uses the color pair from the window attribute.
+\fIcurses\fP uses the color pair from the window attribute.
.bP
-Otherwise, \fBcurses\fP uses the background character.
+Otherwise, \fIcurses\fP uses the background character.
.RE
.bP
If the parameter passed to \fB\%waddch\fP is \fInot blank\fP,
or it does not use the special color pair 0,
-\fBcurses\fP prefers the color pair from the parameter,
+\fIcurses\fP prefers the color pair from the parameter,
if it is nonzero.
Otherwise, it tries the window attribute next, and finally the
background character.
.PP
-Some \fBcurses\fP functions such as \fB\%wprintw\fP call \fB\%waddch\fP.
+Some \fIcurses\fP functions such as \fB\%wprintw\fP call \fB\%waddch\fP.
Those do not combine its parameter with a color pair.
Consequently those calls use only the window attribute or
the background character.
.SH CONSTANTS
In \fB\%<curses.h>\fP the following macros are defined.
These are the standard colors (ISO-6429).
-\fBcurses\fP also assumes that \fB\%COLOR_BLACK\fP is the default
+\fIcurses\fP also assumes that \fB\%COLOR_BLACK\fP is the default
background color for all terminals.
.PP
.nf
@@ -414,7 +414,7 @@ .SH RETURN VALUE
returns an error if the color table cannot be allocated.
.RE
.SH NOTES
-In the \fBncurses\fP implementation, there is a separate color activation flag,
+In the \fIncurses\fP implementation, there is a separate color activation flag,
color palette, color pairs table,
and associated \fB\%COLORS\fP and \fB\%COLOR_PAIRS\fP counts
for each screen; the \fB\%start_color\fP function only affects the current
@@ -490,7 +490,7 @@ .SH HISTORY
by the size of the bitfield.
.SH PORTABILITY
.SS Extensions
-The functions marked as extensions were designed for \fBncurses\fP(3X),
+The functions marked as extensions were designed for \fIncurses\fP(3X),
and are not found in SVr4 curses, 4.4BSD curses,
or any other previous version of curses.
.SS Standards
diff --git a/man/curs_getyx.3x b/man/curs_getyx.3x
index 77020943..dca60095 100644
--- a/man/curs_getyx.3x
+++ b/man/curs_getyx.3x
@@ -78,7 +78,7 @@ .SH PORTABILITY
\fB\%getmaxy\fP,
\fB\%getparx\fP and
\fB\%getpary\fP
-for compatibility with older versions of curses.
+for compatibility with older versions of \fIcurses\fP.
.PP
Although X/Open Curses does not address this,
many implementations provide members of the \fB\%WINDOW\fP structure
@@ -90,7 +90,7 @@ .SH PORTABILITY
Besides the problem of opaque structures,
the data stored in like-named members may not have like-values in
different implementations.
-For example, the \fB\%WINDOW._maxx\fP and \fB\%WINDOW._maxy\fP values in
ncurses
+For example, the \fB\%WINDOW._maxx\fP and \fB\%WINDOW._maxy\fP values in
\fIncurses\fP
have (at least since release 1.8.1) differed by one from some
other implementations.
The difference is hidden by means of the macro \fB\%getmaxyx\fP.
diff --git a/man/curs_inopts.3x b/man/curs_inopts.3x
index 15646db3..31c72fc9 100644
--- a/man/curs_inopts.3x
+++ b/man/curs_inopts.3x
@@ -97,7 +97,7 @@ .SH SYNOPSIS
\fBint is_raw(void);\fP
.nf
.SH DESCRIPTION
-The \fBncurses\fP library provides several functions which let an application
+The \fIncurses\fP library provides several functions which let an application
change the way input from the terminal is handled.
Some are global, applying to all windows.
Others apply only to a specific window.
@@ -119,7 +119,7 @@ .SS cbreak/nocbreak
Initially the terminal may or may not be in \fB\%cbreak\fP mode, as the mode is
inherited; therefore, a program should call \fB\%cbreak\fP or \fB\%nocbreak\fP
explicitly.
-Most interactive programs using \fBcurses\fP set the \fB\%cbreak\fP
+Most interactive programs using \fIcurses\fP set the \fB\%cbreak\fP
mode.
Note that \fB\%cbreak\fP overrides \fBraw\fP.
[See \fB\%curs_getch\fP(3X) for a
@@ -153,7 +153,7 @@ .SS intrflush
If the \fB\%intrflush\fP option is enabled (\fIbf\fP is \fBTRUE\fP), and an
interrupt key is pressed on the keyboard (interrupt, break, quit), all output
in
the tty driver queue will be flushed, giving the effect of faster response to
-the interrupt, but causing \fBcurses\fP to have the wrong idea of what is on
+the interrupt, but causing \fIcurses\fP to have the wrong idea of what is on
the screen.
Disabling the option (\fIbf\fP is \fBFALSE\fP) prevents the
flush.
@@ -167,7 +167,7 @@ .SS keypad
(such as an arrow key) and \fB\%wgetch\fP(3X) returns a single value
representing the function key, as in \fB\%KEY_LEFT\fP.
If disabled
-(\fIbf\fP is \fBFALSE\fP), \fBcurses\fP does not treat function keys
+(\fIbf\fP is \fBFALSE\fP), \fIcurses\fP does not treat function keys
specially and the program has to interpret the escape sequences
itself.
If the keypad in the terminal can be turned on (made to
@@ -221,7 +221,7 @@ .SS raw/noraw
passed through uninterpreted, instead of generating a signal.
The behavior of
the BREAK key depends on other bits in the tty driver that are not set by
-\fBcurses\fP.
+\fIcurses\fP.
.\"
.SS qiflush/noqiflush
When the \fB\%noqiflush\fP routine is used, normal flush of input and
@@ -250,7 +250,7 @@ .SS timeout/wtimeout
\fIdelay\fP milliseconds (where \fIdelay\fP is positive).
.\"
.SS typeahead
-The \fBcurses\fP library does \*(``line-breakout optimization\*(''
+The \fIcurses\fP 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
@@ -304,20 +304,20 @@ .SH EXTENSIONS
if the flag is reset, or
.TP 5
-1
-if the curses library was not initialized.
+if the \fIcurses\fP library was not initialized.
.PP
-These routines are specific to ncurses.
+These routines are specific to \fIncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on ncurses extensions
+It is recommended that any code depending on \fIncurses\fP extensions
be conditioned using \fB\%NCURSES_VERSION\fP.
.SH PORTABILITY
Except as noted in the section on extensions,
these functions are described in the XSI Curses standard, Issue 4.
.PP
-The ncurses library obeys the XPG4 standard and the historical practice of the
-AT&T curses implementations, in that the echo bit is cleared when curses
+The \fIncurses\fP library obeys the XPG4 standard and the historical practice
of the
+AT&T \fIcurses\fP implementations, in that the echo bit is cleared when
\fIcurses\fP
initializes the terminal state.
-BSD curses differed from this slightly; it
+BSD \fIcurses\fP differed from this slightly; it
left the echo bit on at initialization, but the BSD \fBraw\fP call turned it
off as a side-effect.
For best portability, set \fBecho \fPor \fB\%noecho\fP explicitly
@@ -325,24 +325,24 @@ .SH PORTABILITY
.PP
The XSI Curses standard is ambiguous on the question of whether \fBraw\fP
should disable the CRLF translations controlled by \fBnl\fP and \fBnonl\fP.
-BSD curses did turn off these translations; AT&T curses (at least as late as
+BSD \fIcurses\fP did turn off these translations; AT&T \fIcurses\fP (at least
as late as
SVr1) did not.
We chose to do so, on the theory that a programmer requesting
raw input wants a clean (ideally 8-bit clean) connection that the operating
system will not alter.
.PP
When \fB\%keypad\fP is first enabled,
-ncurses loads the key-definitions for the current terminal description.
+\fIncurses\fP loads the key-definitions for the current terminal description.
If the terminal description includes extended string capabilities,
e.g., from using the \fB\-x\fP option of \fB@TIC@\fP,
-then ncurses also defines keys for the capabilities whose names
+then \fIncurses\fP also defines keys for the capabilities whose names
begin with \*(``k\*(''.
The corresponding keycodes are generated and (depending on previous
loads of terminal descriptions) may differ from one execution of a
program to the next.
The generated keycodes are recognized by the \fB\%keyname\fP function
(which will then return a name beginning with \*(``k\*('' denoting the
-terminfo capability name rather than \*(``K\*('', used for curses key-names).
+terminfo capability name rather than \*(``K\*('', used for \fIcurses\fP
key-names).
On the other hand, an application can use \fB\%define_key\fP to establish
a specific keycode for a given string.
This makes it possible for an application to check for an extended
@@ -351,16 +351,16 @@ .SH PORTABILITY
.PP
Low-level applications can use \fB\%tigetstr\fP to obtain the definition
of any particular string capability.
-Higher-level applications which use the curses \fB\%wgetch\fP
+Higher-level applications which use the \fIcurses\fP \fB\%wgetch\fP
and similar functions 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 \fB\%wgetch\fP can return only one keycode.
-Most curses implementations (including ncurses)
+Most \fIcurses\fP implementations (including \fIncurses\fP)
load key definitions in the order
defined by the array of string capability names.
The last key to be loaded determines the keycode which will be returned.
-In ncurses, you may also have extended capabilities interpreted as
+In \fIncurses\fP, 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
diff --git a/man/curs_legacy.3x b/man/curs_legacy.3x
index 3153d9a6..2049430a 100644
--- a/man/curs_legacy.3x
+++ b/man/curs_legacy.3x
@@ -63,7 +63,7 @@ .SH SYNOPSIS
\fBint getpary(const WINDOW *\fIwin\fB);\fR
.fi
.SH DESCRIPTION
-These legacy functions are simpler to use than the X/Open Curses functions:
+These legacy functions are simpler to use than the X/Open \fIcurses\fP
functions:
.bP
The \fB\%getattrs\fP function returns the same attribute data as
\fB\%wattr_get\fP.
.IP
diff --git a/man/curs_mouse.3x b/man/curs_mouse.3x
index 9611f397..c2bb74f0 100644
--- a/man/curs_mouse.3x
+++ b/man/curs_mouse.3x
@@ -274,10 +274,10 @@ .SH RETURN VALUE
are boolean functions returning \fBTRUE\fP or \fBFALSE\fP depending
on their test result.
.SH PORTABILITY
-These calls were designed for \fBncurses\fP(3X), and are not found in SVr4
-curses, 4.4BSD curses, or any other previous version of curses.
+These calls were designed for \fIncurses\fP, and are not found in SVr4
+\fIcurses\fP, 4.4BSD \fIcurses\fP, or any other previous version of
\fIcurses\fP.
.PP
-SVr4 curses had support for the mouse in a variant of \fBxterm\fP(1).
+SVr4 \fIcurses\fP had support for the mouse in a variant of \fBxterm\fP(1).
It is mentioned in a few places, but with no supporting documentation:
.bP
the \*(``libcurses\*('' manual page lists functions for this feature
@@ -301,20 +301,20 @@ .SH PORTABILITY
req_mouse_pos reqmp RQ Request mouse position report
.NE
.bP
-the interface made assumptions (as does ncurses) about the escape sequences
+the interface made assumptions (as does \fIncurses\fP) about the escape
sequences
sent to and received from the terminal.
.IP
For instance
-the SVr4 curses library used the \fB\%get_mouse\fP capability to tell the
+the SVr4 \fIcurses\fP library used the \fB\%get_mouse\fP capability to tell the
terminal which mouse button events it should send,
passing the mouse-button bit-mask to the terminal.
Also, it could ask the terminal
where the mouse was using the \fB\%req_mouse_pos\fP capability.
.IP
-Those features required a terminal which had been modified to work with curses.
+Those features required a terminal which had been modified to work with
\fIcurses\fP.
They were not part of the X Consortium's xterm.
.PP
-When developing the xterm mouse support for ncurses in September 1995,
+When developing the xterm mouse support for \fIncurses\fP in September 1995,
Eric Raymond was uninterested in using the same interface due to its
lack of documentation.
Later, in 1998, Mark Hesseling provided support in
@@ -328,7 +328,7 @@ .SH PORTABILITY
If the interface is changed, the value of \fB\%NCURSES_MOUSE_VERSION\fP will be
incremented.
These values for \fB\%NCURSES_MOUSE_VERSION\fP may be
-specified when configuring ncurses:
+specified when configuring \fIncurses\fP:
.RS 3
.TP 3
1
@@ -344,7 +344,7 @@ .SH PORTABILITY
The order of the \fB\%MEVENT\fP structure members is not guaranteed.
Additional fields may be added to the structure in the future.
.PP
-Under \fBncurses\fP(3X), these calls are implemented using either
+Under \fIncurses\fP, these calls are implemented using either
xterm's built-in mouse-tracking API or
platform-specific drivers including
.RS 3
@@ -358,7 +358,7 @@ .SH PORTABILITY
.PP
If you are using an unsupported configuration,
mouse events will not be visible to
-\fBncurses\fP(3X) (and the \fB\%mousemask\fP function will always
+\fIncurses\fP (and the \fB\%mousemask\fP function will always
return \fB0\fP).
.PP
If the terminfo entry contains a \fBXM\fP string,
@@ -402,7 +402,7 @@ .SH BUGS
i.e., it is the beginning of the response.
.PP
Because there are no standard terminal responses that would serve to identify
-terminals which support the xterm mouse protocol, \fBncurses\fP assumes that
+terminals which support the xterm mouse protocol, \fIncurses\fP assumes that
if \fB\%kmous\fP is defined in the terminal description,
or if the terminal description's primary name or aliases
contain the string \*(``xterm\*('',
diff --git a/man/curs_opaque.3x b/man/curs_opaque.3x
index fcb009b8..ec6eb845 100644
--- a/man/curs_opaque.3x
+++ b/man/curs_opaque.3x
@@ -128,9 +128,9 @@ .SH RETURN VALUE
.SH NOTES
Both a macro and a function are provided for each name.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fIncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on ncurses extensions
+It is recommended that any code depending on \fIncurses\fP extensions
be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
\fB\%curses\fP(3X),
diff --git a/man/curs_pad.3x b/man/curs_pad.3x
index 8271bb1b..ce68b854 100644
--- a/man/curs_pad.3x
+++ b/man/curs_pad.3x
@@ -157,9 +157,9 @@ .SH RETURN VALUE
.SH NOTES
Note that \fB\%pechochar\fP may be a macro.
.SH PORTABILITY
-BSD curses has no \fIpad\fP feature.
+BSD \fIcurses\fP has no \fIpad\fP feature.
.PP
-SVr2 curses (1986) provided the \fB\%newpad\fP and related functions,
+SVr2 \fIcurses\fP (1986) provided the \fB\%newpad\fP and related functions,
documenting them in a single line each.
SVr3 (1987) provided more extensive documentation.
.PP
@@ -181,7 +181,7 @@ .SH PORTABILITY
a pad is undocumented,
and is not checked by the vendor Unix implementations:
.bP
-SVr4 curses sets a flag in the \fB\%WINDOW\fP structure in \fB\%newpad\fP
+SVr4 \fIcurses\fP sets a flag in the \fB\%WINDOW\fP structure in \fB\%newpad\fP
which tells if the window is a \fIpad\fP.
.IP
However, it uses this information only in
@@ -201,7 +201,7 @@ .SH PORTABILITY
though interestingly enough, a comment in the source code
states that the lack of a check was an MKS extension.
.bP
-NetBSD 7 curses
+NetBSD 7 \fIcurses\fP
sets a flag in the \fB\%WINDOW\fP structure for \fB\%newpad\fP and
\fB\%subpad\fP,
using this to help with the distinction between \fB\%wnoutrefresh\fP
and \fB\%pnoutrefresh\fP.
diff --git a/man/curs_print.3x b/man/curs_print.3x
index 1ef48e6c..77f52e1c 100644
--- a/man/curs_print.3x
+++ b/man/curs_print.3x
@@ -64,8 +64,8 @@ .SH RETURN VALUE
When \fB\%mcprint\fP succeeds, it returns the number of characters actually
sent to the printer.
.SH PORTABILITY
-The \fB\%mcprint\fP call was designed for \fB\%ncurses\fP(3X), and is not found
-in SVr4 curses, 4.4BSD curses, or any other previous version of curses.
+The \fB\%mcprint\fP call was designed for \fIncurses\fP, and is not found
+in SVr4 \fIcurses\fP, 4.4BSD \fIcurses\fP, or any other previous version of
\fIcurses\fP.
.SH BUGS
Padding in the \fBmc5p\fP, \fBmc4\fP and \fBmc5\fP capabilities will not be
interpreted.
diff --git a/man/curs_slk.3x b/man/curs_slk.3x
index f36e3e08..b468662d 100644
--- a/man/curs_slk.3x
+++ b/man/curs_slk.3x
@@ -91,15 +91,15 @@ .SH DESCRIPTION
The \fBslk\fP* functions manipulate the set of soft function-key labels that
exist on
many terminals.
For those terminals that do not have soft labels,
-\fBcurses\fP takes over the bottom line of \fB\%stdscr\fP, reducing the size of
+\fIcurses\fP takes over the bottom line of \fB\%stdscr\fP, reducing the size of
\fB\%stdscr\fP and the variable \fBLINES\fP.
-\fBcurses\fP standardizes on eight
+\fIcurses\fP standardizes on eight
labels of up to eight characters each.
-In addition to this, the ncurses
+In addition to this, the \fIncurses\fP
implementation supports a mode where it simulates 12 labels of up to five
characters each.
This is useful for PC-like enduser devices.
-ncurses simulates this mode by taking over up to two lines at
+\fIncurses\fP simulates this mode by taking over up to two lines at
the bottom of the screen;
it does not try to use any hardware support for this
mode.
@@ -171,7 +171,7 @@ .SS Video attributes
They have an effect only if soft labels are simulated on the bottom line of
the screen.
The default highlight for soft keys is A_STANDOUT (as in
-System V curses, which does not document this fact).
+System V \fIcurses\fP, which does not document this fact).
.SS Colors
The \fB\%slk_color\fP routine corresponds to \fB\%color_set\fP.
It has an effect only
@@ -242,14 +242,14 @@ .SH HISTORY
\fBslk_attrset\fP
\fBslk_start\fP
.PP
-X/Open Curses added these:
+X/Open \fIcurses\fP added these:
\fBslk_attr_off\fP
\fBslk_attr_on\fP
\fBslk_attr_set\fP
\fBslk_color\fP
\fBslk_wset\fP
.SH EXTENSIONS
-X/Open Curses documents the \fIopts\fP argument as reserved for future use,
+X/Open \fIcurses\fP documents the \fIopts\fP argument as reserved for future
use,
saying that it must be null.
This implementation
uses that parameter in ABI 6 for the functions which have a color-pair
@@ -262,8 +262,8 @@ .SH NOTES
Most applications would use \fB\%slk_noutrefresh\fP because a
\fB\%wrefresh\fP is likely to follow soon.
.SH PORTABILITY
-The XSI Curses standard, Issue 4, described the soft-key functions,
-with some differences from SVr4 curses:
+The XSI \fIcurses\fP standard, Issue 4, described the soft-key functions,
+with some differences from SVr4 \fIcurses\fP:
.bP
It added functions like the SVr4
attribute-manipulation functions \fB\%slk_attron\fP,
@@ -280,7 +280,7 @@ .SH PORTABILITY
.bP
It added \fB\%slk_color\fP.
.PP
-Although \fB\%slk_start\fP is declared in the curses header file,
+Although \fB\%slk_start\fP is declared in the \fIcurses\fP header file,
it was not documented by SVr4 other than its presence in a list
of libtermlib.so.1 symbols.
Reading the source code (i.e., Illumos):
@@ -312,12 +312,12 @@ .SH PORTABILITY
If there are more than 16 elements, \fB\%slk_start\fP returns an error.
.bP
The format codes \fB2\fP and \fB3\fP for \fB\%slk_init\fP
-were added by ncurses in 1996.
+were added by \fIncurses\fP in 1996.
PDCurses 2.4 added this feature in 2001.
.PP
-The function \fB\%slk_attr\fP was added by ncurses in 1996.
+The function \fB\%slk_attr\fP was added by \fIncurses\fP in 1996.
.PP
-X/Open Curses does not specify a limit for the number of colors and
+X/Open \fIcurses\fP does not specify a limit for the number of colors and
color pairs which a terminal can support.
However, in its use of \fBshort\fP for the parameters,
it carries over SVr4's implementation detail for the compiled
diff --git a/man/curs_terminfo.3x b/man/curs_terminfo.3x
index f32af1a2..f6a9940a 100644
--- a/man/curs_terminfo.3x
+++ b/man/curs_terminfo.3x
@@ -107,10 +107,10 @@ .SH SYNOPSIS
.fi
.SH DESCRIPTION
These low-level routines must be called by programs that have to deal
-directly with the \fBterminfo\fP database to handle certain terminal
+directly with the \fIterminfo\fP database to handle certain terminal
capabilities, such as programming function keys.
For all other
-functionality, \fBcurses\fP routines are more suitable and their use is
+functionality, \fIcurses\fP routines are more suitable and their use is
recommended.
.PP
None of these functions use (or are aware of) multibyte character strings
@@ -122,7 +122,7 @@ .SH DESCRIPTION
they are strings of 8-bit characters.
.SS Initialization
Initially, \fB\%setupterm\fP should be called.
-The high-level curses functions \fB\%initscr\fP and
+The high-level \fIcurses\fP functions \fB\%initscr\fP and
\fB\%newterm\fP call \fB\%setupterm\fP to initialize the
low-level set of terminal-dependent variables
[listed in \fB\%terminfo\fP(\*n)].
@@ -133,12 +133,12 @@ .SS Initialization
The header files \fB\%curses.h\fP and \fB\%term.h\fP should be included (in
this
order) to get the definitions for these strings, numbers, and flags.
.PP
-The \fBterminfo\fP variables
+The \fIterminfo\fP variables
\fBlines\fP and \fB\%columns\fP are initialized by \fB\%setupterm\fP as
follows:
.bP
If \fB\%use_env(FALSE)\fP has been called, values for
-\fBlines\fP and \fB\%columns\fP specified in \fBterminfo\fP are used.
+\fBlines\fP and \fB\%columns\fP specified in \fIterminfo\fP are used.
.bP
Otherwise, if the environment variables \fBLINES\fP and \fB\%COLUMNS\fP
exist, their values are used.
@@ -147,10 +147,10 @@ .SS Initialization
is used.
Otherwise, if the environment variables do not exist, the
values for \fBlines\fP and \fB\%columns\fP specified in the
-\fBterminfo\fP database are used.
+\fIterminfo\fP database are used.
.PP
Parameterized strings should be passed through \fB\%tparm\fP to instantiate
them.
-All \fBterminfo\fP strings
+All \fIterminfo\fP strings
(including the output of \fB\%tparm\fP)
should be printed
with \fB\%tputs\fP or \fBputp\fP.
@@ -173,9 +173,9 @@ .SS Initialization
output \fB\%enter_ca_mode\fP and
call \fB\%reset_prog_mode\fP after returning from the shell.
.PP
-The \fB\%setupterm\fP routine reads in the \fBterminfo\fP database,
-initializing the \fBterminfo\fP structures, but does not set up the
-output virtualization structures used by \fBcurses\fP.
+The \fB\%setupterm\fP routine reads in the \fIterminfo\fP database,
+initializing the \fIterminfo\fP structures, but does not set up the
+output virtualization structures used by \fIcurses\fP.
These are its parameters:
.RS 3
.TP 5
@@ -188,7 +188,7 @@ .SS Initialization
.IP
Higher-level applications use \fB\%newterm\fP(3X) for initializing the
terminal,
passing an output \fIstream\fP rather than a \fIdescriptor\fP.
-In curses, the two are the same because \fB\%newterm\fP calls
\fB\%setupterm\fP,
+In \fIcurses\fP, the two are the same because \fB\%newterm\fP calls
\fB\%setupterm\fP,
passing the file descriptor derived from its output stream parameter.
.TP 5
\fIerrret\fP
@@ -205,7 +205,7 @@ .SS Initialization
.RS
.TP 5
.B 1
-means that the terminal is hardcopy, cannot be used for curses applications.
+means that the terminal is hardcopy, cannot be used for \fIcurses\fP
applications.
.IP
\fBsetupterm\fP determines if the entry is a hardcopy type by
checking the \fBhc\fP (\fBhardcopy\fP) capability.
@@ -213,13 +213,13 @@ .SS Initialization
.B 0
means that the terminal could not be found,
or that it is a generic type,
-having too little information for curses applications to run.
+having too little information for \fIcurses\fP applications to run.
.IP
\fBsetupterm\fP determines if the entry is a generic type by
checking the \fBgn\fP (\fBgeneric_type\fP) capability.
.TP 5
.B \-1
-means that the \fBterminfo\fP database could not be found.
+means that the \fIterminfo\fP database could not be found.
.RE
.IP
If \fIerrret\fP is
@@ -247,14 +247,14 @@ .SS The Terminal State
\fB\%setupterm\fP allocates new storage for each set of terminal capabilities.
.PP
The \fB\%set_curterm\fP routine sets \fB\%cur_term\fP to
-\fInterm\fP, and makes all of the \fBterminfo\fP boolean, numeric, and
+\fInterm\fP, and makes all of the \fIterminfo\fP boolean, numeric, and
string variables use the values from \fInterm\fP.
It returns the old value of \fB\%cur_term\fP.
.PP
The \fB\%del_curterm\fP routine frees the space pointed to by
\fIoterm\fP and makes it available for further use.
If \fIoterm\fP is
-the same as \fB\%cur_term\fP, references to any of the \fBterminfo\fP
+the same as \fB\%cur_term\fP, references to any of the \fIterminfo\fP
boolean, numeric, and string variables thereafter may refer to invalid
memory locations until another \fB\%setupterm\fP has been called.
.PP
@@ -295,7 +295,7 @@ .SS Formatting Output
.bP
\fB\%tiparm_s\fP is an extension which is a safer formatting function
than \fB\%tparm\fR or \fB\%tiparm\fR,
-because it allows the developer to tell the curses
+because it allows the developer to tell the \fIcurses\fP
library how many parameters to expect in the parameter list,
and which may be string parameters.
.IP
@@ -303,16 +303,16 @@ .SS Formatting Output
(up to 9) which will be passed as char* rather than numbers.
.bP
The extension \fB\%tiscan_s\fP allows the application
-to inspect a formatting capability to see what the curses library would assume.
+to inspect a formatting capability to see what the \fIcurses\fP library would
assume.
.\" ***************************************************************************
.SS Output Functions
The \fB\%tputs\fP routine applies padding information
-(i.e., by interpreting marker embedded in the terminfo capability
+(i.e., by interpreting marker embedded in the \fIterminfo\fP capability
such as \*(``$<5>\*('' as 5 milliseconds)
to the string
\fIstr\fP and outputs it:
.bP
-The \fIstr\fP parameter must be a terminfo string
+The \fIstr\fP parameter must be a \fIterminfo\fP string
variable or the return value from
\fB\%tparm\fP, \fB\%tiparm\fP, \fB\%tgetstr\fP, or \fB\%tgoto\fP.
.IP
@@ -365,13 +365,13 @@ .SS Output Functions
the output stream parameter of \fB\%newterm\fP(3X).
.PP
While \fBputp\fP and \fB\%mvcur\fP are low-level functions which
-do not use the high-level curses state,
+do not use the high-level \fIcurses\fP state,
they are declared in \fB\%<curses.h>\fP because SystemV did this
(see \fIHISTORY\fP).
.\" ***************************************************************************
.SS Terminal Capability Functions
The \fB\%tigetflag\fP, \fB\%tigetnum\fP and \fB\%tigetstr\fP routines return
-the value of the capability corresponding to the \fBterminfo\fP
+the value of the capability corresponding to the \fIterminfo\fP
\fIcapname\fP passed to them, such as \fBxenl\fP.
The \fIcapname\fP for each capability is given in the table column entitled
\fIcapname\fP code in the capabilities section of \fB\%terminfo\fP(\*n).
@@ -407,13 +407,13 @@ .SS Terminal Capability Functions
.SS Terminal Capability Names
These null-terminated arrays contain
.bP
-the short terminfo names (\*(``codes\*(''),
+the short \fIterminfo\fP names (\*(``codes\*(''),
.bP
-the \fBtermcap\fP names (\*(``names\*(''), and
+the \fItermcap\fP names (\*(``names\*(''), and
.bP
-the long terminfo names (\*(``fnames\*('')
+the long \fIterminfo\fP names (\*(``fnames\*('')
.PP
-for each of the predefined \fBterminfo\fP variables:
+for each of the predefined \fIterminfo\fP variables:
.sp
.RS
\fBconst char *boolnames[]\fP, \fB*boolcodes[]\fP, \fB*boolfnames[]\fP
@@ -436,12 +436,12 @@ .SS Releasing Memory
The formatting functions \fB\%tparm\fP and \fB\%tiparm\fP extend the storage
allocated by \fB\%setupterm\fP:
.bP
-the \*(``static\*('' terminfo variables [a-z].
-Before ncurses 6.3, those were shared by all screens.
-With ncurses 6.3, those are allocated per screen.
+the \*(``static\*('' \fIterminfo\fP variables [a-z].
+Before \fIncurses\fP 6.3, those were shared by all screens.
+With \fIncurses\fP 6.3, those are allocated per screen.
See \fB\%terminfo\fP(\*n) for details.
.bP
-to improve performance, ncurses 6.3 caches the result of analyzing terminfo
+to improve performance, \fIncurses\fP 6.3 caches the result of analyzing
\fIterminfo\fP
strings for their parameter types.
That is stored as a binary tree referenced from the \fB\%TERMINAL\fP structure.
.PP
@@ -517,21 +517,22 @@ .SS Compatibility macros
.\" ***************************************************************************
.SH HISTORY
SVr2 introduced the terminfo feature.
+SVr2 introduced the \fIterminfo\fP feature.
Its programming manual mentioned these low-level functions:
.PP
.TS
l l.
\fBFunction\fP \fBDescription\fP
_
-fixterm restore tty to \*(``in curses\*('' state
+fixterm restore tty to \*(``in \fIcurses\fP\*('' state
gettmode establish current tty modes
mvcur low level cursor motion
putp T{
utility function that uses \fB\%tputs\fP to send characters via \fB\%putchar\fP
T}
-resetterm set tty modes to \*(``out of curses\*('' state
+resetterm set tty modes to \*(``out of \fIcurses\fP\*('' state
resetty reset tty flags to stored value
-saveterm save current modes as \*(``in curses\*('' state
+saveterm save current modes as \*(``in \fIcurses\fP\*('' state
savetty store current tty flags
setterm establish terminal with given type
setupterm establish terminal with given type
@@ -544,7 +545,7 @@ .SH HISTORY
.TE
.PP
The programming manual also mentioned
-functions provided for termcap compatibility
+functions provided for \fItermcap\fP compatibility
(commenting that they \*(``may go away at a later date\*(''):
.PP
.TS
@@ -562,11 +563,11 @@ .SH HISTORY
T}
.TE
.PP
-Early terminfo programs obtained capability values from the
+Early \fIterminfo\fP programs obtained capability values from the
\fB\%TERMINAL\fP structure initialized by \fB\%setupterm\fP.
.PP
-SVr3 extended terminfo by adding functions to retrieve capability values
-(like the termcap interface),
+SVr3 extended \fIterminfo\fP by adding functions to retrieve capability values
+(like the \fItermcap\fP interface),
and reusing \fB\%tgoto\fP and \fB\%tputs\fP:
.PP
.TS
@@ -579,8 +580,8 @@ .SH HISTORY
tigetstr get string entry for given \fIid\fP
.TE
.PP
-SVr3 also replaced several of the SVr2 terminfo functions
-which had no counterpart in the termcap interface,
+SVr3 also replaced several of the SVr2 \fIterminfo\fP functions
+which had no counterpart in the \fItermcap\fP interface,
documenting them as obsolete:
.TS
l l
@@ -615,7 +616,7 @@ .SH HISTORY
.PP
SVr4 added the \fB\%vid_attr\fP and \fB\%vid_puts\fP functions.
.PP
-There are other low-level functions declared in the curses header files
+There are other low-level functions declared in the \fIcurses\fP header files
on Unix systems,
but none were documented.
The functions marked \*(``obsolete\*('' remained in use
@@ -623,8 +624,8 @@ .SH HISTORY
.SH PORTABILITY
.SS Extensions
The functions marked as extensions were designed for \fB\%ncurses\fP(3X),
-and are not found in SVr4 curses, 4.4BSD curses,
-or any other previous version of curses.
+and are not found in SVr4 \fIcurses\fP, 4.4BSD \fIcurses\fP,
+or any other previous version of \fIcurses\fP.
.SS Legacy functions
X/Open notes that \fB\%vidattr\fP and \fB\%vidputs\fP may be macros.
.PP
@@ -642,24 +643,24 @@ .SS Legacy data
Extended terminal capability names, e.g., as defined by \fB\%@TIC@\ \-x\fP,
are not stored in the arrays described here.
.SS Output buffering
-Older versions of \fBncurses\fP assumed that the file descriptor passed to
+Older versions of \fIncurses\fP assumed that the file descriptor passed to
\fB\%setupterm\fP from \fB\%initscr\fP or \fB\%newterm\fP uses buffered I/O,
and would write to the corresponding stream.
In addition to the limitation that the terminal was left in block-buffered
-mode on exit (like System V curses),
-it was problematic because \fBncurses\fP
+mode on exit (like System V \fIcurses\fP),
+it was problematic because \fIncurses\fP
did not allow a reliable way to cleanup on receiving SIGTSTP.
.PP
-The current version (ncurses6)
-uses output buffers managed directly by \fBncurses\fP.
+The current version (\fIncurses\fP 6)
+uses output buffers managed directly by \fIncurses\fP.
Some of the low-level functions described in this manual page write
to the standard output.
They are not signal-safe.
-The high-level functions in \fBncurses\fP use
+The high-level functions in \fIncurses\fP use
alternate versions of these functions
using the more reliable buffering scheme.
.SS Function prototypes
-The X/Open Curses prototypes are based on the SVr4 curses header declarations,
+The X/Open Curses prototypes are based on the SVr4 \fIcurses\fP header
declarations,
which were defined at the same time the C language was first standardized in
the late 1980s.
.bP
@@ -672,7 +673,7 @@ .SS Function prototypes
.IP
As an extension, this implementation can be configured to change the
function prototypes to use the \fBconst\fP keyword.
-The ncurses ABI 6 enables this feature by default.
+The \fIncurses\fP ABI 6 enables this feature by default.
.bP
X/Open Curses prototypes \fB\%tparm\fP with a fixed number of parameters,
rather than a variable argument list.
@@ -685,7 +686,7 @@ .SS Function prototypes
In response to review comments by Thomas E. Dickey,
X/Open Curses Issue 7 proposed the \fB\%tiparm\fP function in mid-2009.
.IP
-While \fB\%tiparm\fP is always provided in ncurses,
+While \fB\%tiparm\fP is always provided in \fIncurses\fP,
the older form is only available as a build-time configuration option.
If not specially configured, \fB\%tparm\fP is the same as \fB\%tiparm\fP.
.PP
@@ -702,10 +703,10 @@ .SS Function prototypes
.bP
Providing the right number of parameters for a variadic function
such as \fB\%tiparm\fP can be a problem, in particular for string parameters.
-However, only a few terminfo capabilities use string parameters
+However, only a few \fIterminfo\fP capabilities use string parameters
(e.g., the ones used for programmable function keys).
.IP
-The ncurses library checks usage of these capabilities,
+The \fIncurses\fP library checks usage of these capabilities,
and returns an error if the capability mishandles string parameters.
But it cannot check if a calling program provides strings in the right
places for the \fB\%tparm\fP calls.
@@ -719,11 +720,11 @@ .SS Special TERM treatment
\fB\%setupterm\fP interprets a missing/empty TERM variable as the
special value \*(``unknown\*(''.
.IP
-SVr4 curses uses the
+SVr4 \fIcurses\fP uses the
special value \*(``dumb\*(''.
.IP
The difference between the two is that
-the former uses the \fBgn\fP (\fB\%generic_type\fR) terminfo capability,
+the former uses the \fBgn\fP (\fB\%generic_type\fR) \fIterminfo\fP capability,
while the latter does not.
A generic terminal is unsuitable for full-screen applications.
.bP
@@ -742,13 +743,13 @@ .SS Other portability issues
other than \fBOK\fP/\fBERR\fP from \fB\%tputs\fP.
That returns the length of the string, and does no error-checking.
.PP
-X/Open notes that after calling \fB\%mvcur\fP, the curses state may not match
the
+X/Open notes that after calling \fB\%mvcur\fP, the \fIcurses\fP state may not
match the
actual terminal state, and that an application should touch and refresh
-the window before resuming normal curses calls.
-Both \fBncurses\fP and System V Release 4 curses implement \fB\%mvcur\fP using
+the window before resuming normal \fIcurses\fP calls.
+Both \fIncurses\fP and System V Release 4 \fIcurses\fP implement \fB\%mvcur\fP
using
the SCREEN data allocated in either \fB\%initscr\fP or \fB\%newterm\fP.
-So though it is documented as a terminfo function,
-\fB\%mvcur\fP is really a curses function which is not well specified.
+So though it is documented as a \fIterminfo\fP function,
+\fB\%mvcur\fP is really a \fIcurses\fP function which is not well specified.
.PP
X/Open states that the old location must be given for \fB\%mvcur\fP.
This implementation allows the caller to use \-1's for the old ordinates.
diff --git a/man/curs_touch.3x b/man/curs_touch.3x
index 421454f0..96feff16 100644
--- a/man/curs_touch.3x
+++ b/man/curs_touch.3x
@@ -107,10 +107,10 @@ .SH RETURN VALUE
.RE
.SH PORTABILITY
These functions were introduced by SVr4.
-The Solaris curses header file,
+The Solaris \fIcurses\fP header file,
for instance, defines both an actual function and macro for each.
The macros give the same result as the actual functions.
-SVr4 curses does not check the window parameter \fIwin\fP to ensure
+SVr4 \fIcurses\fP does not check the window parameter \fIwin\fP to ensure
that it is not \fBNULL\fP;
otherwise this implementation behaves the same as SVr4.
.PP
diff --git a/man/curs_util.3x b/man/curs_util.3x
index 56562775..35916aad 100644
--- a/man/curs_util.3x
+++ b/man/curs_util.3x
@@ -160,10 +160,10 @@ .SS use_env
should be called before \fB\%initscr\fP or
\fB\%newterm\fP are called
(because those compute the screen size).
-It modifies the way \fBncurses\fP treats environment variables
+It modifies the way \fIncurses\fP treats environment variables
when determining the screen size.
.bP
-Normally \fBncurses\fP looks first at the terminal database for the screen
size.
+Normally \fIncurses\fP looks first at the terminal database for the screen
size.
.IP
If \fB\%use_env\fP was called with \fBFALSE\fP for parameter,
it stops here unless
@@ -174,28 +174,28 @@ .SS use_env
it overrides the values from the terminal database.
.bP
Finally (unless \fB\%use_env\fP was called with \fBFALSE\fP parameter),
-\fBncurses\fP examines the \fBLINES\fP or \fB\%COLUMNS\fP environment
variables,
+\fIncurses\fP examines the \fBLINES\fP or \fB\%COLUMNS\fP environment
variables,
using a value in those to override the results
from the operating system or terminal database.
.IP
-\fBNcurses\fP also updates the screen size in response to \fB\%SIGWINCH\fP,
+\fIncurses\fP also updates the screen size in response to \fB\%SIGWINCH\fP,
unless overridden by the \fBLINES\fP or \fB\%COLUMNS\fP environment variables,
.SS use_tioctl
The \fB\%use_tioctl\fP routine, if used,
should be called before \fB\%initscr\fP or \fB\%newterm\fP are called
(because those compute the screen size).
After \fB\%use_tioctl\fP is called with \fBTRUE\fP as an argument,
-\fBncurses\fP modifies the last step in its computation
+\fIncurses\fP modifies the last step in its computation
of screen size as follows:
.bP
checks if the \fBLINES\fP and \fB\%COLUMNS\fP environment variables
are set to a number greater than zero.
.bP
-for each, \fBncurses\fP updates the corresponding environment variable
+for each, \fIncurses\fP updates the corresponding environment variable
with the value that it has obtained via operating system call
or from the terminal database.
.bP
-\fBncurses\fP re-fetches the value of the environment variables so that
+\fIncurses\fP re-fetches the value of the environment variables so that
it is still the environment variables which set the screen size.
.PP
The \fB\%use_env\fP and \fB\%use_tioctl\fP routines combine as
@@ -209,18 +209,18 @@ .SS use_tioctl
\fBuse_env\fP/\fBuse_tioctl\fP/\fBSummary\fP
TRUE/FALSE/T{
This is the default behavior.
-\fBncurses\fP uses operating system calls
+\fIncurses\fP uses operating system calls
unless overridden by $LINES or $COLUMNS environment variables.
T}
TRUE/TRUE/T{
-\fBncurses\fP updates $LINES and $COLUMNS based on operating system calls.
+\fIncurses\fP updates $LINES and $COLUMNS based on operating system calls.
T}
FALSE/TRUE/T{
-\fBncurses\fP ignores $LINES and $COLUMNS,
+\fIncurses\fP ignores $LINES and $COLUMNS,
uses operating system calls to obtain size.
T}
FALSE/FALSE/T{
-\fBncurses\fP relies on the terminal database to determine size.
+\fIncurses\fP relies on the terminal database to determine size.
T}
.TE
.SS putwin/getwin
@@ -296,9 +296,9 @@ .SS keyname
The \fB\%use_extended_names\fP(3X) function controls whether this data is
loaded when the terminal description is read by the library.
.SS nofilter/use_tioctl
-The \fB\%nofilter\fP and \fB\%use_tioctl\fP routines are specific to
\fBncurses\fP.
+The \fB\%nofilter\fP and \fB\%use_tioctl\fP routines are specific to
\fIncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on \fBncurses\fP extensions
+It is recommended that any code depending on \fIncurses\fP extensions
be conditioned using \fB\%NCURSES_VERSION\fP.
.SS putwin/getwin file-format
The \fB\%putwin\fP and \fB\%getwin\fP functions have several issues with
@@ -313,13 +313,13 @@ .SS putwin/getwin file-format
the functions (along with \fB\%scr_init\fP, etc.) originated with
the University of California, Berkeley (in 1982)
and were later (in 1988) incorporated into SVr4.
-Oddly, there are no such functions in the 4.3BSD curses sources.
+Oddly, there are no such functions in the 4.3BSD \fIcurses\fP sources.
.bP
Most implementations simply dump the binary \fB\%WINDOW\fP structure to the
file.
-These include SVr4 curses, NetBSD and PDCurses,
-as well as older \fBncurses\fP versions.
+These include SVr4 \fIcurses\fP, NetBSD and PDCurses,
+as well as older \fIncurses\fP versions.
This implementation
-(as well as the X/Open variant of Solaris curses, dated 1995)
+(as well as the X/Open variant of Solaris \fIcurses\fP, dated 1995)
uses textual dumps.
.IP
The implementations which use binary dumps use block-I/O
@@ -347,7 +347,7 @@ .SS unctrl/wunctrl
analogous to \*(``^@\*('', \*(``^A\*('', C0 controls.
.IP
X/Open Curses does not document whether \fB\%unctrl\fP can be called before
-initializing curses.
+initializing \fIcurses\fP.
This implementation permits that,
and returns the \*(``~@\*('', etc., values in that case.
.bP
@@ -373,24 +373,24 @@ .SS unctrl/wunctrl
it determines whether to use the \*(``M\-\*('' prefix
for \*(``meta\*('' keys (codes in the range 128 to 255).
Both \fB\%use_legacy_coding\fP(3X) and \fBmeta\fP(3X) succeed only after
-curses is initialized.
+\fIcurses\fP is initialized.
X/Open Curses does not document the treatment of codes 128 to 159.
When treating them as \*(``meta\*('' keys
-(or if \fB\%keyname\fP is called before initializing curses),
+(or if \fB\%keyname\fP is called before initializing \fIcurses\fP),
this implementation returns strings \*(``M\-^@\*('', \*(``M\-^A\*('', etc.
.PP
X/Open Curses documents \fB\%unctrl\fP as declared in \fB<unctrl.h>\fP,
-which \fBncurses\fP does.
-However, \fBncurses\fP' \fB<curses.h>\fP includes \fB<unctrl.h>\fP,
-matching the behavior of SVr4 curses.
+which \fIncurses\fP does.
+However, \fIncurses\fP' \fB<curses.h>\fP includes \fB<unctrl.h>\fP,
+matching the behavior of SVr4 \fIcurses\fP.
Other implementations may not do that.
.SS use_env/use_tioctl
-If \fBncurses\fP is configured to provide the sp-functions extension,
+If \fIncurses\fP is configured to provide the sp-functions extension,
the state of \fB\%use_env\fP and \fB\%use_tioctl\fP may be updated before
creating each \fIscreen\fP rather than once only
(\fB\%curs_sp_funcs\fP(3X)).
This feature of \fB\%use_env\fP
-is not provided by other implementations of curses.
+is not provided by other implementations of \fIcurses\fP.
.SH SEE ALSO
\fB\%curses\fP(3X),
\fB\%curs_initscr\fP(3X),
diff --git a/man/define_key.3x b/man/define_key.3x
index 83145e96..b13a5fc7 100644
--- a/man/define_key.3x
+++ b/man/define_key.3x
@@ -39,9 +39,9 @@ .SH SYNOPSIS
.PP
\fBint define_key(const char *\fIdefinition\fB, int \fIkeycode\fB);\fR
.SH DESCRIPTION
-This is an extension to the curses library.
+This is an extension to the \fIcurses\fP library.
It permits an application to define keycodes with their corresponding control
-strings, so that the ncurses library will interpret them just as it would
+strings, so that the \fIncurses\fP library will interpret them just as it would
the predefined codes in the terminfo database.
.PP
If the given string is null, any existing definition for the keycode is
@@ -55,7 +55,7 @@ .SH RETURN VALUE
data to store the definition.
If no error is detected, \fBOK\fP is returned.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fIncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/key_defined.3x b/man/key_defined.3x
index 187bb4a5..8148a6b5 100644
--- a/man/key_defined.3x
+++ b/man/key_defined.3x
@@ -39,7 +39,7 @@ .SH SYNOPSIS
.PP
\fBint key_defined(const char *\fIdefinition\fB);\fR
.SH DESCRIPTION
-This is an extension to the curses library.
+This is an extension to the \fIcurses\fP library.
It permits an application to determine if a string is currently bound
to any keycode.
.SH RETURN VALUE
@@ -48,7 +48,7 @@ .SH RETURN VALUE
If the string conflicts with longer strings
which are bound to keys, \-1 is returned.
.SH PORTABILITY
-This routine is specific to ncurses.
+This routine is specific to \fIncurses\fP.
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/keybound.3x b/man/keybound.3x
index ad3267ff..32825c71 100644
--- a/man/keybound.3x
+++ b/man/keybound.3x
@@ -39,7 +39,7 @@ .SH SYNOPSIS
.PP
\fBchar * keybound(int \fIkeycode\fB, int \fIcount);\fR
.SH DESCRIPTION
-This is an extension to the curses library.
+This is an extension to the \fIcurses\fP library.
It permits an application to determine the string which is defined
in the terminfo for specific keycodes.
.SH RETURN VALUE
@@ -50,7 +50,7 @@ .SH RETURN VALUE
When successful,
the function returns a string which must be freed by the caller.
.SH PORTABILITY
-This routine is specific to ncurses.
+This routine is specific to \fIncurses\fP.
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/keyok.3x b/man/keyok.3x
index 04a49cf3..5b095f05 100644
--- a/man/keyok.3x
+++ b/man/keyok.3x
@@ -39,7 +39,7 @@ .SH SYNOPSIS
.PP
\fBint keyok(int \fIkeycode\fB, bool \fIenable\fB);\fR
.SH DESCRIPTION
-This is an extension to the curses library.
+This is an extension to the \fIcurses\fP library.
It permits an application to disable specific keycodes, rather than
use the \fB\%keypad\fP function to disable all keycodes.
Keys that have been disabled can be re-enabled.
@@ -50,7 +50,7 @@ .SH RETURN VALUE
and vice versa.
Otherwise, the function returns \fBOK\fP.
.SH PORTABILITY
-This routine is specific to ncurses.
+This routine is specific to \fIncurses\fP.
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/new_pair.3x b/man/new_pair.3x
index 4eedb49d..a7cda8cd 100644
--- a/man/new_pair.3x
+++ b/man/new_pair.3x
@@ -72,7 +72,7 @@ .SH SYNOPSIS
\fBint free_pair(int \fIpair\fB);\fR
.fi
.SH DESCRIPTION
-These functions are an extension to the curses library.
+These functions are an extension to the \fIcurses\fP library.
They permit an application to dynamically allocate a color pair using
the foreground/background colors rather than assign a fixed color pair number,
and return an unused pair to the pool.
@@ -86,7 +86,7 @@ .SH DESCRIPTION
of a given character cell without rewriting it.
That is, the foreground and background colors are applied as a pair.
.bP
-Color pairs are the curses library's way of managing a color palette
+Color pairs are the \fIcurses\fP library's way of managing a color palette
on a terminal.
If the library does not keep track of the \fIcombinations\fP of
colors which are displayed, it will be inefficient.
@@ -136,7 +136,7 @@ .SS alloc_pair
The size of the table is determined by the terminfo \fBpairs\fP capability.
The table is shared with \fBinit_pair\fP;
in fact \fBalloc_pair\fP calls \fBinit_pair\fP after
-updating the ncurses library's fast index to the colors versus color pairs.
+updating the \fIncurses\fP library's fast index to the colors versus color
pairs.
.SS find_pair
The \fBfind_pair\fP function accepts parameters for
foreground and background color, and
@@ -160,7 +160,7 @@ .SH RETURN VALUE
Likewise, \fBfree_pair\fP returns \fBOK\fP unless it encounters an
error updating the fast index or if no such color pair is in use.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fIncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/resizeterm.3x b/man/resizeterm.3x
index f59777c8..54ef5ed5 100644
--- a/man/resizeterm.3x
+++ b/man/resizeterm.3x
@@ -49,22 +49,22 @@ .SH SYNOPSIS
\fBint resizeterm(int \fIlines\fB, int \fIcolumns\fB);\fR
.fi
.SH DESCRIPTION
-This is an extension to the curses library.
-It provides callers with a hook into the \fBncurses\fP data to resize windows,
+This is an extension to the \fIcurses\fP library.
+It provides callers with a hook into the \fIncurses\fP data to resize windows,
primarily for use by programs running in an X Window terminal (e.g., xterm)
when the terminal's screen size is changed by the user:
.bP
-Curses windows cannot extend outside the screen.
-If the terminal is shrunk, curses windows must be shrunk to fit.
+\fIcurses\fP windows cannot extend outside the screen.
+If the terminal is shrunk, \fIcurses\fP windows must be shrunk to fit.
.bP
If the terminal is stretched,
rows and/or columns can be added to existing windows.
The added cells should match the current attributes of the windows.
.PP
If the calling program has not set up a handler for \fB\%SIGWINCH\fP
-when it initializes \fBncurses\fP
+when it initializes \fIncurses\fP
(e.g., using \fB\%initscr\fP(3X) or \fB\%newterm\fP(3X)),
-then \fBncurses\fP sets a handler for \fB\%SIGWINCH\fP which notifies
+then \fIncurses\fP sets a handler for \fB\%SIGWINCH\fP which notifies
the library when a window-size event has occurred.
The library checks for this notification
.bP
@@ -87,7 +87,7 @@ .SS resizeterm
The function \fB\%resizeterm\fP resizes the standard and current windows
(i.e., \fB\%stdscr\fP and \fB\%curscr\fP)
to the specified dimensions, and adjusts other bookkeeping data used by
-the \fB\%ncurses\fP library that record the window dimensions
+the \fIncurses\fP library that record the window dimensions
such as the \fB\%LINES\fP and \fB\%COLS\fP variables.
.SS resize_term
Most of the work for \fB\%resizeterm\fP is
@@ -129,7 +129,7 @@ .SH NOTES
context where \fB\%malloc\fP or \fB\%realloc\fP may have been interrupted,
since it uses those functions.
.PP
-If ncurses is configured to supply its own \fB\%SIGWINCH\fP handler,
+If \fIncurses\fP is configured to supply its own \fB\%SIGWINCH\fP handler,
.bP
on receipt of a \fB\%SIGWINCH\fP, the handler sets a flag
.bP
@@ -149,7 +149,7 @@ .SH NOTES
.IP
Calling \fB\%resizeterm\fP or \fB\%resize_term\fP
directly from a signal handler is unsafe.
-This indirect method is used to provide a safe way to resize the ncurses
+This indirect method is used to provide a safe way to resize the \fIncurses\fP
data structures.
.PP
If the environment variables \fB\%LINES\fP or \fB\%COLUMNS\fP are set,
@@ -158,20 +158,20 @@ .SH NOTES
Thus, even if a \fB\%SIGWINCH\fP is received,
no screen size change may be recorded.
.SH PORTABILITY
-It is possible to resize the screen with SVr4 curses,
+It is possible to resize the screen with SVr4 \fIcurses\fP,
by
.bP
-exiting curses with \fB\%endwin\fP(3X) and
+exiting \fIcurses\fP with \fB\%endwin\fP(3X) and
.bP
resuming using \fB\%refresh\fP(3X).
.PP
Doing that clears the screen and is visually distracting.
.PP
-This extension of ncurses was introduced in mid-1995.
-It was adopted in NetBSD curses (2001) and PDCurses (2003).
+This extension of \fIncurses\fP was introduced in mid-1995.
+It was adopted in NetBSD \fIcurses\fP (2001) and PDCurses (2003).
.SH SEE ALSO
\fB\%curs_getch\fP(3X),
\fB\%curs_variables\fP(3X),
\fB\%wresize\fP(3X)
.SH AUTHOR
-Thomas Dickey (from an equivalent function written in 1988 for BSD curses)
+Thomas Dickey (from an equivalent function written in 1988 for BSD
\fIcurses\fP)
--
2.30.2
signature.asc
Description: PGP signature
- [PATCH v2 06/18] Style {n,}curses, termcap, terminfo as elsewhere.,
G. Branden Robinson <=