[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v2 04/18] Protect literals from hyphenation.
|
From: |
G. Branden Robinson |
|
Subject: |
[PATCH v2 04/18] Protect literals from hyphenation. |
|
Date: |
Sat, 23 Sep 2023 06:56:48 -0500 |
Everything that is boldfaced is literal, so protect it from hyphenation.
A few very short words that *roff won't hyphenate are left as-is, such
as "tic", "TRUE", "FALSE", "ERR", "OK", "NULL", and "bool".
GNU troff (by default) won't hyphenate "color" or "mcprint", but will
"colors" and "errno".
Paragraph tags are not thus protected since they shouldn't need it;
their lines won't ordinarily break and so won't hyphenate. By contrast,
lists of man pages in "SEE ALSO" sections might, so they _do_ get
protection.
* man/curs_color.3x:
* man/curs_getyx.3x:
* man/curs_inopts.3x:
* man/curs_legacy.3x:
* man/curs_memleaks.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_trace.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 | 204 +++++++++++++++---------------
man/curs_getyx.3x | 46 +++----
man/curs_inopts.3x | 134 ++++++++++----------
man/curs_legacy.3x | 42 +++----
man/curs_memleaks.3x | 32 ++---
man/curs_mouse.3x | 86 ++++++-------
man/curs_opaque.3x | 42 +++----
man/curs_pad.3x | 96 +++++++-------
man/curs_print.3x | 12 +-
man/curs_slk.3x | 92 +++++++-------
man/curs_terminfo.3x | 294 +++++++++++++++++++++----------------------
man/curs_touch.3x | 28 ++---
man/curs_trace.3x | 60 ++++-----
man/curs_util.3x | 142 ++++++++++-----------
man/define_key.3x | 6 +-
man/key_defined.3x | 4 +-
man/keybound.3x | 6 +-
man/keyok.3x | 6 +-
man/new_pair.3x | 2 +-
man/resizeterm.3x | 88 ++++++-------
20 files changed, 711 insertions(+), 711 deletions(-)
diff --git a/man/curs_color.3x b/man/curs_color.3x
index 81a2ddea..7519ed59 100644
--- a/man/curs_color.3x
+++ b/man/curs_color.3x
@@ -84,48 +84,48 @@ .SH SYNOPSIS
.SH DESCRIPTION
.SS Overview
\fBcurses\fP supports color attributes on terminals with that capability.
-To use these routines \fBstart_color\fP must be called, usually right after
-\fBinitscr\fP.
+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).
A color-pair consists of a foreground color (for characters) and a background
color (for the blank field on which the characters are displayed).
-A programmer initializes a color-pair with the routine \fBinit_pair\fP.
-After it has been initialized, \fBCOLOR_PAIR\fP(\fIn\fP)
+A programmer initializes a color-pair with the routine \fB\%init_pair\fP.
+After it has been initialized, \fB\%COLOR_PAIR\fP(\fIn\fP)
can be used to convert the pair to a video attribute.
.PP
If a terminal is capable of redefining colors, the programmer can use the
-routine \fBinit_color\fP to change the definition of a color.
-The routines \fBhas_colors\fP and \fBcan_change_color\fP
+routine \fB\%init_color\fP to change the definition of a color.
+The routines \fB\%has_colors\fP and \fB\%can_change_color\fP
return \fBTRUE\fP or \fBFALSE\fP,
depending on whether the terminal has color capabilities and whether the
programmer can change the colors.
-The routine \fBcolor_content\fP allows a
+The routine \fB\%color_content\fP allows a
programmer to extract the amounts of red, green, and blue components in an
initialized color.
-The routine \fBpair_content\fP allows a programmer to find
+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
actual foreground and background colors shown on the screen:
.bP
-per-character video attributes (e.g., via \fBwaddch\fP),
+per-character video attributes (e.g., via \fB\%waddch\fP),
.bP
-the window attribute (e.g., by \fBwattrset\fP), and
+the window attribute (e.g., by \fB\%wattrset\fP), and
.bP
-the background character (e.g., \fBwbkgdset\fP).
+the background character (e.g., \fB\%wbkgdset\fP).
.PP
Per-character and window attributes are usually set by a parameter containing
video attributes including a color pair value.
-Some functions such as \fBwattr_set\fP use a separate parameter which
+Some functions such as \fB\%wattr_set\fP use a separate parameter which
is the color pair number.
.PP
The background character is a special case: it includes a character value,
-just as if it were passed to \fBwaddch\fP.
+just as if it were passed to \fB\%waddch\fP.
.PP
The \fBcurses\fP library does the actual work of combining these color
-pairs in an internal function called from \fBwaddch\fP:
+pairs in an internal function called from \fB\%waddch\fP:
.bP
-If the parameter passed to \fBwaddch\fP is \fIblank\fP,
+If the parameter passed to \fB\%waddch\fP is \fIblank\fP,
and it uses the special color pair 0,
.RS
.bP
@@ -137,21 +137,21 @@ .SS Color Rendering
Otherwise, \fBcurses\fP uses the background character.
.RE
.bP
-If the parameter passed to \fBwaddch\fP is \fInot blank\fP,
+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,
if it is nonzero.
Otherwise, it tries the window attribute next, and finally the
background character.
.PP
-Some \fBcurses\fP functions such as \fBwprintw\fP call \fBwaddch\fP.
+Some \fBcurses\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.
+In \fB\%<curses.h>\fP the following macros are defined.
These are the standard colors (ISO-6429).
-\fBcurses\fP also assumes that \fBCOLOR_BLACK\fP is the default
+\fBcurses\fP also assumes that \fB\%COLOR_BLACK\fP is the default
background color for all terminals.
.PP
.nf
@@ -169,38 +169,38 @@ .SH CONSTANTS
There are no standard names for those additional colors.
.SH VARIABLES
.SS COLORS
-is initialized by \fBstart_color\fP to the maximum number of colors
+is initialized by \fB\%start_color\fP to the maximum number of colors
the terminal can support.
.SS COLOR_PAIRS
-is initialized by \fBstart_color\fP to the maximum number of color pairs
+is initialized by \fB\%start_color\fP to the maximum number of color pairs
the terminal can support.
.SH FUNCTIONS
.SS start_color
-The \fBstart_color\fP routine requires no arguments.
+The \fB\%start_color\fP routine requires no arguments.
It must be called if the programmer wants to use colors, and before any other
color manipulation routine is called.
-It is good practice to call this routine right after \fBinitscr\fP.
-\fBstart_color\fP does this:
+It is good practice to call this routine right after \fB\%initscr\fP.
+\fB\%start_color\fP does this:
.bP
-It initializes two global variables, \fBCOLORS\fP and
-\fBCOLOR_PAIRS\fP (respectively defining the maximum number of colors
+It initializes two global variables, \fB\%COLORS\fP and
+\fB\%COLOR_PAIRS\fP (respectively defining the maximum number of colors
and color-pairs the terminal can support).
.bP
-It initializes the special color pair \fB0\fP to the default foreground
+It initializes the special color pair \fB\%0\fP to the default foreground
and background colors.
No other color pairs are initialized.
.bP
It restores the colors on the terminal to the values
they had when the terminal was just turned on.
.bP
-If the terminal supports the \fBinitc\fP (\fBinitialize_color\fP) capability,
-\fBstart_color\fP
+If the terminal supports the \fBinitc\fP (\fB\%initialize_color\fP) capability,
+\fB\%start_color\fP
initializes its internal table representing the
red, green, and blue components of the color palette.
.IP
The components depend on whether the terminal uses
CGA (aka \*(``ANSI\*('') or
-HLS (i.e., the \fBhls\fP (\fBhue_lightness_saturation\fP) capability is set).
+HLS (i.e., the \fBhls\fP (\fB\%hue_lightness_saturation\fP) capability is set).
The table is initialized first for eight basic colors
(black, red, green, yellow, blue, magenta, cyan, and white),
using weights that depend upon the CGA/HLS choice.
@@ -215,28 +215,28 @@ .SS start_color
SVr4 uses a similar scheme, but uses \fB1000\fP
for the components of the initial eight colors.
.IP
-\fBstart_color\fP does not attempt to set the terminal's color palette
+\fB\%start_color\fP does not attempt to set the terminal's color palette
to match its built-in table.
-An application may use \fBinit_color\fP to alter the internal table
+An application may use \fB\%init_color\fP to alter the internal table
along with the terminal's color.
.PP
These limits apply to color values and color pairs.
Values outside these limits are not legal, and may result in a runtime error:
.bP
-\fBCOLORS\fP corresponds to the terminal database's \fBmax_colors\fP
capability,
-(see \fBterminfo\fP(\*n)).
+\fBCOLORS\fP corresponds to the terminal database's \fB\%max_colors\fP
capability,
+(see \fB\%terminfo\fP(\*n)).
.bP
-color values are expected to be in the range \fB0\fP to \fBCOLORS\-1\fP,
-inclusive (including \fB0\fP and \fBCOLORS\-1\fP).
+color values are expected to be in the range \fB0\fP to \fB\%COLORS\-1\fP,
+inclusive (including \fB0\fP and \fB\%COLORS\-1\fP).
.bP
a special color value \fB\-1\fP is used in certain extended functions
-to denote the \fIdefault color\fP (see \fBuse_default_colors\fP(3X)).
+to denote the \fIdefault color\fP (see \fB\%use_default_colors\fP(3X)).
.bP
-\fBCOLOR_PAIRS\fP corresponds to
-the terminal database's \fBmax_pairs\fP capability,
-(see \fBterminfo\fP(\*n)).
+\fB\%COLOR_PAIRS\fP corresponds to
+the terminal database's \fB\%max_pairs\fP capability,
+(see \fB\%terminfo\fP(\*n)).
.bP
-legal color pair values are in the range \fB1\fP to \fBCOLOR_PAIRS\-1\fP,
+legal color pair values are in the range \fB1\fP to \fB\%COLOR_PAIRS\-1\fP,
inclusive.
.bP
color pair \fB0\fP is special; it denotes \*(``no color\*(''.
@@ -245,27 +245,27 @@ .SS start_color
but is actually whatever the terminal implements before color is initialized.
It cannot be modified by the application.
.SS has_colors
-The \fBhas_colors\fP routine requires no arguments.
+The \fB\%has_colors\fP routine requires no arguments.
It returns \fBTRUE\fP if
the terminal can manipulate colors; otherwise, it returns \fBFALSE\fP.
This routine facilitates writing terminal-independent programs.
For example, a programmer can use it to decide
whether to use color or some other video attribute.
.SS can_change_color
-The \fBcan_change_color\fP routine requires no arguments.
+The \fB\%can_change_color\fP routine requires no arguments.
It returns \fBTRUE\fP if the terminal supports colors
and can change their definitions;
other, it returns \fBFALSE\fP.
This routine facilitates writing terminal-independent programs.
.SS init_pair
-The \fBinit_pair\fP routine changes the definition of a color-pair.
+The \fB\%init_pair\fP routine changes the definition of a color-pair.
It takes three arguments:
the number of the color-pair to be changed, the foreground
color number, and the background color number.
For portable applications:
.bP
The first argument must be a legal color pair value.
-If default colors are used (see \fBuse_default_colors\fP(3X))
+If default colors are used (see \fB\%use_default_colors\fP(3X))
the upper limit is adjusted to allow for extra pairs which use
a default color in foreground and/or background.
.bP
@@ -276,42 +276,42 @@ .SS init_pair
are changed to the new definition.
.PP
As an extension, ncurses allows you to set color pair \fB0\fP via
-the \fBassume_default_colors\fP(3X) routine, or to specify the use of
+the \fB\%assume_default_colors\fP(3X) routine, or to specify the use of
default colors (color number \fB\-1\fP) if you first invoke the
-\fBuse_default_colors\fP(3X) routine.
+\fB\%use_default_colors\fP(3X) routine.
.SS init_extended_pair
-Because \fBinit_pair\fP uses signed \fBshort\fPs for its parameters,
+Because \fB\%init_pair\fP uses signed \fBshort\fPs for its parameters,
that limits color-pairs and color-values
to 32767 on modern hardware.
-The extension \fBinit_extended_pair\fP uses \fBint\fPs
+The extension \fB\%init_extended_pair\fP uses \fBint\fPs
for the color-pair and color-value,
allowing a larger number of colors to be supported.
.SS init_color
-The \fBinit_color\fP routine changes the definition of a color.
+The \fB\%init_color\fP routine changes the definition of a color.
It takes four arguments:
the number of the color to be changed followed by three RGB values
(for the amounts of red, green, and blue components).
.bP
The first argument must be a legal color value;
default colors are not allowed here.
-(See the section \fBColors\fP for the default color index.)
+(See the section \fB\%Colors\fP for the default color index.)
.bP
Each of the last three arguments
must be a value in the range \fB0\fP through \fB1000\fP.
.PP
-When \fBinit_color\fP is used, all
+When \fB\%init_color\fP is used, all
occurrences of that color on the screen immediately change to the new
definition.
.SS init_extended_color
-Because \fBinit_color\fP uses signed \fBshort\fPs for its parameters,
+Because \fB\%init_color\fP uses signed \fBshort\fPs for its parameters,
that limits color-values and their red, green, and blue components
to 32767 on modern hardware.
-The extension \fBinit_extended_color\fP uses \fBint\fPs
+The extension \fB\%init_extended_color\fP uses \fBint\fPs
for the color value and
for setting the red, green, and blue components,
allowing a larger number of colors to be supported.
.SS color_content
-The \fBcolor_content\fP routine gives programmers a way to find the intensity
+The \fB\%color_content\fP routine gives programmers a way to find the intensity
of the red, green, and blue (RGB) components in a color.
It requires four arguments: the color number, and three addresses
of \fBshort\fRs for storing
@@ -319,57 +319,57 @@ .SS color_content
given color.
.bP
The first argument must be a legal color value, i.e.,
-\fB0\fP through \fBCOLORS\-1\fP, inclusive.
+\fB0\fP through \fB\%COLORS\-1\fP, inclusive.
.bP
The values that are stored at the addresses pointed to by the
last three arguments are in the range
\fB0\fP (no component) through \fB1000\fP
(maximum amount of component), inclusive.
.SS extended_color_content
-Because \fBcolor_content\fP uses signed \fBshort\fPs for its parameters,
+Because \fB\%color_content\fP uses signed \fBshort\fPs for its parameters,
that limits color-values and their red, green, and blue components
to 32767 on modern hardware.
-The extension \fBextended_color_content\fP uses \fBint\fPs
+The extension \fB\%extended_color_content\fP uses \fBint\fPs
for the color value and
for returning the red, green, and blue components,
allowing a larger number of colors to be supported.
.SS pair_content
-The \fBpair_content\fP routine allows programmers to find out what colors a
+The \fB\%pair_content\fP routine allows programmers to find out what colors a
given color-pair consists of.
It requires three arguments: the color-pair
number, and two addresses of \fBshort\fRs for storing the foreground and the
background color numbers.
.bP
The first argument must be a legal color value,
-i.e., in the range \fB1\fP through \fBCOLOR_PAIRS\-1\fP, inclusive.
+i.e., in the range \fB1\fP through \fB\%COLOR_PAIRS\-1\fP, inclusive.
.bP
The values that are stored at the addresses pointed
to by the second and third arguments are in the
-range \fB0\fP through \fBCOLORS\fP, inclusive.
+range \fB0\fP through \fB\%COLORS\fP, inclusive.
.SS extended_pair_content
-Because \fBpair_content\fP uses signed \fBshort\fPs for its parameters,
+Because \fB\%pair_content\fP uses signed \fBshort\fPs for its parameters,
that limits color-pair and color-values to 32767 on modern hardware.
-The extension \fBextended_pair_content\fP uses \fBint\fPs
+The extension \fB\%extended_pair_content\fP uses \fBint\fPs
for the color pair and
for returning the foreground and background colors,
allowing a larger number of colors to be supported.
.SS reset_color_pairs
-The extension \fBreset_color_pairs\fP tells ncurses to discard all
-of the color-pair information which was set with \fBinit_pair\fP.
+The extension \fB\%reset_color_pairs\fP tells ncurses to discard all
+of the color-pair information which was set with \fB\%init_pair\fP.
It also touches the current- and standard-screens, allowing an application to
switch color palettes rapidly.
.SS PAIR_NUMBER
-\fBPAIR_NUMBER(\fIattrs\fR) extracts the color
+\fB\%PAIR_NUMBER(\fIattrs\fR) extracts the color
value from its \fIattrs\fP parameter and returns it as a color pair number.
.SS COLOR_PAIR
-Its inverse \fBCOLOR_PAIR(\fIn\fB)\fR converts a color pair number
+Its inverse \fB\%COLOR_PAIR(\fIn\fB)\fR converts a color pair number
to an attribute.
Attributes can hold color pairs in the range 0 to 255.
If you need a color pair larger than that, you must use functions
-such as \fBattr_set\fP (which pass the color pair as a separate parameter)
-rather than the legacy functions such as \fBattrset\fP.
+such as \fB\%attr_set\fP (which pass the color pair as a separate parameter)
+rather than the legacy functions such as \fB\%attrset\fP.
.SH RETURN VALUE
-The routines \fBcan_change_color\fP and \fBhas_colors\fP return \fBTRUE\fP
+The routines \fB\%can_change_color\fP and \fB\%has_colors\fP return \fBTRUE\fP
or \fBFALSE\fP.
.PP
All other routines return the integer \fBERR\fP upon failure and an \fBOK\fP
@@ -380,24 +380,24 @@ .SH RETURN VALUE
SVr4 does document some error conditions which apply in general:
.bP
This implementation will return \fBERR\fP on attempts to
-use color values outside the range \fB0\fP to \fBCOLORS\fP\-1
+use color values outside the range \fB0\fP to \fB\%COLORS\fP\-1
(except for the default colors extension),
-or use color pairs outside the range \fB0\fP to \fBCOLOR_PAIRS\-1\fP.
+or use color pairs outside the range \fB0\fP to \fB\%COLOR_PAIRS\-1\fP.
.IP
-Color values used in \fBinit_color\fP must be
+Color values used in \fB\%init_color\fP must be
in the range \fB0\fP to \fB1000\fP.
.IP
An error is returned from all functions
if the terminal has not been initialized.
.IP
-An error is returned from secondary functions such as \fBinit_pair\fP
-if \fBstart_color\fP was not called.
+An error is returned from secondary functions such as \fB\%init_pair\fP
+if \fB\%start_color\fP was not called.
.bP
SVr4 does much the same, except that
-it returns \fBERR\fP from \fBpair_content\fP if the pair was not initialized
-using \fBinit_pairs\fP
+it returns \fBERR\fP from \fB\%pair_content\fP if the pair was not initialized
+using \fB\%init_pairs\fP
and
-it returns \fBERR\fP from \fBcolor_content\fP
+it returns \fBERR\fP from \fB\%color_content\fP
if the terminal does not support changing colors.
.IP
This implementation does not return \fBERR\fP for either case.
@@ -407,7 +407,7 @@ .SH RETURN VALUE
.TP 5
\fBinit_color\fP
returns an error if the terminal does not support
-this feature, e.g., if the \fBinitialize_color\fP capability is absent
+this feature, e.g., if the \fB\%initialize_color\fP capability is absent
from the terminal description.
.TP 5
\fBstart_color\fP
@@ -416,8 +416,8 @@ .SH RETURN VALUE
.SH NOTES
In the \fBncurses\fP implementation, there is a separate color activation flag,
color palette, color pairs table,
-and associated \fBCOLORS\fP and \fBCOLOR_PAIRS\fP counts
-for each screen; the \fBstart_color\fP function only affects the current
+and associated \fB\%COLORS\fP and \fB\%COLOR_PAIRS\fP counts
+for each screen; the \fB\%start_color\fP function only affects the current
screen.
The SVr4/XSI interface is not really designed with this in mind, and
historical implementations may use a single shared color palette.
@@ -426,7 +426,7 @@ .SH NOTES
character cells that a character write operation explicitly touches.
To change
the background color used when parts of a window are blanked by erasing or
-scrolling operations, see \fBcurs_bkgd\fP(3X).
+scrolling operations, see \fB\%curs_bkgd\fP(3X).
.PP
Several caveats apply on older x86 machines
(e.g., i386, i486) with VGA-compatible graphics:
@@ -447,13 +447,13 @@ .SH HISTORY
SVr4 made internal changes,
e.g., moving the storage for the color state
from \fBSP\fP (the \fBSCREEN\fP structure)
-to \fBcur_term\fP (the \fBTERMINAL\fP structure),
+to \fB\%cur_term\fP (the \fB\%TERMINAL\fP structure),
but provided the same set of library functions.
.PP
SVr4 curses limits the number of color pairs to 64,
reserving color pair zero (0) as the terminal's initial uncolored state.
This limit arises because the color pair information is a bitfield
-in the \fBchtype\fP data type (denoted by \fBA_COLOR\fP).
+in the \fB\%chtype\fP data type (denoted by \fB\%A_COLOR\fP).
.PP
Other implementations of curses had different limits:
.bP
@@ -461,24 +461,24 @@ .SH HISTORY
.bP
PDCurses (1992-present) inherited the 8-color limitation from PCCurses,
but changed this to 256 in version 2.5 (2001),
-along with changing \fBchtype\fP from 16-bits to 32-bits.
+along with changing \fB\%chtype\fP from 16-bits to 32-bits.
.bP
X/Open Curses (1992-present)
-added a new structure \fBcchar_t\fP to store the character,
+added a new structure \fB\%cchar_t\fP to store the character,
attributes and color-pair values, allowing increased range of color-pairs.
Both color-pairs and color-values used a signed \fBshort\fP,
limiting values to 15 bits.
.bP
-ncurses (1992-present) uses eight bits for \fBA_COLOR\fP in \fBchtype\fP
values.
+ncurses (1992-present) uses eight bits for \fB\%A_COLOR\fP in \fB\%chtype\fP
values.
.IP
Version 5.3 provided a wide-character interface (2002),
but left color-pairs as part of the attributes-field.
.IP
Since version 6 (2015),
-ncurses uses a separate \fBint\fP for color-pairs in the \fBcchar_t\fP values.
+ncurses uses a separate \fBint\fP for color-pairs in the \fB\%cchar_t\fP
values.
When those color-pair values fit in 8 bits,
ncurses allows color-pairs to be manipulated
-via the functions using \fBchtype\fP values.
+via the functions using \fB\%chtype\fP values.
.bP
NetBSD curses used 6 bits from
2000 (when colors were first supported) until 2004.
@@ -486,7 +486,7 @@ .SH HISTORY
As of 2021, that size is unchanged.
Like ncurses before version 6,
the NetBSD color-pair information is stored in
-the attributes field of \fBcchar_t\fP, limiting the number of color-pairs
+the attributes field of \fB\%cchar_t\fP, limiting the number of color-pairs
by the size of the bitfield.
.SH PORTABILITY
.SS Extensions
@@ -495,19 +495,19 @@ .SS Extensions
or any other previous version of curses.
.SS Standards
This implementation satisfies XSI Curses's minimum maximums
-for \fBCOLORS\fP and \fBCOLOR_PAIRS\fP.
+for \fB\%COLORS\fP and \fB\%COLOR_PAIRS\fP.
.PP
-The \fBinit_pair\fP routine accepts negative values of foreground
-and background color to support the \fBuse_default_colors\fP(3X) extension,
+The \fB\%init_pair\fP routine accepts negative values of foreground
+and background color to support the \fB\%use_default_colors\fP(3X) extension,
but only if that routine has been first invoked.
.PP
-The assumption that \fBCOLOR_BLACK\fP is the default
+The assumption that \fB\%COLOR_BLACK\fP is the default
background color for all terminals can be modified using the
-\fBassume_default_colors\fP(3X) extension.
+\fB\%assume_default_colors\fP(3X) extension.
.PP
This implementation checks the pointers,
e.g., for the values returned by
-\fBcolor_content\fP and \fBpair_content\fP,
+\fB\%color_content\fP and \fB\%pair_content\fP,
and will treat those as optional parameters when null.
.PP
X/Open Curses does not specify a limit for the number of colors and
@@ -519,10 +519,10 @@ .SS Standards
which use \fBshort\fP parameters,
allowing applications to use larger color- and pair-numbers.
.PP
-The \fBreset_color_pairs\fP function is an extension of ncurses.
+The \fB\%reset_color_pairs\fP function is an extension of ncurses.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_initscr\fP(3X),
-\fBcurs_attr\fP(3X),
-\fBcurs_variables\fP(3X),
-\fBdefault_colors\fP(3X)
+\fB\%curses\fP(3X),
+\fB\%curs_initscr\fP(3X),
+\fB\%curs_attr\fP(3X),
+\fB\%curs_variables\fP(3X),
+\fB\%default_colors\fP(3X)
diff --git a/man/curs_getyx.3x b/man/curs_getyx.3x
index 11501d2d..77020943 100644
--- a/man/curs_getyx.3x
+++ b/man/curs_getyx.3x
@@ -45,15 +45,15 @@ .SH SYNOPSIS
\fBvoid getmaxyx(WINDOW *\fIwin\fB, int \fIy\fB, int \fIx\fB);\fR
.fi
.SH DESCRIPTION
-The \fBgetyx\fP macro places the current cursor position of the given window in
+The \fB\%getyx\fP macro places the current cursor position of the given window
in
the two integer variables \fIy\fP and \fIx\fP.
.PP
-If \fIwin\fP is a subwindow, the \fBgetparyx\fP macro places the beginning
+If \fIwin\fP is a subwindow, the \fB\%getparyx\fP macro places the beginning
coordinates of the subwindow relative to the parent window into two integer
variables \fIy\fP and \fIx\fP.
Otherwise, \fB\-1\fP is placed into \fIy\fP and \fIx\fP.
.PP
-Like \fBgetyx\fP, the \fBgetbegyx\fP and \fBgetmaxyx\fP macros store
+Like \fB\%getyx\fP, the \fB\%getbegyx\fP and \fB\%getmaxyx\fP macros store
the current beginning coordinates and size of the specified window.
.SH RETURN VALUE
The return values of these macros are undefined (i.e.,
@@ -63,38 +63,38 @@ .SH NOTES
A "\fB&\fP" is not necessary before the variables \fIy\fP and \fIx\fP.
.SH PORTABILITY
The
-\fBgetyx\fP,
-\fBgetparyx\fP,
-\fBgetbegyx\fP and
-\fBgetmaxyx\fP
+\fB\%getyx\fP,
+\fB\%getparyx\fP,
+\fB\%getbegyx\fP and
+\fB\%getmaxyx\fP
macros are described in the XSI Curses standard, Issue 4.
.PP
This implementation also provides functions
-\fBgetbegx\fP,
-\fBgetbegy\fP,
-\fBgetcurx\fP,
-\fBgetcury\fP,
-\fBgetmaxx\fP,
-\fBgetmaxy\fP,
-\fBgetparx\fP and
-\fBgetpary\fP
+\fB\%getbegx\fP,
+\fB\%getbegy\fP,
+\fB\%getcurx\fP,
+\fB\%getcury\fP,
+\fB\%getmaxx\fP,
+\fB\%getmaxy\fP,
+\fB\%getparx\fP and
+\fB\%getpary\fP
for compatibility with older versions of curses.
.PP
Although X/Open Curses does not address this,
-many implementations provide members of the \fBWINDOW\fP structure
+many implementations provide members of the \fB\%WINDOW\fP structure
containing values corresponding to these macros.
-For best portability, do not rely on using the data in \fBWINDOW\fP,
-since some implementations make \fBWINDOW\fP opaque (do not allow
+For best portability, do not rely on using the data in \fB\%WINDOW\fP,
+since some implementations make \fB\%WINDOW\fP opaque (do not allow
direct use of its members).
.PP
Besides the problem of opaque structures,
the data stored in like-named members may not have like-values in
different implementations.
-For example, the \fBWINDOW._maxx\fP and \fBWINDOW._maxy\fP values in
\fIncurses\fP
+For example, the \fB\%WINDOW._maxx\fP and \fB\%WINDOW._maxy\fP values in
ncurses
have (at least since release 1.8.1) differed by one from some
other implementations.
-The difference is hidden by means of the macro \fBgetmaxyx\fP.
+The difference is hidden by means of the macro \fB\%getmaxyx\fP.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_legacy\fP(3X),
-\fBcurs_opaque\fP(3X)
+\fB\%curses\fP(3X),
+\fB\%curs_legacy\fP(3X),
+\fB\%curs_opaque\fP(3X)
diff --git a/man/curs_inopts.3x b/man/curs_inopts.3x
index 6e8b7392..15646db3 100644
--- a/man/curs_inopts.3x
+++ b/man/curs_inopts.3x
@@ -109,48 +109,48 @@ .SH DESCRIPTION
.SS cbreak/nocbreak
Normally, the tty driver buffers typed characters until a newline or carriage
return is typed.
-The \fBcbreak\fP routine disables line buffering and
+The \fB\%cbreak\fP routine disables line buffering and
erase/kill character-processing (interrupt and flow control characters are
unaffected), making characters typed by the user immediately available to the
program.
-The \fBnocbreak\fP routine returns the terminal to normal (cooked)
+The \fB\%nocbreak\fP routine returns the terminal to normal (cooked)
mode.
.PP
-Initially the terminal may or may not be in \fBcbreak\fP mode, as the mode is
-inherited; therefore, a program should call \fBcbreak\fP or \fBnocbreak\fP
+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 \fBcbreak\fP
+Most interactive programs using \fBcurses\fP set the \fB\%cbreak\fP
mode.
-Note that \fBcbreak\fP overrides \fBraw\fP.
-[See \fBcurs_getch\fP(3X) for a
-discussion of how these routines interact with \fBecho\fP and \fBnoecho\fP.]
+Note that \fB\%cbreak\fP overrides \fBraw\fP.
+[See \fB\%curs_getch\fP(3X) for a
+discussion of how these routines interact with \fBecho\fP and \fB\%noecho\fP.]
.\"
.SS echo/noecho
-The \fBecho\fP and \fBnoecho\fP routines control whether characters typed by
-the user are echoed by \fBgetch\fP(3X) as they are typed.
+The \fBecho\fP and \fB\%noecho\fP routines control whether characters typed by
+the user are echoed by \fB\%getch\fP(3X) as they are typed.
Echoing by the tty
-driver is always disabled, but initially \fBgetch\fP is in echo mode, so
+driver is always disabled, but initially \fB\%getch\fP is in echo mode, so
characters typed are echoed.
Authors of most interactive programs prefer to do
their own echoing in a controlled area of the screen, or not to echo at all, so
-they disable echoing by calling \fBnoecho\fP.
-[See \fBcurs_getch\fP(3X) for a
-discussion of how these routines interact with \fBcbreak\fP and
-\fBnocbreak\fP.]
+they disable echoing by calling \fB\%noecho\fP.
+[See \fB\%curs_getch\fP(3X) for a
+discussion of how these routines interact with \fB\%cbreak\fP and
+\fB\%nocbreak\fP.]
.\"
.SS halfdelay
-The \fBhalfdelay\fP routine is used for half-delay mode, which is similar to
-\fBcbreak\fP mode in that characters typed by the user are immediately
+The \fB\%halfdelay\fP routine is used for half-delay mode, which is similar to
+\fB\%cbreak\fP mode in that characters typed by the user are immediately
available to the program.
However, after blocking for \fItenths\fP tenths of
seconds, \fBERR\fP is returned if nothing has been typed.
The value of \fItenths\fP
must be a number between 1 and 255.
-Use \fBnocbreak\fP to leave half-delay
+Use \fB\%nocbreak\fP to leave half-delay
mode.
.\"
.SS intrflush
-If the \fBintrflush\fP option is enabled (\fIbf\fP is \fBTRUE\fP), and an
+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
@@ -161,24 +161,24 @@ .SS intrflush
The window argument is ignored.
.\"
.SS keypad
-The \fBkeypad\fP option enables the keypad of the user's terminal.
+The \fB\%keypad\fP option enables the keypad of the user's terminal.
If
enabled (\fIbf\fP is \fBTRUE\fP), the user can press a function key
-(such as an arrow key) and \fBwgetch\fP(3X) returns a single value
-representing the function key, as in \fBKEY_LEFT\fP.
+(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
specially and the program has to interpret the escape sequences
itself.
If the keypad in the terminal can be turned on (made to
transmit) and off (made to work locally), turning on this option
-causes the terminal keypad to be turned on when \fBwgetch\fP(3X) is
+causes the terminal keypad to be turned on when \fB\%wgetch\fP(3X) is
called.
The default value for keypad is \fBFALSE\fP.
.\"
.SS meta
Initially, whether the terminal returns 7 or 8 significant bits on
-input depends on the control mode of the tty driver [see \fBtermios\fP(3)].
+input depends on the control mode of the tty driver [see \fB\%termios\fP(3)].
To force 8 bits to be returned, invoke \fBmeta\fP(\fIwin\fP,
\fBTRUE\fP); this is equivalent, under POSIX, to setting the CS8 flag
on the terminal.
@@ -198,23 +198,23 @@ .SS nl/nonl
device translates the return key into newline on input.
.\"
.SS nodelay
-The \fBnodelay\fP option causes \fBgetch\fP to be a non-blocking call.
-If no input is ready, \fBgetch\fP returns \fBERR\fP.
+The \fB\%nodelay\fP option causes \fB\%getch\fP to be a non-blocking call.
+If no input is ready, \fB\%getch\fP returns \fBERR\fP.
If disabled
-(\fIbf\fP is \fBFALSE\fP), \fBgetch\fP waits until a key is pressed.
+(\fIbf\fP is \fBFALSE\fP), \fB\%getch\fP waits until a key is pressed.
.SS notimeout
-When interpreting an escape sequence, \fBwgetch\fP(3X) sets a timer
+When interpreting an escape sequence, \fB\%wgetch\fP(3X) sets a timer
while waiting for the next character.
-If \fBnotimeout(\fIwin\fR,
-\fBTRUE\fP) is called, then \fBwgetch\fP does not set a timer.
+If \fB\%notimeout(\fIwin\fR,
+\fBTRUE\fP) is called, then \fB\%wgetch\fP does not set a timer.
The
purpose of the timeout is to differentiate between sequences received
from a function key and those typed by a user.
.\"
.SS raw/noraw
-The \fBraw\fP and \fBnoraw\fP routines place the terminal into or out of raw
+The \fBraw\fP and \fB\%noraw\fP routines place the terminal into or out of raw
mode.
-Raw mode is similar to \fBcbreak\fP mode, in that characters typed are
+Raw mode is similar to \fB\%cbreak\fP mode, in that characters typed are
immediately passed through to the user program.
The differences are that in
raw mode, the interrupt, quit, suspend, and flow control characters are all
@@ -224,18 +224,18 @@ .SS raw/noraw
\fBcurses\fP.
.\"
.SS qiflush/noqiflush
-When the \fBnoqiflush\fP routine is used, normal flush of input and
+When the \fB\%noqiflush\fP routine is used, normal flush of input and
output queues associated with the \fBINTR\fP, \fBQUIT\fP and
-\fBSUSP\fP characters will not be done [see \fBtermios\fP(3)].
+\fBSUSP\fP characters will not be done [see \fB\%termios\fP(3)].
When
-\fBqiflush\fP is called, the queues will be flushed when these control
+\fB\%qiflush\fP is called, the queues will be flushed when these control
characters are read.
-You may want to call \fBnoqiflush\fP in a signal
+You may want to call \fB\%noqiflush\fP in a signal
handler if you want output to continue as though the interrupt
had not occurred, after the handler exits.
.\"
.SS timeout/wtimeout
-The \fBtimeout\fP and \fBwtimeout\fP routines set blocking or
+The \fB\%timeout\fP and \fB\%wtimeout\fP routines set blocking or
non-blocking read for a given window.
If \fIdelay\fP is negative,
blocking read is used (i.e., waits indefinitely for
@@ -245,7 +245,7 @@ .SS timeout/wtimeout
If
\fIdelay\fP is positive, then read blocks for \fIdelay\fP
milliseconds, and returns \fBERR\fP if there is still no input.
-Hence, these routines provide the same functionality as \fBnodelay\fP,
+Hence, these routines provide the same functionality as \fB\%nodelay\fP,
plus the additional capability of being able to block for only
\fIdelay\fP milliseconds (where \fIdelay\fP is positive).
.\"
@@ -254,12 +254,12 @@ .SS typeahead
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
-\fBrefresh\fP(3X) or \fBdoupdate\fP is called again.
+\fB\%refresh\fP(3X) or \fB\%doupdate\fP is called again.
This allows faster response to commands typed in advance.
Normally, the input FILE
-pointer passed to \fBnewterm\fP, or \fBstdin\fP in the case that
-\fBinitscr\fP was used, will be used to do this typeahead checking.
-The \fBtypeahead\fP routine specifies that the file descriptor
+pointer passed to \fB\%newterm\fP, or \fBstdin\fP in the case that
+\fB\%initscr\fP was used, will be used to do this typeahead checking.
+The \fB\%typeahead\fP routine specifies that the file descriptor
\fIfd\fP is to be used to check for typeahead instead.
If \fIfd\fP is
\-1, then no typeahead checking is done.
@@ -309,7 +309,7 @@ .SH EXTENSIONS
These routines are specific to ncurses.
They were not supported on Version 7, BSD or System V implementations.
It is recommended that any code depending on ncurses extensions
-be conditioned using \fBNCURSES_VERSION\fP.
+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.
@@ -320,7 +320,7 @@ .SH PORTABILITY
BSD curses 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 \fBnoecho\fP explicitly
+For best portability, set \fBecho \fPor \fB\%noecho\fP explicitly
just after initialization, even if your program remains in cooked mode.
.PP
The XSI Curses standard is ambiguous on the question of whether \fBraw\fP
@@ -331,7 +331,7 @@ .SH PORTABILITY
raw input wants a clean (ideally 8-bit clean) connection that the operating
system will not alter.
.PP
-When \fBkeypad\fP is first enabled,
+When \fB\%keypad\fP is first enabled,
ncurses 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,
@@ -340,22 +340,22 @@ .SH PORTABILITY
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 \fBkeyname\fP function
+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).
-On the other hand, an application can use \fBdefine_key\fP to establish
+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
-capability's presence with \fBtigetstr\fP,
+capability's presence with \fB\%tigetstr\fP,
and reassign the keycode to match its own needs.
.PP
-Low-level applications can use \fBtigetstr\fP to obtain the definition
+Low-level applications can use \fB\%tigetstr\fP to obtain the definition
of any particular string capability.
-Higher-level applications which use the curses \fBwgetch\fP
+Higher-level applications which use the curses \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 \fBwgetch\fP can return only one keycode.
+then \fB\%wgetch\fP can return only one keycode.
Most curses implementations (including ncurses)
load key definitions in the order
defined by the array of string capability names.
@@ -369,28 +369,28 @@ .SH PORTABILITY
.SH NOTES
Note that
\fBecho\fP,
-\fBnoecho\fP,
-\fBhalfdelay\fP,
-\fBintrflush\fP,
+\fB\%noecho\fP,
+\fB\%halfdelay\fP,
+\fB\%intrflush\fP,
\fBmeta\fP,
\fBnl\fP,
\fBnonl\fP,
-\fBnodelay\fP,
-\fBnotimeout\fP,
-\fBnoqiflush\fP,
-\fBqiflush\fP,
-\fBtimeout\fP, and
-\fBwtimeout\fP may be macros.
+\fB\%nodelay\fP,
+\fB\%notimeout\fP,
+\fB\%noqiflush\fP,
+\fB\%qiflush\fP,
+\fB\%timeout\fP, and
+\fB\%wtimeout\fP may be macros.
.PP
-The \fBnoraw\fP and \fBnocbreak\fP calls follow historical practice in that
+The \fB\%noraw\fP and \fB\%nocbreak\fP 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 recommended.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_getch\fP(3X),
-\fBcurs_initscr\fP(3X),
-\fBcurs_util\fP(3X),
-\fBdefine_key\fP(3X),
-\fBtermios\fP(3)
+\fB\%curses\fP(3X),
+\fB\%curs_getch\fP(3X),
+\fB\%curs_initscr\fP(3X),
+\fB\%curs_util\fP(3X),
+\fB\%define_key\fP(3X),
+\fB\%termios\fP(3)
diff --git a/man/curs_legacy.3x b/man/curs_legacy.3x
index 34b33343..3153d9a6 100644
--- a/man/curs_legacy.3x
+++ b/man/curs_legacy.3x
@@ -65,30 +65,30 @@ .SH SYNOPSIS
.SH DESCRIPTION
These legacy functions are simpler to use than the X/Open Curses functions:
.bP
-The \fBgetattrs\fP function returns the same attribute data as \fBwattr_get\fP.
+The \fB\%getattrs\fP function returns the same attribute data as
\fB\%wattr_get\fP.
.IP
-However, \fBgetattrs\fP returns an integer (actually a \fBchtype\fP),
-while \fBwattr_get\fP returns the current color pair in a separate parameter.
+However, \fB\%getattrs\fP returns an integer (actually a \fB\%chtype\fP),
+while \fB\%wattr_get\fP returns the current color pair in a separate parameter.
In the wide-character library configuration,
-color pairs may not fit into a \fBchtype\fP,
-so \fBwattr_get\fP is the only way to obtain the color information.
+color pairs may not fit into a \fB\%chtype\fP,
+so \fB\%wattr_get\fP is the only way to obtain the color information.
.IP
-Because \fBgetattrs\fP returns the attributes in a single parameter,
+Because \fB\%getattrs\fP returns the attributes in a single parameter,
it would not be possible for an application to distinguish that from
\fBERR\fP (a \fI-1\fP).
-If the window parameter is null, \fBgetattrs\fP returns \fBA_NORMAL\fP (zero).
+If the window parameter is null, \fB\%getattrs\fP returns \fB\%A_NORMAL\fP
(zero).
.bP
-The \fBgetbegy\fP and \fBgetbegx\fP functions return the same
-data as \fBgetbegyx\fP.
+The \fB\%getbegy\fP and \fB\%getbegx\fP functions return the same
+data as \fB\%getbegyx\fP.
.bP
-The \fBgetcury\fP and \fBgetcurx\fP functions return the same
-data as \fBgetyx\fP.
+The \fB\%getcury\fP and \fB\%getcurx\fP functions return the same
+data as \fB\%getyx\fP.
.bP
-The \fBgetmaxy\fP and \fBgetmaxx\fP functions return the same
-data as \fBgetmaxyx\fP.
+The \fB\%getmaxy\fP and \fB\%getmaxx\fP functions return the same
+data as \fB\%getmaxyx\fP.
.bP
-The \fBgetpary\fP and \fBgetparx\fP functions return the same
-data as \fBgetparyx\fP.
+The \fB\%getpary\fP and \fB\%getparx\fP functions return the same
+data as \fB\%getparyx\fP.
.SH RETURN VALUE
Except as noted,
these functions return an integer,
@@ -96,8 +96,8 @@ .SH RETURN VALUE
.SH NOTES
All of these interfaces are provided as macros and functions.
The macros are suppressed (and only the functions provided)
-when \fBNCURSES_OPAQUE\fP is defined.
-The standard forms such as \fBgetyx\fP must be implemented as macros,
+when \fB\%NCURSES_OPAQUE\fP is defined.
+The standard forms such as \fB\%getyx\fP must be implemented as macros,
and (in this implementation) are defined in terms of the functions
described here,
to avoid reliance on internal details of the \fB\%WINDOW\fP structure.
@@ -105,10 +105,10 @@ .SH PORTABILITY
These functions were supported on Version 7, BSD or System V implementations.
None of those implementations checked the window parameter.
.PP
-The \fBgetattrs\fP function and macro are defined to return a (signed) integer
+The \fB\%getattrs\fP function and macro are defined to return a (signed)
integer
for compatibility with those implementations
although an unsigned type would have been more appropriate.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_getyx\fP(3X),
-\fBcurs_opaque\fP(3X)
+\fB\%curses\fP(3X),
+\fB\%curs_getyx\fP(3X),
+\fB\%curs_opaque\fP(3X)
diff --git a/man/curs_memleaks.3x b/man/curs_memleaks.3x
index 5dd0f5c2..4012e041 100644
--- a/man/curs_memleaks.3x
+++ b/man/curs_memleaks.3x
@@ -59,8 +59,8 @@ .SH DESCRIPTION
library.
.PP
Any implementation of curses must not free the memory associated with
-a screen, since (even after calling \fBendwin\fP(3X)), it must be available
-for use in the next call to \fBrefresh\fP(3X).
+a screen, since (even after calling \fB\%endwin\fP(3X)), it must be available
+for use in the next call to \fB\%refresh\fP(3X).
There are also chunks of memory held for performance reasons.
That makes it hard to analyze curses applications for memory leaks.
When using the specially configured debugging version of the ncurses library,
@@ -74,24 +74,24 @@ .SH DESCRIPTION
This frees (almost) all of the memory allocated by ncurses.
.TP 5
\fB_nc_free_and_exit\fP
-This frees the memory allocated by ncurses (like \fB_nc_freeall\fP),
+This frees the memory allocated by ncurses (like \fB\%_nc_freeall\fP),
and exits the program.
-It is preferred over \fB_nc_freeall\fP since some of that memory
+It is preferred over \fB\%_nc_freeall\fP since some of that memory
may be required to keep the application running.
Simply exiting (with the given exit-code) is safer.
.TP 5
\fB_nc_free_tinfo\fP
Use this function if only the low-level terminfo functions (and
corresponding library) are used.
-Like \fB_nc_free_and_exit\fP, it exits the program after freeing memory.
+Like \fB\%_nc_free_and_exit\fP, it exits the program after freeing memory.
.PP
The functions prefixed \*(``_nc\*('' are normally not available;
they must be configured into the library
-at build time using the \fB\-\-disable-leaks\fP option.
+at build time using the \fB\%\-\-disable-leaks\fP option.
That compiles-in code that frees memory that normally would not be freed.
.PP
-The \fBexit_curses\fP and \fBexit_terminfo\fP functions
-call \fB_nc_free_and_exit\fP and \fB_nc_free_tinfo\fP if
+The \fB\%exit_curses\fP and \fB\%exit_terminfo\fP functions
+call \fB\%_nc_free_and_exit\fP and \fB\%_nc_free_tinfo\fP if
the library is configured to support memory-leak checking.
If the library is not configured to support memory-leak checking,
they simply call \fBexit\fP.
@@ -104,18 +104,18 @@ .SH PORTABILITY
In any implementation of X/Open Curses, an application can free part
of the memory allocated by curses:
.bP
-The portable part of \fBexit_curses\fP can be freed using \fBdelscreen\fP,
-passing the \fBSCREEN*\fP pointer returned by \fBnewterm\fP.
+The portable part of \fB\%exit_curses\fP can be freed using \fB\%delscreen\fP,
+passing the \fBSCREEN*\fP pointer returned by \fB\%newterm\fP.
.IP
In some implementations, there is a global variable \fBsp\fP
which could be used, e.g., if the screen were only initialized
-using \fBinitscr\fP.
+using \fB\%initscr\fP.
.bP
-The portable part of \fBexit_terminfo\fP can be freed using \fBdel_curterm\fP.
+The portable part of \fB\%exit_terminfo\fP can be freed using
\fB\%del_curterm\fP.
.IP
-In this case, there is a global variable \fBcur_term\fP which can be
+In this case, there is a global variable \fB\%cur_term\fP which can be
used as parameter.
.SH SEE ALSO
-\fBcurs_initscr\fP(3X),
-\fBcurs_terminfo\fP(3X).
-\fBcurses\fP(3X).
+\fB\%curs_initscr\fP(3X),
+\fB\%curs_terminfo\fP(3X).
+\fB\%curses\fP(3X).
diff --git a/man/curs_mouse.3x b/man/curs_mouse.3x
index 35dd1be6..20e784eb 100644
--- a/man/curs_mouse.3x
+++ b/man/curs_mouse.3x
@@ -96,11 +96,11 @@ .SH SYNOPSIS
.fi
.SH DESCRIPTION
These functions provide an interface to mouse events from
-\fBncurses\fP(3X).
-Mouse events are represented by \fBKEY_MOUSE\fP
-pseudo-key values in the \fBwgetch\fP(3X) input stream.
+\fB\%ncurses\fP(3X).
+Mouse events are represented by \fB\%KEY_MOUSE\fP
+pseudo-key values in the \fB\%wgetch\fP(3X) input stream.
.SS mousemask
-To make mouse events visible, use the \fBmousemask\fP function.
+To make mouse events visible, use the \fB\%mousemask\fP function.
This sets the mouse events to be reported.
By default, no mouse events are reported.
.bP
@@ -165,39 +165,39 @@ .SS Mouse events
.TE
.SS getmouse
Once a class of mouse events has been made visible in a window,
-calling the \fBwgetch\fP function on that window may return
-\fBKEY_MOUSE\fP as an indicator that a mouse event has been queued.
+calling the \fB\%wgetch\fP function on that window may return
+\fB\%KEY_MOUSE\fP as an indicator that a mouse event has been queued.
To read the event data and pop the event off the queue, call
-\fBgetmouse\fP.
+\fB\%getmouse\fP.
This function will return \fBOK\fP if a mouse event
is actually visible in the given window, \fBERR\fP otherwise.
-When \fBgetmouse\fP returns \fBOK\fP, the data deposited as y and
+When \fB\%getmouse\fP returns \fBOK\fP, the data deposited as y and
x in the event structure coordinates will be screen-relative character-cell
coordinates.
The returned state mask will have exactly one bit set to
indicate the event type.
The corresponding data in the queue is marked invalid.
-A subsequent call to \fBgetmouse\fP will retrieve the next older
+A subsequent call to \fB\%getmouse\fP will retrieve the next older
item from the queue.
.SS ungetmouse
-The \fBungetmouse\fP function behaves analogously to \fBungetch\fP.
+The \fB\%ungetmouse\fP function behaves analogously to \fB\%ungetch\fP.
It pushes
-a \fBKEY_MOUSE\fP event onto the input queue, and associates with that event
+a \fB\%KEY_MOUSE\fP event onto the input queue, and associates with that event
the given state data and screen-relative character-cell coordinates.
.SS wenclose
-The \fBwenclose\fP function tests whether a given pair of screen-relative
+The \fB\%wenclose\fP function tests whether a given pair of screen-relative
character-cell coordinates is enclosed by a given window, returning \fBTRUE\fP
if it is and \fBFALSE\fP otherwise.
It is useful for determining what subset of
the screen windows enclose the location of a mouse event.
.SS wmouse_trafo
-The \fBwmouse_trafo\fP function transforms a given pair of coordinates
+The \fB\%wmouse_trafo\fP function transforms a given pair of coordinates
from stdscr-relative coordinates
to coordinates relative to the given window or vice versa.
The resulting stdscr-relative coordinates are not always identical
to window-relative coordinates due to the mechanism to reserve lines on top
or bottom of the screen for other purposes
-(see the \fBripoffline\fP and \fBslk_init\fP(3X) calls, for example).
+(see the \fB\%ripoffline\fP and \fB\%slk_init\fP(3X) calls, for example).
.bP
If the parameter \fIto_screen\fP is \fBTRUE\fP, the pointers
\fIpY, pX\fP must reference the coordinates of a location
@@ -222,27 +222,27 @@ .SS wmouse_trafo
are only replaced by the converted coordinates if the transformation was
successful.
.SS mouse_trafo
-The \fBmouse_trafo\fP function performs the same translation
-as \fBwmouse_trafo\fP,
+The \fB\%mouse_trafo\fP function performs the same translation
+as \fB\%wmouse_trafo\fP,
using stdscr for \fIwin\fP.
.SS mouseinterval
-The \fBmouseinterval\fP function sets the maximum time (in thousands of a
+The \fB\%mouseinterval\fP function sets the maximum time (in thousands of a
second) that can elapse between press and release events for them to
be recognized as a click.
-Use \fBmouseinterval(0)\fP to disable click resolution.
+Use \fB\%mouseinterval(0)\fP to disable click resolution.
This function returns the previous interval value.
-Use \fBmouseinterval(\-1)\fP to obtain the interval without altering it.
+Use \fB\%mouseinterval(\-1)\fP to obtain the interval without altering it.
The default is one sixth of a second.
.SS has_mouse
-The \fBhas_mouse\fP function returns \fBTRUE\fP if the mouse driver has been
+The \fB\%has_mouse\fP function returns \fBTRUE\fP if the mouse driver has been
successfully initialized.
.PP
Note that mouse events will be ignored when input is in cooked mode, and will
cause an error beep when cooked mode is being simulated in a window by a
-function such as \fBgetstr\fP that expects a linefeed for input-loop
+function such as \fB\%getstr\fP that expects a linefeed for input-loop
termination.
.SH RETURN VALUE
-\fBgetmouse\fP and \fBungetmouse\fP
+\fB\%getmouse\fP and \fB\%ungetmouse\fP
return the integer \fBERR\fP upon failure or \fBOK\fP
upon successful completion:
.RS 3
@@ -262,15 +262,15 @@ .SH RETURN VALUE
returns an error if the FIFO is full.
.RE
.PP
-\fBmousemask\fP
+\fB\%mousemask\fP
returns the mask of reportable events.
.PP
-\fBmouseinterval\fP
+\fB\%mouseinterval\fP
returns the previous interval value, unless
the terminal was not initialized.
In that case, it returns the maximum interval value (166).
.PP
-\fBwenclose\fP and \fBwmouse_trafo\fP
+\fB\%wenclose\fP and \fB\%wmouse_trafo\fP
are boolean functions returning \fBTRUE\fP or \fBFALSE\fP depending
on their test result.
.SH PORTABILITY
@@ -305,11 +305,11 @@ .SH PORTABILITY
sent to and received from the terminal.
.IP
For instance
-the SVr4 curses library used the \fBget_mouse\fP capability to tell the
+the SVr4 curses 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 \fBreq_mouse_pos\fP capability.
+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.
They were not part of the X Consortium's xterm.
@@ -323,11 +323,11 @@ .SH PORTABILITY
making it unnecessary to be concerned about compatibility with the
escape sequences.
.PP
-The feature macro \fBNCURSES_MOUSE_VERSION\fP is provided so the preprocessor
+The feature macro \fB\%NCURSES_MOUSE_VERSION\fP is provided so the preprocessor
can be used to test whether these features are present.
-If the interface is changed, the value of \fBNCURSES_MOUSE_VERSION\fP will be
+If the interface is changed, the value of \fB\%NCURSES_MOUSE_VERSION\fP will be
incremented.
-These values for \fBNCURSES_MOUSE_VERSION\fP may be
+These values for \fB\%NCURSES_MOUSE_VERSION\fP may be
specified when configuring ncurses:
.RS 3
.TP 3
@@ -341,7 +341,7 @@ .SH PORTABILITY
The mask uses 29 bits.
.RE
.PP
-The order of the \fBMEVENT\fP structure members is not guaranteed.
+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
@@ -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 \fBmousemask\fP function will always
+\fBncurses\fP(3X) (and the \fB\%mousemask\fP function will always
return \fB0\fP).
.PP
If the terminfo entry contains a \fBXM\fP string,
@@ -382,37 +382,37 @@ .SH PORTABILITY
for use with touch screens (which may be pressure-sensitive) or with
3D-mice/trackballs/power gloves.
.PP
-The \fBALL_MOUSE_EVENTS\fP class does not include \fBREPORT_MOUSE_POSITION\fP.
+The \fB\%ALL_MOUSE_EVENTS\fP class does not include
\fB\%REPORT_MOUSE_POSITION\fP.
They are distinct.
For example, in xterm,
wheel/scrolling mice send position reports as a sequence of
presses of buttons 4 or 5 without matching button-releases.
.SH BUGS
Mouse events under xterm will not in fact be ignored during cooked mode,
-if they have been enabled by \fBmousemask\fP.
+if they have been enabled by \fB\%mousemask\fP.
Instead, the xterm mouse
report sequence will appear in the string read.
.PP
Mouse events under xterm will not be detected correctly in a window with
its keypad bit off, since they are interpreted as a variety of function key.
-Your terminfo description should have \fBkmous\fP set to \*(``\\E[M\*(''
+Your terminfo description should have \fB\%kmous\fP set to \*(``\\E[M\*(''
(the beginning of the response from xterm for mouse clicks).
-Other values for \fBkmous\fP are permitted,
+Other values for \fB\%kmous\fP are permitted,
but under the same assumption,
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
-if \fBkmous\fP is defined in the terminal description,
+if \fB\%kmous\fP is defined in the terminal description,
or if the terminal description's primary name or aliases
contain the string \*(``xterm\*('',
then the terminal may send mouse events.
-The \fBkmous\fP capability is checked first,
+The \fB\%kmous\fP capability is checked first,
allowing the use of newer xterm mouse protocols
such as xterm's private mode 1006.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_inopts\fP(3X),
-\fBcurs_kernel\fP(3X),
-\fBcurs_slk\fP(3X),
-\fBcurs_variables\fP(3X).
+\fB\%curses\fP(3X),
+\fB\%curs_inopts\fP(3X),
+\fB\%curs_kernel\fP(3X),
+\fB\%curs_slk\fP(3X),
+\fB\%curs_variables\fP(3X).
diff --git a/man/curs_opaque.3x b/man/curs_opaque.3x
index cfb0502c..fcb009b8 100644
--- a/man/curs_opaque.3x
+++ b/man/curs_opaque.3x
@@ -72,57 +72,57 @@ .SH SYNOPSIS
.fi
.SH DESCRIPTION
This implementation provides functions which return properties
-set in the \fBWINDOW\fP structure, allowing it to be \*(``opaque\*('' if
+set in the \fB\%WINDOW\fP structure, allowing it to be \*(``opaque\*('' if
the symbol \fB\%NCURSES_OPAQUE\fP is defined:
.TP 5
\fBis_cleared\fP
-returns the value set in \fBclearok\fP(3X)
+returns the value set in \fB\%clearok\fP(3X)
.TP 5
\fBis_idcok\fP
-returns the value set in \fBidcok\fP(3X)
+returns the value set in \fB\%idcok\fP(3X)
.TP 5
\fBis_idlok\fP
-returns the value set in \fBidlok\fP(3X)
+returns the value set in \fB\%idlok\fP(3X)
.TP 5
\fBis_immedok\fP
-returns the value set in \fBimmedok\fP(3X)
+returns the value set in \fB\%immedok\fP(3X)
.TP 5
\fBis_keypad\fP
-returns the value set in \fBkeypad\fP(3X)
+returns the value set in \fB\%keypad\fP(3X)
.TP 5
\fBis_leaveok\fP
-returns the value set in \fBleaveok\fP(3X)
+returns the value set in \fB\%leaveok\fP(3X)
.TP 5
\fBis_nodelay\fP
-returns the value set in \fBnodelay\fP(3X)
+returns the value set in \fB\%nodelay\fP(3X)
.TP 5
\fBis_notimeout\fP
-returns the value set in \fBnotimeout\fP(3X)
+returns the value set in \fB\%notimeout\fP(3X)
.TP 5
\fBis_pad\fP
returns \fBTRUE\fP if the window is a pad
-i.e., created by \fBnewpad\fP(3X)
+i.e., created by \fB\%newpad\fP(3X)
.TP 5
\fBis_scrollok\fP
-returns the value set in \fBscrollok\fP(3X)
+returns the value set in \fB\%scrollok\fP(3X)
.TP 5
\fBis_subwin\fP
returns \fBTRUE\fP if the window is a subwindow,
-i.e., created by \fBsubwin\fP(3X) or \fBderwin\fP(3X)
+i.e., created by \fB\%subwin\fP(3X) or \fB\%derwin\fP(3X)
.TP 5
\fBis_syncok\fP
-returns the value set in \fBsyncok\fP(3X)
+returns the value set in \fB\%syncok\fP(3X)
.TP 5
\fBwgetdelay\fP
-returns the delay timeout as set in \fBwtimeout\fP(3X).
+returns the delay timeout as set in \fB\%wtimeout\fP(3X).
.TP 5
\fBwgetparent\fP
-returns the parent \fBWINDOW\fP pointer for subwindows,
+returns the parent \fB\%WINDOW\fP pointer for subwindows,
or \fBNULL\fP for windows having no parent.
.TP 5
\fBwgetscrreg\fP
returns the top and bottom rows for the scrolling margin
-as set in \fBwsetscrreg\fP.
+as set in \fB\%wsetscrreg\fP.
.SH RETURN VALUE
These functions all return \fBTRUE\fP or \fBFALSE\fP, except as noted.
.SH NOTES
@@ -131,9 +131,9 @@ .SH PORTABILITY
These routines are specific to ncurses.
They were not supported on Version 7, BSD or System V implementations.
It is recommended that any code depending on ncurses extensions
-be conditioned using \fBNCURSES_VERSION\fP.
+be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_inopts\fP(3X),
-\fBcurs_outopts\fP(3X),
-\fBcurs_window\fP(3X)
+\fB\%curses\fP(3X),
+\fB\%curs_inopts\fP(3X),
+\fB\%curs_outopts\fP(3X),
+\fB\%curs_window\fP(3X)
diff --git a/man/curs_pad.3x b/man/curs_pad.3x
index ce802305..cfa153b7 100644
--- a/man/curs_pad.3x
+++ b/man/curs_pad.3x
@@ -57,7 +57,7 @@ .SH SYNOPSIS
.fi
.SH DESCRIPTION
.SS newpad
-The \fBnewpad\fP routine creates and returns a pointer to a new pad data
+The \fB\%newpad\fP routine creates and returns a pointer to a new pad data
structure with the given number of lines, \fInlines\fP, and columns,
\fIncols\fP.
A pad is like a window, except that it is not restricted by the
@@ -69,25 +69,25 @@ .SS newpad
(e.g., from scrolling or echoing of input) do not occur.
.PP
It is not
-legal to call \fBwrefresh\fP with a \fIpad\fP as an argument; the routines
-\fBprefresh\fP or \fBpnoutrefresh\fP should be called instead.
+legal to call \fB\%wrefresh\fP with a \fIpad\fP as an argument; the routines
+\fB\%prefresh\fP or \fB\%pnoutrefresh\fP should be called instead.
Note that these
routines require additional parameters to specify the part of the pad to be
displayed and the location on the screen to be used for the display.
.SS subpad
-The \fBsubpad\fP routine creates and returns a pointer to a subwindow within a
+The \fB\%subpad\fP routine creates and returns a pointer to a subwindow within
a
pad with the given number of lines, \fInlines\fP, and columns, \fIncols\fP.
-Unlike \fBsubwin\fP, which uses screen coordinates, the window is at position
+Unlike \fB\%subwin\fP, which uses screen coordinates, the window is at position
(\fIbegin\fR_\fIx\fB,\fR \fIbegin\fR_\fIy\fR) on the pad.
The window is
made in the middle of the window \fIorig\fP, so that changes made to one window
affect both windows.
During the use of this routine, it will often be
-necessary to call \fBtouchwin\fP or \fBtouchline\fP on \fIorig\fP before
-calling \fBprefresh\fP.
+necessary to call \fB\%touchwin\fP or \fB\%touchline\fP on \fIorig\fP before
+calling \fB\%prefresh\fP.
.SS prefresh, pnoutrefresh
-The \fBprefresh\fP and \fBpnoutrefresh\fP routines are analogous to
-\fBwrefresh\fP and \fBwnoutrefresh\fP except that they relate to pads instead
+The \fB\%prefresh\fP and \fB\%pnoutrefresh\fP routines are analogous to
+\fB\%wrefresh\fP and \fB\%wnoutrefresh\fP except that they relate to pads
instead
of windows.
The additional parameters are needed to indicate what part of the
pad and screen are involved.
@@ -109,35 +109,35 @@ .SS prefresh, pnoutrefresh
\fIpminrow\fP, \fIpmincol\fP, \fIsminrow\fP, or \fIsmincol\fP are treated as if
they were zero.
.SS pechochar
-The \fBpechochar\fP routine is functionally equivalent to a call to \fBaddch\fP
-followed by a call to \fBrefresh\fP(3X),
-a call to \fBwaddch\fP followed by a call
-to \fBwrefresh\fP, or a call to \fBwaddch\fP followed by a call to
-\fBprefresh\fP.
+The \fB\%pechochar\fP routine is functionally equivalent to a call to
\fB\%addch\fP
+followed by a call to \fB\%refresh\fP(3X),
+a call to \fB\%waddch\fP followed by a call
+to \fB\%wrefresh\fP, or a call to \fB\%waddch\fP followed by a call to
+\fB\%prefresh\fP.
The knowledge that only a single character is being output is
taken into consideration and, for non-control characters, a considerable
performance gain might be seen by using these routines instead of their
equivalents.
-In the case of \fBpechochar\fP, the last location of the pad on
-the screen is reused for the arguments to \fBprefresh\fP.
+In the case of \fB\%pechochar\fP, the last location of the pad on
+the screen is reused for the arguments to \fB\%prefresh\fP.
.SS pecho_wchar
-The \fBpecho_wchar\fP function is the analogous wide-character
-form of \fBpechochar\fP.
+The \fB\%pecho_wchar\fP function is the analogous wide-character
+form of \fB\%pechochar\fP.
It outputs one character to a pad and immediately refreshes the pad.
-It does this by a call to \fBwadd_wch\fP followed by a call to \fBprefresh\fP.
+It does this by a call to \fB\%wadd_wch\fP followed by a call to
\fB\%prefresh\fP.
.SH RETURN VALUE
Routines that return an integer return \fBERR\fP upon failure and \fBOK\fP
(SVr4 only specifies "an integer value other than \fBERR\fP") upon successful
completion.
.PP
-Routines that return pointers return \fBNULL\fP on error, and set \fBerrno\fP
-to \fBENOMEM\fP.
+Routines that return pointers return \fBNULL\fP on error, and set \fB\%errno\fP
+to \fB\%ENOMEM\fP.
.PP
X/Open does not define any error conditions.
In this implementation
.RS 3
.TP 5
-\fBprefresh\fP and \fBpnoutrefresh\fP
+\fB\%prefresh\fP and \fB\%pnoutrefresh\fP
return an error
if the window pointer is null, or
if the window is not really a pad or
@@ -147,19 +147,19 @@ .SH RETURN VALUE
\fBpechochar\fP
returns an error
if the window is not really a pad, and the associated call
-to \fBwechochar\fP returns an error.
+to \fB\%wechochar\fP returns an error.
.TP 5
\fBpecho_wchar\fP
returns an error
if the window is not really a pad, and the associated call
-to \fBwecho_wchar\fP returns an error.
+to \fB\%wecho_wchar\fP returns an error.
.RE
.SH NOTES
-Note that \fBpechochar\fP may be a macro.
+Note that \fB\%pechochar\fP may be a macro.
.SH PORTABILITY
BSD curses has no \fIpad\fP feature.
.PP
-SVr2 curses (1986) provided the \fBnewpad\fP and related functions,
+SVr2 curses (1986) provided the \fB\%newpad\fP and related functions,
documenting them in a single line each.
SVr3 (1987) provided more extensive documentation.
.PP
@@ -177,56 +177,56 @@ .SH PORTABILITY
The XSI Curses standard, Issue 4 describes these functions,
without significant change from the SVr3 documentation.
It describes no error conditions.
-The behavior of \fBsubpad\fP if the parent window is not
+The behavior of \fB\%subpad\fP if the parent window is not
a pad is undocumented,
and is not checked by the vendor Unix implementations:
.bP
-SVr4 curses sets a flag in the \fBWINDOW\fP structure in \fBnewpad\fP
+SVr4 curses 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
-\fBwaddch\fP (to decide if it should call \fBwrefresh\fP) and
-\fBwscrl\fP (to avoid scrolling a pad),
-and does not check in \fBwrefresh\fP to ensure that the pad
+\fB\%waddch\fP (to decide if it should call \fB\%wrefresh\fP) and
+\fB\%wscrl\fP (to avoid scrolling a pad),
+and does not check in \fB\%wrefresh\fP to ensure that the pad
is refreshed properly.
.bP
-Solaris X/Open Curses checks if a window is a pad in \fBwnoutrefresh\fP,
+Solaris X/Open Curses checks if a window is a pad in \fB\%wnoutrefresh\fP,
returning \fBERR\fP in that case.
.IP
However, it only sets the flag for subwindows if the parent window is a pad.
-Its \fBnewpad\fP function does not set this information.
+Its \fB\%newpad\fP function does not set this information.
Consequently, the check will never fail.
.IP
-It makes no comparable check in \fBpnoutrefresh\fP,
+It makes no comparable check in \fB\%pnoutrefresh\fP,
though interestingly enough, a comment in the source code
states that the lack of a check was an MKS extension.
.bP
NetBSD 7 curses
-sets a flag in the \fBWINDOW\fP structure for \fBnewpad\fP and \fBsubpad\fP,
-using this to help with the distinction between \fBwnoutrefresh\fP
-and \fBpnoutrefresh\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.
.IP
It does not check for the case where a subwindow is created in
-a pad using \fBsubwin\fP or \fBderwin\fP.
+a pad using \fB\%subwin\fP or \fB\%derwin\fP.
.IP
-The \fBdupwin\fP function returns a regular window when duplicating a pad.
-Likewise, \fBgetwin\fP always returns a window, even if the saved
+The \fB\%dupwin\fP function returns a regular window when duplicating a pad.
+Likewise, \fB\%getwin\fP always returns a window, even if the saved
data was from a pad.
.PP
This implementation
.bP
-sets a flag in the \fBWINDOW\fP structure for \fBnewpad\fP and \fBsubpad\fP,
+sets a flag in the \fB\%WINDOW\fP structure for \fB\%newpad\fP and
\fB\%subpad\fP,
.bP
-allows a \fBsubwin\fP or \fBderwin\fP call to succeed having a pad parent by
+allows a \fB\%subwin\fP or \fB\%derwin\fP call to succeed having a pad parent
by
forcing the subwindow to be a pad,
.bP
-checks in both \fBwnoutrefresh\fP and \fBpnoutrefresh\fP to ensure
+checks in both \fB\%wnoutrefresh\fP and \fB\%pnoutrefresh\fP to ensure
that pads and windows are handled distinctly, and
.bP
-ensures that \fBdupwin\fP and \fBgetwin\fP treat
+ensures that \fB\%dupwin\fP and \fB\%getwin\fP treat
pads versus windows consistently.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_refresh\fP(3X),
-\fBcurs_touch\fP(3X),
-\fBcurs_addch\fP(3X).
+\fB\%curses\fP(3X),
+\fB\%curs_refresh\fP(3X),
+\fB\%curs_touch\fP(3X),
+\fB\%curs_addch\fP(3X).
diff --git a/man/curs_print.3x b/man/curs_print.3x
index 75d8c002..1ef48e6c 100644
--- a/man/curs_print.3x
+++ b/man/curs_print.3x
@@ -40,7 +40,7 @@ .SH DESCRIPTION
This function uses the \fBmc5p\fP or \fBmc4\fP and \fBmc5\fP capabilities,
if they are present, to ship given data to a printer attached to the terminal.
.PP
-Note that the \fBmcprint\fP code has no way to do flow control with the printer
+Note that the \fB\%mcprint\fP code has no way to do flow control with the
printer
or to know how much buffering it has.
Your application is responsible for
keeping the rate of writes to the printer below its continuous throughput rate
@@ -50,9 +50,9 @@ .SH DESCRIPTION
rule of thumb is to sleep for a second after shipping each 80-character line.
.
.SH RETURN VALUE
-The \fBmcprint\fP function returns \fBERR\fP if the write operation aborted
+The \fB\%mcprint\fP function returns \fBERR\fP if the write operation aborted
for some reason.
-In this case, \fBerrno\fP will contain either an error associated
+In this case, \fB\%errno\fP will contain either an error associated
with \fBwrite\fP(2) or one of the following:
.TP 5
\fBENODEV\fP
@@ -61,13 +61,13 @@ .SH RETURN VALUE
\fBENOMEM\fP
Couldn't allocate sufficient memory to buffer the printer write.
.PP
-When \fBmcprint\fP succeeds, it returns the number of characters actually
+When \fB\%mcprint\fP succeeds, it returns the number of characters actually
sent to the printer.
.SH PORTABILITY
-The \fBmcprint\fP call was designed for \fBncurses\fP(3X), and is not found
+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.
.SH BUGS
Padding in the \fBmc5p\fP, \fBmc4\fP and \fBmc5\fP capabilities will not be
interpreted.
.SH SEE ALSO
-\fBcurses\fP(3X)
+\fB\%curses\fP(3X)
diff --git a/man/curs_slk.3x b/man/curs_slk.3x
index b38d6aed..c17d21be 100644
--- a/man/curs_slk.3x
+++ b/man/curs_slk.3x
@@ -91,8 +91,8 @@ .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 \fBstdscr\fP, reducing the size of
-\fBstdscr\fP and the variable \fBLINES\fP.
+\fBcurses\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
labels of up to eight characters each.
In addition to this, the ncurses
@@ -104,9 +104,9 @@ .SH DESCRIPTION
it does not try to use any hardware support for this
mode.
.SS Initialization
-The \fBslk_init\fP routine must be called before \fBinitscr\fP or \fBnewterm\fP
+The \fB\%slk_init\fP routine must be called before \fB\%initscr\fP or
\fB\%newterm\fP
is called.
-If \fBinitscr\fP eventually uses a line from \fBstdscr\fP to
+If \fB\%initscr\fP eventually uses a line from \fB\%stdscr\fP to
emulate the soft labels,
then \fIfmt\fP determines how the labels are arranged on the screen:
.RS 3
@@ -127,19 +127,19 @@ .SS Initialization
identify the key numbers easily.
.RE
.SS Labels
-The \fBslk_set\fP routine
-(and the \fBslk_wset\fP routine for the wide-character library)
+The \fB\%slk_set\fP routine
+(and the \fB\%slk_wset\fP routine for the wide-character library)
has three parameters:
.RS 3
.TP 5
.I labnum
is the label number, from \fB1\fP to \fB8\fP
-(12 if \fIfmt\fP in \fBslk_init\fP is \fB2\fP or \fB3\fP);
+(12 if \fIfmt\fP in \fB\%slk_init\fP is \fB2\fP or \fB3\fP);
.TP
.I label
is be the string to put on the label,
up to eight
-(five if \fIfmt\fP in \fBslk_init\fP is \fB2\fP or \fB3\fP)
+(five if \fIfmt\fP in \fB\%slk_init\fP is \fB2\fP or \fB3\fP)
characters in length.
A null string or a null pointer sets up a blank label.
.TP
@@ -150,36 +150,36 @@ .SS Labels
label.
.RE
.PP
-The \fBslk_label\fP routine returns the current label for label number
+The \fB\%slk_label\fP routine returns the current label for label number
\fIlabnum\fP, with leading and trailing blanks stripped.
.SS Screen updates
-The \fBslk_refresh\fP and \fBslk_noutrefresh\fP routines correspond to
-the \fBwrefresh\fP and \fBwnoutrefresh\fP routines.
+The \fB\%slk_refresh\fP and \fB\%slk_noutrefresh\fP routines correspond to
+the \fB\%wrefresh\fP and \fB\%wnoutrefresh\fP routines.
.PP
-The \fBslk_clear\fP routine clears the soft labels from the screen.
+The \fB\%slk_clear\fP routine clears the soft labels from the screen.
.PP
-The \fBslk_restore\fP routine restores the soft labels to the screen
-after a \fBslk_clear\fP has been performed.
+The \fB\%slk_restore\fP routine restores the soft labels to the screen
+after a \fB\%slk_clear\fP has been performed.
.PP
-The \fBslk_touch\fP routine forces all the soft labels to be output
-the next time a \fBslk_noutrefresh\fP is performed.
+The \fB\%slk_touch\fP routine forces all the soft labels to be output
+the next time a \fB\%slk_noutrefresh\fP is performed.
.SS Video attributes
The
-\fBslk_attron\fP, \fBslk_attrset\fP, \fBslk_attroff\fP and \fBslk_attr\fP
+\fB\%slk_attron\fP, \fB\%slk_attrset\fP, \fB\%slk_attroff\fP and
\fB\%slk_attr\fP
routines correspond to
-\fBattron\fP, \fBattrset\fP, \fBattroff\fP and \fBattr_get\fP, respectively.
+\fB\%attron\fP, \fB\%attrset\fP, \fB\%attroff\fP and \fB\%attr_get\fP,
respectively.
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).
.SS Colors
-The \fBslk_color\fP routine corresponds to \fBcolor_set\fP.
+The \fB\%slk_color\fP routine corresponds to \fB\%color_set\fP.
It has an effect only
if soft labels are simulated on the bottom line of the screen.
.PP
-Because \fBslk_color\fP accepts only \fBshort\fP (signed 16-bit integer)
values,
+Because \fB\%slk_color\fP accepts only \fBshort\fP (signed 16-bit integer)
values,
this implementation provides
-\fBextended_slk_color\fP which accepts an integer value, e.g., 32-bits.
+\fB\%extended_slk_color\fP which accepts an integer value, e.g., 32-bits.
.
.SH RETURN VALUE
These routines return \fBERR\fP upon failure
@@ -255,37 +255,37 @@ .SH EXTENSIONS
uses that parameter in ABI 6 for the functions which have a color-pair
parameter to support extended color pairs.
.PP
-For functions which modify the color, e.g., \fBslk_attr_set\fP,
+For functions which modify the color, e.g., \fB\%slk_attr_set\fP,
if \fIopts\fP is set it is treated as a pointer to \fBint\fP,
and used to set the color pair instead of the \fBshort\fP pair parameter.
.SH NOTES
-Most applications would use \fBslk_noutrefresh\fP because a
-\fBwrefresh\fP is likely to follow soon.
+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:
.bP
It added functions like the SVr4
-attribute-manipulation functions \fBslk_attron\fP,
-\fBslk_attroff\fP, \fBslk_attrset\fP,
-but which use \fBattr_t\fP parameters (rather than \fBchtype\fP),
+attribute-manipulation functions \fB\%slk_attron\fP,
+\fB\%slk_attroff\fP, \fB\%slk_attrset\fP,
+but which use \fBattr_t\fP parameters (rather than \fB\%chtype\fP),
along with a reserved \fIopts\fP parameter.
.IP
Two of these new functions (unlike the SVr4 functions) have no provision
-for color: \fBslk_attr_on\fP and \fBslk_attr_off\fP.
+for color: \fB\%slk_attr_on\fP and \fB\%slk_attr_off\fP.
.IP
-The third function (\fBslk_attr_set\fP) has a color-pair parameter.
+The third function (\fB\%slk_attr_set\fP) has a color-pair parameter.
.bP
It added \fBconst\fP qualifiers to parameters (unnecessarily), and
.bP
-It added \fBslk_color\fP.
+It added \fB\%slk_color\fP.
.PP
-Although \fBslk_start\fP is declared in the curses header file,
+Although \fB\%slk_start\fP is declared in the curses 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):
.bP
-\fBslk_start\fP has two parameters:
+\fB\%slk_start\fP has two parameters:
.RS
.bP
\fIng\fP (number of groups) and
@@ -295,27 +295,27 @@ .SH PORTABILITY
.bP
Soft-key groups are an array of \fIng\fP integers.
.bP
-In SVr4, \fBslk_init\fP calls \fBslk_start\fP passing a null for \fIgp\fP.
-For this case, \fBslk_start\fP uses the number of groups \fIng\fP
-(3 for the 3-2-3 layout, 2 for the 4-4 layout) which \fBslk_init\fP provided.
+In SVr4, \fB\%slk_init\fP calls \fB\%slk_start\fP passing a null for \fIgp\fP.
+For this case, \fB\%slk_start\fP uses the number of groups \fIng\fP
+(3 for the 3-2-3 layout, 2 for the 4-4 layout) which \fB\%slk_init\fP provided.
.IP
If \fIng\fP is neither 2 or 3,
-\fBslk_start\fP checks the terminfo \fBfln\fP (label_format) capability,
+\fB\%slk_start\fP checks the terminfo \fBfln\fP (label_format) capability,
interpreting that as a comma-separated list of numbers,
e.g., \*(``3,2,3\*('' for the 3-2-3 layout.
.IP
-Finally, if there is no \fBfln\fP capability, \fBslk_start\fP returns
\fBERR\fP.
+Finally, if there is no \fBfln\fP capability, \fB\%slk_start\fP returns
\fBERR\fP.
.bP
-If \fBslk_start\fP is given a non-null \fIgp\fP,
+If \fB\%slk_start\fP is given a non-null \fIgp\fP,
it copies the \fIng\fP elements of the group of soft-keys, up to 16.
.IP
-If there are more than 16 elements, \fBslk_start\fP returns an error.
+If there are more than 16 elements, \fB\%slk_start\fP returns an error.
.bP
-The format codes \fB2\fP and \fB3\fP for \fBslk_init\fP
+The format codes \fB2\fP and \fB3\fP for \fB\%slk_init\fP
were added by ncurses in 1996.
PDCurses 2.4 added this feature in 2001.
.PP
-The function \fBslk_attr\fP was added by ncurses in 1996.
+The function \fB\%slk_attr\fP was added by ncurses in 1996.
.PP
X/Open Curses does not specify a limit for the number of colors and
color pairs which a terminal can support.
@@ -326,8 +326,8 @@ .SH PORTABILITY
which use \fBint\fP parameters,
allowing applications to use larger color- and pair-numbers.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_attr\fP(3X),
-\fBcurs_initscr\fP(3X),
-\fBcurs_refresh\fP(3X),
-\fBcurs_variables\fP(3X).
+\fB\%curses\fP(3X),
+\fB\%curs_attr\fP(3X),
+\fB\%curs_initscr\fP(3X),
+\fB\%curs_refresh\fP(3X),
+\fB\%curs_variables\fP(3X).
diff --git a/man/curs_terminfo.3x b/man/curs_terminfo.3x
index b887ab40..ca4cc907 100644
--- a/man/curs_terminfo.3x
+++ b/man/curs_terminfo.3x
@@ -121,59 +121,59 @@ .SH DESCRIPTION
capability string values have no associated encoding;
they are strings of 8-bit characters.
.SS Initialization
-Initially, \fBsetupterm\fP should be called.
-The high-level curses functions \fBinitscr\fP and
-\fBnewterm\fP call \fBsetupterm\fP to initialize the
+Initially, \fB\%setupterm\fP should be called.
+The high-level curses functions \fB\%initscr\fP and
+\fB\%newterm\fP call \fB\%setupterm\fP to initialize the
low-level set of terminal-dependent variables
-[listed in \fBterminfo\fP(\*n)].
+[listed in \fB\%terminfo\fP(\*n)].
.PP
Applications can use the
terminal capabilities either directly (via header definitions),
or by special functions.
-The header files \fBcurses.h\fP and \fBterm.h\fP should be included (in this
+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
-\fBlines\fP and \fBcolumns\fP are initialized by \fBsetupterm\fP as
+\fBlines\fP and \fB\%columns\fP are initialized by \fB\%setupterm\fP as
follows:
.bP
-If \fBuse_env(FALSE)\fP has been called, values for
-\fBlines\fP and \fBcolumns\fP specified in \fBterminfo\fP are used.
+If \fB\%use_env(FALSE)\fP has been called, values for
+\fBlines\fP and \fB\%columns\fP specified in \fBterminfo\fP are used.
.bP
-Otherwise, if the environment variables \fBLINES\fP and \fBCOLUMNS\fP
+Otherwise, if the environment variables \fBLINES\fP and \fB\%COLUMNS\fP
exist, their values are used.
If these environment variables do not
exist and the program is running in a window, the current window size
is used.
Otherwise, if the environment variables do not exist, the
-values for \fBlines\fP and \fBcolumns\fP specified in the
+values for \fBlines\fP and \fB\%columns\fP specified in the
\fBterminfo\fP database are used.
.PP
-Parameterized strings should be passed through \fBtparm\fP to instantiate them.
+Parameterized strings should be passed through \fB\%tparm\fP to instantiate
them.
All \fBterminfo\fP strings
-(including the output of \fBtparm\fP)
+(including the output of \fB\%tparm\fP)
should be printed
-with \fBtputs\fP or \fBputp\fP.
-Call \fBreset_shell_mode\fP to restore the
-tty modes before exiting [see \fBcurs_kernel\fP(3X)].
+with \fB\%tputs\fP or \fBputp\fP.
+Call \fB\%reset_shell_mode\fP to restore the
+tty modes before exiting [see \fB\%curs_kernel\fP(3X)].
.PP
Programs which use
cursor addressing should
.bP
-output \fBenter_ca_mode\fP upon startup and
+output \fB\%enter_ca_mode\fP upon startup and
.bP
-output \fBexit_ca_mode\fP before exiting.
+output \fB\%exit_ca_mode\fP before exiting.
.PP
Programs which execute shell subprocesses should
.bP
-call \fBreset_shell_mode\fP and
-output \fBexit_ca_mode\fP before the shell
+call \fB\%reset_shell_mode\fP and
+output \fB\%exit_ca_mode\fP before the shell
is called and
.bP
-output \fBenter_ca_mode\fP and
-call \fBreset_prog_mode\fP after returning from the shell.
+output \fB\%enter_ca_mode\fP and
+call \fB\%reset_prog_mode\fP after returning from the shell.
.PP
-The \fBsetupterm\fP routine reads in the \fBterminfo\fP database,
+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.
These are its parameters:
@@ -186,16 +186,16 @@ .SS Initialization
\fIfiledes\fP
is the file descriptor used for getting and setting terminal I/O modes.
.IP
-Higher-level applications use \fBnewterm\fP(3X) for initializing the terminal,
+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 \fBnewterm\fP calls \fBsetupterm\fP,
+In curses, 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
points to an optional location where an error status can be returned to
the caller.
If \fIerrret\fP is not null,
-then \fBsetupterm\fP returns \fBOK\fP or
+then \fB\%setupterm\fP returns \fBOK\fP or
\fBERR\fP and stores a status value in the integer pointed to by
\fIerrret\fP.
A return value of \fBOK\fP combined with status of \fB1\fP in \fIerrret\fP
@@ -229,72 +229,72 @@ .SS Initialization
.sp
\fBsetupterm((char *)0, 1, (int *)0);\fP,
.sp
-which uses all the defaults and sends the output to \fBstdout\fP.
+which uses all the defaults and sends the output to \fB\%stdout\fP.
.RE
.\" ***************************************************************************
.SS The Terminal State
-The \fBsetupterm\fP routine stores its information about the terminal
-in a \fBTERMINAL\fP structure pointed to by the global variable \fBcur_term\fP.
+The \fB\%setupterm\fP routine stores its information about the terminal
+in a \fB\%TERMINAL\fP structure pointed to by the global variable
\fB\%cur_term\fP.
If it detects an error,
or decides that the terminal is unsuitable (hardcopy or generic),
it discards this information,
making it not available to applications.
.PP
-If \fBsetupterm\fP is called repeatedly for the same terminal type,
+If \fB\%setupterm\fP is called repeatedly for the same terminal type,
it will reuse the information.
It maintains only one copy of a given terminal's capabilities in memory.
If it is called for different terminal types,
-\fBsetupterm\fP allocates new storage for each set of terminal capabilities.
+\fB\%setupterm\fP allocates new storage for each set of terminal capabilities.
.PP
-The \fBset_curterm\fP routine sets \fBcur_term\fP to
+The \fB\%set_curterm\fP routine sets \fB\%cur_term\fP to
\fInterm\fP, and makes all of the \fBterminfo\fP boolean, numeric, and
string variables use the values from \fInterm\fP.
-It returns the old value of \fBcur_term\fP.
+It returns the old value of \fB\%cur_term\fP.
.PP
-The \fBdel_curterm\fP routine frees the space pointed to by
+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 \fBcur_term\fP, references to any of the \fBterminfo\fP
+the same as \fB\%cur_term\fP, references to any of the \fBterminfo\fP
boolean, numeric, and string variables thereafter may refer to invalid
-memory locations until another \fBsetupterm\fP has been called.
+memory locations until another \fB\%setupterm\fP has been called.
.PP
-The \fBrestartterm\fP routine is similar to \fBsetupterm\fP and \fBinitscr\fP,
+The \fB\%restartterm\fP routine is similar to \fB\%setupterm\fP and
\fB\%initscr\fP,
except that it is called after restoring memory to a previous state (for
example, when reloading a game saved as a core image dump).
-\fBrestartterm\fP assumes that the windows and the input and output options
+\fB\%restartterm\fP assumes that the windows and the input and output options
are the same as when memory was saved,
but the terminal type and baud rate may be different.
-Accordingly, \fBrestartterm\fP saves various tty state bits,
-calls \fBsetupterm\fP, and then restores the bits.
+Accordingly, \fB\%restartterm\fP saves various tty state bits,
+calls \fB\%setupterm\fP, and then restores the bits.
.\" ***************************************************************************
.SS Formatting Output
-The \fBtparm\fP routine instantiates the string \fIstr\fP with
+The \fB\%tparm\fP routine instantiates the string \fIstr\fP with
parameters \fIpi\fP. A pointer is returned to the result of \fIstr\fP
with the parameters applied.
Application developers should keep in mind these quirks of the interface:
.bP
-Although \fBtparm\fP's actual parameters may be integers or strings,
+Although \fB\%tparm\fP's actual parameters may be integers or strings,
the prototype expects \fBlong\fP (integer) values.
.bP
-Aside from the \fBset_attributes\fP (\fBsgr\fP) capability,
+Aside from the \fB\%set_attributes\fP (\fBsgr\fP) capability,
most terminal capabilities require no more than one or two parameters.
.bP
-Padding information is ignored by \fBtparm\fP;
-it is interpreted by \fBtputs\fP.
+Padding information is ignored by \fB\%tparm\fP;
+it is interpreted by \fB\%tputs\fP.
.bP
The capability string is null-terminated.
Use \*(``\\200\*('' where an ASCII NUL is needed in the output.
.PP
-\fBtiparm\fP is a newer form of \fBtparm\fP which uses \fI<stdarg.h>\fP
+\fB\%tiparm\fP is a newer form of \fB\%tparm\fP which uses \fI<stdarg.h>\fP
rather than a fixed-parameter list.
Its numeric parameters are integers (int) rather than longs.
.PP
-Both \fBtparm\fP and \fBtiparm\fP assume that the application passes
+Both \fB\%tparm\fP and \fB\%tiparm\fP assume that the application passes
parameters consistent with the terminal description.
Two extensions are provided as alternatives to deal with untrusted data:
.bP
-\fBtiparm_s\fP is an extension which is a safer formatting function
-than \fBtparm\fR or \fBtiparm\fR,
+\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
library how many parameters to expect in the parameter list,
and which may be string parameters.
@@ -302,11 +302,11 @@ .SS Formatting Output
The \fImask\fP parameter has one bit set for each of the parameters
(up to 9) which will be passed as char* rather than numbers.
.bP
-The extension \fBtiscan_s\fP allows the application
+The extension \fB\%tiscan_s\fP allows the application
to inspect a formatting capability to see what the curses library would assume.
.\" ***************************************************************************
.SS Output Functions
-The \fBtputs\fP routine applies padding information
+The \fB\%tputs\fP routine applies padding information
(i.e., by interpreting marker embedded in the terminfo capability
such as \*(``$<5>\*('' as 5 milliseconds)
to the string
@@ -314,41 +314,41 @@ .SS Output Functions
.bP
The \fIstr\fP parameter must be a terminfo string
variable or the return value from
-\fBtparm\fP, \fBtiparm\fP, \fBtgetstr\fP, or \fBtgoto\fP.
+\fB\%tparm\fP, \fB\%tiparm\fP, \fB\%tgetstr\fP, or \fB\%tgoto\fP.
.IP
-The \fBtgetstr\fP and \fBtgoto\fP functions are part of the \fItermcap\fP
+The \fB\%tgetstr\fP and \fB\%tgoto\fP functions are part of the \fItermcap\fP
interface,
which happens to share this function name with the \fIterminfo\fP interface.
.bP
\fIaffcnt\fP is the number of lines affected, or 1 if
not applicable.
.bP
-\fIputc\fP is a \fBputchar\fP-like routine to which
+\fIputc\fP is a \fB\%putchar\fP-like routine to which
the characters are passed, one at a time.
.PP
-The \fBputp\fR routine calls \fBtputs(\fIstr\fB, 1, putchar)\fR.
-The output of \fBputp\fP always goes to \fBstdout\fP, rather than
-the \fIfiledes\fP specified in \fBsetupterm\fP.
+The \fBputp\fR routine calls \fB\%tputs(\fIstr\fB, 1, \%putchar)\fR.
+The output of \fBputp\fP always goes to \fB\%stdout\fP, rather than
+the \fIfiledes\fP specified in \fB\%setupterm\fP.
.PP
-The \fBvidputs\fP routine displays the string on the terminal in the
+The \fB\%vidputs\fP routine displays the string on the terminal in the
video attribute mode \fIattrs\fP, which is any combination of the
-attributes listed in \fBcurses\fP(3X).
+attributes listed in \fB\%curses\fP(3X).
The characters are passed to
-the \fBputchar\fP-like routine \fIputc\fP.
+the \fB\%putchar\fP-like routine \fIputc\fP.
.PP
-The \fBvidattr\fP routine is like the \fBvidputs\fP routine, except
-that it outputs through \fBputchar\fP.
+The \fB\%vidattr\fP routine is like the \fB\%vidputs\fP routine, except
+that it outputs through \fB\%putchar\fP.
.PP
-The \fBvid_attr\fP and \fBvid_puts\fP routines correspond
+The \fB\%vid_attr\fP and \fB\%vid_puts\fP routines correspond
to vidattr and vidputs, respectively.
They use a set of arguments for representing the video attributes plus color,
i.e.,
.bP
-\fIattrs\fP of type \fBattr_t\fP for the attributes and
+\fIattrs\fP of type \fB\%attr_t\fP for the attributes and
.bP
\fIpair\fP of type \fBshort\fP for the color-pair number.
.PP
-The \fBvid_attr\fP and \fBvid_puts\fP routines
+The \fB\%vid_attr\fP and \fB\%vid_puts\fP routines
are designed to use the attribute constants with the \fBWA_\fP prefix.
.PP
X/Open Curses reserves the \fIopts\fP argument for future use,
@@ -357,28 +357,28 @@ .SS Output Functions
this implementation allows \fIopts\fP to be used as a pointer to \fBint\fP,
which overrides the \fIpair\fP (\fBshort\fP) argument.
.PP
-The \fBmvcur\fP routine provides low-level cursor motion.
+The \fB\%mvcur\fP routine provides low-level cursor motion.
It takes effect immediately (rather than at the next refresh).
Unlike the other low-level output functions,
which either write to the standard output or pass an output function parameter,
-\fBmvcur\fP uses an output file descriptor derived from
-the output stream parameter of \fBnewterm\fP(3X).
+\fB\%mvcur\fP uses an output file descriptor derived from
+the output stream parameter of \fB\%newterm\fP(3X).
.PP
-While \fBputp\fP and \fBmvcur\fP are low-level functions which
+While \fBputp\fP and \fB\%mvcur\fP are low-level functions which
do not use the high-level curses state,
-they are declared in \fB<curses.h>\fP because SystemV did this
+they are declared in \fB\%<curses.h>\fP because SystemV did this
(see \fIHISTORY\fP).
.\" ***************************************************************************
.SS Terminal Capability Functions
-The \fBtigetflag\fP, \fBtigetnum\fP and \fBtigetstr\fP routines return
+The \fB\%tigetflag\fP, \fB\%tigetnum\fP and \fB\%tigetstr\fP routines return
the value of the capability corresponding to the \fBterminfo\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 \fBterminfo\fP(\*n).
+\fIcapname\fP code in the capabilities section of \fB\%terminfo\fP(\*n).
.PP
These routines return special values to denote errors.
.PP
-The \fBtigetflag\fP routine returns
+The \fB\%tigetflag\fP routine returns
.TP
\fB\-1\fP
if \fIcapname\fP is not a boolean capability,
@@ -387,7 +387,7 @@ .SS Terminal Capability Functions
\fB0\fP
if it is canceled or absent from the terminal description.
.PP
-The \fBtigetnum\fP routine returns
+The \fB\%tigetnum\fP routine returns
.TP
\fB\-2\fP
if \fIcapname\fP is not a numeric capability, or
@@ -395,7 +395,7 @@ .SS Terminal Capability Functions
\fB\-1\fP
if it is canceled or absent from the terminal description.
.PP
-The \fBtigetstr\fP routine returns
+The \fB\%tigetstr\fP routine returns
.TP
\fB(char *)\-1\fP
if \fIcapname\fP is not a string capability,
@@ -424,30 +424,30 @@ .SS Terminal Capability Names
.RE
.\" ***************************************************************************
.SS Releasing Memory
-Each successful call to \fBsetupterm\fP allocates memory to hold the terminal
+Each successful call to \fB\%setupterm\fP allocates memory to hold the terminal
description.
-As a side-effect, it sets \fBcur_term\fP to point to this memory.
+As a side-effect, it sets \fB\%cur_term\fP to point to this memory.
If an application calls
.sp
\fBdel_curterm(cur_term);\fP
.sp
the memory will be freed.
.PP
-The formatting functions \fBtparm\fP and \fBtiparm\fP extend the storage
-allocated by \fBsetupterm\fP:
+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.
-See \fBterminfo\fP(\*n) for details.
+See \fB\%terminfo\fP(\*n) for details.
.bP
to improve performance, ncurses 6.3 caches the result of analyzing terminfo
strings for their parameter types.
-That is stored as a binary tree referenced from the \fBTERMINAL\fP structure.
+That is stored as a binary tree referenced from the \fB\%TERMINAL\fP structure.
.PP
-The higher-level \fBinitscr\fP and \fBnewterm\fP functions use \fBsetupterm\fP.
+The higher-level \fB\%initscr\fP and \fB\%newterm\fP functions use
\fB\%setupterm\fP.
Normally they do not free this memory, but it is possible to do that using
-the \fBdelscreen\fP(3X) function.
+the \fB\%delscreen\fP(3X) function.
.\" ***************************************************************************
.SH RETURN VALUE
Routines that return an integer return \fBERR\fP upon failure and \fBOK\fP
@@ -466,11 +466,11 @@ .SH RETURN VALUE
if its terminal parameter is null.
.TP 5
\fBputp\fP
-calls \fBtputs\fP, returning the same error-codes.
+calls \fB\%tputs\fP, returning the same error-codes.
.TP 5
\fBrestartterm\fP
returns an error
-if the associated call to \fBsetupterm\fP returns an error.
+if the associated call to \fB\%setupterm\fP returns an error.
.TP 5
\fBsetupterm\fP
returns an error
@@ -486,7 +486,7 @@ .SH RETURN VALUE
\fBtputs\fP
returns an error if the string parameter is null.
It does not detect I/O errors:
-X/Open states that \fBtputs\fP ignores the return value
+X/Open states that \fB\%tputs\fP ignores the return value
of the output function \fIputc\fP.
.RE
.\" ***************************************************************************
@@ -494,23 +494,23 @@ .SS Compatibility macros
This implementation provides a few macros for compatibility with systems
before SVr4 (see \fIHISTORY\fP).
Those include
-\fBcrmode\fP,
-\fBfixterm\fP,
-\fBgettmode\fP,
-\fBnocrmode\fP,
-\fBresetterm\fP,
-\fBsaveterm\fP, and
-\fBsetterm\fP.
-.PP
-In SVr4, those are found in \fB<curses.h>\fP,
-but except for \fBsetterm\fP, are likewise macros.
-The one function, \fBsetterm\fP, is mentioned in the manual page.
-The manual page notes that the \fBsetterm\fP routine
-was replaced by \fBsetupterm\fP, stating that the call:
+\fB\%crmode\fP,
+\fB\%fixterm\fP,
+\fB\%gettmode\fP,
+\fB\%nocrmode\fP,
+\fB\%resetterm\fP,
+\fB\%saveterm\fP, and
+\fB\%setterm\fP.
+.PP
+In SVr4, those are found in \fB\%<curses.h>\fP,
+but except for \fB\%setterm\fP, are likewise macros.
+The one function, \fB\%setterm\fP, is mentioned in the manual page.
+The manual page notes that the \fB\%setterm\fP routine
+was replaced by \fB\%setupterm\fP, stating that the call:
.sp
\fBsetupterm(\fIterm\fB, 1, (int *)0)\fR
.sp
-provides the same functionality as \fBsetterm(\fIterm\fB)\fR,
+provides the same functionality as \fB\%setterm(\fIterm\fB)\fR,
and is not recommended for new programs.
This implementation provides each of those symbols
as macros for BSD compatibility,
@@ -527,7 +527,7 @@ .SH HISTORY
gettmode establish current tty modes
mvcur low level cursor motion
putp T{
-utility function that uses \fBtputs\fP to send characters via \fBputchar\fP.
+utility function that uses \fB\%tputs\fP to send characters via
\fB\%putchar\fP.
T}
resetterm set tty modes to \*(``out of curses\*('' state
resetty reset tty flags to stored value
@@ -537,7 +537,7 @@ .SH HISTORY
setupterm establish terminal with given type
tparm instantiate a string expression with parameters
tputs apply padding information to a string
-vidattr like \fBvidputs\fP, but outputs through \fBputchar\fP
+vidattr like \fB\%vidputs\fP, but outputs through \fB\%putchar\fP
vidputs T{
output a string to put terminal in a specified video attribute mode
T}
@@ -563,11 +563,11 @@ .SH HISTORY
.TE
.PP
Early terminfo programs obtained capability values from the
-\fBTERMINAL\fP structure initialized by \fBsetupterm\fP.
+\fB\%TERMINAL\fP structure initialized by \fB\%setupterm\fP.
.PP
SVr3 extended terminfo by adding functions to retrieve capability values
(like the termcap interface),
-and reusing \fBtgoto\fP and \fBtputs\fP:
+and reusing \fB\%tgoto\fP and \fB\%tputs\fP:
.PP
.TS
l l
@@ -596,24 +596,24 @@ .SH HISTORY
setterm setupterm
.TE
.PP
-SVr3 kept the \fBmvcur\fP, \fBvidattr\fP and \fBvidputs\fP functions,
-along with \fBputp\fP, \fBtparm\fP and \fBtputs\fP.
+SVr3 kept the \fB\%mvcur\fP, \fB\%vidattr\fP and \fB\%vidputs\fP functions,
+along with \fBputp\fP, \fB\%tparm\fP and \fB\%tputs\fP.
The latter were needed to support padding,
-and handling functions such as \fBvidattr\fP
-(which used more than the two parameters supported by \fBtgoto\fP).
+and handling functions such as \fB\%vidattr\fP
+(which used more than the two parameters supported by \fB\%tgoto\fP).
.PP
SVr3 introduced the functions for switching between terminal
-descriptions, e.g., \fBset_curterm\fP.
+descriptions, e.g., \fB\%set_curterm\fP.
Some of that was incremental improvements to the SVr2 library:
.bP
-The \fBTERMINAL\fP type definition was introduced in SVr3.01,
+The \fB\%TERMINAL\fP type definition was introduced in SVr3.01,
for the \fBterm\fP structure provided in SVr2.
.bP
-The various global variables such as \fBboolnames\fP were mentioned
+The various global variables such as \fB\%boolnames\fP were mentioned
in the programming manual at this point,
though the variables were provided in SVr2.
.PP
-SVr4 added the \fBvid_attr\fP and \fBvid_puts\fP functions.
+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
on Unix systems,
@@ -622,28 +622,28 @@ .SH HISTORY
by the Unix \fBvi\fP(1) editor.
.SH PORTABILITY
.SS Extensions
-The functions marked as extensions were designed for \fBncurses\fP(3X),
+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.
.SS Legacy functions
-X/Open notes that \fBvidattr\fP and \fBvidputs\fP may be macros.
+X/Open notes that \fB\%vidattr\fP and \fB\%vidputs\fP may be macros.
.PP
-The function \fBsetterm\fP is not described by X/Open and must
+The function \fB\%setterm\fP is not described by X/Open and must
be considered non-portable.
All other functions are as described by X/Open.
.SS Legacy data
-\fBsetupterm\fP copies the terminal name to the array \fBttytype\fP.
+\fB\%setupterm\fP copies the terminal name to the array \fB\%ttytype\fP.
This is not part of X/Open Curses, but is assumed by some applications.
.PP
Other implementions may not declare the capability name arrays.
Some provide them without declaring them.
X/Open does not specify them.
.PP
-Extended terminal capability names, e.g., as defined by \fB@TIC@\ \-x\fP,
+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
-\fBsetupterm\fP from \fBinitscr\fP or \fBnewterm\fP uses buffered I/O,
+\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),
@@ -674,7 +674,7 @@ .SS Function prototypes
function prototypes to use the \fBconst\fP keyword.
The ncurses ABI 6 enables this feature by default.
.bP
-X/Open Curses prototypes \fBtparm\fP with a fixed number of parameters,
+X/Open Curses prototypes \fB\%tparm\fP with a fixed number of parameters,
rather than a variable argument list.
.IP
This implementation uses a variable argument list, but can be
@@ -683,15 +683,15 @@ .SS Function prototypes
zeroes are fine for this purpose.
.IP
In response to review comments by Thomas E. Dickey,
-X/Open Curses Issue 7 proposed the \fBtiparm\fP function in mid-2009.
+X/Open Curses Issue 7 proposed the \fB\%tiparm\fP function in mid-2009.
.IP
-While \fBtiparm\fP is always provided in ncurses,
+While \fB\%tiparm\fP is always provided in ncurses,
the older form is only available as a build-time configuration option.
-If not specially configured, \fBtparm\fP is the same as \fBtiparm\fP.
+If not specially configured, \fB\%tparm\fP is the same as \fB\%tiparm\fP.
.PP
-Both forms of \fBtparm\fP have drawbacks:
+Both forms of \fB\%tparm\fP have drawbacks:
.bP
-Most of the calls to \fBtparm\fP use only one or two parameters.
+Most of the calls to \fB\%tparm\fP use only one or two parameters.
Passing nine on each call is awkward.
.IP
Using \fBlong\fP for the numeric parameter type is a workaround
@@ -701,65 +701,65 @@ .SS Function prototypes
(and pointers are not required to fit in a long).
.bP
Providing the right number of parameters for a variadic function
-such as \fBtiparm\fP can be a problem, in particular for string parameters.
+such as \fB\%tiparm\fP can be a problem, in particular for string parameters.
However, only a few terminfo capabilities use string parameters
(e.g., the ones used for programmable function keys).
.IP
The ncurses 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 \fBtparm\fP calls.
+places for the \fB\%tparm\fP calls.
.IP
-The \fB@TPUT@\fR(1) program checks its use of these capabilities with a table,
-so that it calls \fBtparm\fP correctly.
+The \fB\%@TPUT@\fR(1) program checks its use of these capabilities with a
table,
+so that it calls \fB\%tparm\fP correctly.
.SS Special TERM treatment
If configured to use the terminal-driver,
e.g., for the MinGW port,
.bP
-\fBsetupterm\fP interprets a missing/empty TERM variable as the
+\fB\%setupterm\fP interprets a missing/empty TERM variable as the
special value \*(``unknown\*(''.
.IP
SVr4 curses uses the
special value \*(``dumb\*(''.
.IP
The difference between the two is that
-the former uses the \fBgn\fP (\fBgeneric_type\fR) terminfo capability,
+the former uses the \fBgn\fP (\fB\%generic_type\fR) terminfo capability,
while the latter does not.
A generic terminal is unsuitable for full-screen applications.
.bP
-\fBsetupterm\fP allows explicit use of the
+\fB\%setupterm\fP allows explicit use of the
the windows console driver by checking if $TERM is set to
\*(``#win32con\*('' or an abbreviation of that string.
.SS Other portability issues
-In System V Release 4, \fBset_curterm\fP has an \fBint\fP return type and
+In System V Release 4, \fB\%set_curterm\fP has an \fBint\fP return type and
returns \fBOK\fP or \fBERR\fP. We have chosen to implement the X/Open Curses
semantics.
.PP
-In System V Release 4, the third argument of \fBtputs\fP has the type
+In System V Release 4, the third argument of \fB\%tputs\fP has the type
\fBint (*putc)(char)\fP.
.PP
At least one implementation of X/Open Curses (Solaris) returns a value
-other than \fBOK\fP/\fBERR\fP from \fBtputs\fP.
+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 \fBmvcur\fP, the curses state may not match the
+X/Open notes that after calling \fB\%mvcur\fP, the curses 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 \fBmvcur\fP using
-the SCREEN data allocated in either \fBinitscr\fP or \fBnewterm\fP.
+Both \fBncurses\fP and System V Release 4 curses 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,
-\fBmvcur\fP is really a curses function which is not well specified.
+\fB\%mvcur\fP is really a curses function which is not well specified.
.PP
-X/Open states that the old location must be given for \fBmvcur\fP.
+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.
In that case, the old location is unknown.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_initscr\fP(3X),
-\fBcurs_kernel\fP(3X),
-\fBcurs_memleaks\fP(3X),
-\fBcurs_termcap\fP(3X),
-\fBcurs_variables\fP(3X),
-\fBterm_variables\fP(3X),
-\fBputc\fP(3),
-\fBterminfo\fP(\*n)
+\fB\%curses\fP(3X),
+\fB\%curs_initscr\fP(3X),
+\fB\%curs_kernel\fP(3X),
+\fB\%curs_memleaks\fP(3X),
+\fB\%curs_termcap\fP(3X),
+\fB\%curs_variables\fP(3X),
+\fB\%term_variables\fP(3X),
+\fB\%putc\fP(3),
+\fB\%terminfo\fP(\*n)
diff --git a/man/curs_touch.3x b/man/curs_touch.3x
index 15337c7b..ca274010 100644
--- a/man/curs_touch.3x
+++ b/man/curs_touch.3x
@@ -52,7 +52,7 @@ .SH SYNOPSIS
\fBbool is_wintouched(WINDOW *\fIwin\fB);\fR
.fi
.SH DESCRIPTION
-The \fBtouchwin\fP and \fBtouchline\fP routines throw away all
+The \fB\%touchwin\fP and \fB\%touchline\fP routines throw away all
optimization information about which parts of the window have been
touched, by pretending that the entire window has been drawn on.
This
@@ -60,21 +60,21 @@ .SH DESCRIPTION
to one window affects the other window, but the records of which lines
have been changed in the other window do not reflect the change.
The
-routine \fBtouchline\fP only pretends that \fIcount\fP lines have been
+routine \fB\%touchline\fP only pretends that \fIcount\fP lines have been
changed, beginning with line \fIstart\fP.
.PP
-The \fBuntouchwin\fP routine marks all lines in the window as unchanged since
-the last call to \fBwrefresh\fP.
+The \fB\%untouchwin\fP routine marks all lines in the window as unchanged since
+the last call to \fB\%wrefresh\fP.
.PP
-The \fBwtouchln\fP routine makes \fIn\fP lines in the window, starting
+The \fB\%wtouchln\fP routine makes \fIn\fP lines in the window, starting
at line \fIy\fR, look as if they have (\fIchanged\fB=1\fR) or have
not (\fIchanged\fB=0\fR) been changed since the last call to
-\fBwrefresh\fP.
+\fB\%wrefresh\fP.
.PP
-The \fBis_linetouched\fP and \fBis_wintouched\fP routines return
+The \fB\%is_linetouched\fP and \fB\%is_wintouched\fP routines return
\fBTRUE\fP if the specified line/window was modified since the last
-call to \fBwrefresh\fP; otherwise they return \fBFALSE\fP. In
-addition, \fBis_linetouched\fP returns \fBERR\fP if \fIline\fP is not
+call to \fB\%wrefresh\fP; otherwise they return \fBFALSE\fP. In
+addition, \fB\%is_linetouched\fP returns \fBERR\fP if \fIline\fP is not
valid for the given window.
.SH RETURN VALUE
All routines return the integer \fBERR\fP upon failure and an integer value
@@ -97,7 +97,7 @@ .SH RETURN VALUE
may not be supported by the compiler.
.IP
To provide error-checking and also match the X/Open function prototype,
-the \fBERR\fP is provided by a macro named \fBis_linetouched\fP.
+the \fBERR\fP is provided by a macro named \fB\%is_linetouched\fP.
The actual function returns \fBFALSE\fP when it detects an error.
.TP 5
\fBwtouchln\fP
@@ -117,8 +117,8 @@ .SH PORTABILITY
The XSI Curses standard, Issue 4 describes these functions,
but defines no error conditions.
.SH NOTES
-All of these routines except \fBwtouchln\fP may be macros.
+All of these routines except \fB\%wtouchln\fP may be macros.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_refresh\fP(3X),
-\fBcurs_variables\fP(3X).
+\fB\%curses\fP(3X),
+\fB\%curs_refresh\fP(3X),
+\fB\%curs_variables\fP(3X).
diff --git a/man/curs_trace.3x b/man/curs_trace.3x
index d9411619..a3189cda 100644
--- a/man/curs_trace.3x
+++ b/man/curs_trace.3x
@@ -80,37 +80,37 @@ .SH DESCRIPTION
as well as applications which use the ncurses libraries.
Some limitations apply:
.bP
-Aside from \fBcurses_trace\fP,
+Aside from \fB\%curses_trace\fP,
the other functions are normally available only with the debugging library
-e.g., \fBlibncurses_g.a\fP.
+e.g., \fB\%libncurses_g.a\fP.
.IP
All of the trace functions may be compiled into any model (shared, static,
-profile) by defining the symbol \fBTRACE\fP.
+profile) by defining the symbol \fB\%TRACE\fP.
.bP
-Additionally, the functions which use \fBcchar_t\fP
+Additionally, the functions which use \fB\%cchar_t\fP
are only available with the wide-character configuration of the libraries.
.SS Functions
The principal parts of this interface are
.bP
-\fBcurses_trace\fP, which selectively enables different tracing features, and
+\fB\%curses_trace\fP, which selectively enables different tracing features, and
.bP
-\fB_tracef\fP, which writes formatted data to the \fItrace\fP file.
+\fB\%_tracef\fP, which writes formatted data to the \fItrace\fP file.
.IP
The other functions either return a pointer to a string-area
(allocated by the corresponding function), or return no value
-(such as \fB_tracedump\fP,
-which implements the screen dump for \fBTRACE_UPDATE\fP).
+(such as \fB\%_tracedump\fP,
+which implements the screen dump for \fB\%TRACE_UPDATE\fP).
The caller should not free these strings,
since the allocation is reused on successive calls.
To work around the problem of a single string-area per function,
some use a buffer-number parameter, telling the library to allocate
additional string-areas.
.PP
-The \fBcurses_trace\fP function is always available,
+The \fB\%curses_trace\fP function is always available,
whether or not the other trace functions are available:
.bP
If tracing is available,
-calling \fBcurses_trace\fP with a nonzero parameter
+calling \fB\%curses_trace\fP with a nonzero parameter
updates the trace mask,
and returns the previous trace mask.
.IP
@@ -118,10 +118,10 @@ .SS Functions
ncurses creates the file \*(``trace\*('' in the current directory for output.
If the file already exists, no tracing is done.
.bP
-If tracing is not available, \fBcurses_trace\fP returns zero (0).
+If tracing is not available, \fB\%curses_trace\fP returns zero (0).
.SS Trace Parameter
The trace parameter is formed by OR'ing
-values from the list of \fBTRACE_\fIxxx\fR definitions in \fB<curses.h>\fR.
+values from the list of \fB\%TRACE_\fIxxx\fR definitions in \fB\%<curses.h>\fR.
These include:
.TP 5
.B TRACE_DISABLE
@@ -130,13 +130,13 @@ .SS Trace Parameter
The library flushes the output file,
but retains an open file-descriptor to the trace file
so that it can resume tracing later if a nonzero parameter is passed
-to the \fBcurses_trace\fP function.
+to the \fB\%curses_trace\fP function.
.TP 5
.B TRACE_TIMES
trace user and system times of updates.
.TP 5
.B TRACE_TPUTS
-trace \fBtputs\fP(3X) calls.
+trace \fB\%tputs\fP(3X) calls.
.TP 5
.B TRACE_UPDATE
trace update actions, old & new screens.
@@ -157,7 +157,7 @@ .SS Trace Parameter
The parameters for each call are traced, as well as return values.
.TP 5
.B TRACE_VIRTPUT
-trace virtual character puts, i.e., calls to \fBaddch\fP.
+trace virtual character puts, i.e., calls to \fB\%addch\fP.
.TP 5
.B TRACE_IEVENT
trace low-level input processing, including timeouts.
@@ -180,13 +180,13 @@ .SS Trace Parameter
.B TRACE_MAXIMUM
maximum trace level, enables all of the separate trace features.
.PP
-Some tracing features are enabled whenever the \fBcurses_trace\fP parameter
+Some tracing features are enabled whenever the \fB\%curses_trace\fP parameter
is nonzero.
Some features overlap.
The specific names are used as a guideline.
.SS Initialization
-These functions check the \fBNCURSES_TRACE\fP environment variable,
-to set the tracing feature as if \fBcurses_trace\fP was called:
+These functions check the \fB\%NCURSES_TRACE\fP environment variable,
+to set the tracing feature as if \fB\%curses_trace\fP was called:
.RS 4
.PP
filter,
@@ -205,15 +205,15 @@ .SS Initialization
.RE
.SS Command-line Utilities
The command-line utilities such as \fBtic\fP(1) provide a verbose option
-which extends the set of messages written using the \fBcurses_trace\fP
function.
-Both of these (\fB\-v\fP and \fBcurses_trace\fP)
-use the same variable (\fB_nc_tracing\fP),
+which extends the set of messages written using the \fB\%curses_trace\fP
function.
+Both of these (\fB\-v\fP and \fB\%curses_trace\fP)
+use the same variable (\fB\%_nc_tracing\fP),
which determines the messages which are written.
.PP
Because the command-line utilities may call initialization functions
-such as \fBsetupterm\fP, \fBtgetent\fP or \fBuse_extended_names\fP,
+such as \fB\%setupterm\fP, \fB\%tgetent\fP or \fB\%use_extended_names\fP,
some of their debugging output may be directed to the \fItrace\fP file
-if the \fBNCURSES_TRACE\fP environment variable is set:
+if the \fB\%NCURSES_TRACE\fP environment variable is set:
.bP
messages produced in the utility are written to the standard error.
.bP
@@ -223,23 +223,23 @@ .SS Command-line Utilities
and fewer diagnostics are provided by the command-line utilities.
.SH RETURN VALUE
Routines which return a value are designed to be used as parameters
-to the \fB_tracef\fP routine.
+to the \fB\%_tracef\fP routine.
.SH PORTABILITY
These functions are not part of the XSI interface.
Some other curses implementations are known to
have similar features,
but they are not compatible with ncurses:
.bP
-SVr4 provided \fBtraceon\fP and \fBtraceoff\fP,
+SVr4 provided \fB\%traceon\fP and \fB\%traceoff\fP,
to control whether debugging information was written
to the \*(``trace\*('' file.
While the functions were always available,
this feature was only enabled
-if \fBDEBUG\fP was defined when building the library.
+if \fB\%DEBUG\fP was defined when building the library.
.IP
The SVr4 tracing feature is undocumented.
.bP
-PDCurses provides \fBtraceon\fP and \fBtraceoff\fP,
+PDCurses provides \fB\%traceon\fP and \fB\%traceoff\fP,
which (like SVr4) are always available,
and enable tracing
to the \*(``trace\*('' file
@@ -254,8 +254,8 @@ .SH PORTABILITY
.bP
NetBSD does not provide functions for enabling/disabling traces.
It uses environment variables
-\fBCURSES_TRACE_MASK\fP and
-\fBCURSES_TRACE_FILE\fP to determine what is traced,
+\fB\%CURSES_TRACE_MASK\fP and
+\fB\%CURSES_TRACE_FILE\fP to determine what is traced,
and where the results are written.
This is available only when a debug-library is built.
.IP
@@ -272,4 +272,4 @@ .SH PORTABILITY
The original \fBtrace\fP routine was deprecated because
it often conflicted with application names.
.SH SEE ALSO
-\fBcurses\fP(3X).
+\fB\%curses\fP(3X).
diff --git a/man/curs_util.3x b/man/curs_util.3x
index 25898333..575a5f10 100644
--- a/man/curs_util.3x
+++ b/man/curs_util.3x
@@ -78,7 +78,7 @@ .SH SYNOPSIS
.fi
.SH DESCRIPTION
.SS unctrl
-The \fBunctrl\fP routine returns a character string which is a printable
+The \fB\%unctrl\fP routine returns a character string which is a printable
representation of the character \fIc\fP:
.bP
Printable characters are displayed as themselves,
@@ -98,18 +98,18 @@ .SS unctrl
In the latter case, the values may not be printable;
this follows the X/Open specification.
.PP
-The corresponding \fBwunctrl\fP returns a printable representation of
+The corresponding \fB\%wunctrl\fP returns a printable representation of
a complex character \fIc\fP.
.PP
-In both \fBunctrl\fP and \fBwunctrl\fP the attributes and color associated
+In both \fB\%unctrl\fP and \fB\%wunctrl\fP the attributes and color associated
with the character parameter are ignored.
.SS keyname/key_name
-The \fBkeyname\fP routine returns a character string
+The \fB\%keyname\fP routine returns a character string
corresponding to the key \fIc\fP.
Key codes are different from character codes.
.bP
Key codes below 256 are characters.
-They are displayed using \fBunctrl\fP.
+They are displayed using \fB\%unctrl\fP.
.bP
Values above 256 may be the codes for function keys.
The function key name is displayed.
@@ -119,19 +119,19 @@ .SS keyname/key_name
X/Open also lists an \*(``UNKNOWN KEY\*('' return value,
which some implementations return rather than null.
.LP
-The corresponding \fBkey_name\fP returns
+The corresponding \fB\%key_name\fP returns
a multibyte character string corresponding
to the wide-character value \fIw\fP.
-The two functions (\fBkeyname\fP and \fBkey_name\fP)
+The two functions (\fB\%keyname\fP and \fB\%key_name\fP)
do not return the same set of strings:
.bP
-\fBkeyname\fP returns null where \fBkey_name\fP would display a meta character.
+\fB\%keyname\fP returns null where \fB\%key_name\fP would display a meta
character.
.bP
-\fBkey_name\fP does not return the name of a function key.
+\fB\%key_name\fP does not return the name of a function key.
.SS filter/nofilter
-The \fBfilter\fP routine, if used, must be called before \fBinitscr\fP or
-\fBnewterm\fP are called.
-Calling \fBfilter\fP causes these changes in initialization:
+The \fB\%filter\fP routine, if used, must be called before \fB\%initscr\fP or
+\fB\%newterm\fP are called.
+Calling \fB\%filter\fP causes these changes in initialization:
.bP
\fBLINES\fP is set to 1;
.bP
@@ -149,46 +149,46 @@ .SS filter/nofilter
.bP
and the \fBhome\fP string is set to the value of \fBcr\fP.
.PP
-The \fBnofilter\fP routine cancels the effect of a preceding \fBfilter\fP
+The \fB\%nofilter\fP routine cancels the effect of a preceding \fB\%filter\fP
call.
That allows the caller to initialize a screen on a different device,
using a different value of \fB$TERM\fP.
-The limitation arises because the \fBfilter\fP routine modifies the
+The limitation arises because the \fB\%filter\fP routine modifies the
in-memory copy of the terminal information.
.SS use_env
-The \fBuse_env\fP routine, if used,
-should be called before \fBinitscr\fP or
-\fBnewterm\fP are called
+The \fB\%use_env\fP routine, if used,
+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
when determining the screen size.
.bP
Normally \fBncurses\fP looks first at the terminal database for the screen
size.
.IP
-If \fBuse_env\fP was called with \fBFALSE\fP for parameter,
+If \fB\%use_env\fP was called with \fBFALSE\fP for parameter,
it stops here unless
-\fBuse_tioctl\fP was also called with \fBTRUE\fP for parameter.
+\fB\%use_tioctl\fP was also called with \fBTRUE\fP for parameter.
.bP
Then it asks for the screen size via operating system calls.
If successful,
it overrides the values from the terminal database.
.bP
-Finally (unless \fBuse_env\fP was called with \fBFALSE\fP parameter),
-\fBncurses\fP examines the \fBLINES\fP or \fBCOLUMNS\fP environment variables,
+Finally (unless \fB\%use_env\fP was called with \fBFALSE\fP parameter),
+\fBncurses\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 \fBSIGWINCH\fP,
-unless overridden by the \fBLINES\fP or \fBCOLUMNS\fP environment variables,
+\fBNcurses\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 \fBuse_tioctl\fP routine, if used,
-should be called before \fBinitscr\fP or \fBnewterm\fP are called
+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 \fBuse_tioctl\fP is called with \fBTRUE\fP as an argument,
+After \fB\%use_tioctl\fP is called with \fBTRUE\fP as an argument,
\fBncurses\fP modifies the last step in its computation
of screen size as follows:
.bP
-checks if the \fBLINES\fP and \fBCOLUMNS\fP environment variables
+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
@@ -198,7 +198,7 @@ .SS use_tioctl
\fBncurses\fP re-fetches the value of the environment variables so that
it is still the environment variables which set the screen size.
.PP
-The \fBuse_env\fP and \fBuse_tioctl\fP routines combine as
+The \fB\%use_env\fP and \fB\%use_tioctl\fP routines combine as
summarized here:
.PP
.TS
@@ -224,23 +224,23 @@ .SS use_tioctl
T}
.TE
.SS putwin/getwin
-The \fBputwin\fP routine writes all data associated
+The \fB\%putwin\fP routine writes all data associated
with window (or pad) \fIwin\fP into
the file to which \fIfilep\fP points.
This information can be later retrieved
-using the \fBgetwin\fP function.
+using the \fB\%getwin\fP function.
.PP
-The \fBgetwin\fP routine reads window related data stored in the file by
-\fBputwin\fP.
+The \fB\%getwin\fP routine reads window related data stored in the file by
+\fB\%putwin\fP.
The routine then creates and initializes a new window using that
data.
It returns a pointer to the new window.
There are a few caveats:
.bP
-the data written is a copy of the \fBWINDOW\fP structure,
+the data written is a copy of the \fB\%WINDOW\fP structure,
and its associated character cells.
-The format differs between the wide-character (\fBncursesw\fP) and
-non-wide (\fBncurses\fP) libraries.
+The format differs between the wide-character (\fB\%ncursesw\fP) and
+non-wide (\fB\%ncurses\fP) libraries.
You can transfer data between the two, however.
.bP
the retrieved window is always created as a top-level window (or pad),
@@ -249,20 +249,20 @@ .SS putwin/getwin
the window's character cells contain the color pair \fIvalue\fP,
but not the actual color \fInumbers\fP.
If cells in the retrieved window use color pairs which have not been
-created in the application using \fBinit_pair\fP,
+created in the application using \fB\%init_pair\fP,
they will not be colored when the window is refreshed.
.SS delay_output
-The \fBdelay_output\fP routine inserts an \fIms\fP millisecond pause
+The \fB\%delay_output\fP routine inserts an \fIms\fP millisecond pause
in output.
This routine should not be used extensively because
padding characters are used rather than a CPU pause.
If no padding character is specified,
-this uses \fBnapms\fP to perform the delay.
+this uses \fB\%napms\fP to perform the delay.
.SS flushinp
-The \fBflushinp\fP routine throws away any typeahead that has been typed by the
+The \fB\%flushinp\fP routine throws away any typeahead that has been typed by
the
user and has not yet been read by the program.
.SH RETURN VALUE
-Except for \fBflushinp\fP, routines that return an integer return \fBERR\fP
+Except for \fB\%flushinp\fP, routines that return an integer return \fBERR\fP
upon failure and \fBOK\fP (SVr4 specifies only "an integer value other than
\fBERR\fP") upon successful completion.
.PP
@@ -280,12 +280,12 @@ .SH RETURN VALUE
.RE
.SH PORTABILITY
.SS filter
-The SVr4 documentation describes the action of \fBfilter\fP only in the vaguest
+The SVr4 documentation describes the action of \fB\%filter\fP only in the
vaguest
terms.
The description here is adapted from the XSI Curses standard (which
erroneously fails to describe the disabling of \fBcuu\fP).
.SS keyname
-The \fBkeyname\fP function may return the names of user-defined
+The \fB\%keyname\fP function may return the names of user-defined
string capabilities which are defined in the terminfo entry via the \fB\-x\fP
option of \fB@TIC@\fP.
This implementation automatically assigns at run-time keycodes to
@@ -293,15 +293,15 @@ .SS keyname
The keycodes 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 \fBuse_extended_names\fP(3X) function controls whether this data is
+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 \fBnofilter\fP and \fBuse_tioctl\fP routines are specific to \fBncurses\fP.
+The \fB\%nofilter\fP and \fB\%use_tioctl\fP routines are specific to
\fBncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
It is recommended that any code depending on \fBncurses\fP extensions
-be conditioned using \fBNCURSES_VERSION\fP.
+be conditioned using \fB\%NCURSES_VERSION\fP.
.SS putwin/getwin file-format
-The \fBputwin\fP and \fBgetwin\fP functions have several issues with
+The \fB\%putwin\fP and \fB\%getwin\fP functions have several issues with
portability:
.bP
The files written and read by these functions
@@ -310,12 +310,12 @@ .SS putwin/getwin file-format
it has been overlooked.
.IP
Interestingly enough, according to the copyright dates in Solaris source,
-the functions (along with \fBscr_init\fP, etc.) originated with
+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.
.bP
-Most implementations simply dump the binary \fBWINDOW\fP structure to the file.
+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.
This implementation
@@ -332,7 +332,7 @@ .SS putwin/getwin file-format
However, reading from a file written using mixed schemes may not be successful.
.SS unctrl/wunctrl
The XSI Curses standard, Issue 4 describes these functions.
-It states that \fBunctrl\fP and \fBwunctrl\fP will return a null pointer if
+It states that \fB\%unctrl\fP and \fB\%wunctrl\fP will return a null pointer if
unsuccessful, but does not define any error conditions.
This implementation checks for three cases:
.bP
@@ -340,21 +340,21 @@ .SS unctrl/wunctrl
This is the case that X/Open Curses documented.
.bP
the parameter is in the range 128\-159, i.e., a C1 control code.
-If \fBuse_legacy_coding\fP(3X) has been called with a \fB2\fP parameter,
-\fBunctrl\fP returns the parameter, i.e., a one-character string with
+If \fB\%use_legacy_coding\fP(3X) has been called with a \fB2\fP parameter,
+\fB\%unctrl\fP returns the parameter, i.e., a one-character string with
the parameter as the first character.
Otherwise, it returns \*(``~@\*('', \*(``~A\*('', etc.,
analogous to \*(``^@\*('', \*(``^A\*('', C0 controls.
.IP
-X/Open Curses does not document whether \fBunctrl\fP can be called before
+X/Open Curses does not document whether \fB\%unctrl\fP can be called before
initializing curses.
This implementation permits that,
and returns the \*(``~@\*('', etc., values in that case.
.bP
parameter values outside the 0 to 255 range.
-\fBunctrl\fP returns a null pointer.
+\fB\%unctrl\fP returns a null pointer.
.PP
-The strings returned by \fBunctrl\fP in this implementation are determined
+The strings returned by \fB\%unctrl\fP in this implementation are determined
at compile time,
showing C1 controls from the upper-128 codes
with a \*(``~\*('' prefix rather than \*(``^\*(''.
@@ -365,38 +365,38 @@ .SS unctrl/wunctrl
printable.
This implementation uses 8 bits but does not modify the string to reflect
locale.
-The \fBuse_legacy_coding\fP(3X) function allows the caller to
-change the output of \fBunctrl\fP.
+The \fB\%use_legacy_coding\fP(3X) function allows the caller to
+change the output of \fB\%unctrl\fP.
.PP
Likewise, the \fBmeta\fP(3X) function allows the caller to change the
-output of \fBkeyname\fP, i.e.,
+output of \fB\%keyname\fP, i.e.,
it determines whether to use the \*(``M\-\*('' prefix
for \*(``meta\*('' keys (codes in the range 128 to 255).
-Both \fBuse_legacy_coding\fP(3X) and \fBmeta\fP(3X) succeed only after
+Both \fB\%use_legacy_coding\fP(3X) and \fBmeta\fP(3X) succeed only after
curses is initialized.
X/Open Curses does not document the treatment of codes 128 to 159.
When treating them as \*(``meta\*('' keys
-(or if \fBkeyname\fP is called before initializing curses),
+(or if \fB\%keyname\fP is called before initializing curses),
this implementation returns strings \*(``M\-^@\*('', \*(``M\-^A\*('', etc.
.PP
-X/Open Curses documents \fBunctrl\fP as declared in \fB<unctrl.h>\fP,
+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.
Other implementations may not do that.
.SS use_env/use_tioctl
If \fBncurses\fP is configured to provide the sp-functions extension,
-the state of \fBuse_env\fP and \fBuse_tioctl\fP may be updated before
+the state of \fB\%use_env\fP and \fB\%use_tioctl\fP may be updated before
creating each \fIscreen\fP rather than once only
-(\fBcurs_sp_funcs\fP(3X)).
-This feature of \fBuse_env\fP
+(\fB\%curs_sp_funcs\fP(3X)).
+This feature of \fB\%use_env\fP
is not provided by other implementations of curses.
.SH SEE ALSO
-\fBcurses\fP(3X),
-\fBcurs_initscr\fP(3X),
-\fBcurs_inopts\fP(3X),
-\fBcurs_kernel\fP(3X),
-\fBcurs_scr_dump\fP(3X),
-\fBcurs_sp_funcs\fP(3X),
-\fBcurs_variables\fP(3X),
-\fBlegacy_coding\fP(3X).
+\fB\%curses\fP(3X),
+\fB\%curs_initscr\fP(3X),
+\fB\%curs_inopts\fP(3X),
+\fB\%curs_kernel\fP(3X),
+\fB\%curs_scr_dump\fP(3X),
+\fB\%curs_sp_funcs\fP(3X),
+\fB\%curs_variables\fP(3X),
+\fB\%legacy_coding\fP(3X).
diff --git a/man/define_key.3x b/man/define_key.3x
index 56468db6..42c9cfe0 100644
--- a/man/define_key.3x
+++ b/man/define_key.3x
@@ -59,9 +59,9 @@ .SH PORTABILITY
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
-any code depending on them be conditioned using \fBNCURSES_VERSION\fP.
+any code depending on them be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
-\fBkeyok\fP(3X),
-\fBkey_defined\fP(3X).
+\fB\%keyok\fP(3X),
+\fB\%key_defined\fP(3X).
.SH AUTHOR
Thomas Dickey.
diff --git a/man/key_defined.3x b/man/key_defined.3x
index d63c9b8e..44bff5be 100644
--- a/man/key_defined.3x
+++ b/man/key_defined.3x
@@ -52,8 +52,8 @@ .SH PORTABILITY
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
-any code depending on them be conditioned using \fBNCURSES_VERSION\fP.
+any code depending on them be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
-\fBdefine_key\fP(3X).
+\fB\%define_key\fP(3X).
.SH AUTHOR
Thomas Dickey.
diff --git a/man/keybound.3x b/man/keybound.3x
index e63dfa86..f1af8963 100644
--- a/man/keybound.3x
+++ b/man/keybound.3x
@@ -54,9 +54,9 @@ .SH PORTABILITY
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
-any code depending on them be conditioned using \fBNCURSES_VERSION\fP.
+any code depending on them be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
-\fBdefine_key\fP(3X),
-\fBkeyok\fP(3X).
+\fB\%define_key\fP(3X),
+\fB\%keyok\fP(3X).
.SH AUTHOR
Thomas Dickey.
diff --git a/man/keyok.3x b/man/keyok.3x
index c330aa4c..a46fb84b 100644
--- a/man/keyok.3x
+++ b/man/keyok.3x
@@ -41,7 +41,7 @@ .SH SYNOPSIS
.SH DESCRIPTION
This is an extension to the curses library.
It permits an application to disable specific keycodes, rather than
-use the \fBkeypad\fP function to disable all keycodes.
+use the \fB\%keypad\fP function to disable all keycodes.
Keys that have been disabled can be re-enabled.
.SH RETURN VALUE
The keycode must be greater than zero, else \fBERR\fP is returned.
@@ -54,8 +54,8 @@ .SH PORTABILITY
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
-any code depending on them be conditioned using \fBNCURSES_VERSION\fP.
+any code depending on them be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
-\fBdefine_key\fP(3X).
+\fB\%define_key\fP(3X).
.SH AUTHOR
Thomas Dickey.
diff --git a/man/new_pair.3x b/man/new_pair.3x
index 813bd5dc..212e7193 100644
--- a/man/new_pair.3x
+++ b/man/new_pair.3x
@@ -164,7 +164,7 @@ .SH PORTABILITY
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
-any code depending on them be conditioned using \fBNCURSES_VERSION\fP.
+any code depending on them be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
\fBcurs_color\fP(3X).
.SH AUTHOR
diff --git a/man/resizeterm.3x b/man/resizeterm.3x
index 9b622341..9c38f75a 100644
--- a/man/resizeterm.3x
+++ b/man/resizeterm.3x
@@ -61,61 +61,61 @@ .SH DESCRIPTION
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 \fBSIGWINCH\fP
+If the calling program has not set up a handler for \fB\%SIGWINCH\fP
when it initializes \fBncurses\fP
-(e.g., using \fBinitscr\fP(3X) or \fBnewterm\fP(3X)),
-then \fBncurses\fP sets a handler for \fBSIGWINCH\fP which notifies
+(e.g., using \fB\%initscr\fP(3X) or \fB\%newterm\fP(3X)),
+then \fBncurses\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
when reading input data,
.bP
when implicitly resuming program mode
-(e.g., between \fBendwin\fP(3X) and \fBwrefresh\fP(3X)),
+(e.g., between \fB\%endwin\fP(3X) and \fB\%wrefresh\fP(3X)),
and
.bP
-when explicitly resuming program mode in \fBrestartterm\fP(3X).
+when explicitly resuming program mode in \fB\%restartterm\fP(3X).
.PP
When the library has found that the terminal's window-size has
-changed, it calls \fBresizeterm\fP to update its data structures.
+changed, it calls \fB\%resizeterm\fP to update its data structures.
.PP
-An application which establishes its own \fBSIGWINCH\fP handler
-can call \fBresizeterm\fP, but in that case, the library will not
-see \fBSIGWINCH\fP, and proper layout will rely upon the application.
+An application which establishes its own \fB\%SIGWINCH\fP handler
+can call \fB\%resizeterm\fP, but in that case, the library will not
+see \fB\%SIGWINCH\fP, and proper layout will rely upon the application.
.SH FUNCTIONS
.SS resizeterm
-The function \fBresizeterm\fP resizes the standard and current windows
-(i.e., \fBstdscr\fP and \fBcurscr\fP)
+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 \fBncurses\fP library that record the window dimensions
-such as the \fBLINES\fP and \fBCOLS\fP variables.
+the \fB\%ncurses\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 \fBresizeterm\fP is
-done by the inner function \fBresize_term\fP.
-The outer function \fBresizeterm\fP adds bookkeeping
-for the \fBSIGWINCH\fP handler,
-as well as repainting the soft-key area (see \fBslk_touch\fP(3X)).
+Most of the work for \fB\%resizeterm\fP is
+done by the inner function \fB\%resize_term\fP.
+The outer function \fB\%resizeterm\fP adds bookkeeping
+for the \fB\%SIGWINCH\fP handler,
+as well as repainting the soft-key area (see \fB\%slk_touch\fP(3X)).
.PP
-The \fBresize_term\fP function attempts to resize all windows.
+The \fB\%resize_term\fP function attempts to resize all windows.
This helps with simple applications.
However:
.bP
It is not possible to automatically resize pads.
.bP
Applications which have complicated layouts should check for
-\fBKEY_RESIZE\fP returned from \fBwgetch\fP,
-and adjust their layout, e.g., using \fBwresize\fP and \fBmvwin\fP,
+\fB\%KEY_RESIZE\fP returned from \fB\%wgetch\fP,
+and adjust their layout, e.g., using \fB\%wresize\fP and \fB\%mvwin\fP,
or by recreating the windows.
.PP
-When resizing windows, \fBresize_term\fP recursively adjusts subwindows,
+When resizing windows, \fB\%resize_term\fP recursively adjusts subwindows,
keeping them within the updated parent window's limits.
If a top-level window happens to extend to the screen's limits,
-then on resizing the window, \fBresize_term\fP will keep the window
+then on resizing the window, \fB\%resize_term\fP will keep the window
extending to the corresponding limit, regardless of whether the
screen has shrunk or grown.
.SS is_term_resized
-A support function \fBis_term_resized\fP is provided so that applications
-can check if the \fBresize_term\fP function would modify the window structures.
+A support function \fB\%is_term_resized\fP is provided so that applications
+can check if the \fB\%resize_term\fP function would modify the window
structures.
It returns \fBTRUE\fP if the windows would be modified,
and \fBFALSE\fP otherwise.
.SH RETURN VALUE
@@ -125,53 +125,53 @@ .SH RETURN VALUE
or if an error occurs while (re)allocating memory for the windows.
.SH NOTES
While these functions are intended to be used to support a signal handler
-(i.e., for \fBSIGWINCH\fP), care should be taken to avoid invoking them in a
-context where \fBmalloc\fP or \fBrealloc\fP may have been interrupted,
+(i.e., for \fB\%SIGWINCH\fP), care should be taken to avoid invoking them in a
+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 \fBSIGWINCH\fP handler,
+If ncurses is configured to supply its own \fB\%SIGWINCH\fP handler,
.bP
-on receipt of a \fBSIGWINCH\fP, the handler sets a flag
+on receipt of a \fB\%SIGWINCH\fP, the handler sets a flag
.bP
which is tested in
-\fBwgetch\fP(3X),
-\fBdoupdate\fP(3X) and
-\fBrestartterm\fP(3X),
+\fB\%wgetch\fP(3X),
+\fB\%doupdate\fP(3X) and
+\fB\%restartterm\fP(3X),
.bP
-in turn, calling the \fBresizeterm\fP function,
+in turn, calling the \fB\%resizeterm\fP function,
.bP
-which \fBungetch\fP's a \fBKEY_RESIZE\fP which
-will be read on the next call to \fBwgetch\fP.
+which \fB\%ungetch\fP's a \fB\%KEY_RESIZE\fP which
+will be read on the next call to \fB\%wgetch\fP.
.IP
-The \fBKEY_RESIZE\fP alerts an application that the screen size has changed,
+The \fB\%KEY_RESIZE\fP alerts an application that the screen size has changed,
and that it should repaint special features such as pads that cannot
be done automatically.
.IP
-Calling \fBresizeterm\fP or \fBresize_term\fP
+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
data structures.
.PP
-If the environment variables \fBLINES\fP or \fBCOLUMNS\fP are set,
+If the environment variables \fB\%LINES\fP or \fB\%COLUMNS\fP are set,
this overrides the library's use of the window size obtained from
the operating system.
-Thus, even if a \fBSIGWINCH\fP is received,
+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,
by
.bP
-exiting curses with \fBendwin\fP(3X) and
+exiting curses with \fB\%endwin\fP(3X) and
.bP
-resuming using \fBrefresh\fP(3X).
+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).
.SH SEE ALSO
-\fBcurs_getch\fP(3X),
-\fBcurs_variables\fP(3X),
-\fBwresize\fP(3X).
+\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).
--
2.30.2
signature.asc
Description: PGP signature
- [PATCH v2 04/18] Protect literals from hyphenation.,
G. Branden Robinson <=