[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH 03/42] Style "ncurses" consistently.
|
From: |
G. Branden Robinson |
|
Subject: |
[PATCH 03/42] Style "ncurses" consistently. |
|
Date: |
Sat, 16 Dec 2023 11:40:47 -0600 |
Set it in italics, not roman or bold (except in man page cross
references), and protect it from hyphenation. Don't capitalize it,
either, even at the beginning of a sentence.
When doing so results in an excessively long input line, break it,
preferring commas and multi-word parentheticals as break points,
backtracking within a sentence if necessary.
* man/MKada_config.in:
* man/MKncu_config.in:
* man/clear.1:
* man/curs_add_wch.3x:
* man/curs_addch.3x:
* man/curs_attr.3x:
* man/curs_clear.3x:
* man/curs_color.3x:
* man/curs_extend.3x:
* man/curs_get_wstr.3x:
* man/curs_getcchar.3x:
* man/curs_getch.3x:
* man/curs_getstr.3x:
* man/curs_getyx.3x:
* man/curs_initscr.3x:
* man/curs_inopts.3x:
* man/curs_instr.3x:
* man/curs_kernel.3x:
* man/curs_memleaks.3x:
* man/curs_mouse.3x:
* man/curs_opaque.3x:
* man/curs_outopts.3x:
* man/curs_print.3x:
* man/curs_scanw.3x:
* man/curs_slk.3x:
* man/curs_sp_funcs.3x:
* man/curs_termcap.3x:
* man/curs_terminfo.3x:
* man/curs_threads.3x:
* man/curs_trace.3x:
* man/curs_util.3x:
* man/curs_variables.3x:
* man/curs_window.3x:
* man/default_colors.3x:
* man/define_key.3x:
* man/infocmp.1m:
* man/key_defined.3x:
* man/keybound.3x:
* man/keyok.3x:
* man/ncurses.3x:
* man/new_pair.3x:
* man/panel.3x:
* man/resizeterm.3x:
* man/scr_dump.5:
* man/term.5:
* man/terminfo.head:
* man/terminfo.tail:
* man/toe.1m:
* man/tset.1:
* man/user_caps.5: Do it.
---
man/MKada_config.in | 4 +-
man/MKncu_config.in | 28 ++---
man/clear.1 | 11 +-
man/curs_add_wch.3x | 11 +-
man/curs_addch.3x | 14 ++-
man/curs_attr.3x | 19 ++--
man/curs_clear.3x | 2 +-
man/curs_color.3x | 22 ++--
man/curs_extend.3x | 2 +-
man/curs_get_wstr.3x | 4 +-
man/curs_getcchar.3x | 2 +-
man/curs_getch.3x | 16 +--
man/curs_getstr.3x | 22 ++--
man/curs_getyx.3x | 2 +-
man/curs_initscr.3x | 10 +-
man/curs_inopts.3x | 21 ++--
man/curs_instr.3x | 4 +-
man/curs_kernel.3x | 8 +-
man/curs_memleaks.3x | 12 +-
man/curs_mouse.3x | 16 +--
man/curs_opaque.3x | 8 +-
man/curs_outopts.3x | 11 +-
man/curs_print.3x | 7 +-
man/curs_scanw.3x | 3 +-
man/curs_slk.3x | 8 +-
man/curs_sp_funcs.3x | 7 +-
man/curs_termcap.3x | 25 +++--
man/curs_terminfo.3x | 29 ++---
man/curs_threads.3x | 24 ++--
man/curs_trace.3x | 17 +--
man/curs_util.3x | 47 ++++----
man/curs_variables.3x | 15 +--
man/curs_window.3x | 5 +-
man/default_colors.3x | 8 +-
man/define_key.3x | 5 +-
man/form.3x | 9 +-
man/form_field_buffer.3x | 2 +-
man/form_field_validation.3x | 2 +-
man/form_page.3x | 3 +-
man/form_requestname.3x | 2 +-
man/infocmp.1m | 21 ++--
man/key_defined.3x | 2 +-
man/keybound.3x | 2 +-
man/keyok.3x | 2 +-
man/legacy_coding.3x | 4 +-
man/menu.3x | 4 +-
man/menu_driver.3x | 2 +-
man/menu_requestname.3x | 2 +-
man/menu_spacing.3x | 2 +-
man/ncurses.3x | 207 ++++++++++++++++++++---------------
man/new_pair.3x | 4 +-
man/panel.3x | 2 +-
man/resizeterm.3x | 18 +--
man/scr_dump.5 | 8 +-
man/tabs.1 | 3 +-
man/term.5 | 41 ++++---
man/terminfo.head | 2 +-
man/terminfo.tail | 74 +++++++------
man/tic.1m | 30 ++---
man/toe.1m | 6 +-
man/tput.1 | 26 +++--
man/tset.1 | 7 +-
man/user_caps.5 | 75 +++++++------
63 files changed, 561 insertions(+), 450 deletions(-)
diff --git a/man/MKada_config.in b/man/MKada_config.in
index 2b5fabe6e..9fd60d513 100644
--- a/man/MKada_config.in
+++ b/man/MKada_config.in
@@ -57,7 +57,7 @@ configuration helper for \fI@ADA_LIBNAME@\fP libraries
.SH DESCRIPTION
This program development aid simplifies the process of configuring
applications to use the \fI@ADA_LIBNAME@\fP library binding to
-\fIncurses\fP.
+\fI\%ncurses\fP.
.SH OPTIONS
.TP 11 \" "--version" + 2n
\fB\-\-cflags\fP
@@ -68,7 +68,7 @@ reports the GNAT (Ada compiler) flags needed to compile with
reports the GNAT libraries needed to link with \fI@ADA_LIBNAME@\fP.
.TP
\fB\-\-version\fP
-reports the release and patch date information of the \fIncurses\fP
+reports the release and patch date information of the \fI\%ncurses\fP
libraries used to configure and build \fI@ADA_LIBNAME@\fP and exits
successfully.
.TP
diff --git a/man/MKncu_config.in b/man/MKncu_config.in
index fb72802b0..2aa221e4e 100644
--- a/man/MKncu_config.in
+++ b/man/MKncu_config.in
@@ -31,7 +31,7 @@
.TH @LIB_NAME@@DFT_ARG_SUFFIX@@cf_cv_abi_version@-config 1 2023-12-02 "ncurses
@NCURSES_MAJOR@.@NCURSES_MINOR@" "User commands"
.SH NAME
\fB\%@LIB_NAME@@DFT_ARG_SUFFIX@@cf_cv_abi_version@-config\fP \-
-configuration helper for \fIncurses\fR libraries
+configuration helper for \fI\%ncurses\fP libraries
.SH SYNOPSIS
.B @LIB_NAME@@DFT_ARG_SUFFIX@@cf_cv_abi_version@-config
.I option
@@ -42,45 +42,45 @@ configuration helper for \fIncurses\fR libraries
.B "@LIB_NAME@@DFT_ARG_SUFFIX@@cf_cv_abi_version@-config \-\-help"
.SH DESCRIPTION
This program development aid simplifies the process of configuring
-applications against a particular set of \fIncurses\fP libraries.
+applications against a particular set of \fI\%ncurses\fP libraries.
.SH OPTIONS
.TP 18 \" "--mouse-version" + 2n + adjustment for PDF
\fB\-\-prefix\fP
-reports the package prefix of \fIncurses\fP.
+reports the package prefix of \fI\%ncurses\fP.
.TP
\fB\-\-exec\-prefix\fP
-reports the executable prefix of \fIncurses\fP.
+reports the executable prefix of \fI\%ncurses\fP.
.TP
\fB\-\-cflags\fP
-reports the C compiler flags needed to compile with \fIncurses\fP.
+reports the C compiler flags needed to compile with \fI\%ncurses\fP.
.TP
\fB\-\-libs\fP
-reports the libraries needed to link with \fIncurses\fP.
+reports the libraries needed to link with \fI\%ncurses\fP.
.TP
\fB\-\-version\fP
-reports the release and patch date information of \fIncurses\fP and
+reports the release and patch date information of \fI\%ncurses\fP and
exits successfully.
.TP
\fB\-\-abi\-version\fP
-reports the ABI version of \fIncurses\fP.
+reports the ABI version of \fI\%ncurses\fP.
.TP
\fB\-\-mouse\-version\fP
-reports the mouse\-interface version of \fIncurses\fP.
+reports the mouse\-interface version of \fI\%ncurses\fP.
.TP
\fB\-\-bindir\fP
-reports the directory containing \fIncurses\fP programs.
+reports the directory containing \fI\%ncurses\fP programs.
.TP
\fB\-\-datadir\fP
-reports the directory containing \fIncurses\fP data.
+reports the directory containing \fI\%ncurses\fP data.
.TP
\fB\-\-includedir\fP
-reports the directory containing \fIncurses\fP header files.
+reports the directory containing \fI\%ncurses\fP header files.
.TP
\fB\-\-libdir\fP
-reports the directory containing \fIncurses\fP libraries.
+reports the directory containing \fI\%ncurses\fP libraries.
.TP
\fB\-\-mandir\fP
-reports the directory containing \fIncurses\fP man pages.
+reports the directory containing \fI\%ncurses\fP man pages.
.TP
\fB\-\-terminfo\fP
reports the \fI\%TERMINFO\fP \fIterminfo\fP database path,
diff --git a/man/clear.1 b/man/clear.1
index 23d31bdf9..61956feb5 100644
--- a/man/clear.1
+++ b/man/clear.1
@@ -69,7 +69,8 @@ .SH DESCRIPTION
The capabilities to clear the screen and scrollback buffer are named
\*(``clear\*('' and \*(``E3\*('', respectively.
The latter is a \fIuser-defined capability\fP,
-applying an extension mechanism introduced in \fIncurses\fP 5.0 (1999).
+applying an extension mechanism introduced in \fI\%ncurses\fP 5.0
+(1999).
.SH OPTIONS
\fB\%@CLEAR@\fP recognizes the following options.
.TP 9 \" "-T type" + 2n
@@ -84,7 +85,7 @@ .SH OPTIONS
\fI\%COLUMNS\fP as well.
.TP
.B \-V
-reports the version of \fIncurses\fP associated with this program and
+reports the version of \fI\%ncurses\fP associated with this program and
exits with a successful status.
.TP
.B \-x
@@ -132,8 +133,8 @@ .SH HISTORY
The remainder of the script in each case is a copyright notice.
.PP
In 1995,
-\fIncurses\fP's \fBclear\fP began by adapting BSD's original \fBclear\fP
-command to use \fIterminfo\fP.
+\fI\%ncurses\fP's \fBclear\fP began by adapting BSD's original
+\fBclear\fP command to use \fIterminfo\fP.
The \fBE3\fP extension came later.
.bP
In June 1999, \fIxterm\fP provided an extension to the standard control
@@ -171,7 +172,7 @@ .SH HISTORY
.bP
Subsequently,
more terminal developers adopted the feature.
-The next relevant step was to change the \fIncurses\fP \fBclear\fP
+The next relevant step was to change the \fI\%ncurses\fP \fBclear\fP
program in 2013 to incorporate this extension.
.bP
In 2013,
diff --git a/man/curs_add_wch.3x b/man/curs_add_wch.3x
index a07570702..c2a765bd3 100644
--- a/man/curs_add_wch.3x
+++ b/man/curs_add_wch.3x
@@ -165,7 +165,7 @@ .SS Line Graphics
WACS_VLINE 0x2502 | x vertical line
.TE
.PP
-The wide-character configuration of ncurses also defines symbols
+The wide-character configuration of \fI\%ncurses\fP also defines symbols
for thick lines (\fBacsc\fP \*(``J\*('' to \*(``V\*(''):
.PP
.TS
@@ -210,7 +210,8 @@ .SS Line Graphics
WACS_D_VLINE 0x2551 | Y double vertical line
.TE
.PP
-Unicode's descriptions for these characters differs slightly from ncurses,
+Unicode's descriptions for these characters differs slightly from
+\fI\%ncurses\fP,
by introducing the term \*(``light\*('' (along with less important details).
Here are its descriptions for the normal, thick, and double horizontal lines:
.bP
@@ -282,7 +283,8 @@ .SS WACS Symbols
use only the \fBacsc\fP character-mapping to provide this feature.
As a result, those implementations can only use single-byte line-drawing
characters.
-Ncurses 5.3 (2002) provided a table of Unicode values to solve these problems.
+\fI\%ncurses\fP 5.3 (2002) provided a table of Unicode values to solve
+these problems.
NetBSD curses incorporated that table in 2010.
.PP
In this implementation, the Unicode values are used instead of the
@@ -347,7 +349,8 @@ .SS Complex Characters
.bP
may hold one non-spacing character.
.PP
-In the latter case, ncurses adds the non-spacing character to the active
+In the latter case,
+\fI\%ncurses\fP adds the non-spacing character to the active
(base) spacing character.
.SH SEE ALSO
\fB\%curses\fP(3X),
diff --git a/man/curs_addch.3x b/man/curs_addch.3x
index 79b7eb1af..48436acb5 100644
--- a/man/curs_addch.3x
+++ b/man/curs_addch.3x
@@ -258,7 +258,9 @@ .SS ACS Symbols
The \fIdisplayed\fP values for the \fBACS_\fP and \fBWACS_\fP constants
depend on
.bP
-the library configuration, i.e., \fBncurses\fP versus \fBncursesw\fP,
+the library configuration,
+i.e.,
+\fI\%ncurses\fP versus \fI\%ncursesw\fP,
where the latter is capable of displaying Unicode while the former is not, and
.bP
whether the \fIlocale\fP uses UTF-8 encoding.
@@ -279,22 +281,22 @@ .SS Character Set
to pass to \fBwaddch\fP.
.PP
In this implementation, \fBchtype\fP holds an eight-bit character.
-But ncurses allows multibyte characters to be passed in a succession
-of calls to \fBwaddch\fP.
+But \fI\%ncurses\fP allows multibyte characters to be passed in a
+succession of calls to \fBwaddch\fP.
The other implementations do not do this;
a call to \fBwaddch\fP passes exactly one character
which may be rendered as one or more cells on the screen
depending on whether it is printable.
.PP
Depending on the locale settings,
-ncurses will inspect the byte passed in each call to \fBwaddch\fP,
+\fI\%ncurses\fP will inspect the byte passed in each call to \fBwaddch\fP,
and check if the latest call will continue a multibyte sequence.
When a character is \fIcomplete\fP,
-ncurses displays the character and moves to the next position in the screen.
+\fI\%ncurses\fP displays the character and moves to the next position in the
screen.
.PP
If the calling application interrupts the succession of bytes in
a multibyte character by moving the current location (e.g., using \fBwmove\fP),
-ncurses discards the partially built character,
+\fI\%ncurses\fP discards the partially built character,
starting over again.
.PP
For portability to other implementations,
diff --git a/man/curs_attr.3x b/man/curs_attr.3x
index 027185ba8..e17e7c4b6 100644
--- a/man/curs_attr.3x
+++ b/man/curs_attr.3x
@@ -176,7 +176,8 @@ .SS Legacy window attributes
.PP
However, if the value does not fit, then the \fBCOLOR_PAIR\fP macro
uses only the bits that fit.
-For example, because in ncurses \fBA_COLOR\fP has eight (8) bits,
+For example,
+because in \fI\%ncurses\fP \fBA_COLOR\fP has eight (8) bits,
then \fBCOLOR_PAIR(\fI259\fB)\fR is 4
(i.e., 259 is 4 more than the limit 255).
.PP
@@ -202,7 +203,7 @@ .SS Legacy window attributes
.PP
There is no corresponding \fB\%attrget\fP function as such
in X/Open Curses,
-although ncurses provides \fB\%getattrs\fP
+although \fI\%ncurses\fP provides \fB\%getattrs\fP
(see \fB\%curs_legacy\fP(3X)).
.\" ---------------------------------------------------------------------------
.SS Change character rendition
@@ -319,9 +320,9 @@ .SH NOTES
number is less than 256.
The alternate functions such as \fBcolor_set\fP can pass a color pair
value directly.
-However, ncurses ABI 4 and 5 simply OR this value
+However, \fI\%ncurses\fP ABI 4 and 5 simply OR this value
within the alternate functions.
-You must use ncurses ABI 6 to support more than 256 color pairs.
+You must use \fI\%ncurses\fP ABI 6 to support more than 256 color pairs.
.\" ---------------------------------------------------------------------------
.SH EXTENSIONS
This implementation provides the \fBA_ITALIC\fP attribute for terminals
@@ -425,7 +426,7 @@ .SH PORTABILITY
the same because it simplifies copying information between
\fBchtype\fP and \fBcchar_t\fP variables.
.bP
-Because ncurses's \fBattr_t\fP can hold a color pair
+Because \fI\%ncurses\fP's \fBattr_t\fP can hold a color pair
(in the \fBA_COLOR\fP field),
a call to
\fBwattr_on\fP,
@@ -536,8 +537,9 @@ .SH HISTORY
Regarding OSF/1 (and Tru64),
.bP
These used 64-bit hardware.
-Like ncurses, the OSF/1 curses interface is not customized for 32-bit
-and 64-bit versions.
+Like \fI\%ncurses\fP,
+the OSF/1 curses interface is not customized for 32-bit and 64-bit
+versions.
.bP
Unlike other systems which evolved from AT&T code,
OSF/1 provided a new implementation for X/Open curses.
@@ -574,7 +576,8 @@ .SH HISTORY
modification to make the library 8-bit clean for \fBnvi\fP(1).
He moved \fIstandout\fP attribute to a structure member.
.IP
-The resulting 4.4BSD curses was replaced by ncurses over the next ten years.
+The resulting 4.4BSD curses was replaced by \fI\%ncurses\fP over the
+next ten years.
.bP
U/Win is rarely used now.
.\" ---------------------------------------------------------------------------
diff --git a/man/curs_clear.3x b/man/curs_clear.3x
index 7349a14ca..978fcb895 100644
--- a/man/curs_clear.3x
+++ b/man/curs_clear.3x
@@ -105,7 +105,7 @@ .SH PORTABILITY
ability to do the equivalent of \fBclearok(..., 1)\fP by saying
\fBtouchwin(stdscr)\fP or \fBclear(stdscr)\fP.
This will not work under
-ncurses.
+\fI\%ncurses\fP.
.PP
This implementation, and others such as Solaris,
sets the current position to 0,0 after erasing
diff --git a/man/curs_color.3x b/man/curs_color.3x
index 20c0fbde6..288201902 100644
--- a/man/curs_color.3x
+++ b/man/curs_color.3x
@@ -282,8 +282,9 @@ .SS init_pair
the screen is refreshed and all occurrences of that color-pair
are changed to the new definition.
.PP
-As an extension, ncurses allows you to set color pair \fB0\fP via
-the \fB\%assume_default_colors\fP(3X) routine, or to specify the use of
+As an extension,
+\fI\%ncurses\fP allows you to set color pair \fB0\fP via 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
\fB\%use_default_colors\fP(3X) routine.
.SS init_extended_pair
@@ -361,8 +362,8 @@ .SS extended_pair_content
for returning the foreground and background colors,
allowing a larger number of colors to be supported.
.SS reset_color_pairs
-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.
+The extension \fB\%reset_color_pairs\fP tells \fI\%ncurses\fP 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
@@ -421,7 +422,8 @@ .SH RETURN VALUE
returns an error if the color table cannot be allocated.
.RE
.SH NOTES
-In the \fIncurses\fP implementation, there is a separate color activation flag,
+In the \fI\%ncurses\fP implementation,
+there is a separate color activation flag,
color palette, color pairs table,
and associated \fB\%COLORS\fP and \fB\%COLOR_PAIRS\fP counts
for each screen; the \fB\%start_color\fP function only affects the current
@@ -449,7 +451,8 @@ .SH NOTES
.bP
Color RGB values are not settable.
.SH 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.
.SH PORTABILITY
@@ -478,7 +481,8 @@ .SH PORTABILITY
which use \fBshort\fP parameters,
allowing applications to use larger color- and pair-numbers.
.PP
-The \fB\%reset_color_pairs\fP function is an extension of ncurses.
+The \fB\%reset_color_pairs\fP function is an extension of
+\fI\%ncurses\fP.
.SH HISTORY
SVr3.2 introduced color support to curses in 1987.
.PP
@@ -507,7 +511,7 @@ .SH HISTORY
Both color-pairs and color-values used a signed \fBshort\fP,
limiting values to 15 bits.
.bP
-ncurses (1992-present) uses eight bits
+\fI\%ncurses\fP (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),
@@ -523,7 +527,7 @@ .SH HISTORY
2000 (when colors were first supported) until 2004.
At that point, NetBSD changed to use 10 bits.
As of 2021, that size is unchanged.
-Like ncurses before version 6,
+Like \fI\%ncurses\fP before version 6,
the NetBSD color-pair information is stored in
the attributes field of \fB\%cchar_t\fP, limiting the number of color-pairs
by the size of the bitfield.
diff --git a/man/curs_extend.3x b/man/curs_extend.3x
index 873870662..a285fcbf1 100644
--- a/man/curs_extend.3x
+++ b/man/curs_extend.3x
@@ -81,7 +81,7 @@ .SH RETURN VALUE
\fBuse_extended_names\fP returns the previous state, allowing you to
save this and restore it.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/curs_get_wstr.3x b/man/curs_get_wstr.3x
index 4ec2c3ec8..37b9eab15 100644
--- a/man/curs_get_wstr.3x
+++ b/man/curs_get_wstr.3x
@@ -208,12 +208,12 @@ .SH PORTABILITY
X/Open Curses does not specify what happens if the length \fIn\fP is negative.
.bP
For analogy with \fBwgetnstr\fP,
-ncurses 6.2 uses a limit (based on \fBLINE_MAX\fP).
+\fI\%ncurses\fP 6.2 uses a limit (based on \fBLINE_MAX\fP).
.bP
Some other implementations (such as Solaris xcurses) do the same,
while others (PDCurses) do not allow this.
.bP
-NetBSD 7 curses imitates ncurses 6.1 in this regard,
+NetBSD 7 curses imitates \fI\%ncurses\fP 6.1 in this regard,
treating a \fB\-1\fP as an indefinite number of characters.
.SH SEE ALSO
\fB\%curses\fP(3X),
diff --git a/man/curs_getcchar.3x b/man/curs_getcchar.3x
index 1f2f74502..636472b49 100644
--- a/man/curs_getcchar.3x
+++ b/man/curs_getcchar.3x
@@ -135,7 +135,7 @@ .SH EXTENSIONS
and used to retrieve the color pair as an \fBint\fP value,
in addition retrieving it via the standard pointer to \fBshort\fP parameter.
.SH PORTABILITY
-The \fBCCHARW_MAX\fP symbol is specific to ncurses.
+The \fBCCHARW_MAX\fP symbol is specific to \fI\%ncurses\fP.
X/Open Curses does not provide details for the layout of the \fBcchar_t\fP
structure.
It tells what data are stored in it:
diff --git a/man/curs_getch.3x b/man/curs_getch.3x
index cf7225b6c..e5035b9fd 100644
--- a/man/curs_getch.3x
+++ b/man/curs_getch.3x
@@ -129,7 +129,7 @@ .SS Keypad mode
For this reason, many terminals experience a delay between the time
a user presses the escape key and the escape is returned to the program.
.PP
-In \fBncurses\fP, the timer normally expires after
+In \fI\%ncurses\fP, the timer normally expires after
the value in \fBESCDELAY\fP (see \fBcurs_variables\fP(3X)).
If \fBnotimeout\fP is \fBTRUE\fP, the timer does not expire;
it is an infinite (or very large) value.
@@ -280,8 +280,10 @@ .SS Predefined key-codes
.B KEY_MOUSE
is returned for mouse-events (see \fBcurs_mouse\fP(3X)).
This code relies upon whether or not \fBkeypad\fP(3X) has been enabled,
-because (e.g., with \fBxterm\fP(1) mouse prototocol) ncurses must
-read escape sequences,
+because
+(e.g.,
+with \fBxterm\fP(1) mouse prototocol)
+\fI\%ncurses\fP must read escape sequences,
just like a function key.
.SS Testing key-codes
The \fBhas_key\fP routine takes a key-code value from the above list, and
@@ -331,7 +333,7 @@ .SH NOTES
Some curses implementations may differ according to whether they
treat these control keys specially (and ignore the terminfo), or
use the terminfo definitions.
-\fBNcurses\fP uses the terminfo definition.
+\fI\%ncurses\fP uses the terminfo definition.
If it says that \fBKEY_ENTER\fP is control/M,
\fBgetch\fP will return \fBKEY_ENTER\fP
when you press control/M.
@@ -391,9 +393,9 @@ .SH PORTABILITY
.PP
\fBKEY_MOUSE\fP is mentioned in XSI Curses, along with a few related
terminfo capabilities, but no higher-level functions use the feature.
-The implementation in ncurses is an extension.
+The implementation in \fI\%ncurses\fP is an extension.
.PP
-\fBKEY_RESIZE\fP is an extension first implemented for ncurses.
+\fBKEY_RESIZE\fP is an extension first implemented for \fI\%ncurses\fP.
NetBSD curses later added this extension.
.PP
Programmers concerned about portability should be prepared for either of two
@@ -401,7 +403,7 @@ .SH PORTABILITY
interrupts \fBgetch\fP and causes it to return \fBERR\fP with \fBerrno\fP set
to
\fBEINTR\fP.
.PP
-The \fBhas_key\fP function is unique to \fBncurses\fP.
+The \fBhas_key\fP function is unique to \fI\%ncurses\fP.
We recommend that
any code using it be conditionalized on the \fBNCURSES_VERSION\fP feature
macro.
.SH SEE ALSO
diff --git a/man/curs_getstr.3x b/man/curs_getstr.3x
index a7d0c8ce3..f509b20c8 100644
--- a/man/curs_getstr.3x
+++ b/man/curs_getstr.3x
@@ -203,7 +203,7 @@ .SH PORTABILITY
to allow for the terminating NUL.
As of 2018, some implementations count it, some do not:
.bP
-ncurses 6.1 and PDCurses do not count the NUL in the given limit, while
+\fI\%ncurses\fP 6.1 and PDCurses do not count the NUL in the given limit, while
.bP
Solaris SVr4 and NetBSD curses count the NUL as part of the limit.
.bP
@@ -231,15 +231,15 @@ .SH PORTABILITY
.IP
A comment in NetBSD's source code states that this is specified in SUSv2.
.bP
-ncurses (before 6.2) assumes no particular limit for the result
+\fI\%ncurses\fP (before 6.2) assumes no particular limit for the result
from \fBwgetstr\fP, and treats the \fIn\fP parameter of \fBwgetnstr\fP
like SVr4 curses.
.bP
-ncurses 6.2 uses \fBLINE_MAX\fP,
+\fI\%ncurses\fP 6.2 uses \fBLINE_MAX\fP,
or a larger (system-dependent) value
which the \fBsysconf\fP function may provide.
If neither \fBLINE_MAX\fP or \fBsysconf\fP is available,
-ncurses uses the POSIX value for \fBLINE_MAX\fP (a 2048 byte limit).
+\fI\%ncurses\fP uses the POSIX value for \fBLINE_MAX\fP (a 2048 byte limit).
In either case, it reserves a byte for the terminating NUL.
.PP
Although \fBgetnstr\fP is equivalent to a series of calls to \fBgetch\fP,
@@ -269,18 +269,22 @@ .SH PORTABILITY
mode set by the caller into account when deciding whether to handle
echoing within \fBgetnstr\fP or as a side-effect of the \fBgetch\fP calls.
.bP
-The original ncurses (as \fIpcurses\fP in 1986) set \fBnoraw\fP and
\fBcbreak\fP
-when accepting input for \fBgetnstr\fP.
+The original \fI\%ncurses\fP
+(as \fIpcurses\fP in 1986)
+set \fBnoraw\fP and \fBcbreak\fP when accepting input for \fBgetnstr\fP.
That may have been done to make function- and cursor-keys work;
-it is not necessary with ncurses.
+it is not necessary with \fI\%ncurses\fP.
.IP
-Since 1995, ncurses has provided signal handlers for INTR and QUIT
+Since 1995,
+\fI\%ncurses\fP has provided signal handlers for INTR and QUIT
(e.g., \fB^C\fP or \fB^\e\fP).
With the \fBnoraw\fP and \fBcbreak\fP settings,
those may catch a signal and stop the program,
where other implementations allow one to enter those characters in the buffer.
.bP
-Starting in 2021 (ncurses 6.3), \fBgetnstr\fP sets \fBraw\fP,
+Starting in 2021
+(\fI\%ncurses\fP 6.3),
+\fBgetnstr\fP sets \fBraw\fP,
rather than \fBnoraw\fP and \fBcbreak\fP for better compatibility with
SVr4-curses, e.g., allowing one to enter a \fB^C\fP into the buffer.
.SH SEE ALSO
diff --git a/man/curs_getyx.3x b/man/curs_getyx.3x
index d75ebeb68..a72905ad4 100644
--- a/man/curs_getyx.3x
+++ b/man/curs_getyx.3x
@@ -92,7 +92,7 @@ .SH PORTABILITY
the data stored in like-named members may not have like-values in
different implementations.
For example, the \fB\%WINDOW._maxx\fP and \fB\%WINDOW._maxy\fP values
-in \fIncurses\fP have
+in \fI\%ncurses\fP have
(at least since release 1.8.1)
differed by one from some other implementations.
The difference is hidden by means of the macro \fB\%getmaxyx\fP.
diff --git a/man/curs_initscr.3x b/man/curs_initscr.3x
index 47f9d4091..20a52ad4f 100644
--- a/man/curs_initscr.3x
+++ b/man/curs_initscr.3x
@@ -208,11 +208,11 @@ .SS Differences
\fBstdscr\fP and \fBcurscr\fP as well as a work area \fBnewscr\fP.
SVr4 curses ignores other windows.
.bP
-Since version 4.0 (1996), ncurses has maintained a list of all windows
-for each screen,
+Since version 4.0 (1996),
+\fI\%ncurses\fP has maintained a list of all windows for each screen,
using that information to delete those windows when \fBdelscreen\fP is called.
.bP
-NetBSD copied this feature of ncurses in 2001.
+NetBSD copied this feature of \fI\%ncurses\fP in 2001.
PDCurses follows the SVr4 model,
deleting only the standard \fBWINDOW\fP structures.
.SS High-level versus low-level
@@ -228,9 +228,9 @@ .SS High-level versus low-level
For example
.bP
NetBSD's \fBbaudrate\fP(3X) function uses the descriptor in \fBTERMINAL\fP.
-\fBncurses\fP and SVr4 use the descriptor in \fBSCREEN\fP.
+\fI\%ncurses\fP and SVr4 use the descriptor in \fBSCREEN\fP.
.bP
-NetBSD and \fBncurses\fP use the descriptor
+NetBSD and \fI\%ncurses\fP use the descriptor
in \fBTERMINAL\fP
for terminal I/O modes,
e.g.,
diff --git a/man/curs_inopts.3x b/man/curs_inopts.3x
index fd07da5f2..7cc03a7d9 100644
--- a/man/curs_inopts.3x
+++ b/man/curs_inopts.3x
@@ -103,8 +103,8 @@ .SH SYNOPSIS
\fBint is_raw(void);
.fi
.SH DESCRIPTION
-The \fIncurses\fP library provides several functions which let an application
-change the way input from the terminal is handled.
+The \fI\%ncurses\fP library provides several functions which let an
+application change the way input from the terminal is handled.
Some are global, applying to all windows.
Others apply only to a specific window.
Window-specific settings are not automatically applied to new or derived
@@ -333,15 +333,15 @@ .SH EXTENSIONS
\-1
if the \fIcurses\fP library was not initialized.
.PP
-These routines are specific to \fIncurses\fP.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on \fIncurses\fP extensions
+It is recommended that any code depending on \fI\%ncurses\fP extensions
be conditioned using NCURSES_VERSION.
.SH PORTABILITY
Except as noted in the section on extensions,
these functions are described in the XSI Curses standard, Issue 4.
.PP
-The \fIncurses\fP library obeys the XPG4 standard
+The \fI\%ncurses\fP library obeys the XPG4 standard
and the historical practice of the
AT&T \fIcurses\fP implementations,
in that the echo bit is cleared when \fIcurses\fP
@@ -361,10 +361,11 @@ .SH PORTABILITY
system will not alter.
.PP
When \fB\%keypad\fP is first enabled,
-\fIncurses\fP loads the key-definitions for the current terminal description.
+\fI\%ncurses\fP loads the key-definitions for the current terminal
+description.
If the terminal description includes extended string capabilities,
e.g., from using the \fB\-x\fP option of \fB@TIC@\fP,
-then \fIncurses\fP also defines keys for the capabilities whose names
+then \fI\%ncurses\fP also defines keys for the capabilities whose names
begin with \*(``k\*(''.
The corresponding keycodes are generated and (depending on previous
loads of terminal descriptions) may differ from one execution of a
@@ -386,12 +387,12 @@ .SH PORTABILITY
the strings are loaded.
If more than one key definition has the same string value,
then \fB\%wgetch\fP can return only one keycode.
-Most \fIcurses\fP implementations (including \fIncurses\fP)
+Most \fIcurses\fP implementations (including \fI\%ncurses\fP)
load key definitions in the order
defined by the array of string capability names.
The last key to be loaded determines the keycode which will be returned.
-In \fIncurses\fP, you may also have extended capabilities interpreted as
-key definitions.
+In \fI\%ncurses\fP,
+you may also have extended capabilities interpreted as key definitions.
These are loaded after the predefined keys,
and if a capability's value is the same as a previously-loaded
key definition,
diff --git a/man/curs_instr.3x b/man/curs_instr.3x
index 13835a4e8..088600251 100644
--- a/man/curs_instr.3x
+++ b/man/curs_instr.3x
@@ -114,8 +114,8 @@ .SH PORTABILITY
SVr4 does not
document whether a length limit includes or excludes the trailing NUL.
.PP
-The ncurses library extends the XSI description by allowing a negative
-value for \fIn\fP.
+The \fI\%ncurses\fP library extends the XSI description by allowing a
+negative value for \fIn\fP.
In this case, the functions return the string ending at the right margin.
.SH SEE ALSO
\fB\%curses\fP(3X),
diff --git a/man/curs_kernel.3x b/man/curs_kernel.3x
index 3ff80107b..4c8de5c4b 100644
--- a/man/curs_kernel.3x
+++ b/man/curs_kernel.3x
@@ -197,12 +197,12 @@ .SH NOTES
This implementation gets it right, but it may be unwise to count
on the correctness of the return value anywhere else.
.PP
-Both ncurses and SVr4 will call \fBcurs_set\fP in \fBendwin\fP
+Both \fI\%ncurses\fP and SVr4 will call \fBcurs_set\fP in \fBendwin\fP
if \fBcurs_set\fP
has been called to make the cursor other than normal, i.e., either
invisible or very visible.
-There is no way for ncurses to determine the initial cursor state to
-restore that.
+There is no way for \fI\%ncurses\fP to determine the initial cursor
+state to restore that.
.SH PORTABILITY
The \fIvirtual screen\fP functions \fBsetsyx\fP and \fBgetsyx\fP
are not described in the XSI Curses standard, Issue 4.
@@ -213,7 +213,7 @@ .SH PORTABILITY
This is misleading, as they are macros with no documented semantics
for the return value.
.PP
-If interrupted, ncurses restarts \fBnapms\fP.
+If interrupted, \fI\%ncurses\fP restarts \fBnapms\fP.
That, and the limitation to 30 seconds,
are different from other implementations.
.SH SEE ALSO
diff --git a/man/curs_memleaks.3x b/man/curs_memleaks.3x
index 0f52899c7..a22ef872f 100644
--- a/man/curs_memleaks.3x
+++ b/man/curs_memleaks.3x
@@ -62,15 +62,16 @@ .SH SYNOPSIS
\fBvoid _nc_free_tinfo(int \fIcode\fP);
.fi
.SH DESCRIPTION
-These functions are used to simplify analysis of memory leaks in the ncurses
-library.
+These functions are used to simplify analysis of memory leaks in the
+\fI\%ncurses\fP library.
.PP
Any implementation of curses must not free the memory associated with
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,
+When using the specially configured debugging version of the
+\fI\%ncurses\fP library,
applications can call functions which free those chunks of memory,
simplifying the process of memory-leak checking.
.PP
@@ -78,10 +79,11 @@ .SH DESCRIPTION
because they are not intended for use in the non-debugging library:
.TP 5
\fB\%_nc_freeall\fP
-This frees (almost) all of the memory allocated by ncurses.
+This frees (almost) all of the memory allocated by \fI\%ncurses\fP.
.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 \fI\%ncurses\fP
+(like \fB\%_nc_freeall\fP),
and exits the program.
It is preferred over \fB\%_nc_freeall\fP since some of that memory
may be required to keep the application running.
diff --git a/man/curs_mouse.3x b/man/curs_mouse.3x
index b65403ae2..5c54ad4da 100644
--- a/man/curs_mouse.3x
+++ b/man/curs_mouse.3x
@@ -262,8 +262,9 @@ .SH RETURN VALUE
are boolean functions returning \fBTRUE\fP or \fBFALSE\fP depending
on their test result.
.SH PORTABILITY
-These calls were designed for \fIncurses\fP, and are not found in SVr4
-\fIcurses\fP, 4.4BSD \fIcurses\fP, or any other previous version of
\fIcurses\fP.
+These calls were designed for \fI\%ncurses\fP,
+and are not found in SVr4 \fIcurses\fP,
+4.4BSD \fIcurses\fP, or any other previous version of \fIcurses\fP.
.PP
SVr4 \fIcurses\fP had support for the mouse in a variant of \fBxterm\fP(1).
It is mentioned in a few places, but with no supporting documentation:
@@ -295,7 +296,7 @@ .SH PORTABILITY
.EE
.RE
.bP
-the interface made assumptions (as does \fIncurses\fP)
+the interface made assumptions (as does \fI\%ncurses\fP)
about the escape sequences
sent to and received from the terminal.
.IP
@@ -310,7 +311,8 @@ .SH PORTABILITY
to work with \fIcurses\fP.
They were not part of the X Consortium's xterm.
.PP
-When developing the xterm mouse support for \fIncurses\fP in September 1995,
+When developing the xterm mouse support for \fI\%ncurses\fP in September
+1995,
Eric Raymond was uninterested in using the same interface due to its
lack of documentation.
Later, in 1998, Mark Hesseling provided support in
@@ -324,7 +326,7 @@ .SH PORTABILITY
If the interface is changed, the value of \fB\%NCURSES_MOUSE_VERSION\fP will be
incremented.
These values for \fB\%NCURSES_MOUSE_VERSION\fP may be
-specified when configuring \fIncurses\fP:
+specified when configuring \fI\%ncurses\fP:
.RS 3
.TP 3
1
@@ -340,7 +342,7 @@ .SH PORTABILITY
The order of the \fB\%MEVENT\fP structure members is not guaranteed.
Additional fields may be added to the structure in the future.
.PP
-Under \fIncurses\fP, these calls are implemented using either
+Under \fI\%ncurses\fP, these calls are implemented using either
xterm's built-in mouse-tracking API or
platform-specific drivers including
.RS 3
@@ -354,7 +356,7 @@ .SH PORTABILITY
.PP
If you are using an unsupported configuration,
mouse events will not be visible to
-\fIncurses\fP (and the \fB\%mousemask\fP function will always
+\fI\%ncurses\fP (and the \fB\%mousemask\fP function will always
return \fB0\fP).
.PP
If the terminfo entry contains a \fBXM\fP string,
diff --git a/man/curs_opaque.3x b/man/curs_opaque.3x
index 3eac44faf..c69055702 100644
--- a/man/curs_opaque.3x
+++ b/man/curs_opaque.3x
@@ -78,7 +78,7 @@ .SH SYNOPSIS
\fBint wgetscrreg(const WINDOW *\fIwin\fP, int *\fItop\fP, int *\fIbottom\fP);
.fi
.SH DESCRIPTION
-\fIncurses\fP provides functions returning properties of a
+\fI\%ncurses\fP provides functions returning properties of a
\fI\%WINDOW\fP structure,
allowing it to be \*(``opaque\*('' if
the application defines the \fB\%NCURSES_OPAQUE\fP preprocessor symbol.
@@ -146,12 +146,12 @@ .SH DESCRIPTION
.SH RETURN VALUE
These functions return \fBTRUE\fP or \fBFALSE\fP except as noted.
.SH NOTES
-\fIncurses\fP provides both a C function and a preprocessor macro for
+\fI\%ncurses\fP provides both a C function and a preprocessor macro for
each function documented in this page.
.SH PORTABILITY
-These routines are specific to \fIncurses\fP.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on \fIncurses\fP extensions
+It is recommended that any code depending on \fI\%ncurses\fP extensions
be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
\fB\%curses\fP(3X),
diff --git a/man/curs_outopts.3x b/man/curs_outopts.3x
index 2fa712752..08313cd6f 100644
--- a/man/curs_outopts.3x
+++ b/man/curs_outopts.3x
@@ -169,8 +169,9 @@ .SH NOTES
.SH PORTABILITY
These functions are described in the XSI Curses standard, Issue 4.
.PP
-From the outset, ncurses used \fBnl\fP/\fBnonl\fP to control the conversion
-of newlines to carriage return/line-feed on output as well as input.
+From the outset,
+\fI\%ncurses\fP used \fBnl\fP/\fBnonl\fP to control the conversion of
+newlines to carriage return/line-feed on output as well as input.
XSI Curses documents only the use of these functions for input.
This difference arose from converting the \fIpcurses\fP source
(which used \fBioctl\fP calls with the \fBsgttyb\fP structure)
@@ -179,18 +180,18 @@ .SH PORTABILITY
option \fBCRMOD\fP,
while the latter separates these features.
Because that conversion interferes with output optimization,
-\fBnl\fP/\fBnonl\fP were amended after ncurses 6.2
+\fBnl\fP/\fBnonl\fP were amended after \fI\%ncurses\fP 6.2
to eliminate their effect on output.
.PP
Some historic curses implementations had, as an undocumented feature, the
ability to do the equivalent of \fBclearok(..., 1)\fP by saying
\fBtouchwin(stdscr)\fP or \fBclear(stdscr)\fP.
-This will not work under ncurses.
+This will not work under \fI\%ncurses\fP.
.PP
Earlier System V curses implementations specified that with \fBscrollok\fP
enabled, any window modification triggering a scroll also forced a physical
refresh.
-XSI Curses does not require this, and \fBncurses\fP avoids doing
+XSI Curses does not require this, and \fI\%ncurses\fP avoids doing
it to perform better vertical-motion optimization at \fBwrefresh\fP
time.
.PP
diff --git a/man/curs_print.3x b/man/curs_print.3x
index 8c9211cc7..de49e7499 100644
--- a/man/curs_print.3x
+++ b/man/curs_print.3x
@@ -67,10 +67,11 @@ .SH RETURN VALUE
When \fB\%mcprint\fP succeeds, it returns the number of characters actually
sent to the printer.
.SH PORTABILITY
-The \fB\%mcprint\fP call was designed for \fIncurses\fP, and is not found
-in SVr4 \fIcurses\fP, 4.4BSD \fIcurses\fP,
+The \fB\%mcprint\fP call was designed for \fI\%ncurses\fP,
+and is not found in SVr4 \fIcurses\fP,
+4.4BSD \fIcurses\fP,
or any other previous version of \fIcurses\fP.
-It is recommended that any code depending on \fIncurses\fP extensions
+It is recommended that any code depending on \fI\%ncurses\fP extensions
be conditioned using \fB\%NCURSES_VERSION\fP.
.SH BUGS
Padding in the
diff --git a/man/curs_scanw.3x b/man/curs_scanw.3x
index 47993a7ed..8ec1e3952 100644
--- a/man/curs_scanw.3x
+++ b/man/curs_scanw.3x
@@ -121,7 +121,8 @@ .SH PORTABILITY
This implementation returns the number of items scanned,
for compatibility with SVr4 curses.
As of 2018, NetBSD curses also returns the number of items scanned.
-Both ncurses and NetBSD curses call \fBvsscanf\fP to scan the string,
+Both \fI\%ncurses\fP and NetBSD curses call \fBvsscanf\fP to scan the
+string,
which returns \fBEOF\fP on error.
.bP
Portable applications should only test if the return value is \fBERR\fP,
diff --git a/man/curs_slk.3x b/man/curs_slk.3x
index 550005c88..3f8e0188a 100644
--- a/man/curs_slk.3x
+++ b/man/curs_slk.3x
@@ -102,11 +102,11 @@ .SH DESCRIPTION
\fB\%stdscr\fP and the variable \fBLINES\fP.
\fIcurses\fP standardizes on eight
labels of up to eight characters each.
-In addition to this, the \fIncurses\fP
+In addition to this, the \fI\%ncurses\fP
implementation supports a mode where it simulates 12 labels of up to five
characters each.
This is useful for PC-like enduser devices.
-\fIncurses\fP simulates this mode by taking over up to two lines at
+\fI\%ncurses\fP simulates this mode by taking over up to two lines at
the bottom of the screen;
it does not try to use any hardware support for this
mode.
@@ -300,10 +300,10 @@ .SH PORTABILITY
If there are more than 16 elements, \fB\%slk_start\fP returns an error.
.bP
The format codes \fB2\fP and \fB3\fP for \fB\%slk_init\fP
-were added by \fIncurses\fP in 1996.
+were added by \fI\%ncurses\fP in 1996.
PDCurses 2.4 added this feature in 2001.
.PP
-The function \fB\%slk_attr\fP was added by \fIncurses\fP in 1996.
+The function \fB\%slk_attr\fP was added by \fI\%ncurses\fP in 1996.
.PP
X/Open \fIcurses\fP does not specify a limit for the number of colors and
color pairs which a terminal can support.
diff --git a/man/curs_sp_funcs.3x b/man/curs_sp_funcs.3x
index 1c075cd08..0a62234f7 100644
--- a/man/curs_sp_funcs.3x
+++ b/man/curs_sp_funcs.3x
@@ -213,7 +213,8 @@ .SH SYNOPSIS
.SH DESCRIPTION
This implementation can be configured to provide a set of functions which
improve the ability to manage multiple screens.
-This feature can be added to any of the configurations supported by ncurses;
+This feature can be added to any of the configurations supported by
+\fI\%ncurses\fP;
it adds new entrypoints
without changing the meaning of any of the existing ones.
.\" ***************************************************************************
@@ -273,9 +274,9 @@ .SH NOTES
This is a function-pointer type used for the cases where a function passes
characters to the output stream, e.g., \fBvidputs\fP(3X).
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on ncurses extensions
+It is recommended that any code depending on \fI\%ncurses\fP extensions
be conditioned using \fINCURSES_SP_FUNCS\fP.
.SH SEE ALSO
\fB\%curses\fP(3X),
diff --git a/man/curs_termcap.3x b/man/curs_termcap.3x
index 09e3384ae..9feb8b110 100644
--- a/man/curs_termcap.3x
+++ b/man/curs_termcap.3x
@@ -105,7 +105,7 @@ .SS Initialization
The emulation ignores the buffer pointer \fIbp\fP.
The \fItermcap\fP library would store a copy of the terminal
description in the area referenced by this pointer.
-However, ncurses stores its terminal descriptions in compiled
+However, \fI\%ncurses\fP stores its terminal descriptions in compiled
binary form, which is not the same thing.
.bP
There is a difference in return codes.
@@ -129,11 +129,11 @@ .SS Capability Values
It is assumed to be the address of a pointer to a buffer managed by the
calling application.
.bP
-However, ncurses checks to ensure that \fBarea\fP is not NULL,
+However, \fI\%ncurses\fP checks to ensure that \fBarea\fP is not NULL,
and also that the resulting buffer pointer is not NULL.
If either check fails, the \fIarea\fP parameter is ignored.
.bP
-If the checks succeed, ncurses also copies the return value to
+If the checks succeed, \fI\%ncurses\fP also copies the return value to
the buffer pointed to by \fIarea\fP,
and the \fIarea\fP value will be updated to point past the null ending
this value.
@@ -165,7 +165,7 @@ .SS Formatting Capabilities
It does this also for calls requiring only a single parameter.
In that case, the first parameter is merely a placeholder.
.bP
-Normally the ncurses library is compiled with terminfo support.
+Normally the \fI\%ncurses\fP library is compiled with terminfo support.
In that case, \fBtgoto\fP uses an internal version of
\fBtparm\fP(3X) (a more capable formatter).
.IP
@@ -190,11 +190,11 @@ .SS Global Variables
\fBcursor_up\fP and
\fBbackspace_if_not_bs\fP,
respectively.
-\fBUP\fP is not used by ncurses.
+\fBUP\fP is not used by \fI\%ncurses\fP.
\fBPC\fP is used in the \fBtdelay_output\fP function.
\fBBC\fP is used in the \fBtgoto\fP emulation.
-The variable \fBospeed\fP is set by ncurses in a system-specific coding
-to reflect the terminal speed.
+The variable \fBospeed\fP is set by \fI\%ncurses\fP in a system-specific
+coding to reflect the terminal speed.
.SS Releasing Memory
The termcap functions provide no means for freeing memory,
because legacy termcap implementations used only the buffer
@@ -209,7 +209,8 @@ .SS Releasing Memory
\fBdel_curterm(cur_term);\fP
.sp
.PP
-to free this memory, but there is an additional complication with ncurses.
+to free this memory,
+but there is an additional complication with \fI\%ncurses\fP.
It uses a fixed-size \fIpool\fP of storage locations,
one per setting of the \fITERM\fP variable when \fBtgetent\fP is called.
The \fBscreen\fP(1) program relies upon this arrangement,
@@ -260,7 +261,7 @@ .SS Standards
misinterpreted to mean that \fBtgetent\fP returns \fBOK\fP or \fBERR\fP.
Because the purpose of these functions is to provide compatibility with
the \fItermcap\fP library, that is a defect in XCurses, Issue 4, Version 2
-rather than in ncurses.
+rather than in \fI\%ncurses\fP.
.SS Compatibility with BSD Termcap
External variables are provided for support of certain termcap applications.
However, termcap applications' use of those variables is poorly documented,
@@ -328,7 +329,7 @@ .SS Other Compatibility
A copy of GNU termcap 1.3 was bundled with \fIbash\fP in mid-1993,
to support the \fBreadline\fP(3) library.
.PP
-A termcap.h file was provided in ncurses 1.8.1 (November 1993).
+A termcap.h file was provided in \fI\%ncurses\fP 1.8.1 (November 1993).
That reflected influence by \fBemacs\fP(1) (rather than \fBjove\fP(1))
and GNU termcap:
.bP
@@ -338,7 +339,9 @@ .SS Other Compatibility
.bP
a prototype for \fBtparam\fP (a GNU termcap feature) was provided.
.PP
-Later (in mid-1996) the \fBtparam\fP function was removed from ncurses.
+Later
+(in mid-1996)
+the \fBtparam\fP function was removed from \fI\%ncurses\fP.
As a result, there are differences between any of the four implementations,
which must be taken into account by programs which can work with all
termcap library interfaces.
diff --git a/man/curs_terminfo.3x b/man/curs_terminfo.3x
index e0b07ae45..43429d5b1 100644
--- a/man/curs_terminfo.3x
+++ b/man/curs_terminfo.3x
@@ -457,11 +457,12 @@ .SS Releasing Memory
allocated by \fBsetupterm\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.
+Before \fI\%ncurses\fP 6.3, those were shared by all screens.
+With \fI\%ncurses\fP 6.3, those are allocated per screen.
See \fBterminfo\fP(5) for details.
.bP
-to improve performance, ncurses 6.3 caches the result of analyzing terminfo
+to improve performance,
+\fI\%ncurses\fP 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.
.PP
@@ -558,20 +559,21 @@ .SS Legacy data
Extended terminal capability names, e.g., as defined by \fB@TIC@\ \-x\fP,
are not stored in the arrays described here.
.SS Output buffering
-Older versions of \fBncurses\fP assumed that the file descriptor passed to
-\fBsetupterm\fP from \fBinitscr\fP or \fBnewterm\fP uses buffered I/O,
+Older versions of \fI\%ncurses\fP assumed that the file descriptor
+passed to \fBsetupterm\fP from \fBinitscr\fP or \fBnewterm\fP uses
+buffered I/O,
and would write to the corresponding stream.
In addition to the limitation that the terminal was left in block-buffered
mode on exit (like System V curses),
-it was problematic because \fBncurses\fP
+it was problematic because \fI\%ncurses\fP
did not allow a reliable way to cleanup on receiving SIGTSTP.
.PP
The current version (ncurses6)
-uses output buffers managed directly by \fBncurses\fP.
+uses output buffers managed directly by \fI\%ncurses\fP.
Some of the low-level functions described in this manual page write
to the standard output.
They are not signal-safe.
-The high-level functions in \fBncurses\fP use
+The high-level functions in \fI\%ncurses\fP use
alternate versions of these functions
using the more reliable buffering scheme.
.SS Function prototypes
@@ -588,7 +590,7 @@ .SS Function prototypes
.IP
As an extension, this implementation can be configured to change the
function prototypes to use the \fBconst\fP keyword.
-The \fIncurses\fP ABI 6 enables this feature by default.
+The \fI\%ncurses\fP ABI 6 enables this feature by default.
.bP
X/Open Curses prototypes \fBtparm\fP with a fixed number of parameters,
rather than a variable argument list.
@@ -601,7 +603,7 @@ .SS Function prototypes
In response to review comments by Thomas E. Dickey,
X/Open Curses Issue 7 proposed the \fBtiparm\fP function in mid-2009.
.IP
-While \fBtiparm\fP is always provided in ncurses,
+While \fBtiparm\fP is always provided in \fI\%ncurses\fP,
the older form is only available as a build-time configuration option.
If not specially configured, \fBtparm\fP is the same as \fBtiparm\fP.
.PP
@@ -621,7 +623,7 @@ .SS Function prototypes
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,
+The \fI\%ncurses\fP library checks usage of these capabilities,
and returns an error if the capability mishandles string parameters.
But it cannot check if a calling program provides strings in the right
places for the \fBtparm\fP calls.
@@ -661,8 +663,9 @@ .SS Other portability issues
X/Open notes that after calling \fBmvcur\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 \fI\%ncurses\fP and System V Release 4 curses implement \fBmvcur\fP
+using the SCREEN data allocated in either \fBinitscr\fP or
+\fBnewterm\fP.
So though it is documented as a terminfo function,
\fBmvcur\fP is really a curses function which is not well specified.
.PP
diff --git a/man/curs_threads.3x b/man/curs_threads.3x
index 1648dee20..a198cc9c0 100644
--- a/man/curs_threads.3x
+++ b/man/curs_threads.3x
@@ -70,16 +70,16 @@ .SH SYNOPSIS
\fBint use_window(WINDOW *\fIwin\fP, NCURSES_WINDOW_CB \fIfunc\fP, void
*\fIdata\fP);
.fi
.SH DESCRIPTION
-The \fIncurses\fP library can be configured to support multi-threaded
+The \fI\%ncurses\fP library can be configured to support multi-threaded
applications in a rudimentary way.
Such configuration produces a different set of libraries,
named \fIlibncursest\fP,
for example,
-since doing so alters \fIncurses\fP's application binary interface
+since doing so alters \fI\%ncurses\fP's application binary interface
(ABI).
.PP
Instead of modifying the programming interface (API) to make
-\fIncurses\fP functions expect an additional argument specifying a
+\fI\%ncurses\fP functions expect an additional argument specifying a
thread,
the library adds functions,
usable in any configuration,
@@ -88,8 +88,9 @@ .SH DESCRIPTION
needed to prevent concurrent access to variables shared by multiple
threads of execution.
.PP
-\fIncurses\fP threading support requires the use of functions to access
-members of the \fI\%WINDOW\fP structure (see \fBcurs_opaque\fP(3X)).
+\fI\%ncurses\fP threading support requires the use of functions to
+access members of the \fI\%WINDOW\fP structure (see
+\fBcurs_opaque\fP(3X)).
It further makes functions of the common global variables
\fB\%COLORS\fP,
\fB\%COLOR_PAIRS\fP,
@@ -127,7 +128,7 @@ .SH DESCRIPTION
and return the value from the user-supplied function to the application.
.\" ***************************************************************************
.SS Usage
-All \fIncurses\fP library functions assume that the locale is not
+All \fI\%ncurses\fP library functions assume that the locale is not
altered during operation.
In addition,
they use data that is maintained within a hierarchy of scopes.
@@ -154,8 +155,9 @@ .SS Usage
reentrant data associated with \*(``pure\*('' functions that alter no
shared variables
.PP
-The following table lists the scope of each symbol in the \fIncurses\fP
-library when configured to support multi-threaded applications.
+The following table lists the scope of each symbol in the
+\fI\%ncurses\fP library when configured to support multi-threaded
+applications.
.PP
.TS
center tab(/);
@@ -623,12 +625,12 @@ .SH RETURN VALUE
\fB\%use_screen\fP and \fB\%use_window\fP return the \fIint\fP returned
by the user-supplied function they are called with.
.SH NOTES
-\fIncurses\fP provides both a C function and a preprocessor macro for
+\fI\%ncurses\fP provides both a C function and a preprocessor macro for
each function documented in this page.
.SH PORTABILITY
-These routines are specific to \fIncurses\fP.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on \fIncurses\fP extensions
+It is recommended that any code depending on \fI\%ncurses\fP extensions
be conditioned using \fB\%NCURSES_VERSION\fP.
.SH SEE ALSO
\fB\%curses\fP(3X),
diff --git a/man/curs_trace.3x b/man/curs_trace.3x
index 6233edb6c..70d24f309 100644
--- a/man/curs_trace.3x
+++ b/man/curs_trace.3x
@@ -83,8 +83,9 @@ .SH SYNOPSIS
\fBvoid trace(const unsigned int \fIparam\fP);
.fi
.SH DESCRIPTION
-The \fIcurses trace\fP routines are used for debugging the ncurses libraries,
-as well as applications which use the ncurses libraries.
+The \fIcurses trace\fP routines are used for debugging the
+\fI\%ncurses\fP libraries,
+as well as applications which use the \fI\%ncurses\fP libraries.
Some limitations apply:
.bP
Aside from \fBcurses_trace\fP,
@@ -122,7 +123,7 @@ .SS Functions
and returns the previous trace mask.
.IP
When the trace mask is nonzero,
-ncurses creates the file \*(``trace\*('' in the current directory for output.
+\fI\%ncurses\fP 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).
@@ -226,7 +227,8 @@ .SS Command-line Utilities
.bP
messages produced by the underlying library are written to \fItrace\fP.
.PP
-If ncurses is built without tracing, none of the latter are produced,
+If \fI\%ncurses\fP is built without tracing,
+none of the latter are produced,
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
@@ -235,7 +237,7 @@ .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:
+but they are not compatible with \fI\%ncurses\fP:
.bP
SVr4 provided \fBtraceon\fP and \fBtraceoff\fP,
to control whether debugging information was written
@@ -254,7 +256,7 @@ .SH PORTABILITY
.IP
PDCurses has a short description of these functions,
with a note that they are not present in X/Open Curses,
-ncurses or NetBSD.
+\fI\%ncurses\fP or NetBSD.
It does not mention SVr4,
but the functions' inclusion in a header file section
labeled \*(``Quasi-standard\*('' hints at the origin.
@@ -268,7 +270,8 @@ .SH PORTABILITY
.IP
The NetBSD tracing feature is undocumented.
.PP
-A few ncurses functions are not provided when symbol versioning is used:
+A few \fI\%ncurses\fP functions are not provided when symbol versioning
+is used:
.RS 4
.PP
_nc_tracebits,
diff --git a/man/curs_util.3x b/man/curs_util.3x
index 6878b43e7..02f8edd0c 100644
--- a/man/curs_util.3x
+++ b/man/curs_util.3x
@@ -167,10 +167,11 @@ .SS use_env
should be called before \fBinitscr\fP or
\fBnewterm\fP are called
(because those compute the screen size).
-It modifies the way \fIncurses\fP treats environment variables
+It modifies the way \fI\%ncurses\fP treats environment variables
when determining the screen size.
.bP
-Normally \fIncurses\fP looks first at the terminal database for the screen
size.
+Normally \fI\%ncurses\fP looks first at the terminal database for the
+screen size.
.IP
If \fBuse_env\fP was called with \fBFALSE\fP for parameter,
it stops here unless
@@ -181,12 +182,13 @@ .SS use_env
it overrides the values from the terminal database.
.bP
Finally (unless \fBuse_env\fP was called with \fBFALSE\fP parameter),
-\fBncurses\fP examines the \fILINES\fP or \fI\%COLUMNS\fP environment
+\fI\%ncurses\fP examines the \fILINES\fP or \fI\%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,
+\fI\%curses\fP also updates the screen size in response to
+\fBSIGWINCH\fP,
unless overridden by the \fILINES\fP or \fI\%COLUMNS\fP environment
variables,
.SS use_tioctl
@@ -194,18 +196,18 @@ .SS use_tioctl
should be called before \fBinitscr\fP or \fBnewterm\fP are called
(because those compute the screen size).
After \fBuse_tioctl\fP is called with \fBTRUE\fP as an argument,
-\fBncurses\fP modifies the last step in its computation
+\fI\%ncurses\fP modifies the last step in its computation
of screen size as follows:
.bP
checks if the \fILINES\fP and \fI\%COLUMNS\fP environment variables
are set to a number greater than zero.
.bP
-for each, \fBncurses\fP updates the corresponding environment variable
+for each, \fI\%ncurses\fP updates the corresponding environment variable
with the value that it has obtained via operating system call
or from the terminal database.
.bP
-\fBncurses\fP re-fetches the value of the environment variables so that
-it is still the environment variables which set the screen size.
+\fI\%ncurses\fP re-fetches the value of the environment variables so
+that it is still the environment variables which set the screen size.
.PP
The \fB\%use_env\fP and \fB\%use_tioctl\fP routines combine as follows.
.IP
@@ -216,17 +218,17 @@ .SS use_tioctl
_
TRUE FALSE T{
This is the default behavior.
-\fIncurses\fP uses operating system calls
+\fI\%ncurses\fP uses operating system calls
unless overridden by \fILINES\fP or \fI\%COLUMNS\fP environment
variables;
default.
T}
TRUE TRUE T{
-\fIncurses\fP updates \fILINES\fP and \fI\%COLUMNS\fP based on operating
-system calls.
+\fI\%ncurses\fP updates \fILINES\fP and \fI\%COLUMNS\fP based on
+operating system calls.
T}
FALSE TRUE T{
-\fIncurses\fP ignores \fILINES\fP and \fI\%COLUMNS\fP,
+\fI\%ncurses\fP ignores \fILINES\fP and \fI\%COLUMNS\fP,
using operating system calls to obtain size.
T}
.TE
@@ -246,8 +248,8 @@ .SS putwin/getwin
.bP
the data written is a copy of the \fBWINDOW\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 (\fI\%ncursesw\fP) and
+non-wide (\fI\%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),
@@ -262,7 +264,7 @@ .SS delay_output
The \fBdelay_output\fP routine inserts an \fIms\fP millisecond pause
in output.
Employ this function judiciously when terminal output uses padding,
-because \fIncurses\fP transmits null characters
+because \fI\%ncurses\fP transmits null characters
(consuming CPU and I/O resources)
instead of sleeping and requesting resumption from the operating system.
Padding is used unless:
@@ -272,7 +274,7 @@ .SS delay_output
the environment variable \fB\%NCURSES_NO_PADDING\fP is set.
.PP
If padding is not in use,
-\fIncurses\fP uses \fBnapms\fP to perform the delay.
+\fI\%ncurses\fP uses \fBnapms\fP to perform the delay.
If the value of \fIms\fP exceeds 30,000
(thirty seconds),
it is capped at that value.
@@ -325,9 +327,10 @@ .SS keyname
The \fBuse_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 \fBnofilter\fP and \fBuse_tioctl\fP routines are specific to
+\fI\%ncurses\fP.
They were not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on \fBncurses\fP extensions
+It is recommended that any code depending on \fI\%ncurses\fP extensions
be conditioned using \fBNCURSES_VERSION\fP.
.SS putwin/getwin file-format
The \fBputwin\fP and \fBgetwin\fP functions have several issues with
@@ -346,7 +349,7 @@ .SS putwin/getwin file-format
.bP
Most implementations simply dump the binary \fBWINDOW\fP structure to the file.
These include SVr4 curses, NetBSD and PDCurses,
-as well as older \fBncurses\fP versions.
+as well as older \fI\%ncurses\fP versions.
This implementation
(as well as the X/Open variant of Solaris curses, dated 1995)
uses textual dumps.
@@ -409,12 +412,12 @@ .SS unctrl/wunctrl
this implementation returns strings \*(``M\-^@\*('', \*(``M\-^A\*('', etc.
.PP
X/Open Curses documents \fBunctrl\fP as declared in \fB<unctrl.h>\fP,
-which \fBncurses\fP does.
-However, \fBncurses\fP' \fB<curses.h>\fP includes \fB<unctrl.h>\fP,
+which \fI\%ncurses\fP does.
+However, \fI\%ncurses\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,
+If \fI\%ncurses\fP is configured to provide the sp-functions extension,
the state of \fBuse_env\fP and \fBuse_tioctl\fP may be updated before
creating each \fIscreen\fP rather than once only
(\fBcurs_sp_funcs\fP(3X)).
diff --git a/man/curs_variables.3x b/man/curs_variables.3x
index 913ad6b8c..d01b5d55a 100644
--- a/man/curs_variables.3x
+++ b/man/curs_variables.3x
@@ -103,7 +103,7 @@ .SH DESCRIPTION
and variables provided by the \fIcurses\fP library.
Locate further discussion in \fB\%curses\fP(3X).
.PP
-Depending on \fIncurses\fP's build-time configuration,
+Depending on \fI\%ncurses\fP's build-time configuration,
the variables may instead be
macros (see \fB\%curs_threads\fP(3X) and \fB\%curs_opaque\fP(3X))
that provide read-only access to the library's state.
@@ -201,7 +201,7 @@ .SS curscr
\fB\%curs_refresh\fP(3X) and
\fB\%curs_outopts\fP(3X).
.SS newscr
-\fIncurses\fP collects pending updates to the terminal screen in a
+\fI\%ncurses\fP collects pending updates to the terminal screen in a
\fI\%WINDOW\fP structure named \fB\%newscr\fP.
.PP
This object is referred to as the \*(``virtual screen\*('' in the
@@ -222,7 +222,7 @@ .SH NOTES
Either \fB\%initscr\fP(3X) or \fB\%newterm\fP(3X) initializes
\fIcurses\fP.
.PP
-If \fIncurses\fP is configured to provide separate \fIcurses\fP and
+If \fI\%ncurses\fP is configured to provide separate \fIcurses\fP and
\fIterminfo\fP libraries,
most of these variables reside in the \fIcurses\fP library.
.SH PORTABILITY
@@ -258,7 +258,7 @@ .SH PORTABILITY
the virtual screen with \fB\%addch\fP(3X) and
the physical screen with \fB\%mvcur\fP(3X).
.bP
-\fIncurses\fP uses the value of \fB\%TABSIZE\fP only to update the
+\fI\%ncurses\fP uses the value of \fB\%TABSIZE\fP only to update the
virtual screen.
It uses the terminal description's \*(``\fBit\fP\*(''
(\fB\%init_tabs\fP) capability for computing hardware tabs
@@ -269,7 +269,7 @@ .SH PORTABILITY
For instance,
NetBSD \fIcurses\fP allows \fB\%TABSIZE\fP to be set through an
environment variable.
-\fIncurses\fP does not.
+\fI\%ncurses\fP does not.
.IP
NetBSD \fIcurses\fP does not support hardware tabs;
it uses the \fB\%init_tabs\fP capability and the \fB\%TABSIZE\fP
@@ -283,9 +283,10 @@ .SH PORTABILITY
The default value for AIX's \fB\%ESCDELAY\fP equals 0.1 seconds.
.bP
AIX also enforces a limit of 10,000 seconds for \fB\%ESCDELAY\fP;
-\fIncurses\fP does not enforce any upper limit.
+\fI\%ncurses\fP does not enforce any upper limit.
.PP
-\fIncurses\fP has long used \fB\%ESCDELAY\fP with units of milliseconds,
+\fI\%ncurses\fP has long used \fB\%ESCDELAY\fP with units of
+milliseconds,
making it impossible to be completely compatible with AIX.
Consequently,
most users have decided either to override the value,
diff --git a/man/curs_window.3x b/man/curs_window.3x
index a4cc25242..e32eaf05b 100644
--- a/man/curs_window.3x
+++ b/man/curs_window.3x
@@ -235,10 +235,11 @@ .SH PORTABILITY
Solaris X/Open curses does not even make that check,
and will delete a parent window which still has subwindows.
.bP
-Since release 4.0 (1996), ncurses maintains a list of windows for each screen,
+Since release 4.0 (1996),
+\fI\%ncurses\fP maintains a list of windows for each screen,
to ensure that a window has no subwindows before allowing deletion.
.bP
-NetBSD copied this feature of ncurses in 2003.
+NetBSD copied this feature of \fI\%ncurses\fP in 2003.
.br
PDCurses follows the scheme used in Solaris X/Open curses.
.SH BUGS
diff --git a/man/default_colors.3x b/man/default_colors.3x
index b33f8f09e..036bd2cba 100644
--- a/man/default_colors.3x
+++ b/man/default_colors.3x
@@ -93,9 +93,9 @@ .SH DESCRIPTION
.I assume_default_colors(\-1,\-1);
.RE
.PP
-These are ncurses extensions.
+These are \fI\%ncurses\fP extensions.
For other curses implementations, color
-number \-1 does not mean anything, just as for ncurses before a
+number \-1 does not mean anything, just as for \fI\%ncurses\fP before a
successful call of \fBuse_default_colors\fP or \fBassume_default_colors\fP.
.PP
Other curses implementations do not allow an application to modify color pair
0.
@@ -106,7 +106,7 @@ .SH DESCRIPTION
.B use_default_colors
or
.B assume_default_colors
-ncurses will paint a white foreground (text) with black background
+\fI\%ncurses\fP will paint a white foreground (text) with black background
for color pair 0.
.SH RETURN VALUE
These functions return the integer \fBERR\fP upon failure
@@ -140,7 +140,7 @@ .SH NOTES
environment variables and other configuration to bypass curses'
notion of the terminal's default colors, setting specific values.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/define_key.3x b/man/define_key.3x
index 48e7b61a4..8fe3b3f15 100644
--- a/man/define_key.3x
+++ b/man/define_key.3x
@@ -43,7 +43,8 @@ .SH SYNOPSIS
.SH DESCRIPTION
This is an extension to the \fIcurses\fP library.
It permits an application to define keycodes with their corresponding control
-strings, so that the \fIncurses\fP library will interpret them just as it would
+strings,
+so that the \fI\%ncurses\fP library will interpret them just as it would
the predefined codes in the terminfo database.
.PP
If \fIdefinition\fP is \fBNULL\fP,
@@ -58,7 +59,7 @@ .SH RETURN VALUE
data to store the definition.
If no error is detected, \fBOK\fP is returned.
.SH PORTABILITY
-These routines are specific to \fIncurses\fP.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/form.3x b/man/form.3x
index 0ce6bbb4e..08d17e859 100644
--- a/man/form.3x
+++ b/man/form.3x
@@ -89,7 +89,7 @@ .SS Routine Name Index
The following table lists each \fBform\fP routine and the name of
the manual page on which it is described.
Routines flagged with \*(``*\*(''
-are ncurses-specific, not present in SVr4.
+are \fI\%ncurses\fP-specific, not present in SVr4.
.PP
.TS
l l
@@ -226,19 +226,20 @@ .SH PORTABILITY
.PP
It is not part of X/Open Curses.
.PP
-Aside from ncurses, there are few implementations:
+Aside from \fI\%ncurses\fP, there are few implementations:
.bP
systems based on SVr4 source code, e.g., Solaris.
.bP
NetBSD curses.
.PP
-A few functions in this implementation are extensions added for ncurses,
+A few functions in this implementation are extensions added for
+\fI\%ncurses\fP,
but not provided by other implementations, e.g.,
\fBform_driver_w\fP,
\fBunfocus_current_field\fP.
.SH AUTHORS
Juergen Pfeifer.
-Manual pages and adaptation for ncurses by Eric
+Manual pages and adaptation for \fI\%ncurses\fP by Eric
S. Raymond.
.SH SEE ALSO
\fBcurses\fP(3X) and related pages whose names begin \*(``form_\*('' for
diff --git a/man/form_field_buffer.3x b/man/form_field_buffer.3x
index fde890e3e..ddd0cfed6 100644
--- a/man/form_field_buffer.3x
+++ b/man/form_field_buffer.3x
@@ -136,7 +136,7 @@ .SH PORTABILITY
They were not supported on
Version 7 or BSD versions.
.PP
-The \fBset_max_field\fP function checks for an ncurses extension
+The \fBset_max_field\fP function checks for an \fI\%ncurses\fP extension
\fBO_INPUT_FIELD\fP which allows a dynamic field to shrink if the new
limit is smaller than the current field size.
.SH AUTHORS
diff --git a/man/form_field_validation.3x b/man/form_field_validation.3x
index c037d59ef..843f400b3 100644
--- a/man/form_field_validation.3x
+++ b/man/form_field_validation.3x
@@ -184,7 +184,7 @@ .SS TYPE_IPV4
Trailing blanks in the buffer are ignored.
The address itself is not validated.
.PP
-This is an ncurses extension;
+This is an \fI\%ncurses\fP extension;
this field type may not be available in other curses implementations.
.SH RETURN VALUE
The functions \fBfield_type\fP and \fBfield_arg\fP return \fBNULL\fP on error.
diff --git a/man/form_page.3x b/man/form_page.3x
index a4e94f37d..b5cf36b30 100644
--- a/man/form_page.3x
+++ b/man/form_page.3x
@@ -88,7 +88,8 @@ .SH PORTABILITY
They were not supported on
Version 7 or BSD versions.
.PP
-The \fBunfocus_current_field\fP function is an ncurses extension.
+The \fBunfocus_current_field\fP function is an \fI\%ncurses\fP
+extension.
.SH AUTHORS
Juergen Pfeifer.
Manual pages and adaptation for new curses by Eric S. Raymond.
diff --git a/man/form_requestname.3x b/man/form_requestname.3x
index 68cfb8abd..8765ac96a 100644
--- a/man/form_requestname.3x
+++ b/man/form_requestname.3x
@@ -53,7 +53,7 @@ .SH RETURN VALUE
\fBform_request_by_name\fP returns \fBE_NO_MATCH\fP on error.
It does not set \fBerrno\fP.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/infocmp.1m b/man/infocmp.1m
index 291fe2163..718577644 100644
--- a/man/infocmp.1m
+++ b/man/infocmp.1m
@@ -270,7 +270,7 @@ .SS Use= Option [\-u]
\fB@INFOCMP@\fP will flag any other \fIterminal-type use=\fP fields that
were not needed.
.SS Changing Databases [\-A \fIdirectory\fR] [\-B \fIdirectory\fR]
-Like other \fBncurses\fP utilities,
+Like other \fI\%ncurses\fP utilities,
\fB@INFOCMP@\fP looks for the terminal descriptions in several places.
You can use the \fI\%TERMINFO\fP and \fI\%TERMINFO_DIRS\fP environment
variables to override the compiled-in default list of places to search.
@@ -321,9 +321,10 @@ .SS Other Options
The tables are all declared static, and are named according to the type
and the name of the corresponding terminal entry.
.sp
-Before ncurses 5.0, the split between the \fB\-e\fP and \fB\-E\fP
-options was not needed; but support for extended names required making
-the arrays of terminal capabilities separate from the TERMTYPE structure.
+Before \fI\%ncurses\fP 5.0,
+the split between the \fB\-e\fP and \fB\-E\fP options was not needed;
+but support for extended names required making the arrays of terminal
+capabilities separate from the TERMTYPE structure.
.TP 5
\fB\-e\fP
Dump the capabilities of the given terminal as a C initializer for a
@@ -551,14 +552,16 @@ .SS Other Options
data.
.TP 5
\fB\-V\fP
-reports the version of ncurses which was used in this program, and exits.
+reports the version of \fI\%ncurses\fP which was used in this program,
+and exits.
.TP 5
\fB\-v\fP \fIn\fP
prints out tracing information on standard error as the program runs.
.IP
The optional parameter \fIn\fP is a number from 1 to 10, inclusive,
indicating the desired level of detail of information.
-If ncurses is built without tracing support, the optional parameter is ignored.
+If \fI\%ncurses\fP is built without tracing support,
+the optional parameter is ignored.
.TP
\fB\-W\fP
By itself, the \fB\-w\fP option will not force long strings to be wrapped.
@@ -618,7 +621,7 @@ .SH HISTORY
for System V Release 3.
.PP
Eric Raymond used the AT&T documentation in 1995 to provide an equivalent
-\fB@INFOCMP@\fP for ncurses.
+\fB@INFOCMP@\fP for \fI\%ncurses\fP.
In addition, he added a few new features such as:
.bP
the \fB\-e\fP option, to support \fIfallback\fP
@@ -633,9 +636,9 @@ .SH HISTORY
For a complete list, see the \fIEXTENSIONS\fP section.
.PP
In 2010, Roy Marples provided an \fBinfocmp\fP program for NetBSD.
-It is less capable than the SVr4 or ncurses versions
+It is less capable than the SVr4 or \fI\%ncurses\fP versions
(e.g., it lacks the sorting options documented in X/Open),
-but does include the \fB\-x\fP option adapted from ncurses.
+but does include the \fB\-x\fP option adapted from \fI\%ncurses\fP.
.SH BUGS
The \fB\-F\fP option of \fB\%@INFOCMP@\fP(1M) should be a
\fB\%@TOE@\fP(1M) mode.
diff --git a/man/key_defined.3x b/man/key_defined.3x
index 311315418..1b15cabbd 100644
--- a/man/key_defined.3x
+++ b/man/key_defined.3x
@@ -50,7 +50,7 @@ .SH RETURN VALUE
If the string conflicts with longer strings
which are bound to keys, \-1 is returned.
.SH PORTABILITY
-This routine is specific to \fIncurses\fP.
+This routine is specific to \fI\%ncurses\fP.
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/keybound.3x b/man/keybound.3x
index f72cd664d..c9ee48a4b 100644
--- a/man/keybound.3x
+++ b/man/keybound.3x
@@ -53,7 +53,7 @@ .SH RETURN VALUE
When successful,
the function returns a string which must be freed by the caller.
.SH PORTABILITY
-This routine is specific to \fIncurses\fP.
+This routine is specific to \fI\%ncurses\fP.
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/keyok.3x b/man/keyok.3x
index b2e402d1f..202bacf69 100644
--- a/man/keyok.3x
+++ b/man/keyok.3x
@@ -52,7 +52,7 @@ .SH RETURN VALUE
and vice versa.
Otherwise, the function returns \fBOK\fP.
.SH PORTABILITY
-This routine is specific to \fIncurses\fP.
+This routine is specific to \fI\%ncurses\fP.
It was not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/legacy_coding.3x b/man/legacy_coding.3x
index fad145c04..004309039 100644
--- a/man/legacy_coding.3x
+++ b/man/legacy_coding.3x
@@ -68,9 +68,9 @@ .SH RETURN VALUE
the function returns \fBERR\fP.
Otherwise, it returns the previous level: \fB0\fP, \fB1\fP or \fB2\fP.
.SH PORTABILITY
-This routine is specific to ncurses.
+This routine is specific to \fI\%ncurses\fP.
It was not supported on Version 7, BSD or System V implementations.
-It is recommended that any code depending on ncurses extensions
+It is recommended that any code depending on \fI\%ncurses\fP extensions
be conditioned using NCURSES_VERSION.
.SH AUTHORS
Thomas Dickey (to support lynx's font-switching feature).
diff --git a/man/menu.3x b/man/menu.3x
index 601ec050c..1d7dd923f 100644
--- a/man/menu.3x
+++ b/man/menu.3x
@@ -202,14 +202,14 @@ .SH PORTABILITY
.PP
It is not part of X/Open Curses.
.PP
-Aside from ncurses, there are few implementations:
+Aside from \fI\%ncurses\fP, there are few implementations:
.bP
systems based on SVr4 source code, e.g., Solaris.
.bP
NetBSD curses.
.SH AUTHORS
Juergen Pfeifer.
-Manual pages and adaptation for ncurses by Eric S. Raymond.
+Manual pages and adaptation for \fI\%ncurses\fP by Eric S. Raymond.
.SH SEE ALSO
\fB\%curses\fP(3X) and related pages whose names begin \*(``menu_\*(''
for detailed descriptions of the entry points.
diff --git a/man/menu_driver.3x b/man/menu_driver.3x
index 19ab95e53..dfc6b8dff 100644
--- a/man/menu_driver.3x
+++ b/man/menu_driver.3x
@@ -195,7 +195,7 @@ .SH PORTABILITY
These routines emulate the System V menu library.
They were not supported on
Version 7 or BSD versions.
-The support for mouse events is ncurses specific.
+The support for mouse events is \fI\%ncurses\fP specific.
.SH AUTHORS
Juergen Pfeifer.
Manual pages and adaptation for new curses by Eric S. Raymond.
diff --git a/man/menu_requestname.3x b/man/menu_requestname.3x
index 897fd7354..9d4993b41 100644
--- a/man/menu_requestname.3x
+++ b/man/menu_requestname.3x
@@ -54,7 +54,7 @@ .SH RETURN VALUE
\fBmenu_request_by_name\fP returns \fBE_NO_MATCH\fP on error.
It does not set \fBerrno\fP.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/menu_spacing.3x b/man/menu_spacing.3x
index 06a9b03ba..ba10a27da 100644
--- a/man/menu_spacing.3x
+++ b/man/menu_spacing.3x
@@ -80,7 +80,7 @@ .SH RETURN VALUE
\fBE_POSTED\fP if the menu is posted, or \fBE_BAD_ARGUMENT\fP if one of the
spacing values is out of range.
.SH PORTABILITY
-These routines are specific to ncurses.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/ncurses.3x b/man/ncurses.3x
index c8a58fac8..18923c082 100644
--- a/man/ncurses.3x
+++ b/man/ncurses.3x
@@ -54,19 +54,20 @@ .SH SYNOPSIS
\fB#include <curses.h>
.fi
.SH DESCRIPTION
-The \fBncurses\fP library routines give the user a terminal-independent method
-of updating character screens with reasonable optimization.
-This implementation is \*(``new curses\*('' (ncurses) and
+The \fI\%ncurses\fP library routines give the user a
+terminal-independent method of updating character screens with
+reasonable optimization.
+This implementation is \*(``new curses\*('' (\fI\%ncurses\fP) and
is the approved replacement for
4.4BSD classic curses, which has been discontinued.
-This describes \fBncurses\fP
+This describes \fI\%ncurses\fP
version @NCURSES_MAJOR@.@NCURSES_MINOR@ (patch @NCURSES_PATCH@).
.PP
-The \fBncurses\fP library emulates the curses library of
+The \fI\%ncurses\fP library emulates the curses library of
System V Release 4 Unix (\*(``SVr4\*(''),
and XPG4 (X/Open Portability Guide) curses (also known as XSI curses).
XSI stands for X/Open System Interfaces Extension.
-The \fBncurses\fP library is freely redistributable in source form.
+The \fI\%ncurses\fP library is freely redistributable in source form.
.PP
\fI\%ncurses\fP man pages employ several sections to clarify matters of
usage and interoperability with other \fIcurses\fP implementations.
@@ -106,7 +107,7 @@ .SH DESCRIPTION
that describe curses actions.
See also the section on \fBALTERNATE CONFIGURATIONS\fP.
.PP
-The \fBncurses\fP package supports: overall screen, window and pad
+The \fI\%ncurses\fP package supports: overall screen, window and pad
manipulation; output to windows and pads; reading terminal input; control over
terminal and \fBcurses\fP input and output options; environment query
routines; color manipulation; use of soft label keys; terminfo capabilities;
@@ -159,7 +160,7 @@ .SS Initialization
(The BSD-style \fB\%@TSET@\fP(1) utility also performs this function.)
See subsection \*(``Tabs and Initialization\*('' of \fBterminfo\fP(5).
.SS Datatypes
-The \fBncurses\fP library permits manipulation of data structures,
+The \fI\%ncurses\fP library permits manipulation of data structures,
called \fIwindows\fP, which can be thought of as two-dimensional
arrays of characters representing all or part of a CRT screen.
A default window called \fBstdscr\fP, which is the size of the terminal
@@ -175,7 +176,7 @@ .SS Datatypes
.PP
Windows are referred to by variables declared as \fBWINDOW *\fP.
These data structures are manipulated with routines described here and
-elsewhere in the \fBncurses\fP manual pages.
+elsewhere in the \fI\%ncurses\fP manual pages.
Among those, the most basic
routines are \fBmove\fP and \fBaddch\fP.
More general versions of
@@ -353,7 +354,7 @@ .SS Routine Name Index
the \*(``normal\*('' and \*(``wide\*('' libraries and the names of
the manual pages on which they are described.
Routines flagged with \*(``*\*(''
-are ncurses-specific, not described by XPG4 or present in SVr4.
+are \fI\%ncurses\fP-specific, not described by XPG4 or present in SVr4.
.PP
.TS
center tab(/);
@@ -854,7 +855,7 @@ .SH RETURN VALUE
Routines that return pointers return \fBNULL\fP on error.
.SH ENVIRONMENT
The following environment symbols are useful for customizing the
-runtime behavior of the \fBncurses\fP library.
+runtime behavior of the \fI\%ncurses\fP library.
The most important ones have been already discussed in detail.
.SS \fICC\fP command-character
When set, change occurrences of the command_character
@@ -863,13 +864,14 @@ .SS \fICC\fP command-character
Very few terminfo entries provide this feature.
.PP
Because this name is also used in development environments to represent
-the C compiler's name, \fBncurses\fP ignores it if it does not happen to
-be a single character.
+the C compiler's name,
+\fI\%ncurses\fP ignores it if it does not happen to be a single
+character.
.SS \fIBAUDRATE\fP
The debugging library checks this environment variable when the application
has redirected output to a file.
The variable's numeric value is used for the baudrate.
-If no value is found, \fBncurses\fP uses 9600.
+If no value is found, \fI\%ncurses\fP uses 9600.
This allows testers to construct repeatable test-cases
that take into account costs that depend on baudrate.
.SS \fICOLUMNS\fP
@@ -877,7 +879,8 @@ .SS \fICOLUMNS\fP
Applications running in a windowing environment usually are able to
obtain the width of the window in which they are executing.
If neither the \fI\%COLUMNS\fP value nor the terminal's screen size is
available,
-\fBncurses\fP uses the size which may be specified in the terminfo database
+\fI\%ncurses\fP uses the size which may be specified in the terminfo
+database
(i.e., the \fBcols\fP capability).
.PP
It is important that your application use a correct size for the screen.
@@ -901,8 +904,11 @@ .SS \fICOLUMNS\fP
\fILINES\fP to match the screen size obtained from system calls or the
terminal database.
.SS \fIESCDELAY\fP
-Specifies the total time, in milliseconds, for which ncurses will
-await a character sequence, e.g., a function key.
+Specifies the total time,
+in milliseconds,
+for which \fI\%ncurses\fP will await a character sequence,
+e.g.,
+a function key.
The default value, 1000 milliseconds, is enough for most uses.
However, it is made a variable to accommodate unusual applications.
.PP
@@ -925,7 +931,7 @@ .SS \fIESCDELAY\fP
but setting the environment variable rather than the global variable
does not create problems when compiling an application.
.SS \fIHOME\fP
-Tells \fBncurses\fP where your home directory is.
+Tells \fI\%ncurses\fP where your home directory is.
That is where it may read and write auxiliary terminal descriptions:
.PP
.RS 4
@@ -953,19 +959,19 @@ .SS \fIMOUSE_BUTTONS_123\fP
.PP
This variable lets you customize the mouse.
The variable must be three numeric digits 1\-3 in any order, e.g., 123 or 321.
-If it is not specified, \fBncurses\fP uses 132.
+If it is not specified, \fI\%ncurses\fP uses 132.
.SS \fINCURSES_ASSUMED_COLORS\fP
Override the compiled-in assumption that the
terminal's default colors are white-on-black
(see \fBdefault_colors\fP(3X)).
You may set the foreground and background color values with this environment
variable by proving a 2-element list: foreground,background.
-For example, to tell ncurses to not assume anything
+For example, to tell \fI\%ncurses\fP to not assume anything
about the colors, set this to "\-1,\-1".
To make it green-on-black, set it to "2,0".
Any positive value from zero to the terminfo \fBmax_colors\fP value is allowed.
.SS \fINCURSES_CONSOLE2\fP
-This applies only to the MinGW port of ncurses.
+This applies only to the MinGW port of \fI\%ncurses\fP.
.PP
The \fBConsole2\fP program's handling of the Microsoft Console API call
\fBCreateConsoleScreenBuffer\fP is defective.
@@ -975,7 +981,8 @@ .SS \fINCURSES_CONSOLE2\fP
explicitly saving and restoring the original screen contents.
Setting the environment variable \fBNCGDB\fP has the same effect.
.SS \fINCURSES_GPM_TERMS\fP
-This applies only to ncurses configured to use the GPM interface.
+This applies only to \fI\%ncurses\fP configured to use the GPM
+interface.
.PP
If present,
the environment variable is a list of one or more terminal names
@@ -984,9 +991,11 @@ .SS \fINCURSES_GPM_TERMS\fP
using the built-in support for xterm, etc.
.PP
If the environment variable is absent,
-ncurses will attempt to open GPM if \fITERM\fP contains \*(``linux\*(''.
+\fI\%ncurses\fP will attempt to open GPM if \fITERM\fP contains
+\*(``linux\*(''.
.SS \fINCURSES_NO_HARD_TABS\fP
-\fBNcurses\fP may use tabs as part of the cursor movement optimization.
+\fI\%ncurses\fP may use tabs as part of the cursor movement
+optimization.
In some cases,
your terminal driver may not handle these properly.
Set this environment variable to disable the feature.
@@ -1034,38 +1043,39 @@ .SS \fINCURSES_NO_SETBUF\fP
though 5.9 patch 20130126
.RE
.PP
-\fBncurses\fP enabled buffered output during terminal initialization.
+\fI\%ncurses\fP enabled buffered output during terminal initialization.
This was done (as in SVr4 curses) for performance reasons.
-For testing purposes, both of \fBncurses\fP and certain applications,
+For testing purposes, both of \fI\%ncurses\fP and certain applications,
this feature was made optional.
Setting the \fI\%NCURSES_NO_SETBUF\fP variable
disabled output buffering, leaving the output in the original (usually
line buffered) mode.
.PP
In the current implementation,
-ncurses performs its own buffering and does not require this workaround.
+\fI\%ncurses\fP performs its own buffering and does not require this
+workaround.
It does not modify the buffering of the standard output.
.PP
The reason for the change was to make the behavior for interrupts and
other signals more robust.
One drawback is that certain nonconventional programs would mix
-ordinary stdio calls with ncurses calls and (usually) work.
-This is no longer possible since ncurses is not using
+ordinary stdio calls with \fI\%ncurses\fP calls and (usually) work.
+This is no longer possible since \fI\%ncurses\fP is not using
the buffered standard output but its own output (to the same file descriptor).
As a special case, the low-level calls such as \fBputp\fP still use the
standard output.
But high-level curses calls do not.
.SS \fINCURSES_NO_UTF8_ACS\fP
-During initialization, the \fBncurses\fP library
+During initialization, the \fI\%ncurses\fP library
checks for special cases where VT100 line-drawing (and the corresponding
alternate character set capabilities) described in the terminfo are known
to be missing.
Specifically, when running in a UTF\-8 locale,
the Linux console emulator and the GNU screen program ignore these.
-Ncurses checks the \fITERM\fP environment variable for these.
+\fI\%ncurses checks the \fITERM\fP environment variable for these.
For other special cases, you should set this environment variable.
-Doing this tells ncurses to use Unicode values which correspond to
-the VT100 line-drawing glyphs.
+Doing this tells \fI\%ncurses\fP to use Unicode values which correspond
+to the VT100 line-drawing glyphs.
That works for the special cases cited,
and is likely to work for terminal emulators.
.PP
@@ -1074,7 +1084,7 @@ .SS \fINCURSES_NO_UTF8_ACS\fP
disables the special check for \*(``linux\*('' and \*(``screen\*(''.
.PP
As an alternative to the environment variable,
-ncurses checks for an extended terminfo capability \fBU8\fP.
+\fI\%ncurses\fP checks for an extended terminfo capability \fBU8\fP.
This is a numeric capability which can be compiled using \fB@TIC@\ \-x\fP.
For example
.PP
@@ -1092,13 +1102,15 @@ .SS \fINCURSES_NO_UTF8_ACS\fP
.RE
.PP
The name \*(``U8\*('' is chosen to be two characters,
-to permit it to be used by applications that use ncurses'
+to permit it to be used by applications that use \fI\%ncurses\fP'
termcap interface.
.SS \fINCURSES_TRACE\fP
-During initialization, the \fBncurses\fP debugging library
+During initialization, the \fI\%ncurses\fP debugging library
checks the \fI\%NCURSES_TRACE\fP environment variable.
-If it is defined, to a numeric value, \fBncurses\fP calls the \fBtrace\fP
-function, using that value as the argument.
+If it is defined,
+to a numeric value,
+\fI\%ncurses\fP calls the \fBtrace\fP function,
+using that value as the argument.
.PP
The argument values, which are defined in \fBcurses.h\fP, provide several
types of information.
@@ -1125,18 +1137,19 @@ .SS \fITERM\fP
specify \fITERM\fP as a parameter or configuration value do
not change their behavior to match that setting.
.SS \fITERMCAP\fP
-If the \fBncurses\fP library has been configured with \fItermcap\fP
-support, \fBncurses\fP will check for a terminal's description in
+If the \fI\%ncurses\fP library has been configured with \fItermcap\fP
+support, \fI\%ncurses\fP will check for a terminal's description in
termcap form if it is not available in the terminfo database.
.PP
The \fI\%TERMCAP\fP environment variable contains
either a terminal description (with newlines stripped out),
or a file name telling where the information denoted by
the \fITERM\fP environment variable exists.
-In either case, setting it directs \fBncurses\fP to ignore
+In either case, setting it directs \fI\%ncurses\fP to ignore
the usual place for this information, e.g., /etc/termcap.
.SS \fITERMINFO\fP
-\fBncurses\fP can be configured to read from multiple terminal databases.
+\fI\%ncurses\fP can be configured to read from multiple terminal
+databases.
The \fI\%TERMINFO\fP variable overrides the location for
the default terminal database.
Terminal descriptions (in terminal format) are stored in terminal databases:
@@ -1149,7 +1162,7 @@ .SS \fITERMINFO\fP
on those
systems to override the default location of the terminal database.
.IP \(bu 4
-If \fBncurses\fP is built to use hashed databases,
+If \fI\%ncurses\fP is built to use hashed databases,
then each entry in this list may be the path of a hashed database file, e.g.,
.RS 4
.PP
@@ -1175,13 +1188,13 @@ .SS \fITERMINFO\fP
rather than using the terminfo library calls.
.RE
.bP
-If \fBncurses\fP is built with a support for reading termcap files
+If \fI\%ncurses\fP is built with a support for reading termcap files
directly, then an entry in this list may be the path of a termcap file.
.IP \(bu 4
If the \fI\%TERMINFO\fP variable begins with
\*(``hex:\*('' or \*(``b64:\*('',
-\fBncurses\fP uses the remainder of that variable as a compiled terminal
-description.
+\fI\%ncurses\fP uses the remainder of that variable as a compiled
+terminal description.
You might produce the base64 format using \fBinfocmp\fP(1M):
.RS 4
.PP
@@ -1201,7 +1214,7 @@ .SS \fITERMINFO\fP
The complete list of database locations in order follows:
.RS 3
.bP
-the last terminal database to which \fBncurses\fP wrote,
+the last terminal database to which \fI\%ncurses\fP wrote,
if any, is searched first
.bP
the location specified by the \fI\%TERMINFO\fP environment variable
@@ -1211,7 +1224,7 @@ .SS \fITERMINFO\fP
locations listed in the \fI\%TERMINFO_DIRS\fP environment variable
.bP
one or more locations whose names are configured and compiled into the
-ncurses library, i.e.,
+\fI\%ncurses\fP library, i.e.,
.RS 3
.bP
@TERMINFO_DIRS@ (corresponding to the \fI\%TERMINFO_DIRS\fP variable)
@@ -1226,15 +1239,15 @@ .SS \fITERMINFO_DIRS\fP
The list is separated by colons (i.e., ":") on Unix, semicolons on OS/2 EMX.
.PP
There is no corresponding feature in System V terminfo;
-it is an extension developed for \fBncurses\fP.
+it is an extension developed for \fI\%ncurses\fP.
.SS \fITERMPATH\fP
-If \fI\%TERMCAP\fP does not hold a file name then \fBncurses\fP checks
+If \fI\%TERMCAP\fP does not hold a file name then \fI\%ncurses\fP checks
the \fI\%TERMPATH\fP environment variable.
This is a list of filenames separated by spaces or colons (i.e., ":") on Unix,
semicolons on OS/2 EMX.
.PP
If the \fI\%TERMPATH\fP environment variable is not set,
-\fBncurses\fP looks in the files
+\fI\%ncurses\fP looks in the files
.PP
.RS 4
.EX
@@ -1255,12 +1268,13 @@ .SS \fITERMPATH\fP
.RE
.SH ALTERNATE CONFIGURATIONS
Several different configurations are possible,
-depending on the configure script options used when building \fBncurses\fP.
+depending on the configure script options used when building
+\fI\%ncurses\fP.
There are a few main options whose effects are visible to the applications
-developer using \fBncurses\fP:
+developer using \fI\%ncurses\fP:
.TP 5
\-\-disable\-overwrite
-The standard include for \fBncurses\fP is as noted in \fBSYNOPSIS\fP:
+The standard include for \fI\%ncurses\fP is as noted in \fBSYNOPSIS\fP:
.RS 5
.PP
.RS 4
@@ -1269,10 +1283,11 @@ .SH ALTERNATE CONFIGURATIONS
.EE
.RE
.PP
-This option is used to avoid filename conflicts when \fBncurses\fP
+This option is used to avoid filename conflicts when \fI\%ncurses\fP
is not the main implementation of curses of the computer.
-If \fBncurses\fP is installed disabling overwrite, it puts its headers in
-a subdirectory, e.g.,
+If \fI\%ncurses\fP is installed disabling overwrite,
+it puts its headers in a subdirectory,
+e.g.,
.PP
.RS 4
.EX
@@ -1400,58 +1415,64 @@ .SH FILES
.I \*d
compiled terminal capability database
.SH NOTES
-If standard output from a \fBncurses\fP program is re-directed to something
-which is not a tty, screen updates will be directed to standard error.
+If standard output from a \fI\%ncurses\fP program is re-directed to
+something which is not a tty,
+screen updates will be directed to standard error.
This was an undocumented feature of AT&T System V Release 3 curses.
.PP
See subsection \*(``Header files\*('' below regarding symbols exposed by
inclusion of \fI\%curses.h\fP.
.SH EXTENSIONS
-The \fBncurses\fP library can be compiled with an option (\fB\-DUSE_GETCAP\fP)
+The \fI\%ncurses\fP library can be compiled with an option
+(\fB\-DUSE_GETCAP\fP)
that falls back to the old-style /etc/termcap file if the terminal setup code
cannot find a terminfo entry corresponding to \fITERM\fP.
-Use of this feature
-is not recommended, as it essentially includes an entire termcap compiler in
-the \fBncurses\fP startup code, at significant cost in core and startup cycles.
-.PP
-The \fBncurses\fP library includes facilities for capturing mouse events on
-certain terminals (including xterm).
+Use of this feature is not recommended,
+as it essentially includes an entire termcap compiler in the
+\fI\%ncurses\fP startup code,
+at significant cost in core and startup cycles.
+.PP
+The \fI\%ncurses\fP library includes facilities for capturing mouse
+events on certain terminals
+(including xterm).
See the \fBcurs_mouse\fP(3X)
manual page for details.
.PP
-The \fBncurses\fP library includes facilities for responding to window
+The \fI\%ncurses\fP library includes facilities for responding to window
resizing events, e.g., when running in an xterm.
See the \fBresizeterm\fP(3X)
and \fBwresize\fP(3X) manual pages for details.
In addition, the library may be configured with a \fBSIGWINCH\fP handler.
.PP
-The \fBncurses\fP library extends the fixed set of function key capabilities
-of terminals by allowing the application designer to define additional
-key sequences at runtime.
+The \fI\%ncurses\fP library extends the fixed set of function key
+capabilities of terminals by allowing the application designer to define
+additional key sequences at runtime.
See the \fBdefine_key\fP(3X)
\fBkey_defined\fP(3X),
and \fBkeyok\fP(3X) manual pages for details.
.PP
-The \fBncurses\fP library can exploit the capabilities of terminals which
-implement the ISO\-6429 SGR 39 and SGR 49 controls, which allow an application
-to reset the terminal to its original foreground and background colors.
+The \fI\%ncurses\fP library can exploit the capabilities of terminals
+which implement the ISO\-6429 SGR 39 and SGR 49 controls,
+which allow an application to reset the terminal to its original
+foreground and background colors.
From the users' perspective, the application is able to draw colored
text on a background whose color is set independently, providing better
control over color contrasts.
See the \fBdefault_colors\fP(3X) manual page for details.
.PP
-The \fBncurses\fP library includes a function for directing application output
-to a printer attached to the terminal device.
+The \fI\%ncurses\fP library includes a function for directing
+application output to a printer attached to the terminal device.
See the \fBcurs_print\fP(3X) manual page for details.
.SH PORTABILITY
-The \fBncurses\fP library is intended to be BASE-level conformant with XSI
-Curses.
+The \fI\%ncurses\fP library is intended to be BASE-level conformant with
+XSI Curses.
The EXTENDED XSI Curses functionality
(including color support) is supported.
.PP
-A small number of local differences (that is, individual differences between
-the XSI Curses and \fBncurses\fP calls) are described in \fBPORTABILITY\fP
-sections of the library man pages.
+A small number of local differences
+(that is,
+individual differences between the XSI Curses and \fI\%ncurses\fP calls)
+are described in \fBPORTABILITY\fP sections of the library man pages.
.SS Error checking
In many cases, X/Open Curses is vague about error conditions,
omitting some of the SVr4 documentation.
@@ -1465,7 +1486,8 @@ .SS Error checking
Relying on this (or some other) extension will adversely affect the
portability of curses applications.
.SS Extensions versus portability
-Most of the extensions provided by ncurses have not been standardized.
+Most of the extensions provided by \fI\%ncurses\fP have not been
+standardized.
Some have been incorporated into other implementations, such as
PDCurses or NetBSD curses.
Here are a few to consider:
@@ -1543,17 +1565,18 @@ .SS Header files
.bP
X/Open Curses is inconsistent with respect to SVr4 regarding <unctrl.h>.
.IP
-As noted in \fBcurs_util\fP(3X), ncurses includes <unctrl.h> from
-<curses.h> (like SVr4).
+As noted in \fBcurs_util\fP(3X),
+\fI\%ncurses\fP includes <unctrl.h> from <curses.h>
+(like SVr4).
.bP
X/Open's comments about <term.h> and <termios.h> may refer to HP-UX and AIX:
.IP
HP-UX curses includes <term.h> from <curses.h>
to declare \fBsetupterm\fP in curses.h,
-but ncurses (and Solaris curses) do not.
+but \fI\%ncurses\fP (and Solaris curses) do not.
.IP
AIX curses includes <term.h> and <termios.h>.
-Again, ncurses (and Solaris curses) do not.
+Again, \fI\%ncurses\fP (and Solaris curses) do not.
.bP
X/Open says that <curses.h> \fImay\fP include <term.h>,
but there is no requirement that it do that.
@@ -1563,17 +1586,17 @@ .SS Header files
Very old versions of AIX curses required including <curses.h>
before including <term.h>.
.IP
-Because ncurses header files include the headers needed to
+Because \fI\%ncurses\fP header files include the headers needed to
define datatypes used in the headers,
-ncurses header files can be included in any order.
+\fI\%ncurses\fP header files can be included in any order.
But for portability, you should include <curses.h> before <term.h>.
.bP
X/Open Curses says \fI"may make visible"\fP
because including a header file does not necessarily make all symbols
in it visible (there are ifdef's to consider).
.IP
-For instance, in ncurses <wchar.h> \fImay\fP be included if
-the proper symbol is defined, and if ncurses is configured for
+For instance, in \fI\%ncurses\fP <wchar.h> \fImay\fP be included if
+the proper symbol is defined, and if \fI\%ncurses\fP is configured for
wide-character support.
If the header is included, its symbols may be made visible.
That depends on the value used for \fB_XOPEN_SOURCE\fP
@@ -1599,8 +1622,10 @@ .SS Header files
.IP
None of the X/Open Curses implementations require an application
to include <stdarg.h> before <curses.h> because they either
-have allowed for a special type, or (like ncurses) include <stdarg.h>
-directly to provide a portable interface.
+have allowed for a special type,
+or
+(like \fI\%ncurses\fP)
+include <stdarg.h> directly to provide a portable interface.
.SH AUTHORS
Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.
Based on \fIpcurses\fP by Pavel Curtis.
diff --git a/man/new_pair.3x b/man/new_pair.3x
index 8da580b30..81b24eec1 100644
--- a/man/new_pair.3x
+++ b/man/new_pair.3x
@@ -130,7 +130,7 @@ .SS alloc_pair
The size of the table is determined by the terminfo \fBpairs\fP capability.
The table is shared with \fBinit_pair\fP;
in fact \fBalloc_pair\fP calls \fBinit_pair\fP after
-updating the \fIncurses\fP library's fast index
+updating the \fI\%ncurses\fP library's fast index
to the colors versus color pairs.
.SS find_pair
The \fBfind_pair\fP function accepts parameters for
@@ -155,7 +155,7 @@ .SH RETURN VALUE
Likewise, \fBfree_pair\fP returns \fBOK\fP unless it encounters an
error updating the fast index or if no such color pair is in use.
.SH PORTABILITY
-These routines are specific to \fIncurses\fP.
+These routines are specific to \fI\%ncurses\fP.
They were not supported on
Version 7, BSD or System V implementations.
It is recommended that
diff --git a/man/panel.3x b/man/panel.3x
index 497006ff4..81ad61c66 100644
--- a/man/panel.3x
+++ b/man/panel.3x
@@ -260,7 +260,7 @@ .SH HISTORY
such as Solaris,
provide this library.
.bP
-\fIncurses\fP (since version 0.6 in 1993)
+\fI\%ncurses\fP (since version 0.6 in 1993)
and \fIPDCurses\fP (since version 2.2 in 1995)
provide a panel library whose common ancestor
is a public domain implementation by Warren Tucker
diff --git a/man/resizeterm.3x b/man/resizeterm.3x
index 9b21b819e..46124da69 100644
--- a/man/resizeterm.3x
+++ b/man/resizeterm.3x
@@ -50,7 +50,8 @@ .SH SYNOPSIS
.fi
.SH DESCRIPTION
This is an extension to the \fIcurses\fP library.
-It provides callers with a hook into the \fIncurses\fP data to resize windows,
+It provides callers with a hook into the \fI\%ncurses\fP data to resize
+windows,
primarily for use by programs running in an X Window terminal (e.g., xterm)
when the terminal's screen size is changed by the user:
.bP
@@ -62,9 +63,9 @@ .SH DESCRIPTION
The added cells should match the current attributes of the windows.
.PP
If the calling program has not set up a handler for \fB\%SIGWINCH\fP
-when it initializes \fIncurses\fP
+when it initializes \fI\%ncurses\fP
(e.g., using \fB\%initscr\fP(3X) or \fB\%newterm\fP(3X)),
-then \fIncurses\fP sets a handler for \fB\%SIGWINCH\fP which notifies
+then \fI\%ncurses\fP sets a handler for \fB\%SIGWINCH\fP which notifies
the library when a window-size event has occurred.
The library checks for this notification
.bP
@@ -87,7 +88,7 @@ .SS resizeterm
The function \fB\%resizeterm\fP resizes the standard and current windows
(i.e., \fB\%stdscr\fP and \fB\%curscr\fP)
to the specified dimensions, and adjusts other bookkeeping data used by
-the \fIncurses\fP library that record the window dimensions
+the \fI\%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 \fB\%resizeterm\fP is
@@ -130,7 +131,8 @@ .SH NOTES
context where \fB\%malloc\fP or \fB\%realloc\fP may have been interrupted,
since it uses those functions.
.PP
-If \fIncurses\fP is configured to supply its own \fB\%SIGWINCH\fP handler,
+If \fI\%ncurses\fP is configured to supply its own \fB\%SIGWINCH\fP
+handler,
.bP
on receipt of a \fB\%SIGWINCH\fP, the handler sets a flag
.bP
@@ -150,8 +152,8 @@ .SH NOTES
.IP
Calling \fB\%resizeterm\fP or \fB\%resize_term\fP
directly from a signal handler is unsafe.
-This indirect method is used to provide a safe way to resize the \fIncurses\fP
-data structures.
+This indirect method is used to provide a safe way to resize the
+\fI\%ncurses\fP data structures.
.PP
If the environment variables \fILINES\fP or \fI\%COLUMNS\fP are set,
this overrides the library's use of the window size obtained from
@@ -168,7 +170,7 @@ .SH PORTABILITY
.PP
Doing that clears the screen and is visually distracting.
.PP
-This extension of \fIncurses\fP was introduced in mid-1995.
+This extension of \fI\%ncurses\fP was introduced in mid-1995.
It was adopted in NetBSD \fIcurses\fP (2001) and PDCurses (2003).
.SH AUTHORS
Thomas Dickey (from an equivalent function written in 1988 for BSD
\fIcurses\fP)
diff --git a/man/scr_dump.5 b/man/scr_dump.5
index 5d4981807..ed929e8fe 100644
--- a/man/scr_dump.5
+++ b/man/scr_dump.5
@@ -115,7 +115,7 @@ .SS ncurses6
.bP
The ncurses6 \fBgetwin\fP reads the legacy screen dumps from ncurses5.
.SS ncurses5 (legacy)
-The screen-dump feature was added to ncurses in June 1995.
+The screen-dump feature was added to \fI\%ncurses\fP in June 1995.
While there were fixes and improvements in succeeding years,
the basic scheme was unchanged:
.bP
@@ -228,7 +228,7 @@ .SS Unix System V
.bP
Solaris 10 (13273 bytes)
.bP
-ncurses5 (12888 bytes)
+\fI\%ncurses\fP5 (12888 bytes)
.SS Solaris
As noted above, Solaris curses has no magic number corresponding
to SVr4 curses.
@@ -436,11 +436,11 @@ .SH EXAMPLES
.SH AUTHORS
Thomas E. Dickey
.br
-extended screen-dump format for ncurses 6.0 (2015)
+extended screen-dump format for \fI\%ncurses\fP 6.0 (2015)
.sp
Eric S. Raymond
.br
-screen dump feature in ncurses 1.9.2d (1995)
+screen dump feature in \fI\%ncurses\fP 1.9.2d (1995)
.SH SEE ALSO
\fB\%curs_scr_dump\fP(3X),
\fB\%curs_util\fP(3X)
diff --git a/man/tabs.1 b/man/tabs.1
index a13fd2409..caa31445f 100644
--- a/man/tabs.1
+++ b/man/tabs.1
@@ -104,7 +104,8 @@ .SS General Options
option, but not to modify the terminal settings.
.TP
\fB\-V\fP
-reports the version of ncurses which was used in this program, and exits.
+reports the version of \fI\%ncurses\fP which was used in this program,
+and exits.
.PP
The \fB@TABS@\fP program processes a single list of tab stops.
The last option to be processed which defines a list is the one that
diff --git a/man/term.5 b/man/term.5
index 000a9da40..ab91a60c1 100644
--- a/man/term.5
+++ b/man/term.5
@@ -64,7 +64,8 @@ .SH SYNOPSIS
.SH DESCRIPTION
.SS STORAGE LOCATION
Compiled terminfo descriptions are placed under the directory \fB\*d\fP.
-Two configurations are supported (when building the \fBncurses\fP libraries):
+Two configurations are supported
+(when building the \fI\%ncurses\fP libraries):
.TP 5
.B directory tree
A two-level scheme is used to avoid a linear search
@@ -87,11 +88,12 @@ .SS STORAGE LOCATION
and records containing only aliases pointing to the primary name.
.IP
If built to write hashed databases,
-\fBncurses\fP can still read terminfo databases organized as a directory tree,
+\fI\%ncurses\fP can still read terminfo databases organized as a
+directory tree,
but cannot write entries into the directory tree.
It can write (or rewrite) entries in the hashed database.
.IP
-\fBncurses\fP distinguishes the two cases in the \fI\%TERMINFO\fP and
+\fI\%ncurses\fP distinguishes the two cases in the \fI\%TERMINFO\fP and
\fI\%TERMINFO_DIRS\fP environment variable by assuming a directory tree
for entries that correspond to an existing directory,
and hashed database otherwise.
@@ -219,14 +221,14 @@ .SS EXTENDED STORAGE FORMAT
the same binary format is used in all modern Unix systems.
Each system uses a predefined set of boolean, number or string capabilities.
.PP
-The \fBncurses\fP libraries and applications support
+The \fI\%ncurses\fP libraries and applications support
extended terminfo binary format,
allowing users to define capabilities which are loaded at runtime.
This
extension is made possible by using the fact that the other implementations
stop reading the terminfo data when they have reached the end of the size given
in the header.
-\fBncurses\fP checks the size,
+\fI\%ncurses\fP checks the size,
and if it exceeds that due to the predefined data,
continues to parse according to its own scheme.
.PP
@@ -253,8 +255,9 @@ .SS EXTENDED STORAGE FORMAT
include the extended capability \fInames\fP as well as
extended capability \fIvalues\fP.
.PP
-Using the counts and sizes, \fBncurses\fP allocates arrays and reads data
-for the extended capabilities in the same order as the header information.
+Using the counts and sizes,
+\fI\%ncurses\fP allocates arrays and reads data for the extended
+capabilities in the same order as the header information.
.PP
The extended string table contains values for string capabilities.
After the end of these values, it contains the names for each of
@@ -262,11 +265,12 @@ .SS EXTENDED STORAGE FORMAT
finally strings.
.PP
By storing terminal descriptions in this way,
-\fBncurses\fP is able to provide a database useful with legacy applications,
+\fI\%ncurses\fP is able to provide a database useful with legacy
+applications,
as well as providing data for applications which need more than the
predefined capabilities.
See \fBuser_caps\fP(5) for an overview
-of the way \fBncurses\fP uses this extended information.
+of the way \fI\%ncurses\fP uses this extended information.
.PP
Applications which manipulate terminal data can use the definitions
described in \fBterm_variables\fP(3X) which associate the long capability
@@ -274,7 +278,8 @@ .SS EXTENDED STORAGE FORMAT
.
.SS EXTENDED NUMBER FORMAT
On occasion, 16-bit signed integers are not large enough.
-With \fBncurses\fP 6.1, a new format was introduced by making a few changes
+With \fI\%ncurses\fP 6.1,
+a new format was introduced by making a few changes
to the legacy format:
.bP
a different magic number (octal 01036)
@@ -331,7 +336,7 @@ .SS Binary format
except in a few less-used details
where it was found that the latter did not match X/Open Curses.
The format used by the other Unix versions
-can be matched by building ncurses
+can be matched by building \fI\%ncurses\fP
with different configuration options.
.SS Magic codes
The magic number in a binary terminfo file is the first 16-bits (two bytes).
@@ -352,11 +357,11 @@ .SS Mixed-case terminal names
their names.
If the underlying filesystem ignores the difference between
uppercase and lowercase,
-\fBncurses\fP represents the \*(``first character\*(''
+\fI\%ncurses\fP represents the \*(``first character\*(''
of the terminal name used as
the intermediate level of a directory tree in (two-character) hexadecimal form.
.SS Limits
-\fBncurses\fP stores compiled terminal descriptions
+\fI\%ncurses\fP stores compiled terminal descriptions
in three related formats,
described in the sections
.bP
@@ -369,8 +374,8 @@ .SS Limits
The legacy storage format and the extended number format differ by
the types of numeric capability which they can store
(i.e., 16-bit versus 32-bit integers).
-The extended storage format introduced by ncurses 5.0 adds data to
-either of these formats.
+The extended storage format introduced by \fI\%ncurses\fP 5.0 adds data
+to either of these formats.
.PP
Some limitations apply:
.bP
@@ -432,11 +437,11 @@ .SH EXAMPLES
.SH AUTHORS
Thomas E. Dickey
.br
-extended terminfo format for ncurses 5.0
+extended terminfo format for \fI\%ncurses\fP 5.0
.br
-hashed database support for ncurses 5.6
+hashed database support for \fI\%ncurses\fP 5.6
.br
-extended number support for ncurses 6.1
+extended number support for \fI\%ncurses\fP 6.1
.sp
Eric S. Raymond
.br
diff --git a/man/terminfo.head b/man/terminfo.head
index 45475851c..77468a03b 100644
--- a/man/terminfo.head
+++ b/man/terminfo.head
@@ -75,7 +75,7 @@ describes terminals by giving a set of capabilities which they
have, by specifying how to perform screen operations, and by
specifying padding requirements and initialization sequences.
.PP
-This manual describes \fBncurses\fP
+This manual describes \fI\%ncurses\fP
version @NCURSES_MAJOR@.@NCURSES_MINOR@ (patch @NCURSES_PATCH@).
.SS Terminfo Entry Syntax
Entries in
diff --git a/man/terminfo.tail b/man/terminfo.tail
index 3560a461f..1f20e81d4 100644
--- a/man/terminfo.tail
+++ b/man/terminfo.tail
@@ -38,7 +38,8 @@ Occasionally there are special features of newer terminals
which
are awkward or impossible to represent by reusing the predefined
capabilities.
.PP
-\fBncurses\fP addresses this limitation by allowing user-defined capabilities.
+\fI\%ncurses\fP addresses this limitation by allowing user-defined
+capabilities.
The \fB@TIC@\fP and \fB@INFOCMP@\fP programs provide
the \fB\-x\fP option for this purpose.
When \fB\-x\fP is set,
@@ -49,8 +50,8 @@ it infers its type (boolean, number or string) from the syntax
and makes an extended table entry for that capability.
The \fBuse_extended_names\fP(3X) function makes this information
conditionally available to applications.
-The ncurses library provides the data leaving most of the behavior
-to applications:
+The \fI\%ncurses\fP library provides the data leaving most of the
+behavior to applications:
.bP
User-defined capability strings whose name begins
with \*(``k\*('' are treated as function keys.
@@ -73,7 +74,8 @@ In particular, providing extended sets of function keys (past
the 60
numbered keys and the handful of special named keys) is best done using
the longer names available using terminfo.
.PP
-The ncurses library uses a few of these user-defined capabilities,
+The \fI\%ncurses\fP library uses a few of these user-defined
+capabilities,
as described in \fBuser_caps\fR(5).
Other user-defined capabilities (including function keys) are
described in the terminal database, in the section on
@@ -244,7 +246,8 @@ in the example above.
.br
.ne 5
.SS Fetching Compiled Descriptions
-Terminal descriptions in \fBncurses\fP are stored in terminal databases.
+Terminal descriptions in \fI\%ncurses\fP are stored in terminal
+databases.
These databases, which are found by their pathname,
may be configured either as directory trees or hashed databases
(see \fBterm\fR(5)),
@@ -252,16 +255,16 @@ may be configured either as directory trees or hashed
databases
The library uses a compiled-in list of pathnames,
which can be overridden by environment variables.
Before starting to search,
-\fBncurses\fP checks the search list,
+\fI\%ncurses\fP checks the search list,
eliminating duplicates and pathnames where no terminal database is found.
-The \fBncurses\fP library reads the first description
+The \fI\%ncurses\fP library reads the first description
which passes its consistency checks.
.bP
The environment variable \fBTERMINFO\fR is checked first, for
a terminal database containing the terminal description.
.bP
Next,
-\fBncurses\fP looks in \fI$HOME/.terminfo\fP
+\fI\%ncurses\fP looks in \fI$HOME/.terminfo\fP
for a compiled description.
.IP
This is an optional feature which may be omitted entirely from
@@ -269,14 +272,14 @@ the library, or limited to prevent accidental use by
privileged applications.
.bP
Next,
if the environment variable \fI\%TERMINFO_DIRS\fP is set,
-\fBncurses\fP interprets the contents of that variable
+\fI\%ncurses\fP interprets the contents of that variable
as a list of colon-separated pathnames of terminal databases to be searched.
.IP
An empty pathname (i.e., if the variable begins or ends
with a colon, or contains adjacent colons)
is interpreted as the system location \fI\*d\fP.
.bP
-Finally, \fBncurses\fP searches these compiled-in locations:
+Finally, \fI\%ncurses\fP searches these compiled-in locations:
.RS
.bP
a list of directories (@TERMINFO_DIRS@), and
@@ -287,16 +290,17 @@ the system terminfo directory, \fI\*d\fP
The \fBTERMINFO\fP variable can contain a terminal description instead
of the pathname of a terminal database.
If this variable begins with \*(``hex:\*('' or \*(``b64:\*(''
-then \fBncurses\fP reads a terminal description from
+then \fI\%ncurses\fP reads a terminal description from
hexadecimal- or base64-encoded data,
and if that description matches the name sought, will use that.
This encoded data can be set using the \*(``\-Q\*('' option of
\fB@TIC@\fR or \fB@INFOCMP@\fR.
.PP
-The preceding addresses the usual configuration of \fBncurses\fP,
+The preceding addresses the usual configuration of \fI\%ncurses\fP,
which uses terminal descriptions prepared in \fIterminfo\fP format.
While \fItermcap\fP is less expressive,
-\fBncurses\fP can also be configured to read \fItermcap\fP descriptions.
+\fI\%ncurses\fP can also be configured to read \fItermcap\fP
+descriptions.
In that configuration,
it checks the \fI\%TERMCAP\fP and \fI\%TERMPATH\fP variables
(for content and search path,
@@ -532,18 +536,20 @@ Solaris XPG4 curses does not distinguish between
\fIdynamic\fP and
They are the same.
Like SVr4 curses, XPG4 curses does not initialize these explicitly.
.bP
-Before version 6.3, ncurses stores both \fIdynamic\fP and \fIstatic\fP
+Before version 6.3,
+\fI\%ncurses\fP stores both \fIdynamic\fP and \fIstatic\fP
variables in persistent storage, initialized to zeros.
.bP
-Beginning with version 6.3, ncurses stores \fIstatic\fP and \fIdynamic\fP
+Beginning with version 6.3,
+\fI\%ncurses\fP stores \fIstatic\fP and \fIdynamic\fP
variables in the same manner as SVr4.
.RS
.bP
-Unlike other implementations, ncurses zeros dynamic variables
+Unlike other implementations, \fI\%ncurses\fP zeros dynamic variables
before the first \fB%g\fP or \fB%P\fP operator.
.bP
Like SVr2,
-the scope of dynamic variables in ncurses
+the scope of dynamic variables in \fI\%ncurses\fP
is within the current call to
\fBtparm\fP.
Use static variables if persistent storage is needed.
@@ -861,7 +867,7 @@ and
.B rc
(save and restore cursor) commands may be useful for ensuring that
your synthesized insert/delete string does not move the cursor.
-(Note that the \fBncurses\fP(3X) library does this synthesis
+(Note that the \fB\%ncurses\fP(3X) library does this synthesis
automatically, so you need not compose insert/delete strings for
an entry with \fBcsr\fP).
.PP
@@ -1533,7 +1539,8 @@ A command to erase or blank the status line may be
specified as \fBdsl\fP.
The boolean capability \fBeslok\fP specifies that escape sequences, tabs,
etc., work ordinarily in the status line.
.PP
-The \fBncurses\fP implementation does not yet use any of these capabilities.
+The \fI\%ncurses\fP implementation does not yet use any of these
+capabilities.
They are documented here in case they ever become important.
.SS Line Graphics
Many terminals have alternate character sets useful for forms-drawing.
@@ -1668,7 +1675,7 @@ The \fBsetaf\fP/\fBsetab\fP and \fBsetf\fP/\fBsetb\fP
capabilities take a
single numeric argument each.
Argument values 0-7 of \fBsetaf\fP/\fBsetab\fP are portably defined as
follows (the middle column is the symbolic #define available in the header for
-the \fBcurses\fP or \fBncurses\fP libraries).
+the \fBcurses\fP or \fI\%ncurses\fP libraries).
The terminal hardware is free to
map these as it likes, but the RGB values indicate normal locations in color
space.
@@ -1773,16 +1780,19 @@ foreground color blue and is not available in color
mode.
These should have
an \fBncv\fP capability of 2.
.PP
-SVr4 curses does nothing with \fBncv\fP, ncurses recognizes it and optimizes
+SVr4 curses does nothing with \fBncv\fP,
+\fI\%ncurses\fP recognizes it and optimizes
the output in favor of colors.
.SS Miscellaneous
If the terminal requires other than a null (zero) character as a pad, then this
can be given as pad.
Only the first character of the pad string is used.
If the terminal does not have a pad character, specify npc.
-Note that ncurses implements the termcap-compatible \fBPC\fP variable;
+Note that \fI\%ncurses\fP implements the termcap-compatible \fBPC\fP
+variable;
though the application may set this value to something other than
-a null, ncurses will test \fBnpc\fP first and use napms if the terminal
+a null,
+\fI\%ncurses\fP will test \fBnpc\fP first and use napms if the terminal
has no pad character.
.PP
If the terminal can move up or down half a line,
@@ -1905,7 +1915,7 @@ This glitch is also taken to mean that it is not possible
to position
the cursor on top of a \*(``magic cookie\*('',
that to erase standout mode it is instead necessary to use
delete and insert line.
-The ncurses implementation ignores this glitch.
+The \fI\%ncurses\fP implementation ignores this glitch.
.PP
The Beehive Superbee, which is unable to correctly transmit the escape
or control/C characters, has
@@ -1999,7 +2009,8 @@ If it is too long even before
terminal types and users whose \fITERM\fP variable does not have a termcap
entry.
.PP
-When in \-C (translate to termcap) mode, the \fBncurses\fP implementation of
+When in \-C (translate to termcap) mode,
+the \fI\%ncurses\fP implementation of
\fB@TIC@\fP(1M) issues warning messages when the pre-tc length of a termcap
translation is too long.
The \-c (check) option also checks resolved (after tc
@@ -2024,14 +2035,15 @@ interpret the %A and %O operators in parameter strings.
SVr4/XPG4 do not specify whether \fBmsgr\fP licenses movement while in
an alternate-character-set mode (such modes may, among other things, map
CR and NL to characters that do not trigger local motions).
-The \fBncurses\fP implementation ignores \fBmsgr\fP in \fBALTCHARSET\fP
-mode.
+The \fI\%ncurses\fP implementation ignores \fBmsgr\fP in
+\fBALTCHARSET\fP mode.
This raises the possibility that an XPG4
implementation making the opposite interpretation may need terminfo
-entries made for \fBncurses\fP to have \fBmsgr\fP turned off.
+entries made for \fI\%ncurses\fP to have \fBmsgr\fP turned off.
.PP
-The \fBncurses\fP library handles insert-character and insert-character modes
-in a slightly non-standard way to get better update efficiency.
+The \fI\%ncurses\fP library handles insert-character and
+insert-character modes in a slightly non-standard way to get better
+update efficiency.
See
the \fBInsert/Delete Character\fP subsection above.
.PP
@@ -2041,7 +2053,7 @@ They are deduced from the
documentation for the AT&T 505 terminal.
.PP
Be careful assigning the \fBkmous\fP capability.
-The \fBncurses\fP library wants to interpret it as \fBKEY_MOUSE\fP,
+The \fI\%ncurses\fP library wants to interpret it as \fBKEY_MOUSE\fP,
for use by terminals and emulators like xterm
that can return mouse-tracking information in the keyboard-input stream.
.PP
diff --git a/man/tic.1m b/man/tic.1m
index bf4fa1ee9..52fb58fb0 100644
--- a/man/tic.1m
+++ b/man/tic.1m
@@ -242,7 +242,7 @@ .SH OPTIONS
Force source translation to terminfo format.
.TP
\fB\-K\fP
-Suppress some longstanding ncurses extensions to termcap format,
+Suppress some longstanding \fI\%ncurses\fP extensions to termcap format,
e.g., "\es" for space.
.TP
\fB\-L\fP
@@ -331,7 +331,8 @@ .SH OPTIONS
or in termcaps.
.TP
\fB\-V\fP
-reports the version of ncurses which was used in this program, and exits.
+reports the version of \fI\%ncurses\fP which was used in this program,
+and exits.
.TP
\fB\-v\fIn\fR
specifies that (verbose) output be written to standard error trace
@@ -341,7 +342,8 @@ .SH OPTIONS
indicating the desired level of detail of information.
.RS
.bP
-If ncurses is built without tracing support, the optional parameter is ignored.
+If \fI\%ncurses\fP is built without tracing support,
+the optional parameter is ignored.
.bP
If \fIn\fP is omitted, the default level is 1.
.bP
@@ -500,7 +502,7 @@ .SH EXTENSIONS
\fB\-x\fP
.RE
.bP
-The NetBSD \fBtic\fP supports a few of the ncurses options
+The NetBSD \fBtic\fP supports a few of the \fI\%ncurses\fP options
.sp
.RS
\fB\-a\fP
@@ -527,7 +529,7 @@ .SH PORTABILITY
Shortly after Issue 7 was released, Tru64 was discontinued.
As of 2019, the surviving implementations of \fBtic\fP
are SVr4 (AIX, HP-UX and Solaris),
-ncurses
+\fI\%ncurses\fP
and NetBSD curses.
The SVr4 \fBtic\fP programs all support the \fB\-v\fP option.
The NetBSD \fBtic\fP program follows X/Open's documentation,
@@ -559,7 +561,7 @@ .SH HISTORY
continued with System V Release 4,
the table of capabilities grew from 180 (\fIpcurses\fP) to 464 (Solaris).
.PP
-In early development of ncurses (1993),
+In early development of \fI\%ncurses\fP (1993),
Zeyd Ben-Halim used the table from \fImytinfo\fP to
extend the \fIpcurses\fP table to 469 capabilities
(456 matched SVr4, 8 were only in SVr4, 13 were not in SVr4).
@@ -569,7 +571,7 @@ .SH HISTORY
\fB\%memory_lock_above\fP and
\fB\%memory_unlock\fP (see \fB\%user_caps\fP(5)).
.PP
-Eric Raymond incorporated parts of \fImytinfo\fP into ncurses
+Eric Raymond incorporated parts of \fImytinfo\fP into \fI\%ncurses\fP
to implement the termcap-to-terminfo source conversion,
and extended that to begin development of
the corresponding terminfo-to-termcap source conversion,
@@ -580,7 +582,7 @@ .SH HISTORY
.PP
In 2010, Roy Marples provided a \fBtic\fP program
and terminfo library for NetBSD.
-That implementation adapts several features from ncurses,
+That implementation adapts several features from \fI\%ncurses\fP,
including \fB@TIC@\fP's \fB\-x\fP option.
.PP
The \fB\-c\fP option tells \fB@TIC@\fP to check for problems in the
@@ -589,18 +591,20 @@ .SH HISTORY
.bP
\fIpcurses\fP had 8 warnings
.bP
-ncurses in 1996 had 16 warnings
+\fI\%ncurses\fP in 1996 had 16 warnings
.bP
Solaris (SVr4) curses has 28 warnings
.bP
NetBSD tic in 2019 has 19 warnings.
.bP
-ncurses in 2019 has 96 warnings
+\fI\%ncurses\fP in 2019 has 96 warnings
.PP
-The checking done in ncurses' \fB@TIC@\fP helps with the conversion to
-termcap, as well as pointing out errors and inconsistencies.
+The checking done in \fI\%ncurses\fP' \fB@TIC@\fP helps with the
+conversion to termcap,
+as well as pointing out errors and inconsistencies.
It is also used to ensure consistency with the user-defined capabilities.
-There are 527 distinct capabilities in ncurses' terminal database;
+There are 527 distinct capabilities in \fI\%ncurses\fP' terminal
+database;
128 of those are user-defined.
.SH AUTHORS
Eric S. Raymond <esr@snark.thyrsus.com>
diff --git a/man/toe.1m b/man/toe.1m
index 0a462b9dd..db6913fe4 100644
--- a/man/toe.1m
+++ b/man/toe.1m
@@ -132,11 +132,11 @@ .SH OPTIONS
.IP
The optional parameter \fIn\fP is an integer between 1 and 10 inclusive,
interpreted as for \fB\%@TIC@\fP(1M).
-If \fIncurses\fP is built without tracing support,
+If \fI\%ncurses\fP is built without tracing support,
\fIn\fP is ignored.
.TP
\fB\-V\fP
-reports the version of \fIncurses\fP associated
+reports the version of \fI\%ncurses\fP associated
with this program and exits with a successful status.
.SH FILES
.TP
@@ -147,7 +147,7 @@ .SH HISTORY
There is no applicable X/Open or POSIX standard for it.
.PP
It replaces a \fB\-T\fP option that was briefly supported by
-the \fIncurses\fP \fB\%infocmp\fP utility in 1995.
+the \fI\%ncurses\fP \fB\%infocmp\fP utility in 1995.
.PP
The \fB\-a\fP and \fB\-s\fP options were added in 2006 and 2011,
respectively.
diff --git a/man/tput.1 b/man/tput.1
index a4da5d049..7e231cf57 100644
--- a/man/tput.1
+++ b/man/tput.1
@@ -119,7 +119,8 @@ .SS Options
variables \fILINES\fP and \fI\%COLUMNS\fP will also be ignored.
.TP
\fB\-V\fP
-reports the version of ncurses which was used in this program, and exits.
+reports the version of \fI\%ncurses\fP which was used in this program,
+and exits.
.TP
.B \-x
prevents \fB\%@TPUT@\fP from attempting to clear the scrollback buffer.
@@ -248,7 +249,8 @@ .SS Aliases
same effect as \fB@TPUT@ reset\fP.
The \fB@TSET@\fP(1) utility also treats a link named \fBreset\fP specially.
.PP
-Before ncurses 6.1, the two utilities were different from each other:
+Before \fI\%ncurses\fP 6.1,
+the two utilities were different from each other:
.bP
\fB@TSET@\fP utility reset the terminal modes and special characters
(not done with \fB@TPUT@\fP).
@@ -261,8 +263,8 @@ .SS Aliases
The \fBreset\fP program is usually an alias for \fB@TSET@\fP,
because of this difference with resetting terminal modes and special
characters.
.PP
-With the changes made for ncurses 6.1, the \fIreset\fP feature of the
-two programs is (mostly) the same.
+With the changes made for \fI\%ncurses\fP 6.1,
+the \fIreset\fP feature of the two programs is (mostly) the same.
A few differences remain:
.bP
The \fB@TSET@\fP program waits one second when resetting,
@@ -383,7 +385,7 @@ .SH PORTABILITY
a 1200Bd terminal.
When updating terminal modes, it ignores errors.
.IP
-Until changes made after ncurses 6.0,
+Until changes made after \fI\%ncurses\fP 6.0,
\fB@TPUT@\fP did not modify terminal modes.
\fB@TPUT@\fP now uses a similar scheme,
using functions shared with \fB@TSET@\fP
@@ -405,11 +407,11 @@ .SH PORTABILITY
.IP
Besides providing more reliable operation than AT&T's utility,
a portability problem is introduced by this analysis:
-An OpenBSD developer adapted the internal library function from ncurses
-to port NetBSD's termcap-based \fBtput\fP to terminfo.
+An OpenBSD developer adapted the internal library function from
+\fI\%ncurses\fP to port NetBSD's termcap-based \fBtput\fP to terminfo.
That had been modified to interpret multiple commands on a line.
Portable applications should not rely upon this feature;
-ncurses provides it to support applications written
+\fI\%ncurses\fP provides it to support applications written
specifically for OpenBSD.
.PP
This implementation (unlike others) can accept both \fItermcap\fP
@@ -454,7 +456,7 @@ .SH PORTABILITY
Since 2010, NetBSD's \fBtput\fP uses terminfo names.
Before that, it (like FreeBSD) recognized termcap names.
.IP
-Beginning in 2021, FreeBSD uses the ncurses \fBtput\fP,
+Beginning in 2021, FreeBSD uses the \fI\%ncurses\fP \fBtput\fP,
configured for both terminfo (tested first) and termcap (as a fallback).
.PP
Because (apparently) \fIall\fP of the certified Unix systems
@@ -490,10 +492,10 @@ .SH PORTABILITY
or cancelled numeric value versus an (unsigned) exit code.
.PP
The various Unix systems (AIX, HP-UX, Solaris) use the same exit-codes
-as ncurses.
+as \fI\%ncurses\fP.
.PP
NetBSD curses documents different exit codes which do not correspond
-to either ncurses or X/Open.
+to either \fI\%ncurses\fP or X/Open.
.SH HISTORY
The \fBtput\fP command was begun by Bill Joy in 1980.
The initial version only cleared the screen.
@@ -537,7 +539,7 @@ .SH HISTORY
Ridge's program made more sophisticated use of the terminal capabilities
than the BSD program.
Eric Raymond used that \fBtput\fP program
-(and other parts of \fImytinfo\fP) in ncurses in June 1995.
+(and other parts of \fImytinfo\fP) in \fI\%ncurses\fP in June 1995.
Using the portions dealing with terminal capabilities
almost without change,
Raymond made improvements to the way the command-line parameters
diff --git a/man/tset.1 b/man/tset.1
index ec9610932..703b8c6ae 100644
--- a/man/tset.1
+++ b/man/tset.1
@@ -277,7 +277,8 @@ .SH OPTIONS
see subsection \*(``Setting the Environment\*(''.
.TP
.B \-V
-reports the version of ncurses which was used in this program, and exits.
+reports the version of \fI\%ncurses\fP which was used in this program,
+and exits.
.TP
.B \-w
Resize the window to match the size deduced via \fBsetupterm\fP(3X).
@@ -337,7 +338,7 @@ .SH PORTABILITY
.PP
A few options are different
because the \fI\%TERMCAP\fP variable
-is no longer supported under terminfo-based \fBncurses\fP:
+is no longer supported under terminfo-based \fI\%ncurses\fP:
.bP
The \fB\-S\fP option of BSD \fBtset\fP no longer works;
it prints an error message to the standard error and dies.
@@ -387,7 +388,7 @@ .SH PORTABILITY
to set the window size if \fBtset\fP is not able to obtain the window
size from the operating system.
.bP
-In ncurses, \fB@TSET@\fP obtains the window size using
+In \fI\%ncurses\fP, \fB@TSET@\fP obtains the window size using
\fBsetupterm\fP, which may be from
the operating system,
the \fILINES\fP and \fICOLUMNS\fP environment variables or
diff --git a/man/user_caps.5 b/man/user_caps.5
index 9f73606ed..d218b8a7b 100644
--- a/man/user_caps.5
+++ b/man/user_caps.5
@@ -54,7 +54,7 @@ .SH SYNOPSIS
.B @TIC@ \-x
.SH DESCRIPTION
.SS Background
-Before ncurses 5.0,
+Before \fI\%ncurses\fP 5.0,
terminfo databases used a \fIfixed repertoire\fP of terminal
capabilities designed for the SVr2 terminal database in 1984,
and extended in stages through SVr4 (1989),
@@ -88,22 +88,24 @@ .SS Background
the position in the tables differs because some features were added as needed,
while others were added (out of order) to comply with X/Open Curses.
.IP
-While ncurses' repertoire of predefined capabilities is closest to Solaris,
+While \fI\%ncurses\fP' repertoire of predefined capabilities is closest
+to Solaris,
Solaris's terminfo database has a few differences from
the list published by X/Open Curses.
-For example, ncurses can be configured with tables which match the
-terminal databases for AIX, HP-UX or OSF/1,
+For example,
+\fI\%ncurses\fP can be configured with tables which match the terminal
+databases for AIX, HP-UX or OSF/1,
rather than the default Solaris-like configuration.
.bP
-In SVr4 curses and ncurses,
+In SVr4 curses and \fI\%ncurses\fP,
the terminal database is defined at compile-time using a text file
which lists the different terminal capabilities.
.IP
In principle, the text-file can be extended,
but doing this requires recompiling and reinstalling the library.
-The text-file used in ncurses for terminal capabilities includes
+The text-file used in \fI\%ncurses\fP for terminal capabilities includes
details for various systems past the documented X/Open Curses features.
-For example, ncurses supports these capabilities in each configuration:
+For example, \fI\%ncurses\fP supports these capabilities in each configuration:
.RS 8
.TP 5
memory_lock
@@ -138,16 +140,16 @@ .SS Background
Although termcap's extensibility was rarely used
(it was never the \fIspeaker\fP who had actually used the feature),
the criticism had a point.
-ncurses 5.0 provided a way to detect nonstandard capabilities,
+\fI\%ncurses\fP 5.0 provided a way to detect nonstandard capabilities,
determine their
type and optionally store and retrieve them in a way which did not interfere
with other applications.
These are referred to as \fIuser-defined capabilities\fP because no
modifications to the toolset's predefined capability names are needed.
.PP
-The ncurses utilities \fB@TIC@\fP and \fB@INFOCMP@\fP have a command-line
-option \*(``\-x\*('' to control whether the nonstandard capabilities
-are stored or retrieved.
+The \fI\%ncurses\fP utilities \fB@TIC@\fP and \fB@INFOCMP@\fP have a
+command-line option \*(``\-x\*('' to control whether the nonstandard
+capabilities are stored or retrieved.
A library function \fBuse_extended_names\fP
is provided for the same purpose.
.PP
@@ -155,7 +157,7 @@ .SS Background
\fB@TIC@\fP will store a user-defined capability if the capability name is not
one of the predefined names.
.PP
-Because ncurses provides a termcap library interface,
+Because \fI\%ncurses\fP provides a termcap library interface,
these user-defined capabilities may be visible to termcap applications:
.bP
The termcap interface (like all implementations of termcap)
@@ -177,16 +179,16 @@ .SS Background
to which a series of keys can be assigned,
that is insufficient for more than a dozen keys multiplied by more than
a couple of modifier combinations.
-The ncurses database uses a convention based on \fBxterm\fP(1) to
-provide extended special-key names.
+The \fI\%ncurses\fP database uses a convention based on \fBxterm\fP(1)
+to provide extended special-key names.
.IP
Fitting that into termcap's limitation of 2-character names
would be pointless.
These extended keys are available only with terminfo.
.SS Recognized capabilities
-The ncurses library uses the user-definable capabilities.
+The \fI\%ncurses\fP library uses the user-definable capabilities.
While the terminfo database may have other extensions,
-ncurses makes explicit checks for these:
+\fI\%ncurses\fP makes explicit checks for these:
.RS 3
.TP 3
AX
@@ -204,7 +206,8 @@ .SS Recognized capabilities
.TP 3
NQ
\fIboolean\fP,
-used to suppress a consistency check in @TIC@ for the ncurses capabilities
+used to suppress a consistency check in @TIC@ for the \fI\%ncurses\fP
+capabilities
in user6 through user9 (u6, u7, u8 and u9)
which tell how to query the terminal's cursor position
and its device attributes.
@@ -219,21 +222,23 @@ .SS Recognized capabilities
return appropriate values without requiring the application
to initialize colors using \fBinit_color\fP.
.IP
-The capability type determines the values which ncurses sees:
+The capability type determines the values which \fI\%ncurses\fP sees:
.RS 3
.TP 3
\fIboolean\fP
implies that the number of bits for red, green and blue are the same.
Using the maximum number of colors,
-ncurses adds two, divides that sum by three, and assigns the result
-to red, green and blue in that order.
+\fI\%ncurses\fP adds two,
+divides that sum by three,
+and assigns the result to red,
+green and blue in that order.
.IP
If the number of bits needed for the number of colors is not a multiple
of three, the blue (and green) components lose in comparison to red.
.TP 3
\fInumber\fP
-tells ncurses what result to add to red, green and blue.
-If ncurses runs out of bits,
+tells \fI\%ncurses\fP what result to add to red, green and blue.
+If \fI\%ncurses\fP runs out of bits,
blue (and green) lose just as in the \fIboolean\fP case.
.TP 3
\fIstring\fP
@@ -249,7 +254,8 @@ .SS Recognized capabilities
.TP 3
U8
\fInumber\fP,
-asserts that ncurses must use Unicode values for line-drawing characters,
+asserts that \fI\%ncurses\fP must use Unicode values for line-drawing
+characters,
and that it should ignore the alternate character set capabilities
when the locale uses UTF-8 encoding.
For more information, see the discussion of
@@ -259,17 +265,18 @@ .SS Recognized capabilities
.TP 3
XM
\fIstring\fP,
-override ncurses's built-in string which
+override \fI\%ncurses\fP's built-in string which
enables/disables \fBxterm\fP(1) mouse mode.
.IP
-ncurses sends a character sequence to the terminal to initialize mouse mode,
+\fI\%ncurses\fP sends a character sequence to the terminal to initialize mouse
mode,
and when the user clicks the mouse buttons or (in certain modes) moves the
mouse, handles the characters sent back by the terminal to tell it what
was done with the mouse.
.IP
The mouse protocol is enabled when
the \fImask\fP passed in the \fBmousemask\fP function is nonzero.
-By default, ncurses handles the responses for the X11 xterm mouse protocol.
+By default,
+\fI\%ncurses\fP handles the responses for the X11 xterm mouse protocol.
It also knows about the \fISGR 1006\fP xterm mouse protocol,
but must to be told to look for this specifically.
It will not be able to guess which mode is used,
@@ -278,7 +285,7 @@ .SS Recognized capabilities
The \fBXM\fP capability has a single parameter.
If nonzero, the mouse protocol should be enabled.
If zero, the mouse protocol should be disabled.
-ncurses inspects this capability if it is present,
+\fI\%ncurses\fP inspects this capability if it is present,
to see whether the 1006 protocol is used.
If so, it expects the responses to use the \fISGR 1006\fP xterm mouse protocol.
.IP
@@ -348,14 +355,15 @@ .SS Extended key-definitions
Since 1999, \fBxterm\fP(1) has supported
\fIshift\fP, \fIcontrol\fP, \fIalt\fP, and \fImeta\fP modifiers which produce
distinct special-key strings.
-In a terminal description, ncurses has no special knowledge of the
-modifiers used.
+In a terminal description,
+\fI\%ncurses\fP has no special knowledge of the modifiers used.
Applications can use the \fInaming convention\fP established for \fBxterm\fP
to find these special keys in the terminal description.
.PP
Starting with the curses convention that \fIkey names\fP begin with \*(``k\*(''
and that shifted special keys are an uppercase name,
-ncurses' terminal database defines these names to which a suffix is added:
+\fI\%ncurses\fP' terminal database defines these names to which a suffix
+is added:
.PP
.RS 5
.TS
@@ -402,8 +410,9 @@ .SS Extended key-definitions
.RE
.PP
None of these are predefined; terminal descriptions can refer to \fInames\fP
-which ncurses will allocate at runtime to \fIkey-codes\fP.
-To use these keys in an ncurses program, an application could do this:
+which \fI\%ncurses\fP will allocate at runtime to \fIkey-codes\fP.
+To use these keys in an \fI\%ncurses\fP program,
+an application could do this:
.bP
using a list of extended key \fInames\fP,
ask \fBtigetstr\fP(3X) for their values, and
@@ -421,7 +430,7 @@ .SH PORTABILITY
.SH AUTHORS
Thomas E. Dickey
.br
-beginning with ncurses 5.0 (1999)
+beginning with \fI\%ncurses\fP 5.0 (1999)
.\"
.SH SEE ALSO
\fB\%@INFOCMP@\fP(1M),
--
2.30.2
signature.asc
Description: PGP signature
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- [PATCH 03/42] Style "ncurses" consistently.,
G. Branden Robinson <=