From: Thomas E. Dickey Date: Sun, 20 Jun 2021 00:21:42 +0000 (+0000) Subject: ncurses 6.2 - patch 20210619 X-Git-Tag: v6.3~21 X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=commitdiff_plain;h=9f479192e3ca3413d235c66bf058f8cc63764898 ncurses 6.2 - patch 20210619 + improve configure-macro used for dependencies of --disable-leaks such as --with-valgrind + trim trailing blanks from files --- diff --git a/AUTHORS b/AUTHORS index 0018842c..09dfc9a9 100644 --- a/AUTHORS +++ b/AUTHORS @@ -1,5 +1,5 @@ ------------------------------------------------------------------------------- --- Copyright 2020 Thomas E. Dickey -- +-- Copyright 2020,2021 Thomas E. Dickey -- -- Copyright 2006,2017 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -26,13 +26,13 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- --- $Id: AUTHORS,v 1.4 2020/02/02 23:34:34 tom Exp $ +-- $Id: AUTHORS,v 1.5 2021/06/17 21:20:30 tom Exp $ ------------------------------------------------------------------------------- These are the principal authors/contributors of ncurses since 1.9.9e, in decreasing order of their contribution: TD Thomas E. Dickey -JPF Juergen Pfeifer +JPF Juergen Pfeifer ESR Eric S Raymond AVL Alexander V Lukyanov PB Philippe Blain diff --git a/Ada95/README b/Ada95/README index d014f327..2e66625f 100644 --- a/Ada95/README +++ b/Ada95/README @@ -1,5 +1,5 @@ ------------------------------------------------------------------------------- --- Copyright 2020 Thomas E. Dickey -- +-- Copyright 2020,2021 Thomas E. Dickey -- -- Copyright 1998-2002,2003 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -29,6 +29,6 @@ -- Author: Juergen Pfeifer, 1996 -The documentation is provided in HTML format in the ./html +The documentation is provided in HTML format in the ./html subdirectory. The main document is named index.html diff --git a/Ada95/TODO b/Ada95/TODO index 122275f9..15323458 100644 --- a/Ada95/TODO +++ b/Ada95/TODO @@ -1,5 +1,5 @@ ------------------------------------------------------------------------------- --- Copyright 2020 Thomas E. Dickey -- +-- Copyright 2020,2021 Thomas E. Dickey -- -- Copyright 1998-1999,2006 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -26,7 +26,7 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- --- $Id: TODO,v 1.6 2020/02/02 23:34:34 tom Exp $ +-- $Id: TODO,v 1.7 2021/06/17 21:20:30 tom Exp $ ------------------------------------------------------------------------------- -- Intensive testing @@ -36,7 +36,7 @@ Like most WEB pages: under continuous construction -- Style cleanup - + -- Alternate functions for procedures with out params Comfort purpose diff --git a/Ada95/aclocal.m4 b/Ada95/aclocal.m4 index bf7cca0f..e2bc2cd7 100644 --- a/Ada95/aclocal.m4 +++ b/Ada95/aclocal.m4 @@ -29,7 +29,7 @@ dnl*************************************************************************** dnl dnl Author: Thomas E. Dickey dnl -dnl $Id: aclocal.m4,v 1.175 2021/05/19 23:35:25 tom Exp $ +dnl $Id: aclocal.m4,v 1.176 2021/06/19 23:44:07 tom Exp $ dnl Macros used in NCURSES Ada95 auto-configuration script. dnl dnl These macros are maintained separately from NCURSES. The copyright on @@ -827,7 +827,7 @@ if test "x$ifelse([$2],,CLANG_COMPILER,[$2])" = "xyes" ; then fi ]) dnl --------------------------------------------------------------------------- -dnl CF_CONST_X_STRING version: 6 updated: 2021/01/01 13:31:04 +dnl CF_CONST_X_STRING version: 7 updated: 2021/06/07 17:39:17 dnl ----------------- dnl The X11R4-X11R6 Xt specification uses an ambiguous String type for most dnl character-strings. @@ -857,7 +857,7 @@ AC_TRY_COMPILE( #include #include ], -[String foo = malloc(1); (void)foo],[ +[String foo = malloc(1); free((void*)foo)],[ AC_CACHE_CHECK(for X11/Xt const-feature,cf_cv_const_x_string,[ AC_TRY_COMPILE( @@ -887,7 +887,7 @@ esac ]) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_CONST_X_STRING version: 6 updated: 2021/01/01 13:31:04 +dnl CF_CONST_X_STRING version: 7 updated: 2021/06/07 17:39:17 dnl ----------------- dnl The X11R4-X11R6 Xt specification uses an ambiguous String type for most dnl character-strings. @@ -917,7 +917,7 @@ AC_TRY_COMPILE( #include #include ], -[String foo = malloc(1); (void)foo],[ +[String foo = malloc(1); free((void*)foo)],[ AC_CACHE_CHECK(for X11/Xt const-feature,cf_cv_const_x_string,[ AC_TRY_COMPILE( diff --git a/Ada95/configure b/Ada95/configure index 39766b3f..ac4da280 100755 --- a/Ada95/configure +++ b/Ada95/configure @@ -15081,7 +15081,7 @@ cat >"conftest.$ac_ext" <<_ACEOF int main (void) { -String foo = malloc(1); (void)foo +String foo = malloc(1); free((void*)foo) ; return 0; } diff --git a/Ada95/include/ncurses_defs b/Ada95/include/ncurses_defs index 7a7059bf..50da8e5c 100644 --- a/Ada95/include/ncurses_defs +++ b/Ada95/include/ncurses_defs @@ -1,6 +1,6 @@ -# $Id: ncurses_defs,v 1.45 2020/02/02 23:34:34 tom Exp $ +# $Id: ncurses_defs,v 1.46 2021/06/17 21:20:30 tom Exp $ ############################################################################## -# Copyright 2020 Thomas E. Dickey # +# Copyright 2020,2021 Thomas E. Dickey # # Copyright 2008-2012,2013 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -44,7 +44,7 @@ GCC_UNUSED /* nothing */ HAVE_BIG_CORE HAVE_BSD_CGETENT HAVE_BSD_SIGNAL_H -HAVE_BTOWC +HAVE_BTOWC HAVE_BUILTIN_H HAVE_CHGAT 1 HAVE_COLOR_SET 1 @@ -101,7 +101,7 @@ HAVE_PANEL_H HAVE_POLL HAVE_POLL_H HAVE_PURIFY -HAVE_PUTWC +HAVE_PUTWC HAVE_PUTWIN 1 HAVE_REGEXPR_H_FUNCS HAVE_REGEXP_H_FUNCS @@ -156,7 +156,7 @@ HAVE_VSNPRINTF HAVE_VSSCANF HAVE_WCSRTOMBS HAVE_WCSTOMBS -HAVE_WCTOB +HAVE_WCTOB HAVE_WCTOMB HAVE_WCTYPE_H HAVE_WINSSTR 1 diff --git a/Ada95/make-tar.sh b/Ada95/make-tar.sh index e88b3128..5a99fb9d 100755 --- a/Ada95/make-tar.sh +++ b/Ada95/make-tar.sh @@ -1,7 +1,7 @@ #!/bin/sh -# $Id: make-tar.sh,v 1.18 2020/02/02 23:34:34 tom Exp $ +# $Id: make-tar.sh,v 1.19 2021/06/17 21:26:02 tom Exp $ ############################################################################## -# Copyright 2019,2020 Thomas E. Dickey # +# Copyright 2019-2020,2021 Thomas E. Dickey # # Copyright 2010-2015,2017 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -128,10 +128,10 @@ cp -p $SOURCE/NEWS $BUILD/$ROOTNAME # cleanup empty directories (an artifact of ncurses source archives) -touch $BUILD/$ROOTNAME/MANIFEST +touch $BUILD/$ROOTNAME/MANIFEST ( cd $BUILD/$ROOTNAME && find . -type f -print |$SOURCE/misc/csort >MANIFEST ) -cd $BUILD || exit +cd $BUILD || exit # Remove build-artifacts. find . -name RCS -exec rm -rf {} \; diff --git a/Ada95/package/debian/rules b/Ada95/package/debian/rules index 708d3eb2..47bbdc04 100755 --- a/Ada95/package/debian/rules +++ b/Ada95/package/debian/rules @@ -71,7 +71,7 @@ install-stamp: build-stamp dh_installdirs $(MAKE) install DESTDIR=$(TARGET_DIR) - + # FIXME: it would be nice to make these into separate packages ( cd samples && $(MAKE) install.examples DESTDIR=$(TARGET_DIR) BINDIR=$(SAMPLE_DIR) ) ( cd doc && $(MAKE) install.html DESTDIR=$(TARGET_DIR) ) diff --git a/Ada95/samples/Makefile.in b/Ada95/samples/Makefile.in index 3a0c272f..495f7083 100644 --- a/Ada95/samples/Makefile.in +++ b/Ada95/samples/Makefile.in @@ -29,7 +29,7 @@ # # Author: Juergen Pfeifer, 1996 # -# $Id: Makefile.in,v 1.62 2021/01/23 20:42:08 tom Exp $ +# $Id: Makefile.in,v 1.63 2021/06/17 21:11:08 tom Exp $ # .SUFFIXES: @@ -107,7 +107,7 @@ THISLIB = sample CARGS = -cargs $(ADAFLAGS) LARGS = -largs -L../lib -l@ADA_LIBNAME@ @TEST_ARG2@ $(LD_FLAGS) @TEST_LIBS2@ -PROGS = tour$x ncurses$x @USE_GNAT_SIGINT@ rain$x +PROGS = tour$x ncurses$x @USE_GNAT_SIGINT@ rain$x all :: $(PROGS) @echo made $@ diff --git a/Ada95/samples/explain.txt b/Ada95/samples/explain.txt index be2cba15..d36d4ea7 100644 --- a/Ada95/samples/explain.txt +++ b/Ada95/samples/explain.txt @@ -27,15 +27,15 @@ In a menu you can use the following Keys in the whole application: - Cursor Right Right one item - END Key Go to last item #FORMKEYS - - CTRL-X eXit the form + - CTRL-X eXit the form - CTRL-F Go forward to the next field - CTRL-B Go backward to the previous field - - CTRL-L Go to the field left of the current one + - CTRL-L Go to the field left of the current one - CTRL-R Go to the field right of the current one - - CTRL-U Go to the field above the current one - - CTRL-D Go to the field below the current one + - CTRL-U Go to the field above the current one + - CTRL-D Go to the field below the current one - - CTRL-W Go to the next word in the field + - CTRL-W Go to the next word in the field - CTRL-T Go to the previous word in the field - CTRL-A Go to the beginning of the field @@ -43,13 +43,13 @@ In a menu you can use the following Keys in the whole application: - CTRL-I Insert a blank character at the current position - CTRL-O Insert a line - - CTRL-V Delete a character - - CTRL-H Delete previous character - - CTRL-Y Delete a line - - CTRL-G Delete a word - - CTRL-K Clear to end of field + - CTRL-V Delete a character + - CTRL-H Delete previous character + - CTRL-Y Delete a line + - CTRL-G Delete a word + - CTRL-K Clear to end of field - - CTRL-N Next choice in a choice field (Enumerations etc.) + - CTRL-N Next choice in a choice field (Enumerations etc.) - CTRL-P Previous choice in a choice field. #HELP #HELPKEYS @@ -62,7 +62,7 @@ You may leave the help with the Function Key labeled 'Quit'. This is the main menu of the sample program for the ncurses Ada95 binding. The main intention of the demo is not to demonstrate or test all the features of ncurses and it's subsystems, but to provide -to you some sample code how to use the binding with Ada95. +to you some sample code how to use the binding with Ada95. You may select this options: @@ -71,7 +71,7 @@ You may select this options: * Look at some features of the form subsystem * Look at the output of the Ada.Text_IO like functions for ncurses. - + #MAINPAD You may press at any place in this demo CTRL-C. This will give you a command window. You can just type in the Label-String of a function key, then this @@ -86,13 +86,13 @@ descriptions for the items, a marker and a padding character between the item name and the description. #MENU01 This is a demo of the some of the menu layout options. One of them -is the spacing functionality. Just press the Key labeled "Flip" to +is the spacing functionality. Just press the Key labeled "Flip" to flip between the non-spaced and a spaced version of the menu. Please -note that this functionality is unique for ncurses and is not found -in the SVr4 menu implementation. +note that this functionality is unique for ncurses and is not found +in the SVr4 menu implementation. -This is a menu that sometimes does not fit into it's window and -therefore it becomes a scroll menu. +This is a menu that sometimes does not fit into it's window and +therefore it becomes a scroll menu. You can also see here very nicely the pattern matching functionality of menus. Type for example a 'J' and you will be positioned to the @@ -106,7 +106,7 @@ labeled "4x1", "4x2" or "4x3" to get a menu with that many rows and columns. With the Keys "O-Row" or "O-Col" (they occupy the same label and -switch on selection) you can change the major order scheme for +switch on selection) you can change the major order scheme for the menu. If "O-Col" is visible, the menu is currently major ordered by rows, you can switch to major column order by pressing the key. If "O-Row" is visible, it's just the reverse situation. @@ -136,7 +136,7 @@ For more details press the Key labeled "Help". This is a demo of the forms package. #FORM-PAD00 Please note that this demo is far from being complete. It really shows -only a small part of the functionality of the forms package. Let's hope +only a small part of the functionality of the forms package. Let's hope the next version will have a richer demo (You want to contribute ?). #NOTIMPL Sorry this functionality of the demo is not implemented at the moment. @@ -148,7 +148,7 @@ This is a menu where you can select some different demos of the ncurses functionality. #CURSES-PAD00 Please note that this demo is far from being complete. It really shows -only a small part of the functionality of the curses package. Let's hope +only a small part of the functionality of the curses package. Let's hope the next version will have a richer demo (You want to contribute ?). #MOUSEKEYS In this demo you may use this keys: @@ -161,11 +161,11 @@ You may click the mouse buttons at any location at the screen and look at the protocol window ! #MOUSE00 A rather simple use of a mouse as demo. It's there just to test the -code and to provide the sample source. +code and to provide the sample source. It might be of interest, that the output into the protocol window is done by the (n)curses Text_IO subpackages. Especially the output of -the button and state names is done by Ads's enumeration IO, which +the button and state names is done by Ads's enumeration IO, which allows you to print the names of enumeration literals. That's really nice. #MOUSE-PAD00 diff --git a/INSTALL b/INSTALL index dddedd11..8ea212e6 100644 --- a/INSTALL +++ b/INSTALL @@ -26,7 +26,7 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- --- $Id: INSTALL,v 1.229 2021/04/17 22:26:34 tom Exp $ +-- $Id: INSTALL,v 1.230 2021/06/17 21:11:08 tom Exp $ --------------------------------------------------------------------- How to install Ncurses/Terminfo on your system --------------------------------------------------------------------- @@ -2197,7 +2197,7 @@ CONFIGURING FALLBACK ENTRIES: tree is accessible (that is, in single-user mode or at OS installation time) the ncurses library can be compiled to include an array of pre-fetched fallback entries. - + NOTE: This must be done on a machine which has ncurses' infocmp and terminfo database installed (as well as ncurses' tic and infocmp programs). That is because the fallback sources are generated and diff --git a/Makefile.os2 b/Makefile.os2 index 960c2bdb..bc3407d6 100644 --- a/Makefile.os2 +++ b/Makefile.os2 @@ -1,5 +1,5 @@ ############################################################################## -# Copyright 2020 Thomas E. Dickey # +# Copyright 2020,2021 Thomas E. Dickey # # Copyright 1998-2000,2006 Free Software Foundation, Inc. # # # # Permission is hereby granted, free of charge, to any person obtaining a # @@ -26,7 +26,7 @@ # use or other dealings in this Software without prior written # # authorization. # ################################################################################ -# $Id: Makefile.os2,v 1.12 2020/02/02 23:34:34 tom Exp $ +# $Id: Makefile.os2,v 1.13 2021/06/17 21:20:30 tom Exp $ # # Wrapper Makefile for ncurses library under OS/2. # Author: Juan Jose Garcia Ripoll . @@ -70,7 +70,7 @@ # disappear are not essential. # # I first thought about killing '_nc_*' symbols, but it seems that some of -# them --_nc_panel_hook, _nc_ada*, etc-- are needed outside ncurses.dll. +# them --_nc_panel_hook, _nc_ada*, etc-- are needed outside ncurses.dll. # However, the whole size of the export table will not be larger than 1k or # so. # diff --git a/NEWS b/NEWS index 3265d19f..4b1e7d3c 100644 --- a/NEWS +++ b/NEWS @@ -26,7 +26,7 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- --- $Id: NEWS,v 1.3673 2021/06/13 00:16:30 tom Exp $ +-- $Id: NEWS,v 1.3676 2021/06/19 19:09:22 tom Exp $ ------------------------------------------------------------------------------- This is a log of changes that ncurses has gone through since Zeyd started @@ -46,6 +46,11 @@ See the AUTHORS file for the corresponding full names. Changes through 1.9.9e did not credit all contributions; it is not possible to add this information. +20210619 + + improve configure-macro used for dependencies of --disable-leaks such + as --with-valgrind + + trim trailing blanks from files + 20210612 + fixes for scan-build, valgrind build/testing. + update config.guess @@ -119,7 +124,7 @@ it is not possible to add this information. + relax modification-time comparison in CF_LINK_FUNCS to allow it to accept link() function with NFS filesystems which change the mtime on the link target, e.g., several BSD systems. - + call delay_output_sp to handle BSD-style padding when tputs_sp is + + call delay_output_sp to handle BSD-style padding when tputs_sp is called, whether directly or internally, to ensure that the SCREEN pointer is passed correctly (reports by Henric Jungheim, Juraj Lutter). diff --git a/README b/README index a48e3f61..84998f23 100644 --- a/README +++ b/README @@ -1,5 +1,5 @@ ------------------------------------------------------------------------------- --- Copyright 2020 Thomas E. Dickey -- +-- Copyright 2020,2021 Thomas E. Dickey -- -- Copyright 1998-2012,2018 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -26,7 +26,7 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- --- $Id: README,v 1.28 2020/02/02 23:34:34 tom Exp $ +-- $Id: README,v 1.29 2021/06/17 21:20:30 tom Exp $ ------------------------------------------------------------------------------- README file for the ncurses package @@ -37,7 +37,7 @@ See the file TO-DO for things that still need doing, including known bugs. Browse the file misc/ncurses-intro.html for narrative descriptions of how to use ncurses and the panel, menu, and form libraries. - + Browse the file doc/html/hackguide.html for a tour of the package internals. ROADMAP AND PACKAGE OVERVIEW: @@ -45,7 +45,7 @@ ROADMAP AND PACKAGE OVERVIEW: You should be reading this file in a directory called: ncurses-d.d, where d.d is the current version number (see the dist.mk file in this directory for that). There should be a number of subdirectories, including `c++', `form', -`man', `menu', `misc', `ncurses', `panel', `progs', `test', 'tack' and `Ada95'. +`man', `menu', `misc', `ncurses', `panel', `progs', `test', 'tack' and `Ada95'. (The 'tack' program may be distributed separately). A full build/install of this package typically installs several libraries, a @@ -149,7 +149,7 @@ help you systematically exercise the library functions. AUTHORS: -Pavel Curtis: +Pavel Curtis: wrote the original ncurses Zeyd M. Ben-Halim: diff --git a/README.emx b/README.emx index c48b312c..666eaec7 100644 --- a/README.emx +++ b/README.emx @@ -1,5 +1,5 @@ ------------------------------------------------------------------------------- --- Copyright 2020 Thomas E. Dickey -- +-- Copyright 2020,2021 Thomas E. Dickey -- -- Copyright 1998-2006,2018 Free Software Foundation, Inc. -- -- -- -- Permission is hereby granted, free of charge, to any person obtaining a -- @@ -26,7 +26,7 @@ -- sale, use or other dealings in this Software without prior written -- -- authorization. -- ------------------------------------------------------------------------------- --- $Id: README.emx,v 1.11 2020/02/02 23:34:34 tom Exp $ +-- $Id: README.emx,v 1.12 2021/06/17 21:20:30 tom Exp $ -- Author: Thomas Dickey ------------------------------------------------------------------------------- @@ -34,7 +34,7 @@ You can build ncurses on OS/2 in the EMX environment. But you must build and acquire tools. Not all of the tools distributed with EMX work properly, and some additional ones are required. -First, the configure script distributed with ncurses will not run as-is in EMX. +First, the configure script distributed with ncurses will not run as-is in EMX. You can generate a new one if you have autoconf built for EMX. You will need the EMX development tools, of course. Get these programs to start: @@ -65,7 +65,7 @@ may fix these problems: + I also built from sources (because the distributed binaries did not work) the cmp, diff programs. - + Other required utilities such as ar, cat, chmod, cp, gawk, grep, mv, ls, rm, mkdir, sed, sort and tr worked. diff --git a/VERSION b/VERSION index 9c6a6134..c54fc1f1 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -5:0:10 6.2 20210612 +5:0:10 6.2 20210619 diff --git a/aclocal.m4 b/aclocal.m4 index d48cde0c..02a57484 100644 --- a/aclocal.m4 +++ b/aclocal.m4 @@ -29,7 +29,7 @@ dnl*************************************************************************** dnl dnl Author: Thomas E. Dickey 1995-on dnl -dnl $Id: aclocal.m4,v 1.961 2021/05/19 23:35:25 tom Exp $ +dnl $Id: aclocal.m4,v 1.963 2021/06/19 23:41:36 tom Exp $ dnl Macros used in NCURSES auto-configuration script. dnl dnl These macros are maintained separately from NCURSES. The copyright on @@ -1603,7 +1603,7 @@ if test "x$ifelse([$2],,CLANG_COMPILER,[$2])" = "xyes" ; then fi ]) dnl --------------------------------------------------------------------------- -dnl CF_CONST_X_STRING version: 6 updated: 2021/01/01 13:31:04 +dnl CF_CONST_X_STRING version: 7 updated: 2021/06/07 17:39:17 dnl ----------------- dnl The X11R4-X11R6 Xt specification uses an ambiguous String type for most dnl character-strings. @@ -1633,7 +1633,7 @@ AC_TRY_COMPILE( #include #include ], -[String foo = malloc(1); (void)foo],[ +[String foo = malloc(1); free((void*)foo)],[ AC_CACHE_CHECK(for X11/Xt const-feature,cf_cv_const_x_string,[ AC_TRY_COMPILE( @@ -2964,7 +2964,7 @@ rm -rf ./conftest* AC_SUBST(EXTRA_CFLAGS) ])dnl dnl --------------------------------------------------------------------------- -dnl CF_GETOPT_HEADER version: 7 updated: 2021/01/01 13:31:04 +dnl CF_GETOPT_HEADER version: 8 updated: 2021/06/19 19:16:16 dnl ---------------- dnl Check for getopt's variables which are commonly defined in stdlib.h, dnl unistd.h or (nonstandard) in getopt.h @@ -2977,7 +2977,7 @@ for cf_header in stdio.h stdlib.h unistd.h getopt.h do AC_TRY_COMPILE([ #include <$cf_header>], -[int x = optind; char *y = optarg], +[int x = optind; char *y = optarg; (void)x; (void)y], [cf_cv_getopt_header=$cf_header break]) done @@ -5986,19 +5986,29 @@ then fi ])dnl dnl --------------------------------------------------------------------------- -dnl CF_NO_LEAKS_OPTION version: 8 updated: 2021/01/05 20:05:09 +dnl CF_NO_LEAKS_OPTION version: 9 updated: 2021/06/13 19:45:41 dnl ------------------ dnl see CF_WITH_NO_LEAKS +dnl +dnl $1 = option/name +dnl $2 = help-text +dnl $3 = symbol to define if the option is set +dnl $4 = additional actions to take if the option is set AC_DEFUN([CF_NO_LEAKS_OPTION],[ AC_MSG_CHECKING(if you want to use $1 for testing) AC_ARG_WITH($1, [$2], - [AC_DEFINE_UNQUOTED($3,1,"Define to 1 if you want to use $1 for testing.")ifelse([$4],,[ + [case "x$withval" in + (x|xno) ;; + (*) + : "${with_cflags:=-g}" + : "${enable_leaks:=no}" + with_$1=yes + AC_DEFINE_UNQUOTED($3,1,"Define to 1 if you want to use $1 for testing.")ifelse([$4],,[ $4 ]) - : "${with_cflags:=-g}" - : "${enable_leaks:=no}" - with_$1=yes], + ;; + esac], [with_$1=]) AC_MSG_RESULT(${with_$1:-no}) diff --git a/announce.html.in b/announce.html.in index 84b9d429..9651b06f 100644 --- a/announce.html.in +++ b/announce.html.in @@ -1,7 +1,7 @@ @@ -41,7 +41,7 @@

ADACURSES 1 User Commands

-ADACURSES(1)                     User Commands                    ADACURSES(1)
+ADACURSES(1)                     User Commands                    ADACURSES(1)
 
 
 
@@ -51,7 +51,7 @@

SYNOPSIS

-       adacurses6-config [options]
+       adacurses6-config [options]

DESCRIPTION

@@ -60,20 +60,20 @@

OPTIONS

-       --cflags
+       --cflags
               echos the gnat (Ada  compiler)  flags  needed  to  compile  with
               AdaCurses.
 
-       --libs echos the gnat libraries needed to link with AdaCurses.
+       --libs echos the gnat libraries needed to link with AdaCurses.
 
-       --version
+       --version
               echos  the  release+patchdate  version  of the ncurses libraries
               used to configure and build AdaCurses.
 
-       --help prints a list of the adacurses6-config script's options.
+       --help prints a list of the adacurses6-config script's options.
 
-       If no options are given, adacurses6-config prints  the  combination  of
-       --cflags and --libs that gnatmake expects (see example).
+       If no options are given, adacurses6-config prints  the  combination  of
+       --cflags and --libs that gnatmake expects (see example).

EXAMPLE

@@ -124,13 +124,13 @@

SEE ALSO

-       curses(3x)
+       curses(3X)
 
-       This describes ncurses version 6.2 (patch 20210522).
+       This describes ncurses version 6.2 (patch 20210612).
 
 
 
-                                                                  ADACURSES(1)
+                                                                  ADACURSES(1)
    diff --git a/doc/html/man/captoinfo.1m.html b/doc/html/man/captoinfo.1m.html index 010332cd..78146fa6 100644 --- a/doc/html/man/captoinfo.1m.html +++ b/doc/html/man/captoinfo.1m.html @@ -1,4 +1,4 @@ - -curs_addch 3x +curs_addch 3X -

    curs_addch 3x

    +

    curs_addch 3X

    -curs_addch(3x)                                                  curs_addch(3x)
+curs_addch(3X)                                                  curs_addch(3X)

    NAME

    -       addch, waddch, mvaddch, mvwaddch, echochar, wechochar - add a character
-       (with attributes) to a curses window, then advance the cursor
+       addch, waddch, mvaddch, mvwaddch, echochar, wechochar - add a character
+       (with attributes) to a curses window, then advance the cursor

    SYNOPSIS

    -       #include <curses.h>
+       #include <curses.h>
 
-       int addch(const chtype ch);
-       int waddch(WINDOW *win, const chtype ch);
-       int mvaddch(int y, int x, const chtype ch);
-       int mvwaddch(WINDOW *win, int y, int x, const chtype ch);
+       int addch(const chtype ch);
+       int waddch(WINDOW *win, const chtype ch);
+       int mvaddch(int y, int x, const chtype ch);
+       int mvwaddch(WINDOW *win, int y, int x, const chtype ch);
 
-       int echochar(const chtype ch);
-       int wechochar(WINDOW *win, const chtype ch);
+       int echochar(const chtype ch);
+       int wechochar(WINDOW *win, const chtype ch);

    DESCRIPTION

    Adding characters

    -       The addch, waddch, mvaddch and mvwaddch routines put the  character  ch
+       The addch, waddch, mvaddch and mvwaddch routines put the  character  ch
        into  the  given  window  at its current window position, which is then
-       advanced.  They are  analogous  to  putchar(3)  in  stdio(3).   If  the
+       advanced.  They are  analogous  to  putchar(3)  in  stdio(3).   If  the
        advance is at the right margin:
 
-       o   The cursor automatically wraps to the beginning of the next line.
+       o   The cursor automatically wraps to the beginning of the next line.
 
-       o   At  the  bottom of the current scrolling region, and if scrollok is
+       o   At  the  bottom of the current scrolling region, and if scrollok is
            enabled, the scrolling region is scrolled up one line.
 
-       o   If scrollok is not enabled, writing a character at the lower  right
+       o   If scrollok is not enabled, writing a character at the lower  right
            margin  succeeds.   However, an error is returned because it is not
            possible to wrap to a new line
 
-       If ch is a tab, newline, carriage return or backspace,  the  cursor  is
+       If ch is a tab, newline, carriage return or backspace,  the  cursor  is
        moved appropriately within the window:
 
-       o   Backspace  moves the cursor one character left; at the left edge of
+       o   Backspace  moves the cursor one character left; at the left edge of
            a window it does nothing.
 
-       o   Carriage return moves the cursor to the window left margin  on  the
+       o   Carriage return moves the cursor to the window left margin  on  the
            current line.
 
-       o   Newline  does  a clrtoeol, then moves the cursor to the window left
+       o   Newline  does  a clrtoeol, then moves the cursor to the window left
            margin on the next line, scrolling the window if on the last line.
 
-       o   Tabs are considered to be at every eighth column.  The tab interval
-           may be altered by setting the TABSIZE variable.
+       o   Tabs are considered to be at every eighth column.  The tab interval
+           may be altered by setting the TABSIZE variable.
 
-       If  ch  is  any  other nonprintable character, it is drawn in printable
-       form, i.e., the ^X notation used by unctrl(3x).   Calling  winch  after
+       If  ch  is  any  other nonprintable character, it is drawn in printable
+       form, i.e., the ^X notation used by unctrl(3X).   Calling  winch  after
        adding  a  nonprintable character does not return the character itself,
        but instead returns the printable representation of the character.
 
        Video attributes can be combined with a character  argument  passed  to
-       addch  or  related  functions by logical-ORing them into the character.
+       addch  or  related  functions by logical-ORing them into the character.
        (Thus, text, including attributes, can be  copied  from  one  place  to
-       another  using  inch(3x)  and  addch.)   See the curs_attr(3x) page for
+       another  using  inch(3X)  and  addch.)   See the curs_attr(3X) page for
        values of predefined video attribute constants  that  can  be  usefully
        OR'ed into characters.

    Echoing characters

    -       The  echochar  and wechochar routines are equivalent to a call to addch
-       followed by a call to refresh(3x), or a call to waddch  followed  by  a
-       call  to wrefresh.  The knowledge that only a single character is being
+       The  echochar  and wechochar routines are equivalent to a call to addch
+       followed by a call to refresh(3X), or a call to waddch  followed  by  a
+       call  to wrefresh.  The knowledge that only a single character is being
        output  is  used  and,  for  non-control  characters,  a   considerable
        performance  gain  may be seen by using these routines instead of their
        equivalents.
@@ -120,16 +120,16 @@

    Line Graphics

            The following variables may be used to add line drawing  characters  to
-       the  screen  with  routines of the addch family.  The default character
-       listed below is used if the acsc capability does not define a terminal-
+       the  screen  with  routines of the addch family.  The default character
+       listed below is used if the acsc capability does not define a terminal-
        specific   replacement   for   it,   or  if  the  terminal  and  locale
        configuration requires  Unicode  but  the  library  is  unable  to  use
        Unicode.
 
        The names are taken from VT100 nomenclature.
 
-       ACS            ACS       acsc   Glyph
-       Name           Default   char   Name
+       ACS            ACS       acsc   Glyph
+       Name           Default   char   Name
        ---------------------------------------------------------
        ACS_BLOCK      #         0      solid square block
        ACS_BOARD      #         h      board of squares
@@ -166,29 +166,29 @@

    RETURN VALUE

    -       All routines return the integer ERR upon failure and OK on success (the
-       SVr4 manuals specify only "an  integer  value  other  than  ERR")  upon
+       All routines return the integer ERR upon failure and OK on success (the
+       SVr4 manuals specify only "an  integer  value  other  than  ERR")  upon
        successful  completion, unless otherwise noted in the preceding routine
        descriptions.
 
        Functions with a "mv" prefix first  perform  a  cursor  movement  using
-       wmove, and return an error if the position is outside the window, or if
+       wmove, and return an error if the position is outside the window, or if
        the window pointer is null.
 
        If it is not  possible  to  add  a  complete  character,  an  error  is
        returned:
 
-       o   If  scrollok is not enabled, writing a character at the lower right
+       o   If  scrollok is not enabled, writing a character at the lower right
            margin succeeds.  However, an error is returned because it  is  not
            possible to wrap to a new line
 
-       o   If  an error is detected when converting a multibyte character to a
+       o   If  an error is detected when converting a multibyte character to a
            sequence of bytes, or if it is not  possible  to  add  all  of  the
            resulting bytes in the window, an error is returned.

    NOTES

    -       Note that addch, mvaddch, mvwaddch, and echochar may be macros.
+       Note that addch, mvaddch, mvwaddch, and echochar may be macros.

    PORTABILITY

    @@ -198,107 +198,107 @@

    ACS Symbols

    -       X/Open Curses states that the ACS_ definitions are char constants.  For
-       the  wide-character  implementation  (see  curs_add_wch),   there   are
-       analogous   WACS_   definitions  which  are  cchar_t  constants.   Some
+       X/Open Curses states that the ACS_ definitions are char constants.  For
+       the  wide-character  implementation  (see  curs_add_wch),   there   are
+       analogous   WACS_   definitions  which  are  cchar_t  constants.   Some
        implementations are problematic:
 
-       o   Some implementations define the ACS symbols to a constant (such  as
+       o   Some implementations define the ACS symbols to a constant (such  as
            Solaris), while others define those to entries in an array.
 
-           This  implementation uses an array acs_map, as done in SVr4 curses.
-           NetBSD also uses an array, actually named _acs_char, with a #define
+           This  implementation uses an array acs_map, as done in SVr4 curses.
+           NetBSD also uses an array, actually named _acs_char, with a #define
            for compatibility.
 
-       o   HPUX curses equates some of the ACS_ symbols to the analogous WACS_
-           symbols  as  if  the  ACS_  symbols  were  wide  characters.    The
+       o   HPUX curses equates some of the ACS_ symbols to the analogous WACS_
+           symbols  as  if  the  ACS_  symbols  were  wide  characters.    The
            misdefined  symbols  are the arrows and other symbols which are not
            used for line-drawing.
 
-       o   X/Open Curses (issues 2 through 7) has a  typographical  error  for
-           the  ACS_LANTERN  symbol,  equating  its  "VT100+  Character"  to I
+       o   X/Open Curses (issues 2 through 7) has a  typographical  error  for
+           the  ACS_LANTERN  symbol,  equating  its  "VT100+  Character"  to I
            (capital I), while the header files for SVr4 curses and the various
-           implementations use i (lowercase).
+           implementations use i (lowercase).
 
            None  of the terminal descriptions on Unix platforms use uppercase-
-           I,  except  for  Solaris  (i.e.,  screen's  terminal   description,
+           I,  except  for  Solaris  (i.e.,  screen's  terminal   description,
            apparently  based on the X/Open documentation around 1995).  On the
-           other hand, the terminal description gs6300 (AT&T PC6300 with EMOTS
+           other hand, the terminal description gs6300 (AT&T PC6300 with EMOTS
            Terminal Emulator) uses lowercase-i.
 
        Some  ACS  symbols  (ACS_S3,  ACS_S7,  ACS_LEQUAL,  ACS_GEQUAL, ACS_PI,
        ACS_NEQUAL, ACS_STERLING) were not documented in any publicly  released
-       System  V.   However,  many  publicly  available terminfos include acsc
+       System  V.   However,  many  publicly  available terminfos include acsc
        strings in which their key characters (pryz{|})  are  embedded,  and  a
        second-hand  list  of  their  character descriptions has come to light.
-       The ACS-prefixed names for them were invented for ncurses(3x).
+       The ACS-prefixed names for them were invented for ncurses(3X).
 
-       The displayed values for the ACS_ and WACS_ constants depend on
+       The displayed values for the ACS_ and WACS_ constants depend on
 
-       o   the library configuration, i.e., ncurses versus ncursesw, where the
+       o   the library configuration, i.e., ncurses versus ncursesw, where the
            latter  is  capable  of displaying Unicode while the former is not,
            and
 
-       o   whether the locale uses UTF-8 encoding.
+       o   whether the locale uses UTF-8 encoding.
 
        In certain cases,  the  terminal  is  unable  to  display  line-drawing
        characters   except   by   using   UTF-8   (see   the   discussion   of
-       NCURSES_NO_UTF8_ACS in ncurses(3x)).
+       NCURSES_NO_UTF8_ACS in ncurses(3X)).

    Character Set

    -       X/Open Curses assumes that the parameter passed to  waddch  contains  a
-       single  character.   As  discussed in curs_attr(3x), that character may
+       X/Open Curses assumes that the parameter passed to  waddch  contains  a
+       single  character.   As  discussed in curs_attr(3X), that character may
        have been more than eight bits in an SVr3 or SVr4  implementation,  but
        in  the  X/Open Curses model, the details are not given.  The important
        distinction between SVr4 curses and X/Open  Curses  is  that  the  non-
        character  information  (attributes  and  color) was separated from the
-       character information which is packed in a chtype to pass to waddch.
+       character information which is packed in a chtype to pass to waddch.
 
-       In this implementation,  chtype  holds  an  eight-bit  character.   But
+       In this implementation,  chtype  holds  an  eight-bit  character.   But
        ncurses  allows  multibyte  characters  to be passed in a succession of
-       calls to waddch.  The other implementations do not do this; a  call  to
-       waddch  passes  exactly  one  character which may be rendered as one or
+       calls to waddch.  The other implementations do not do this; a  call  to
+       waddch  passes  exactly  one  character which may be rendered as one or
        more cells on the screen depending on whether it is printable.
 
        Depending on the locale settings, ncurses will inspect the byte  passed
-       in  each  call  to waddch, and check if the latest call will continue a
-       multibyte sequence.  When a character is complete, ncurses displays the
+       in  each  call  to waddch, and check if the latest call will continue a
+       multibyte sequence.  When a character is complete, ncurses displays the
        character and moves to the next position in the screen.
 
        If  the  calling  application  interrupts  the succession of bytes in a
-       multibyte character by moving the current location (e.g., using wmove),
+       multibyte character by moving the current location (e.g., using wmove),
        ncurses discards the partially built character, starting over again.
 
        For  portability  to  other  implementations,  do  not  rely  upon this
        behavior:
 
-       o   check if a character can be represented as a  single  byte  in  the
-           current locale before attempting call waddch, and
+       o   check if a character can be represented as a  single  byte  in  the
+           current locale before attempting call waddch, and
 
-       o   call wadd_wch for characters which cannot be handled by waddch.
+       o   call wadd_wch for characters which cannot be handled by waddch.

    TABSIZE

    -       The  TABSIZE  variable  is  implemented  in  SVr4 and other versions of
-       curses, but is not part of X/Open curses  (see  curs_variables(3x)  for
+       The  TABSIZE  variable  is  implemented  in  SVr4 and other versions of
+       curses, but is not part of X/Open curses  (see  curs_variables(3X)  for
        more details).
 
-       If ch is a carriage return, the cursor is moved to the beginning of the
+       If ch is a carriage return, the cursor is moved to the beginning of the
        current row of the window.  This is true of other implementations,  but
        is not documented.

    SEE ALSO

    -       curses(3x),      curs_attr(3x),      curs_clear(3x),     curs_inch(3x),
-       curs_outopts(3x), curs_refresh(3x), curs_variables(3x), putc(3).
+       curses(3X),      curs_attr(3X),      curs_clear(3X),     curs_inch(3X),
+       curs_outopts(3X), curs_refresh(3X), curs_variables(3X), putc(3).
 
        Comparable functions  in  the  wide-character  (ncursesw)  library  are
-       described in curs_add_wch(3x).
+       described in curs_add_wch(3X).
 
 
 
-                                                                curs_addch(3x)
+                                                                curs_addch(3X)
      diff --git a/doc/html/man/curs_addchstr.3x.html b/doc/html/man/curs_addchstr.3x.html index 5712a67c..5b37fc44 100644 --- a/doc/html/man/curs_addchstr.3x.html +++ b/doc/html/man/curs_addchstr.3x.html @@ -1,4 +1,4 @@ - -curs_bkgd 3x +curs_bkgd 3X -

      curs_bkgd 3x

      +

      curs_bkgd 3X

      -curs_bkgd(3x)                                                    curs_bkgd(3x)
+curs_bkgd(3X)                                                    curs_bkgd(3X)

      NAME

      -       bkgdset,  wbkgdset,  bkgd,  wbkgd,  getbkgd  - curses window background
+       bkgdset,  wbkgdset,  bkgd,  wbkgd,  getbkgd  - curses window background
        manipulation routines

      SYNOPSIS

      -       #include <curses.h>
+       #include <curses.h>
 
-       void bkgdset(chtype ch);
-       void wbkgdset(WINDOW *win, chtype ch);
+       void bkgdset(chtype ch);
+       void wbkgdset(WINDOW *win, chtype ch);
 
-       int bkgd(chtype ch);
-       int wbkgd(WINDOW *win, chtype ch);
+       int bkgd(chtype ch);
+       int wbkgd(WINDOW *win, chtype ch);
 
-       chtype getbkgd(WINDOW *win);
+       chtype getbkgd(WINDOW *win);

      DESCRIPTION

      bkgdset

      -       The bkgdset and wbkgdset routines  manipulate  the  background  of  the
-       named  window.   The  window  background  is a chtype consisting of any
+       The bkgdset and wbkgdset routines  manipulate  the  background  of  the
+       named  window.   The  window  background  is a chtype consisting of any
        combination of attributes  (i.e.,  rendition)  and  a  character.   The
        attribute part of the background is combined (OR'ed) with all non-blank
-       characters that are written into the  window  with  waddch.   Both  the
+       characters that are written into the  window  with  waddch.   Both  the
        character  and  attribute parts of the background are combined with the
        blank characters.  The background becomes a property of  the  character
        and  moves  with  the character through any scrolling and insert/delete
@@ -82,20 +82,20 @@

      bkgd

      -       The bkgd and wbkgd functions set the background property of the current
+       The bkgd and wbkgd functions set the background property of the current
        or  specified  window  and  then  apply this setting to every character
        position in that window.  According to  X/Open  Curses,  it  should  do
        this:
 
-       o   The  rendition  of  every character on the screen is changed to the
+       o   The  rendition  of  every character on the screen is changed to the
            new background rendition.
 
-       o   Wherever the former background character appears, it is changed  to
+       o   Wherever the former background character appears, it is changed  to
            the new background character.
 
        Neither  X/Open Curses nor the SVr4 manual pages give details about the
-       way the rendition of characters on the screen is updated when  bkgd  or
-       wbkgd is used to change the background character.
+       way the rendition of characters on the screen is updated when  bkgd  or
+       wbkgd is used to change the background character.
 
        This  implementation,  like  SVr4 curses, does not store the background
        and window attribute contributions to each cell separately.  It updates
@@ -103,22 +103,22 @@
        colors contained in the background.   For  each  cell  in  the  window,
        whether or not it is blank:
 
-       o   The  library  first  compares  the character, and if it matches the
+       o   The  library  first  compares  the character, and if it matches the
            current character part of the background, it replaces that with the
            new background character.
 
-       o   The  library  then  checks  if the cell uses color, i.e., its color
+       o   The  library  then  checks  if the cell uses color, i.e., its color
            pair value is nonzero.  If not, it simply replaces  the  attributes
            and  color  pair  in  the  cell  with those from the new background
            character.
 
-       o   If the cell uses color, and that matches the color in  the  current
+       o   If the cell uses color, and that matches the color in  the  current
            background, the library removes attributes which may have come from
            the current background and adds attributes from the new background.
            It  finishes  by  setting  the  cell  to use the color from the new
            background.
 
-       o   If the cell uses color, and that does not match the  color  in  the
+       o   If the cell uses color, and that does not match the  color  in  the
            current   background,   the  library  updates  only  the  non-color
            attributes, first removing those  which  may  have  come  from  the
            current  background,  and  then  adding  attributes  from  the  new
@@ -127,32 +127,32 @@
        If the background's character value is zero, a space is assumed.
 
        If the terminal does not support  color,  or  if  color  has  not  been
-       started   with   start_color,  the  new  background  character's  color
+       started   with   start_color,  the  new  background  character's  color
        attribute will be ignored.

      getbkgd

      -       The getbkgd function returns  the  given  window's  current  background
+       The getbkgd function returns  the  given  window's  current  background
        character/attribute pair.

      RETURN VALUE

              These  functions are described in the XSI Curses standard, Issue 4.  It
-       specifies that bkgd and wbkgd return  ERR  on  failure,  but  gives  no
+       specifies that bkgd and wbkgd return  ERR  on  failure,  but  gives  no
        failure conditions.
 
-       The  routines  bkgd and wbkgd return the integer OK, unless the library
+       The  routines  bkgd and wbkgd return the integer OK, unless the library
        has not been initialized.
 
-       In contrast, the SVr4.0 manual says bkgd and wbkgd may return OK "or  a
-       non-negative  integer  if  immedok  is set", which refers to the return
-       value from wrefresh (used to implement the immediate repainting).   The
-       SVr4  curses  wrefresh  returns the number of characters written to the
+       In contrast, the SVr4.0 manual says bkgd and wbkgd may return OK "or  a
+       non-negative  integer  if  immedok  is set", which refers to the return
+       value from wrefresh (used to implement the immediate repainting).   The
+       SVr4  curses  wrefresh  returns the number of characters written to the
        screen during the refresh.  This implementation does not do that.

      NOTES

      -       Note that bkgdset and bkgd may be macros.
+       Note that bkgdset and bkgd may be macros.
 
        X/Open Curses mentions that the character part of the  background  must
        be  a  single-byte  value.   This  implementation, like SVr4, checks to
@@ -166,11 +166,11 @@

      SEE ALSO

      -       curses(3x), curs_addch(3x), curs_attr(3x), curs_outopts(3x)
+       curses(3X), curs_addch(3X), curs_attr(3X), curs_outopts(3X)
 
 
 
-                                                                 curs_bkgd(3x)
+                                                                 curs_bkgd(3X)
        diff --git a/doc/html/man/curs_bkgrnd.3x.html b/doc/html/man/curs_bkgrnd.3x.html index ec8a36e7..4e86eeee 100644 --- a/doc/html/man/curs_bkgrnd.3x.html +++ b/doc/html/man/curs_bkgrnd.3x.html @@ -1,4 +1,4 @@ - -curs_color 3x +curs_color 3X -

        curs_color 3x

        +

        curs_color 3X

        -curs_color(3x)                                                  curs_color(3x)
+curs_color(3X)                                                  curs_color(3X)

        NAME

        -       start_color, has_colors, can_change_color, init_pair, init_color,
-       init_extended_pair, init_extended_color, color_content, pair_content,
-       extended_color_content, extended_pair_content, reset_color_pairs,
-       COLOR_PAIR, PAIR_NUMBER - curses color manipulation routines
+       start_color, has_colors, can_change_color, init_pair, init_color,
+       init_extended_pair, init_extended_color, color_content, pair_content,
+       extended_color_content, extended_pair_content, reset_color_pairs,
+       COLOR_PAIR, PAIR_NUMBER - curses color manipulation routines

        SYNOPSIS

        -       #include <curses.h>
+       #include <curses.h>
 
-       int start_color(void);
+       int start_color(void);
 
-       bool has_colors(void);
-       bool can_change_color(void);
+       bool has_colors(void);
+       bool can_change_color(void);
 
-       int init_pair(short pair, short f, short b);
-       int init_color(short color, short r, short g, short b);
+       int init_pair(short pair, short f, short b);
+       int init_color(short color, short r, short g, short b);
        /* extensions */
-       int init_extended_pair(int pair, int f, int b);
-       int init_extended_color(int color, int r, int g, int b);
+       int init_extended_pair(int pair, int f, int b);
+       int init_extended_color(int color, int r, int g, int b);
 
-       int color_content(short color, short *r, short *g, short *b);
-       int pair_content(short pair, short *f, short *b);
+       int color_content(short color, short *r, short *g, short *b);
+       int pair_content(short pair, short *f, short *b);
        /* extensions */
-       int extended_color_content(int color, int *r, int *g, int *b);
-       int extended_pair_content(int pair, int *f, int *b);
+       int extended_color_content(int color, int *r, int *g, int *b);
+       int extended_pair_content(int pair, int *f, int *b);
 
        /* extensions */
-       void reset_color_pairs(void);
+       void reset_color_pairs(void);
 
-       int COLOR_PAIR(int n);
-       PAIR_NUMBER(attrs);
+       int COLOR_PAIR(int n);
+       PAIR_NUMBER(attrs);

        DESCRIPTION

        Overview

        -       curses supports color attributes on terminals with that capability.  To
-       use  these  routines  start_color  must  be called, usually right after
-       initscr.  Colors are always used in pairs (referred to as color-pairs).
+       curses supports color attributes on terminals with that capability.  To
+       use  these  routines  start_color  must  be called, usually right after
+       initscr.  Colors are always used in pairs (referred to as color-pairs).
        A  color-pair  consists  of  a  foreground color (for characters) and a
        background color (for the blank field on which the characters are  dis-
        played).   A  programmer  initializes  a  color-pair  with  the routine
-       init_pair.  After it has been initialized, COLOR_PAIR(n) can be used to
+       init_pair.  After it has been initialized, COLOR_PAIR(n) can be used to
        convert the pair to a video attribute.
 
        If  a  terminal is capable of redefining colors, the programmer can use
-       the routine init_color to change the definition of a color.   The  rou-
-       tines  has_colors  and can_change_color return TRUE or FALSE, depending
+       the routine init_color to change the definition of a color.   The  rou-
+       tines  has_colors  and can_change_color return TRUE or FALSE, depending
        on whether the terminal has color capabilities and whether the program-
-       mer can change the colors.  The routine color_content allows a program-
+       mer can change the colors.  The routine color_content allows a program-
        mer to extract the amounts of red, green, and  blue  components  in  an
-       initialized  color.   The  routine  pair_content allows a programmer to
+       initialized  color.   The  routine  pair_content allows a programmer to
        find out how a given color-pair is currently defined.

        Color Rendering

        -       The curses library combines these inputs to produce  the  actual  fore-
+       The curses library combines these inputs to produce  the  actual  fore-
        ground and background colors shown on the screen:
 
-       o   per-character video attributes (e.g., via waddch),
+       o   per-character video attributes (e.g., via waddch),
 
-       o   the window attribute (e.g., by wattrset), and
+       o   the window attribute (e.g., by wattrset), and
 
-       o   the background character (e.g., wbkgdset).
+       o   the background character (e.g., wbkgdset).
 
        Per-character and window attributes are usually set by a parameter con-
        taining video attributes including a color pair value.  Some  functions
-       such as wattr_set use a separate parameter which is the color pair num-
+       such as wattr_set use a separate parameter which is the color pair num-
        ber.
 
        The background character is a special case:  it  includes  a  character
-       value, just as if it were passed to waddch.
+       value, just as if it were passed to waddch.
 
-       The  curses library does the actual work of combining these color pairs
-       in an internal function called from waddch:
+       The  curses library does the actual work of combining these color pairs
+       in an internal function called from waddch:
 
-       o   If the parameter passed to waddch is blank, and it uses the special
+       o   If the parameter passed to waddch is blank, and it uses the special
            color pair 0,
 
-           o   curses next checks the window attribute.
+           o   curses next checks the window attribute.
 
-           o   If  the window attribute does not use color pair 0, curses uses
+           o   If  the window attribute does not use color pair 0, curses uses
                the color pair from the window attribute.
 
-           o   Otherwise, curses uses the background character.
+           o   Otherwise, curses uses the background character.
 
-       o   If the parameter passed to waddch is not blank, or it does not  use
-           the  special  color  pair 0, curses prefers the color pair from the
+       o   If the parameter passed to waddch is not blank, or it does not  use
+           the  special  color  pair 0, curses prefers the color pair from the
            parameter, if it is nonzero.  Otherwise, it tries the window attri-
            bute next, and finally the background character.
 
-       Some  curses  functions such as wprintw call waddch.  Those do not com-
+       Some  curses  functions such as wprintw call waddch.  Those do not com-
        bine its parameter with a color pair.  Consequently those calls use on-
        ly the window attribute or the background character.

        CONSTANTS

        -       In <curses.h> the following macros are defined.  These are the standard
-       colors (ISO-6429).  curses also assumes that COLOR_BLACK is the default
+       In <curses.h> the following macros are defined.  These are the standard
+       colors (ISO-6429).  curses also assumes that COLOR_BLACK is the default
        background color for all terminals.
 
-             COLOR_BLACK
-             COLOR_RED
-             COLOR_GREEN
-             COLOR_YELLOW
-             COLOR_BLUE
-             COLOR_MAGENTA
-             COLOR_CYAN
-             COLOR_WHITE
+             COLOR_BLACK
+             COLOR_RED
+             COLOR_GREEN
+             COLOR_YELLOW
+             COLOR_BLUE
+             COLOR_MAGENTA
+             COLOR_CYAN
+             COLOR_WHITE
 
        Some  terminals  support  more than the eight (8) "ANSI" colors.  There
        are no standard names for those additional colors.
@@ -164,257 +164,257 @@

        VARIABLES

        COLORS

        -       is initialized by start_color to the maximum number of colors the  ter-
+       is initialized by start_color to the maximum number of colors the  ter-
        minal can support.

        COLOR_PAIRS

        -       is  initialized by start_color to the maximum number of color pairs the
+       is  initialized by start_color to the maximum number of color pairs the
        terminal can support.

        FUNCTIONS

        start_color

        -       The start_color routine requires no arguments.  It must  be  called  if
+       The start_color routine requires no arguments.  It must  be  called  if
        the  programmer wants to use colors, and before any other color manipu-
        lation routine is called.  It is good practice  to  call  this  routine
-       right after initscr.  start_color does this:
+       right after initscr.  start_color does this:
 
-       o   It  initializes  two  global variables, COLORS and COLOR_PAIRS (re-
+       o   It  initializes  two  global variables, COLORS and COLOR_PAIRS (re-
            spectively defining the maximum number of  colors  and  color-pairs
            the terminal can support).
 
-       o   It  initializes  the special color pair 0 to the default foreground
+       o   It  initializes  the special color pair 0 to the default foreground
            and background colors.  No other color pairs are initialized.
 
-       o   It restores the colors on the terminal to the values they had  when
+       o   It restores the colors on the terminal to the values they had  when
            the terminal was just turned on.
 
-       o   If  the  terminal supports the initc (initialize_color) capability,
-           start_color initializes its internal table  representing  the  red,
+       o   If  the  terminal supports the initc (initialize_color) capability,
+           start_color initializes its internal table  representing  the  red,
            green, and blue components of the color palette.
 
            The components depend on whether the terminal uses CGA (aka "ANSI")
-           or HLS (i.e.,  the  hls  (hue_lightness_saturation)  capability  is
+           or HLS (i.e.,  the  hls  (hue_lightness_saturation)  capability  is
            set).   The  table  is  initialized  first  for  eight basic colors
            (black, red, green, yellow, blue, magenta, cyan, and white),  using
            weights that depend upon the CGA/HLS choice.  For "ANSI" colors the
-           weights are 680 or 0 depending on whether  the  corresponding  red,
-           green,  or  blue component is used or not.  That permits using 1000
+           weights are 680 or 0 depending on whether  the  corresponding  red,
+           green,  or  blue component is used or not.  That permits using 1000
            to represent bold/bright colors.  After the  initial  eight  colors
            (if  the  terminal  supports more than eight colors) the components
-           are initialized using the same pattern, but with weights  of  1000.
-           SVr4 uses a similar scheme, but uses 1000 for the components of the
+           are initialized using the same pattern, but with weights  of  1000.
+           SVr4 uses a similar scheme, but uses 1000 for the components of the
            initial eight colors.
 
-           start_color does not attempt to set the terminal's color palette to
-           match its built-in table.  An application may use init_color to al-
+           start_color does not attempt to set the terminal's color palette to
+           match its built-in table.  An application may use init_color to al-
            ter the internal table along with the terminal's color.
 
        These limits apply to color values and  color  pairs.   Values  outside
        these limits are not legal, and may result in a runtime error:
 
-       o   COLORS  corresponds to the terminal database's max_colors capabili-
-           ty, (see terminfo(5)).
+       o   COLORS  corresponds to the terminal database's max_colors capabili-
+           ty, (see terminfo(5)).
 
-       o   color values are expected to be in the range 0 to COLORS-1,  inclu-
-           sive (including 0 and COLORS-1).
+       o   color values are expected to be in the range 0 to COLORS-1,  inclu-
+           sive (including 0 and COLORS-1).
 
-       o   a  special  color value -1 is used in certain extended functions to
-           denote the default color (see use_default_colors(3x)).
+       o   a  special  color value -1 is used in certain extended functions to
+           denote the default color (see use_default_colors(3X)).
 
-       o   COLOR_PAIRS corresponds to the terminal database's max_pairs  capa-
-           bility, (see terminfo(5)).
+       o   COLOR_PAIRS corresponds to the terminal database's max_pairs  capa-
+           bility, (see terminfo(5)).
 
-       o   legal color pair values are in the range 1 to COLOR_PAIRS-1, inclu-
+       o   legal color pair values are in the range 1 to COLOR_PAIRS-1, inclu-
            sive.
 
-       o   color pair 0 is special; it denotes "no color".
+       o   color pair 0 is special; it denotes "no color".
 
-           Color pair 0 is assumed to be white on black, but is actually what-
+           Color pair 0 is assumed to be white on black, but is actually what-
            ever  the terminal implements before color is initialized.  It can-
            not be modified by the application.

        has_colors

        -       The has_colors routine requires no arguments.  It returns TRUE  if  the
-       terminal can manipulate colors; otherwise, it returns FALSE.  This rou-
+       The has_colors routine requires no arguments.  It returns TRUE  if  the
+       terminal can manipulate colors; otherwise, it returns FALSE.  This rou-
        tine facilitates writing terminal-independent programs.  For example, a
        programmer  can  use  it  to  decide whether to use color or some other
        video attribute.

        can_change_color

        -       The can_change_color routine requires no arguments.  It returns TRUE if
+       The can_change_color routine requires no arguments.  It returns TRUE if
        the  terminal  supports colors and can change their definitions; other,
-       it returns FALSE.  This routine facilitates  writing  terminal-indepen-
+       it returns FALSE.  This routine facilitates  writing  terminal-indepen-
        dent programs.

        init_pair

        -       The init_pair routine changes the definition of a color-pair.  It takes
+       The init_pair routine changes the definition of a color-pair.  It takes
        three arguments: the number of the color-pair to be changed, the  fore-
        ground color number, and the background color number.  For portable ap-
        plications:
 
-       o   The first argument must be a legal color pair  value.   If  default
-           colors are used (see use_default_colors(3x)) the upper limit is ad-
+       o   The first argument must be a legal color pair  value.   If  default
+           colors are used (see use_default_colors(3X)) the upper limit is ad-
            justed to allow for extra pairs which use a default color in  fore-
            ground and/or background.
 
-       o   The second and third arguments must be legal color values.
+       o   The second and third arguments must be legal color values.
 
        If  the  color-pair was previously initialized, the screen is refreshed
        and all occurrences of that color-pair are changed to the  new  defini-
        tion.
 
-       As  an  extension,  ncurses  allows you to set color pair 0 via the as-
-       sume_default_colors(3x) routine, or to specify the use of default  col-
-       ors  (color  number  -1) if you first invoke the use_default_colors(3x)
+       As  an  extension,  ncurses  allows you to set color pair 0 via the as-
+       sume_default_colors(3X) routine, or to specify the use of default  col-
+       ors  (color  number  -1) if you first invoke the use_default_colors(3X)
        routine.

        init_extended_pair

        -       Because init_pair uses signed shorts for its  parameters,  that  limits
+       Because init_pair uses signed shorts for its  parameters,  that  limits
        color-pairs  and  color-values to 32767 on modern hardware.  The exten-
-       sion init_extended_pair uses ints for the color-pair  and  color-value,
+       sion init_extended_pair uses ints for the color-pair  and  color-value,
        allowing a larger number of colors to be supported.

        init_color

        -       The  init_color  routine  changes  the definition of a color.  It takes
+       The  init_color  routine  changes  the definition of a color.  It takes
        four arguments: the number of the color to be changed followed by three
        RGB values (for the amounts of red, green, and blue components).
 
-       o   The  first argument must be a legal color value; default colors are
-           not allowed here.  (See the section Colors for  the  default  color
+       o   The  first argument must be a legal color value; default colors are
+           not allowed here.  (See the section Colors for  the  default  color
            index.)
 
-       o   Each  of  the  last  three arguments must be a value in the range 0
-           through 1000.
+       o   Each  of  the  last  three arguments must be a value in the range 0
+           through 1000.
 
-       When init_color is used, all occurrences of that color  on  the  screen
+       When init_color is used, all occurrences of that color  on  the  screen
        immediately change to the new definition.

        init_extended_color

        -       Because  init_color  uses signed shorts for its parameters, that limits
+       Because  init_color  uses signed shorts for its parameters, that limits
        color-values and their red, green, and blue components to 32767 on mod-
-       ern hardware.  The extension init_extended_color uses ints for the col-
+       ern hardware.  The extension init_extended_color uses ints for the col-
        or value and for setting the red, green, and blue components,  allowing
        a larger number of colors to be supported.

        color_content

        -       The color_content routine gives programmers a way to find the intensity
+       The color_content routine gives programmers a way to find the intensity
        of the red, green, and blue (RGB) components in a color.   It  requires
-       four  arguments:  the  color  number, and three addresses of shorts for
+       four  arguments:  the  color  number, and three addresses of shorts for
        storing the information about the amounts of red, green, and blue  com-
        ponents in the given color.
 
-       o   The  first  argument  must  be a legal color value, i.e., 0 through
-           COLORS-1, inclusive.
+       o   The  first  argument  must  be a legal color value, i.e., 0 through
+           COLORS-1, inclusive.
 
-       o   The values that are stored at the addresses pointed to by the  last
-           three  arguments  are  in  the  range 0 (no component) through 1000
+       o   The values that are stored at the addresses pointed to by the  last
+           three  arguments  are  in  the  range 0 (no component) through 1000
            (maximum amount of component), inclusive.

        extended_color_content

        -       Because color_content uses signed shorts for its parameters, that  lim-
+       Because color_content uses signed shorts for its parameters, that  lim-
        its  color-values and their red, green, and blue components to 32767 on
-       modern hardware.  The extension extended_color_content  uses  ints  for
+       modern hardware.  The extension extended_color_content  uses  ints  for
        the  color value and for returning the red, green, and blue components,
        allowing a larger number of colors to be supported.

        pair_content

        -       The pair_content routine allows programmers to find out what  colors  a
+       The pair_content routine allows programmers to find out what  colors  a
        given  color-pair consists of.  It requires three arguments: the color-
-       pair number, and two addresses of shorts for storing the foreground and
+       pair number, and two addresses of shorts for storing the foreground and
        the background color numbers.
 
-       o   The  first argument must be a legal color value, i.e., in the range
-           1 through COLOR_PAIRS-1, inclusive.
+       o   The  first argument must be a legal color value, i.e., in the range
+           1 through COLOR_PAIRS-1, inclusive.
 
-       o   The values that are stored at the addresses pointed to by the  sec-
-           ond  and  third arguments are in the range 0 through COLORS, inclu-
+       o   The values that are stored at the addresses pointed to by the  sec-
+           ond  and  third arguments are in the range 0 through COLORS, inclu-
            sive.

        extended_pair_content

        -       Because pair_content uses signed shorts for its parameters, that limits
+       Because pair_content uses signed shorts for its parameters, that limits
        color-pair and color-values to 32767 on modern hardware.  The extension
-       extended_pair_content uses ints for the color pair  and  for  returning
+       extended_pair_content uses ints for the color pair  and  for  returning
        the  foreground and background colors, allowing a larger number of col-
        ors to be supported.

        reset_color_pairs

        -       The extension reset_color_pairs tells ncurses to  discard  all  of  the
-       color-pair  information  which was set with init_pair.  It also touches
+       The extension reset_color_pairs tells ncurses to  discard  all  of  the
+       color-pair  information  which was set with init_pair.  It also touches
        the current- and standard-screens, allowing an  application  to  switch
        color palettes rapidly.

        PAIR_NUMBER

        -       PAIR_NUMBER(attrs)  extracts  the  color value from its attrs parameter
+       PAIR_NUMBER(attrs)  extracts  the  color value from its attrs parameter
        and returns it as a color pair number.

        COLOR_PAIR

        -       Its inverse COLOR_PAIR(n) converts a color pair number to an attribute.
+       Its inverse COLOR_PAIR(n) converts a color pair number to an attribute.
        Attributes  can  hold color pairs in the range 0 to 255.  If you need a
-       color pair larger than that, you must use functions  such  as  attr_set
+       color pair larger than that, you must use functions  such  as  attr_set
        (which  pass  the  color  pair as a separate parameter) rather than the
-       legacy functions such as attrset.
+       legacy functions such as attrset.

        RETURN VALUE

        -       The routines can_change_color and has_colors return TRUE or FALSE.
+       The routines can_change_color and has_colors return TRUE or FALSE.
 
-       All other routines return the integer ERR upon failure and an OK  (SVr4
-       specifies  only "an integer value other than ERR") upon successful com-
+       All other routines return the integer ERR upon failure and an OK  (SVr4
+       specifies  only "an integer value other than ERR") upon successful com-
        pletion.
 
        X/Open defines no error conditions.  SVr4 does document some error con-
        ditions which apply in general:
 
-       o   This implementation will return ERR on attempts to use color values
-           outside the range 0 to COLORS-1 (except for the default colors  ex-
-           tension), or use color pairs outside the range 0 to COLOR_PAIRS-1.
+       o   This implementation will return ERR on attempts to use color values
+           outside the range 0 to COLORS-1 (except for the default colors  ex-
+           tension), or use color pairs outside the range 0 to COLOR_PAIRS-1.
 
-           Color values used in init_color must be in the range 0 to 1000.
+           Color values used in init_color must be in the range 0 to 1000.
 
            An  error  is  returned  from all functions if the terminal has not
            been initialized.
 
-           An error is returned from secondary functions such as init_pair  if
-           start_color was not called.
+           An error is returned from secondary functions such as init_pair  if
+           start_color was not called.
 
-       o   SVr4  does much the same, except that it returns ERR from pair_con-
-           tent if the pair was not initialized using init_pairs  and  it  re-
-           turns  ERR  from  color_content  if  the  terminal does not support
+       o   SVr4  does much the same, except that it returns ERR from pair_con-
+           tent if the pair was not initialized using init_pairs  and  it  re-
+           turns  ERR  from  color_content  if  the  terminal does not support
            changing colors.
 
-           This implementation does not return ERR for either case.
+           This implementation does not return ERR for either case.
 
        Specific functions make additional checks:
 
-          init_color
+          init_color
                returns an error if the terminal does not support this feature,
-               e.g.,  if  the  initialize_color  capability is absent from the
+               e.g.,  if  the  initialize_color  capability is absent from the
                terminal description.
 
-          start_color
+          start_color
                returns an error if the color table cannot be allocated.

        NOTES

        -       In the ncurses implementation, there is  a  separate  color  activation
-       flag,  color palette, color pairs table, and associated COLORS and COL-
-       OR_PAIRS counts for each screen; the start_color function only  affects
+       In the ncurses implementation, there is  a  separate  color  activation
+       flag,  color palette, color pairs table, and associated COLORS and COL-
+       OR_PAIRS counts for each screen; the start_color function only  affects
        the current screen.  The SVr4/XSI interface is not really designed with
        this in mind, and historical implementations may use  a  single  shared
        color palette.
@@ -422,57 +422,57 @@
        Setting  an  implicit  background  color  via a color pair affects only
        character cells that a character write  operation  explicitly  touches.
        To  change the background color used when parts of a window are blanked
-       by erasing or scrolling operations, see curs_bkgd(3x).
+       by erasing or scrolling operations, see curs_bkgd(3X).
 
        Several caveats apply on older x86 machines  (e.g.,  i386,  i486)  with
        VGA-compatible graphics:
 
-       o   COLOR_YELLOW  is  actually  brown.  To get yellow, use COLOR_YELLOW
-           combined with the A_BOLD attribute.
+       o   COLOR_YELLOW  is  actually  brown.  To get yellow, use COLOR_YELLOW
+           combined with the A_BOLD attribute.
 
-       o   The A_BLINK attribute should in theory cause the background  to  go
+       o   The A_BLINK attribute should in theory cause the background  to  go
            bright.  This often fails to work, and even some cards for which it
            mostly works (such as the Paradise and compatibles)  do  the  wrong
            thing  when  you try to set a bright "yellow" background (you get a
            blinking yellow foreground instead).
 
-       o   Color RGB values are not settable.
+       o   Color RGB values are not settable.

        PORTABILITY

        -       This implementation satisfies XSI Curses's minimum maximums for  COLORS
-       and COLOR_PAIRS.
+       This implementation satisfies XSI Curses's minimum maximums for  COLORS
+       and COLOR_PAIRS.
 
-       The  init_pair  routine accepts negative values of foreground and back-
-       ground color to support the use_default_colors(3x) extension, but  only
+       The  init_pair  routine accepts negative values of foreground and back-
+       ground color to support the use_default_colors(3X) extension, but  only
        if that routine has been first invoked.
 
-       The assumption that COLOR_BLACK is the default background color for all
-       terminals can be modified using  the  assume_default_colors(3x)  exten-
+       The assumption that COLOR_BLACK is the default background color for all
+       terminals can be modified using  the  assume_default_colors(3X)  exten-
        sion.
 
        This  implementation checks the pointers, e.g., for the values returned
-       by color_content and pair_content, and will treat those as optional pa-
+       by color_content and pair_content, and will treat those as optional pa-
        rameters when null.
 
        X/Open  Curses  does  not  specify a limit for the number of colors and
-       color pairs which a terminal can support.  However, in its use of short
+       color pairs which a terminal can support.  However, in its use of short
        for  the  parameters,  it carries over SVr4's implementation detail for
        the compiled terminfo database, which uses signed 16-bit numbers.  This
        implementation  provides extended versions of those functions which use
-       short parameters, allowing applications to use larger color- and  pair-
+       short parameters, allowing applications to use larger color- and  pair-
        numbers.
 
-       The reset_color_pairs function is an extension of ncurses.
+       The reset_color_pairs function is an extension of ncurses.

        SEE ALSO

        -       curses(3x),  curs_initscr(3x),  curs_attr(3x),  curs_variables(3x), de-
-       fault_colors(3x)
+       curses(3X),  curs_initscr(3X),  curs_attr(3X),  curs_variables(3X), de-
+       fault_colors(3X)
 
 
 
-                                                                curs_color(3x)
+                                                                curs_color(3X)
          diff --git a/doc/html/man/curs_delch.3x.html b/doc/html/man/curs_delch.3x.html index 17698ec5..28dc7595 100644 --- a/doc/html/man/curs_delch.3x.html +++ b/doc/html/man/curs_delch.3x.html @@ -1,4 +1,4 @@ - -curs_getcchar 3x +curs_getcchar 3X -

          curs_getcchar 3x

          +

          curs_getcchar 3X

          -curs_getcchar(3x)                                            curs_getcchar(3x)
+curs_getcchar(3X)                                            curs_getcchar(3X)

          NAME

          -       getcchar,  setcchar  - Get a wide character string and rendition from a
-       cchar_t or set a cchar_t from a wide-character string
+       getcchar,  setcchar  - Get a wide character string and rendition from a
+       cchar_t or set a cchar_t from a wide-character string

          SYNOPSIS

          -       #include <curses.h>
+       #include <curses.h>
 
-       int getcchar(
-               const cchar_t *wcval,
-               wchar_t *wch,
-               attr_t *attrs,
-               short *color_pair,
-               void *opts );
+       int getcchar(
+               const cchar_t *wcval,
+               wchar_t *wch,
+               attr_t *attrs,
+               short *color_pair,
+               void *opts );
 
-       int setcchar(
-               cchar_t *wcval,
-               const wchar_t *wch,
-               const attr_t attrs,
-               short color_pair,
-               const void *opts );
+       int setcchar(
+               cchar_t *wcval,
+               const wchar_t *wch,
+               const attr_t attrs,
+               short color_pair,
+               const void *opts );

          DESCRIPTION

          getcchar

          -       The getcchar function gets a wide-character string and rendition from a
-       cchar_t  argument.   When  wch  is  not  a  null  pointer, the getcchar
+       The getcchar function gets a wide-character string and rendition from a
+       cchar_t  argument.   When  wch  is  not  a  null  pointer, the getcchar
        function does the following:
 
-       o   Extracts information from a cchar_t value wcval
+       o   Extracts information from a cchar_t value wcval
 
-       o   Stores the character attributes in the location pointed to by attrs
+       o   Stores the character attributes in the location pointed to by attrs
 
-       o   Stores the color-pair in the location pointed to by color_pair
+       o   Stores the color-pair in the location pointed to by color_pair
 
-       o   Stores the wide-character string, characters referenced  by  wcval,
-           into the array pointed to by wch.
+       o   Stores the wide-character string, characters referenced  by  wcval,
+           into the array pointed to by wch.
 
-       When wch is a null pointer, the getcchar function does the following:
+       When wch is a null pointer, the getcchar function does the following:
 
-       o   Obtains the number of wide characters pointed to by wcval
+       o   Obtains the number of wide characters pointed to by wcval
 
-       o   Does not change the data referenced by attrs or color_pair
+       o   Does not change the data referenced by attrs or color_pair

          setcchar

          -       The  setcchar  function initializes the location pointed to by wcval by
+       The  setcchar  function initializes the location pointed to by wcval by
        using:
 
-       o   The character attributes in attrs
+       o   The character attributes in attrs
 
-       o   The color pair in color_pair
+       o   The color pair in color_pair
 
-       o   The wide-character string pointed to by wch.  The  string  must  be
+       o   The wide-character string pointed to by wch.  The  string  must  be
            L'\0' terminated, contain at most one spacing character, which must
            be the first.
 
-           Up to CCHARW_MAX-1 nonspacing characters  may  follow.   Additional
+           Up to CCHARW_MAX-1 nonspacing characters  may  follow.   Additional
            nonspacing characters are ignored.
 
            The string may contain a single control character instead.  In that
@@ -112,55 +112,55 @@

          EXTENSIONS

          -       X/Open Curses documents the opts argument as reserved for  future  use,
+       X/Open Curses documents the opts argument as reserved for  future  use,
        saying  that  it must be null.  This implementation uses that parameter
        in ABI 6 for the functions which have a color-pair parameter to support
        extended color pairs:
 
-       o   For   functions  which modify the color, e.g., setcchar, if opts is
-           set it is treated as a pointer to int, and used to  set  the  color
-           pair instead of the short pair parameter.
+       o   For   functions  which modify the color, e.g., setcchar, if opts is
+           set it is treated as a pointer to int, and used to  set  the  color
+           pair instead of the short pair parameter.
 
-       o   For  functions which retrieve the color, e.g., getcchar, if opts is
-           set it is treated as a pointer to int, and  used  to  retrieve  the
-           color  pair  as  an  int  value,  in addition retrieving it via the
-           standard pointer to short parameter.
+       o   For  functions which retrieve the color, e.g., getcchar, if opts is
+           set it is treated as a pointer to int, and  used  to  retrieve  the
+           color  pair  as  an  int  value,  in addition retrieving it via the
+           standard pointer to short parameter.

          NOTES

          -       The wcval argument may be a value generated by a call to setcchar or by
-       a function that has a cchar_t output argument.  If wcval is constructed
+       The wcval argument may be a value generated by a call to setcchar or by
+       a function that has a cchar_t output argument.  If wcval is constructed
        by any other means, the effect is unspecified.

          RETURN VALUE

          -       When wch is a  null  pointer,  getcchar  returns  the  number  of  wide
-       characters referenced by wcval, including one for a trailing null.
+       When wch is a  null  pointer,  getcchar  returns  the  number  of  wide
+       characters referenced by wcval, including one for a trailing null.
 
-       When  wch  is  not  a null pointer, getcchar returns OK upon successful
-       completion, and ERR otherwise.
+       When  wch  is  not  a null pointer, getcchar returns OK upon successful
+       completion, and ERR otherwise.
 
-       Upon successful completion, setcchar returns OK.  Otherwise, it returns
-       ERR.
+       Upon successful completion, setcchar returns OK.  Otherwise, it returns
+       ERR.

          PORTABILITY

          -       The  CCHARW_MAX  symbol is specific to ncurses.  X/Open Curses does not
-       provide details for the layout of the cchar_t structure.  It tells what
+       The  CCHARW_MAX  symbol is specific to ncurses.  X/Open Curses does not
+       provide details for the layout of the cchar_t structure.  It tells what
        data are stored in it:
 
-       o   a spacing character (wchar_t, i.e., 32-bits).
+       o   a spacing character (wchar_t, i.e., 32-bits).
 
-       o   non-spacing characters (again, wchar_t's).
+       o   non-spacing characters (again, wchar_t's).
 
-       o   attributes  (at  least  16 bits, inferred from the various ACS- and
+       o   attributes  (at  least  16 bits, inferred from the various ACS- and
            WACS-flags).
 
-       o   color pair (at least 16 bits,  inferred  from  the  unsigned  short
+       o   color pair (at least 16 bits,  inferred  from  the  unsigned  short
            type).
 
        The non-spacing characters are optional, in the sense that zero or more
-       may be stored in a cchar_t.  XOpen/Curses specifies a limit:
+       may be stored in a cchar_t.  XOpen/Curses specifies a limit:
 
            Implementations may limit the number of non-spacing characters that
            can  be  associated with a spacing character, provided any limit is
@@ -168,16 +168,16 @@
 
        The Unix implementations at the time follow that limit:
 
-       o   AIX 4 and OSF1 4 use the same declaration with an array of  5  non-
-           spacing characters z and a single spacing character c.
+       o   AIX 4 and OSF1 4 use the same declaration with an array of  5  non-
+           spacing characters z and a single spacing character c.
 
-       o   HP-UX 10  uses  an  opaque  structure with 28 bytes, which is large
-           enough for the 6 wchar_t values.
+       o   HP-UX 10  uses  an  opaque  structure with 28 bytes, which is large
+           enough for the 6 wchar_t values.
 
-       o   Solaris xpg4 curses uses a single array of 6 wchar_t values.
+       o   Solaris xpg4 curses uses a single array of 6 wchar_t values.
 
-       This implementation's cchar_t was defined in 1995 using 5 for the total
-       of  spacing and non-spacing characters (CCHARW_MAX).  That was probably
+       This implementation's cchar_t was defined in 1995 using 5 for the total
+       of  spacing and non-spacing characters (CCHARW_MAX).  That was probably
        due to a misreading of the  AIX 4  header  files,  because  the  X/Open
        Curses  document  was  not generally available at that time.  Later (in
        2002), this detail was  overlooked  when  beginning  to  implement  the
@@ -192,11 +192,11 @@

          SEE ALSO

          -       Functions: curs_attr(3x), curs_color(3x), curses(3x), wcwidth(3).
+       Functions: curs_attr(3X), curs_color(3X), curses(3X), wcwidth(3).
 
 
 
-                                                             curs_getcchar(3x)
+                                                             curs_getcchar(3X)
            diff --git a/doc/html/man/curs_getch.3x.html b/doc/html/man/curs_getch.3x.html index b4e6c5cd..d4729923 100644 --- a/doc/html/man/curs_getch.3x.html +++ b/doc/html/man/curs_getch.3x.html @@ -1,4 +1,4 @@ - -curs_inch 3x +curs_inch 3X -

            curs_inch 3x

            +

            curs_inch 3X

            -curs_inch(3x)                                                    curs_inch(3x)
+curs_inch(3X)                                                    curs_inch(3X)

            NAME

            -       inch,  winch,  mvinch,  mvwinch - get a character and attributes from a
-       curses window
+       inch,  winch,  mvinch,  mvwinch - get a character and attributes from a
+       curses window

            SYNOPSIS

            -       #include <curses.h>
+       #include <curses.h>
 
-       chtype inch(void);
-       chtype winch(WINDOW *win);
+       chtype inch(void);
+       chtype winch(WINDOW *win);
 
-       chtype mvinch(int y, int x);
-       chtype mvwinch(WINDOW *win, int y, int x);
+       chtype mvinch(int y, int x);
+       chtype mvwinch(WINDOW *win, int y, int x);

            DESCRIPTION

            -       These routines return the character, of type  chtype,  at  the  current
+       These routines return the character, of type  chtype,  at  the  current
        position  in  the  named  window.   If  any attributes are set for that
        position, their values are OR'ed into the  value  returned.   Constants
-       defined  in <curses.h> can be used with the & (logical AND) operator to
+       defined  in <curses.h> can be used with the & (logical AND) operator to
        extract the character or attributes alone.

            Attributes

                    The following bit-masks may  be  AND-ed  with  characters  returned  by
-       winch.
+       winch.
 
-       A_CHARTEXT     Bit-mask to extract character
-       A_ATTRIBUTES   Bit-mask to extract attributes
-       A_COLOR        Bit-mask to extract color-pair field information
+       A_CHARTEXT     Bit-mask to extract character
+       A_ATTRIBUTES   Bit-mask to extract attributes
+       A_COLOR        Bit-mask to extract color-pair field information

            RETURN VALUE

                    Functions  with  a  "mv"  prefix  first perform a cursor movement using
-       wmove, and return an error if the position is outside the window, or if
+       wmove, and return an error if the position is outside the window, or if
        the window pointer is null.
 
-       The  winch  function  does  not  return an error if the window contains
+       The  winch  function  does  not  return an error if the window contains
        characters larger than 8-bits (255).  Only the low-order 8 bits of  the
-       character are used by winch.
+       character are used by winch.

            NOTES

            @@ -99,41 +99,41 @@
        Very  old systems (before standardization) provide a different function
        with the same name:
 
-       o   The winch function was part of the  original  BSD  curses  library,
-           which   stored   a  7-bit  character  combined  with  the  standout
+       o   The winch function was part of the  original  BSD  curses  library,
+           which   stored   a  7-bit  character  combined  with  the  standout
            attribute.
 
-           In BSD curses, winch returned only the character  (as  an  integer)
-           with the standout attribute removed.
+           In BSD curses, winch returned only the character  (as  an  integer)
+           with the standout attribute removed.
 
-       o   System  V  curses  added support for several video attributes which
+       o   System  V  curses  added support for several video attributes which
            could be combined with characters in the window.
 
            Reflecting this improvement, the function was altered to return the
-           character combined with all video attributes in a chtype value.
+           character combined with all video attributes in a chtype value.
 
        X/Open Curses does not specify the size and layout of attributes, color
-       and character values in chtype; it is  implementation-dependent.   This
+       and character values in chtype; it is  implementation-dependent.   This
        implementation  uses 8 bits for character values.  An application using
        more bits,  e.g.,  a  Unicode  value,  should  use  the  wide-character
        equivalents to these functions.

            SEE ALSO

            -       curses(3x)
-            gives an overview of the WINDOW and chtype data types.
+       curses(3X)
+            gives an overview of the WINDOW and chtype data types.
 
-       curs_attr(3x)
+       curs_attr(3X)
             goes  into  more  detail,  pointing  out  portability problems and
-            constraints on the use of chtype for returning window information.
+            constraints on the use of chtype for returning window information.
 
-       curs_in_wch(3x)
+       curs_in_wch(3X)
             describes comparable functions for the  wide-character  (ncursesw)
             library.
 
 
 
-                                                                 curs_inch(3x)
+                                                                 curs_inch(3X)
              diff --git a/doc/html/man/curs_inchstr.3x.html b/doc/html/man/curs_inchstr.3x.html index a94a7fcf..8b64d97b 100644 --- a/doc/html/man/curs_inchstr.3x.html +++ b/doc/html/man/curs_inchstr.3x.html @@ -1,4 +1,4 @@ - -curs_insstr 3x +curs_insstr 3X -

              curs_insstr 3x

              +

              curs_insstr 3X

              -curs_insstr(3x)                                                curs_insstr(3x)
+curs_insstr(3X)                                                curs_insstr(3X)

              NAME

              -       insstr,  insnstr,  winsstr,  winsnstr,  mvinsstr, mvinsnstr, mvwinsstr,
-       mvwinsnstr - insert string before cursor in a curses window
+       insstr,  insnstr,  winsstr,  winsnstr,  mvinsstr, mvinsnstr, mvwinsstr,
+       mvwinsnstr - insert string before cursor in a curses window

              SYNOPSIS

              -       #include <curses.h>
-       int insstr(const char *str);
-       int insnstr(const char *str, int n);
-       int winsstr(WINDOW *win, const char *str);
-       int winsnstr(WINDOW *win, const char *str, int n);
+       #include <curses.h>
+       int insstr(const char *str);
+       int insnstr(const char *str, int n);
+       int winsstr(WINDOW *win, const char *str);
+       int winsnstr(WINDOW *win, const char *str, int n);
 
-       int mvinsstr(int y, int x, const char *str);
-       int mvinsnstr(int y, int x, const char *str, int n);
-       int mvwinsstr(WINDOW *win, int y, int x, const char *str);
-       int mvwinsnstr(WINDOW *win, int y, int x, const char *str, int n);
+       int mvinsstr(int y, int x, const char *str);
+       int mvinsnstr(int y, int x, const char *str, int n);
+       int mvwinsstr(WINDOW *win, int y, int x, const char *str);
+       int mvwinsnstr(WINDOW *win, int y, int x, const char *str, int n);

              DESCRIPTION

              @@ -69,16 +69,16 @@
        fit on the line) before the character under the cursor.  All characters
        to the right of the cursor are shifted right with  the  possibility  of
        the  rightmost  characters on the line being lost.  The cursor position
-       does not change (after moving to y, x, if  specified).   The  functions
-       with  n  as  the  last argument insert a leading substring of at most n
-       characters.  If n<=0, then the entire string is inserted.
+       does not change (after moving to y, x, if  specified).   The  functions
+       with  n  as  the  last argument insert a leading substring of at most n
+       characters.  If n<=0, then the entire string is inserted.
 
-       Special characters are handled as in addch.
+       Special characters are handled as in addch.

              RETURN VALUE

              -       All routines that return an integer return  ERR  upon  failure  and  OK
-       (SVr4 specifies only "an integer value other than ERR") upon successful
+       All routines that return an integer return  ERR  upon  failure  and  OK
+       (SVr4 specifies only "an integer value other than ERR") upon successful
        completion,  unless  otherwise   noted   in   the   preceding   routine
        descriptions.
 
@@ -87,30 +87,30 @@
        returned.
 
        Functions  with  a  "mv"  prefix  first perform a cursor movement using
-       wmove, and return an error if the position is outside the window, or if
+       wmove, and return an error if the position is outside the window, or if
        the window pointer is null.

              NOTES

              -       Note that all but winsnstr may be macros.
+       Note that all but winsnstr may be macros.

              PORTABILITY

                      These  functions  are  described  in  the XSI Curses standard, Issue 4,
        which adds const qualifiers to the arguments.
 
-       The Single Unix  Specification,  Version  2  states  that  insnstr  and
-       winsnstr  perform  wrapping.  This is probably an error, since it makes
+       The Single Unix  Specification,  Version  2  states  that  insnstr  and
+       winsnstr  perform  wrapping.  This is probably an error, since it makes
        this group of  functions  inconsistent.   Also,  no  implementation  of
        curses documents this inconsistency.

              SEE ALSO

              -       curses(3x), curs_util(3x), curs_clear(3x), curs_inch(3x).
+       curses(3X), curs_util(3X), curs_clear(3X), curs_inch(3X).
 
 
 
-                                                               curs_insstr(3x)
+                                                               curs_insstr(3X)
                diff --git a/doc/html/man/curs_instr.3x.html b/doc/html/man/curs_instr.3x.html index cd6e7278..89ab99c1 100644 --- a/doc/html/man/curs_instr.3x.html +++ b/doc/html/man/curs_instr.3x.html @@ -1,4 +1,4 @@ - -curs_slk 3x +curs_slk 3X -

                curs_slk 3x

                +

                curs_slk 3X

                -curs_slk(3x)                                                      curs_slk(3x)
+curs_slk(3X)                                                      curs_slk(3X)

                NAME

                -       slk_init, slk_set, slk_wset, slk_refresh, slk_noutrefresh, slk_label,
-       slk_clear, slk_restore, slk_touch, slk_attron, slk_attrset,
-       slk_attroff, slk_attr_on, slk_attr_set, slk_attr_off, slk_attr,
-       slk_color, extended_slk_color - curses soft label routines
+       slk_init, slk_set, slk_wset, slk_refresh, slk_noutrefresh, slk_label,
+       slk_clear, slk_restore, slk_touch, slk_attron, slk_attrset,
+       slk_attroff, slk_attr_on, slk_attr_set, slk_attr_off, slk_attr,
+       slk_color, extended_slk_color - curses soft label routines

                SYNOPSIS

                -       #include <curses.h>
+       #include <curses.h>
 
-       int slk_init(int fmt);
+       int slk_init(int fmt);
 
-       int slk_set(int labnum, const char *label, int fmt);
+       int slk_set(int labnum, const char *label, int fmt);
        /* extension */
-       int slk_wset(int labnum, const wchar_t *label, int fmt);
+       int slk_wset(int labnum, const wchar_t *label, int fmt);
 
-       char *slk_label(int labnum);
+       char *slk_label(int labnum);
 
-       int slk_refresh(void);
-       int slk_noutrefresh(void);
-       int slk_clear(void);
-       int slk_restore(void);
-       int slk_touch(void);
+       int slk_refresh(void);
+       int slk_noutrefresh(void);
+       int slk_clear(void);
+       int slk_restore(void);
+       int slk_touch(void);
 
-       int slk_attron(const chtype attrs);
-       int slk_attroff(const chtype attrs);
-       int slk_attrset(const chtype attrs);
-       int slk_attr_on(attr_t attrs, void* opts);
-       int slk_attr_off(const attr_t attrs, void * opts);
-       int slk_attr_set(const attr_t attrs, short pair, void* opts);
+       int slk_attron(const chtype attrs);
+       int slk_attroff(const chtype attrs);
+       int slk_attrset(const chtype attrs);
+       int slk_attr_on(attr_t attrs, void* opts);
+       int slk_attr_off(const attr_t attrs, void * opts);
+       int slk_attr_set(const attr_t attrs, short pair, void* opts);
 
-       attr_t slk_attr(void);
+       attr_t slk_attr(void);
 
-       int slk_color(short pair);
+       int slk_color(short pair);
        /* extension */
-       int extended_slk_color(int pair);
+       int extended_slk_color(int pair);

                DESCRIPTION

                        The slk* functions manipulate the set of soft function-key labels  that
        exist on many terminals.  For those terminals that do not have soft la-
-       bels, curses takes over the bottom line of stdscr, reducing the size of
-       stdscr  and the variable LINES.  curses standardizes on eight labels of
+       bels, curses takes over the bottom line of stdscr, reducing the size of
+       stdscr  and the variable LINES.  curses standardizes on eight labels of
        up to eight characters each.  In addition to this, the  ncurses  imple-
        mentation  supports  a  mode where it simulates 12 labels of up to five
        characters each.  This is useful for PC-like enduser devices.   ncurses
@@ -97,110 +97,110 @@

                Initialization

                -       The slk_init routine must  be  called  before  initscr  or  newterm  is
-       called.   If  initscr eventually uses a line from stdscr to emulate the
-       soft labels, then fmt determines how the labels  are  arranged  on  the
+       The slk_init routine must  be  called  before  initscr  or  newterm  is
+       called.   If  initscr eventually uses a line from stdscr to emulate the
+       soft labels, then fmt determines how the labels  are  arranged  on  the
        screen:
 
-          0  indicates a 3-2-3 arrangement of the labels.
+          0  indicates a 3-2-3 arrangement of the labels.
 
-          1  indicates a 4-4 arrangement
+          1  indicates a 4-4 arrangement
 
-          2  indicates the PC-like 4-4-4 mode.
+          2  indicates the PC-like 4-4-4 mode.
 
-          3  is again the PC-like 4-4-4 mode, but in addition an index line is
+          3  is again the PC-like 4-4-4 mode, but in addition an index line is
              generated, helping the user to identify the key numbers easily.

                Labels

                -       The slk_set routine (and the slk_wset routine  for  the  wide-character
+       The slk_set routine (and the slk_wset routine  for  the  wide-character
        library) has three parameters:
 
-          labnum
-               is  the  label number, from 1 to 8 (12 for fmt in slk_init is 2
-               or 3);
+          labnum
+               is  the  label number, from 1 to 8 (12 for fmt in slk_init is 2
+               or 3);
 
-          label
-               is be the string to put on the label, up to eight (five for fmt
-               in  slk_init is 2 or 3) characters in length.  A null string or
+          label
+               is be the string to put on the label, up to eight (five for fmt
+               in  slk_init is 2 or 3) characters in length.  A null string or
                a null pointer sets up a blank label.
 
-          fmt  is either 0, 1, or 2, indicating whether the  label  is  to  be
+          fmt  is either 0, 1, or 2, indicating whether the  label  is  to  be
                left-justified,  centered,  or  right-justified,  respectively,
                within the label.
 
-       The slk_label routine returns the current label for label  number  lab-
-       num, with leading and trailing blanks stripped.
+       The slk_label routine returns the current label for label  number  lab-
+       num, with leading and trailing blanks stripped.

                Screen updates

                -       The slk_refresh and slk_noutrefresh routines correspond to the wrefresh
-       and wnoutrefresh routines.
+       The slk_refresh and slk_noutrefresh routines correspond to the wrefresh
+       and wnoutrefresh routines.
 
-       The slk_clear routine clears the soft labels from the screen.
+       The slk_clear routine clears the soft labels from the screen.
 
-       The slk_restore routine restores the soft labels to the screen after  a
-       slk_clear has been performed.
+       The slk_restore routine restores the soft labels to the screen after  a
+       slk_clear has been performed.
 
-       The  slk_touch routine forces all the soft labels to be output the next
-       time a slk_noutrefresh is performed.
+       The  slk_touch routine forces all the soft labels to be output the next
+       time a slk_noutrefresh is performed.

                Video attributes

                -       The slk_attron, slk_attrset, slk_attroff and slk_attr  routines  corre-
-       spond  to  attron,  attrset,  attroff and attr_get, respectively.  They
+       The slk_attron, slk_attrset, slk_attroff and slk_attr  routines  corre-
+       spond  to  attron,  attrset,  attroff and attr_get, respectively.  They
        have an effect only if soft labels are simulated on the bottom line  of
        the  screen.   The default highlight for soft keys is A_STANDOUT (as in
        System V curses, which does not document this fact).

                Colors

                -       The slk_color routine corresponds to color_set.  It has an effect  only
+       The slk_color routine corresponds to color_set.  It has an effect  only
        if soft labels are simulated on the bottom line of the screen.
 
-       Because  slk_color  accepts  only short (signed 16-bit integer) values,
-       this implementation provides extended_slk_color which accepts an  inte-
+       Because  slk_color  accepts  only short (signed 16-bit integer) values,
+       this implementation provides extended_slk_color which accepts an  inte-
        ger value, e.g., 32-bits.

                RETURN VALUE

                -       These  routines return ERR upon failure and OK (SVr4 specifies only "an
-       integer value other than ERR") upon successful completion.
+       These  routines return ERR upon failure and OK (SVr4 specifies only "an
+       integer value other than ERR") upon successful completion.
 
        X/Open defines no error conditions.  In this implementation
 
-          slk_attr
+          slk_attr
                returns the attribute used for the soft keys.
 
-          slk_attroff, slk_attron, slk_clear, slk_noutrefresh, slk_refresh,
-          slk_touch
+          slk_attroff, slk_attron, slk_clear, slk_noutrefresh, slk_refresh,
+          slk_touch
                return  an  error if the terminal or the softkeys were not ini-
                tialized.
 
-          slk_attrset
+          slk_attrset
                returns an error if the terminal or the softkeys were not  ini-
                tialized.
 
-          slk_attr_set
+          slk_attr_set
                returns  an error if the terminal or the softkeys were not ini-
                tialized, or the  color  pair  is  outside  the  range  0..COL-
                OR_PAIRS-1.
 
-          slk_color
+          slk_color
                returns  an error if the terminal or the softkeys were not ini-
                tialized, or the  color  pair  is  outside  the  range  0..COL-
                OR_PAIRS-1.
 
-          slk_init
+          slk_init
                returns  an  error if the format parameter is outside the range
                0..3.
 
-          slk_label
-               returns NULL on error.
+          slk_label
+               returns NULL on error.
 
-          slk_set
+          slk_set
                returns an error if the terminal or the softkeys were not  ini-
-               tialized, or the labnum parameter is outside the range of label
+               tialized, or the labnum parameter is outside the range of label
                counts, or if the format parameter is outside the  range  0..2,
                or if memory for the labels cannot be allocated.
 
@@ -231,18 +231,18 @@

                EXTENSIONS

                -       X/Open  Curses  documents the opts argument as reserved for future use,
+       X/Open  Curses  documents the opts argument as reserved for future use,
        saying that it must be null.  This implementation uses  that  parameter
        in ABI 6 for the functions which have a color-pair parameter to support
        extended color pairs.
 
-       For  functions  which modify the color, e.g., slk_attr_set, if opts  is
-       set  it  is  treated  as a pointer to int, and used to  set  the  color
-       pair instead of the short pair parameter.
+       For  functions  which modify the color, e.g., slk_attr_set, if opts  is
+       set  it  is  treated  as a pointer to int, and used to  set  the  color
+       pair instead of the short pair parameter.

                NOTES

                -       Most applications would use slk_noutrefresh because a wrefresh is like-
+       Most applications would use slk_noutrefresh because a wrefresh is like-
        ly to follow soon.
 
 
@@ -250,38 +250,38 @@
        The  XSI  Curses  standard,  Issue 4, described the soft-key functions,
        with some differences from SVr4 curses:
 
-       o   It added functions like the SVr4  attribute-manipulation  functions
-           slk_attron,  slk_attroff, slk_attrset, but which use attr_t parame-
-           ters (rather than chtype), along with a reserved opts parameter.
+       o   It added functions like the SVr4  attribute-manipulation  functions
+           slk_attron,  slk_attroff, slk_attrset, but which use attr_t parame-
+           ters (rather than chtype), along with a reserved opts parameter.
 
            Two of these new functions (unlike the SVr4 functions) have no pro-
-           vision for color: slk_attr_on and slk_attr_off.
+           vision for color: slk_attr_on and slk_attr_off.
 
-           The third function (slk_attr_set) has a color-pair parameter.
+           The third function (slk_attr_set) has a color-pair parameter.
 
-       o   It added const qualifiers to parameters (unnecessarily), and
+       o   It added const qualifiers to parameters (unnecessarily), and
 
-       o   It added slk_color.
+       o   It added slk_color.
 
-       The  format  codes  2  and 3 for slk_init and the function slk_attr are
+       The  format  codes  2  and 3 for slk_init and the function slk_attr are
        specific to ncurses.
 
        X/Open Curses does not specify a limit for the  number  of  colors  and
-       color pairs which a terminal can support.  However, in its use of short
+       color pairs which a terminal can support.  However, in its use of short
        for the parameters, it carries over SVr4's  implementation  detail  for
        the compiled terminfo database, which uses signed 16-bit numbers.  This
        implementation provides extended versions of those functions which  use
-       short  parameters, allowing applications to use larger color- and pair-
+       short  parameters, allowing applications to use larger color- and pair-
        numbers.

                SEE ALSO

                -       curses(3x),    curs_attr(3x),    curs_initscr(3x),    curs_refresh(3x),
-       curs_variables(3x).
+       curses(3X),    curs_attr(3X),    curs_initscr(3X),    curs_refresh(3X),
+       curs_variables(3X).
 
 
 
-                                                                  curs_slk(3x)
+                                                                  curs_slk(3X)
                  diff --git a/doc/html/man/curs_sp_funcs.3x.html b/doc/html/man/curs_sp_funcs.3x.html index 17bf5247..c8bed9b6 100644 --- a/doc/html/man/curs_sp_funcs.3x.html +++ b/doc/html/man/curs_sp_funcs.3x.html @@ -1,4 +1,4 @@ - -curs_touch 3x +curs_touch 3X -

                  curs_touch 3x

                  +

                  curs_touch 3X

                  -curs_touch(3x)                                                  curs_touch(3x)
+curs_touch(3X)                                                  curs_touch(3X)

                  NAME

                  -       touchwin, touchline, untouchwin, wtouchln, is_linetouched,
-       is_wintouched - curses refresh control routines
+       touchwin, touchline, untouchwin, wtouchln, is_linetouched,
+       is_wintouched - curses refresh control routines

                  SYNOPSIS

                  -       #include <curses.h>
+       #include <curses.h>
 
-       int touchline(WINDOW *win, int start, int count);
+       int touchline(WINDOW *win, int start, int count);
 
-       int touchwin(WINDOW *win);
-       int wtouchln(WINDOW *win, int y, int n, int changed);
+       int touchwin(WINDOW *win);
+       int wtouchln(WINDOW *win, int y, int n, int changed);
 
-       int untouchwin(WINDOW *win);
+       int untouchwin(WINDOW *win);
 
-       bool is_linetouched(WINDOW *win, int line);
-       bool is_wintouched(WINDOW *win);
+       bool is_linetouched(WINDOW *win, int line);
+       bool is_wintouched(WINDOW *win);

                  DESCRIPTION

                  -       The touchwin and touchline routines throw away all optimization  infor-
+       The touchwin and touchline routines throw away all optimization  infor-
        mation about which parts of the window have been touched, by pretending
        that the entire window has been drawn on.  This is sometimes  necessary
        when  using  overlapping  windows, since a change to one window affects
        the other window, but the records of which lines have been  changed  in
-       the other window do not reflect the change.  The routine touchline only
-       pretends that count lines have been changed, beginning with line start.
+       the other window do not reflect the change.  The routine touchline only
+       pretends that count lines have been changed, beginning with line start.
 
-       The untouchwin routine marks all lines in the window as unchanged since
-       the last call to wrefresh.
+       The untouchwin routine marks all lines in the window as unchanged since
+       the last call to wrefresh.
 
-       The  wtouchln  routine makes n lines in the window, starting at line y,
-       look as if they have (changed=1) or have not (changed=0)  been  changed
-       since the last call to wrefresh.
+       The  wtouchln  routine makes n lines in the window, starting at line y,
+       look as if they have (changed=1) or have not (changed=0)  been  changed
+       since the last call to wrefresh.
 
-       The is_linetouched and is_wintouched routines return TRUE if the speci-
-       fied line/window was modified since the last call to  wrefresh;  other-
-       wise  they  return  FALSE.   In addition, is_linetouched returns ERR if
-       line is not valid for the given window.
+       The is_linetouched and is_wintouched routines return TRUE if the speci-
+       fied line/window was modified since the last call to  wrefresh;  other-
+       wise  they  return  FALSE.   In addition, is_linetouched returns ERR if
+       line is not valid for the given window.

                  RETURN VALUE

                  -       All routines return the integer ERR upon failure and an  integer  value
-       other  than  ERR  upon successful completion, unless otherwise noted in
+       All routines return the integer ERR upon failure and an  integer  value
+       other  than  ERR  upon successful completion, unless otherwise noted in
        the preceding routine descriptions.
 
        X/Open does not define any error conditions.  In this implementation
 
-          is_linetouched
+          is_linetouched
                returns an error if the window pointer is null, or if the  line
                number is outside the window.
 
-               The constant ERR is distinct from TRUE and FALSE, which are the
+               The constant ERR is distinct from TRUE and FALSE, which are the
                normal return values of this function.   Because  the  function
-               returns a bool, returning ERR (which is neither TRUE nor FALSE)
+               returns a bool, returning ERR (which is neither TRUE nor FALSE)
                may not be supported by the compiler.
 
                To provide error-checking and also match  the  X/Open  function
-               prototype, the ERR is provided by a macro named is_linetouched.
-               The actual function returns FALSE when it detects an error.
+               prototype, the ERR is provided by a macro named is_linetouched.
+               The actual function returns FALSE when it detects an error.
 
-          wtouchln
+          wtouchln
                returns an error if the window pointer is null, or if the  line
                number is outside the window.
 
@@ -116,7 +116,7 @@
        These  functions  were  introduced  by SVr4.  The Solaris curses header
        file, for instance, defines both an actual function and macro for each.
        The  macros  give the same result as the actual functions.  SVr4 curses
-       does not check the window parameter win to ensure that it is not  NULL;
+       does not check the window parameter win to ensure that it is not  NULL;
        otherwise this implementation behaves the same as SVr4.
 
        The XSI Curses standard, Issue 4 describes these functions, but defines
@@ -124,15 +124,15 @@

                  NOTES

                  -       All of these routines except wtouchln may be macros.
+       All of these routines except wtouchln may be macros.

                  SEE ALSO

                  -       curses(3x), curs_refresh(3x), curs_variables(3x).
+       curses(3X), curs_refresh(3X), curs_variables(3X).
 
 
 
-                                                                curs_touch(3x)
+                                                                curs_touch(3X)
                    diff --git a/doc/html/man/curs_trace.3x.html b/doc/html/man/curs_trace.3x.html index a60ae970..5e8643d8 100644 --- a/doc/html/man/curs_trace.3x.html +++ b/doc/html/man/curs_trace.3x.html @@ -1,4 +1,4 @@ - -curs_window 3x +curs_window 3X -

                    curs_window 3x

                    +

                    curs_window 3X

                    -curs_window(3x)                                                curs_window(3x)
+curs_window(3X)                                                curs_window(3X)

                    NAME

                    -       newwin, delwin, mvwin, subwin, derwin, mvderwin, dupwin, wsyncup,
-       syncok, wcursyncup, wsyncdown - create curses windows
+       newwin, delwin, mvwin, subwin, derwin, mvderwin, dupwin, wsyncup,
+       syncok, wcursyncup, wsyncdown - create curses windows

                    SYNOPSIS

                    -       #include <curses.h>
-
-       WINDOW *newwin(
-             int nlines, int ncols,
-             int begin_y, int begin_x);
-       int delwin(WINDOW *win);
-       int mvwin(WINDOW *win, int y, int x);
-       WINDOW *subwin(WINDOW *orig,
-             int nlines, int ncols,
-             int begin_y, int begin_x);
-       WINDOW *derwin(WINDOW *orig,
-             int nlines, int ncols,
-             int begin_y, int begin_x);
-       int mvderwin(WINDOW *win, int par_y, int par_x);
-       WINDOW *dupwin(WINDOW *win);
-       void wsyncup(WINDOW *win);
-       int syncok(WINDOW *win, bool bf);
-       void wcursyncup(WINDOW *win);
-       void wsyncdown(WINDOW *win);
+       #include <curses.h>
+
+       WINDOW *newwin(
+             int nlines, int ncols,
+             int begin_y, int begin_x);
+       int delwin(WINDOW *win);
+       int mvwin(WINDOW *win, int y, int x);
+       WINDOW *subwin(WINDOW *orig,
+             int nlines, int ncols,
+             int begin_y, int begin_x);
+       WINDOW *derwin(WINDOW *orig,
+             int nlines, int ncols,
+             int begin_y, int begin_x);
+       int mvderwin(WINDOW *win, int par_y, int par_x);
+       WINDOW *dupwin(WINDOW *win);
+       void wsyncup(WINDOW *win);
+       int syncok(WINDOW *win, bool bf);
+       void wcursyncup(WINDOW *win);
+       void wsyncdown(WINDOW *win);

                    DESCRIPTION

                    newwin

                    -       Calling newwin creates and returns a pointer to a new window  with  the
+       Calling newwin creates and returns a pointer to a new window  with  the
        given  number  of lines and columns.  The upper left-hand corner of the
        window is at
-              line begin_y,
-              column begin_x
+              line begin_y,
+              column begin_x
 
-       If either nlines or ncols is zero, they default to
-              LINES - begin_y and
-              COLS - begin_x.
+       If either nlines or ncols is zero, they default to
+              LINES - begin_y and
+              COLS - begin_x.
 
-       A new full-screen window is created by calling newwin(0,0,0,0).
+       A new full-screen window is created by calling newwin(0,0,0,0).
 
        Regardless of the function  used  for  creating  a  new  window  (e.g.,
-       newwin, subwin, derwin, newpad), rather than a duplicate (with dupwin),
+       newwin, subwin, derwin, newpad), rather than a duplicate (with dupwin),
        all of the window modes are initialized to the default  values.   These
        functions set window modes after a window is created:
 
@@ -98,130 +98,130 @@

                    delwin

                    -       Calling delwin deletes the named window, freeing all memory  associated
+       Calling delwin deletes the named window, freeing all memory  associated
        with  it  (it does not actually erase the window's screen image).  Sub-
        windows must be deleted before the main window can be deleted.

                    mvwin

                    -       Calling mvwin moves the window so that the upper left-hand corner is at
-       position  (x,  y).   If  the  move would cause the window to be off the
+       Calling mvwin moves the window so that the upper left-hand corner is at
+       position  (x,  y).   If  the  move would cause the window to be off the
        screen, it is an error and the window is not moved.  Moving  subwindows
        is allowed, but should be avoided.

                    subwin

                    -       Calling  subwin  creates and returns a pointer to a new window with the
-       given number of lines, nlines, and columns, ncols.  The  window  is  at
-       position (begin_y, begin_x) on the screen.  The subwindow shares memory
-       with the window orig, so that changes made to one  window  will  affect
-       both  windows.  When using this routine, it is necessary to call touch-
-       win or touchline on orig before calling wrefresh on the subwindow.
+       Calling  subwin  creates and returns a pointer to a new window with the
+       given number of lines, nlines, and columns, ncols.  The  window  is  at
+       position (begin_y, begin_x) on the screen.  The subwindow shares memory
+       with the window orig, so that changes made to one  window  will  affect
+       both  windows.  When using this routine, it is necessary to call touch-
+       win or touchline on orig before calling wrefresh on the subwindow.

                    derwin

                    -       Calling derwin is the same as calling subwin, except that  begin_y  and
-       begin_x  are  relative to the origin of the window orig rather than the
+       Calling derwin is the same as calling subwin, except that  begin_y  and
+       begin_x  are  relative to the origin of the window orig rather than the
        screen.  There is no difference between the subwindows and the  derived
        windows.
 
-       Calling  mvderwin moves a derived window (or subwindow) inside its par-
+       Calling  mvderwin moves a derived window (or subwindow) inside its par-
        ent window.  The screen-relative  parameters  of  the  window  are  not
        changed.  This routine is used to display different parts of the parent
        window at the same physical position on the screen.

                    dupwin

                    -       Calling dupwin creates an exact duplicate of the window win.
+       Calling dupwin creates an exact duplicate of the window win.

                    wsyncup

                    -       Calling wsyncup touches all locations in  ancestors  of  win  that  are
-       changed  in  win.   If  syncok is called with second argument TRUE then
-       wsyncup is called automatically whenever there is a change in the  win-
+       Calling wsyncup touches all locations in  ancestors  of  win  that  are
+       changed  in  win.   If  syncok is called with second argument TRUE then
+       wsyncup is called automatically whenever there is a change in the  win-
        dow.

                    wsyncdown

                    -       The  wsyncdown  routine  touches  each  location  in  win that has been
-       touched in any of its ancestor windows.  This routine is called by wre-
-       fresh, so it should almost never be necessary to call it manually.
+       The  wsyncdown  routine  touches  each  location  in  win that has been
+       touched in any of its ancestor windows.  This routine is called by wre-
+       fresh, so it should almost never be necessary to call it manually.

                    wcursyncup

                    -       The  routine  wcursyncup updates the current cursor position of all the
+       The  routine  wcursyncup updates the current cursor position of all the
        ancestors of the window to reflect the current cursor position  of  the
        window.

                    RETURN VALUE

                    -       Routines that return an integer return the integer ERR upon failure and
-       OK (SVr4 only specifies "an integer value other than  ERR")  upon  suc-
+       Routines that return an integer return the integer ERR upon failure and
+       OK (SVr4 only specifies "an integer value other than  ERR")  upon  suc-
        cessful completion.
 
-       Routines that return pointers return NULL on error.
+       Routines that return pointers return NULL on error.
 
        X/Open defines no error conditions.  In this implementation
 
-       delwin
+       delwin
             returns  an  error if the window pointer is null, or if the window
             is the parent of another window.
 
-       derwin
+       derwin
             returns an error if the parent window pointer is null, or  if  any
             of  its  ordinates  or dimensions is negative, or if the resulting
             window does not fit inside the parent window.
 
-       dupwin
+       dupwin
             returns an error if the window pointer is null.
 
             This implementation also maintains a list of windows,  and  checks
-            that  the pointer passed to delwin is one that it created, return-
+            that  the pointer passed to delwin is one that it created, return-
             ing an error if it was not..
 
-       mvderwin
+       mvderwin
             returns an error if the window pointer is null, or if some part of
             the window would be placed off-screen.
 
-       mvwin
+       mvwin
             returns  an  error if the window pointer is null, or if the window
             is really a pad, or if some part of the  window  would  be  placed
             off-screen.
 
-       newwin
+       newwin
             will  fail if either of its beginning ordinates is negative, or if
             either the number of lines or columns is negative.
 
-       syncok
+       syncok
             returns an error if the window pointer is null.
 
-       subwin
+       subwin
             returns an error if the parent window pointer is null, or  if  any
             of  its  ordinates  or dimensions is negative, or if the resulting
             window does not fit inside the parent window.
 
        The functions which return a window pointer may also fail if  there  is
        insufficient  memory  for  its data structures.  Any of these functions
-       will fail if the screen has not been initialized, i.e., with initscr or
-       newterm.
+       will fail if the screen has not been initialized, i.e., with initscr or
+       newterm.

                    NOTES

                    -       If  many small changes are made to the window, the wsyncup option could
+       If  many small changes are made to the window, the wsyncup option could
        degrade performance.
 
-       Note that syncok may be a macro.
+       Note that syncok may be a macro.

                    BUGS

                    -       The subwindow functions (subwin, derwin, mvderwin, wsyncup,  wsyncdown,
-       wcursyncup,  syncok)  are flaky, incompletely implemented, and not well
+       The subwindow functions (subwin, derwin, mvderwin, wsyncup,  wsyncdown,
+       wcursyncup,  syncok)  are flaky, incompletely implemented, and not well
        tested.
 
-       The System V curses documentation is very unclear  about  what  wsyncup
-       and  wsyncdown  actually do.  It seems to imply that they are only sup-
+       The System V curses documentation is very unclear  about  what  wsyncup
+       and  wsyncdown  actually do.  It seems to imply that they are only sup-
        posed to touch exactly  those  lines  that  are  affected  by  ancestor
-       changes.  The language here, and the behavior of the curses implementa-
+       changes.  The language here, and the behavior of the curses implementa-
        tion, is patterned on the XPG4 curses standard.  The weaker  XPG4  spec
        may result in slower updates.
 
@@ -231,11 +231,11 @@

                    SEE ALSO

                    -       curses(3x), curs_refresh(3x), curs_touch(3x), curs_variables(3x)
+       curses(3X), curs_refresh(3X), curs_touch(3X), curs_variables(3X)
 
 
 
-                                                               curs_window(3x)
+                                                               curs_window(3X)
                      diff --git a/doc/html/man/default_colors.3x.html b/doc/html/man/default_colors.3x.html index bb525b37..a918b828 100644 --- a/doc/html/man/default_colors.3x.html +++ b/doc/html/man/default_colors.3x.html @@ -1,4 +1,4 @@ - -infocmp 1m +@INFOCMP@ 1M -

                      infocmp 1m

                      +

                      @INFOCMP@ 1M

                      -infocmp(1m)                                                        infocmp(1m)
+infocmp(1M)                                                        infocmp(1M)

                      NAME

                      -       infocmp - compare or print out terminfo descriptions
+       infocmp - compare or print out terminfo descriptions

                      SYNOPSIS

                      -       infocmp [-1CDEFGIKLTUVWcdegilnpqrtux]
-             [-v n] [-s d| i| l| c] [-Q n] [-R subset]
-             [-w width] [-A directory] [-B directory]
-             [termname...]
+       infocmp [-1CDEFGIKLTUVWcdegilnpqrtux]
+             [-v n] [-s d| i| l| c] [-Q n] [-R subset]
+             [-w width] [-A directory] [-B directory]
+             [termname...]

                      DESCRIPTION

                      -       infocmp  can  be  used  to  compare  a binary terminfo entry with other
-       terminfo entries, rewrite a terminfo description to take  advantage  of
-       the  use=  terminfo field, or print out a terminfo description from the
-       binary file (term) in a variety of formats.  In all cases, the  boolean
+       infocmp  can  be  used  to  compare  a binary terminfo entry with other
+       terminfo entries, rewrite a terminfo description to take  advantage  of
+       the  use=  terminfo field, or print out a terminfo description from the
+       binary file (term) in a variety of formats.  In all cases, the  boolean
        fields  will be printed first, followed by the numeric fields, followed
        by the string fields.

                      Default Options

                      -       If no options are specified and zero or one  termnames  are  specified,
-       the -I option will be assumed.  If more than one termname is specified,
-       the -d option will be assumed.
+       If no options are specified and zero or one  termnames  are  specified,
+       the -I option will be assumed.  If more than one termname is specified,
+       the -d option will be assumed.

                      Comparison Options [-d] [-c] [-n]

                      -       infocmp  compares  the  terminfo  description  of  the  first  terminal
-       termname  with  each  of  the descriptions given by the entries for the
-       other terminal's termnames.  If a capability is defined for only one of
+       infocmp  compares  the  terminfo  description  of  the  first  terminal
+       termname  with  each  of  the descriptions given by the entries for the
+       other terminal's termnames.  If a capability is defined for only one of
        the   terminals,  the  value  returned  depends  on  the  type  of  the
        capability:
 
-       o   F for missing boolean variables
+       o   F for missing boolean variables
 
-       o   NULL for missing integer or string variables
+       o   NULL for missing integer or string variables
 
-       Use the -q option to show the distinction between absent and  cancelled
+       Use the -q option to show the distinction between absent and  cancelled
        capabilities.
 
        These  options  produce a list which you can use to compare two or more
        terminal descriptions:
 
-       -d   produces a list of each capability that is different  between  two
+       -d   produces a list of each capability that is different  between  two
             entries.   Each  item  in  the list shows ":" after the capability
             name, followed by the capability values, separated by a comma.
 
-       -c   produces a list of each capability that is common between  two  or
+       -c   produces a list of each capability that is common between  two  or
             more entries.  Missing capabilities are ignored.  Each item in the
             list  shows  "="  after  the  capability  name,  followed  by  the
             capability value.
 
-            The  -u  option  provides  a  related  output,  showing  the first
+            The  -u  option  provides  a  related  output,  showing  the first
             terminal description rewritten to use the  second  as  a  building
             block via the "use=" clause.
 
-       -n   produces  a  list  of each capability that is in none of the given
+       -n   produces  a  list  of each capability that is in none of the given
             entries.  Each item in the list shows "!"  before  the  capability
             name.
 
-            Normally only the conventional capabilities are shown.  Use the -x
+            Normally only the conventional capabilities are shown.  Use the -x
             option to add the BSD-compatibility capabilities  (names  prefixed
             with "OT").
 
-            If  no  termnames are given, infocmp uses the environment variable
-            TERM for each of the termnames.
+            If  no  termnames are given, infocmp uses the environment variable
+            TERM for each of the termnames.

                      Source Listing Options [-I] [-L] [-C] [-r]

                      -       The -I, -L, and -C options will  produce  a  source  listing  for  each
+       The -I, -L, and -C options will  produce  a  source  listing  for  each
        terminal named.
 
-            -I   use the terminfo names
-            -L   use the long C variable name listed in <term.h>
-            -C   use the termcap names
-            -r   when using -C, put out all capabilities in termcap form
-            -K   modifies the -C option, improving BSD-compatibility.
+            -I   use the terminfo names
+            -L   use the long C variable name listed in <term.h>
+            -C   use the termcap names
+            -r   when using -C, put out all capabilities in termcap form
+            -K   modifies the -C option, improving BSD-compatibility.
 
-       If  no  termnames are given, the environment variable TERM will be used
+       If  no  termnames are given, the environment variable TERM will be used
        for the terminal name.
 
-       The source produced by the -C option may be used directly as a  termcap
-       entry,  but not all parameterized strings can be changed to the termcap
-       format.  infocmp will attempt to  convert  most  of  the  parameterized
+       The source produced by the -C option may be used directly as a  termcap
+       entry,  but not all parameterized strings can be changed to the termcap
+       format.  infocmp will attempt to  convert  most  of  the  parameterized
        information,  and  anything not converted will be plainly marked in the
        output and commented out.  These should be edited by hand.
 
-       For best results when converting to termcap format, you should use both
-       -C  and  -r.   Normally a termcap description is limited to 1023 bytes.
-       infocmp trims away less essential parts to make it  fit.   If  you  are
+       For best results when converting to termcap format, you should use both
+       -C  and  -r.   Normally a termcap description is limited to 1023 bytes.
+       infocmp trims away less essential parts to make it  fit.   If  you  are
        converting to one of the (rare) termcap implementations which accept an
-       unlimited size of termcap, you may want to add  the  -T  option.   More
+       unlimited size of termcap, you may want to add  the  -T  option.   More
        often  however,  you  must  help  the  termcap implementation, and trim
-       excess whitespace (use the -0 option for that).
+       excess whitespace (use the -0 option for that).
 
        All padding information for strings  will  be  collected  together  and
-       placed  at  the  beginning  of  the  string  where  termcap expects it.
+       placed  at  the  beginning  of  the  string  where  termcap expects it.
        Mandatory padding (padding information with a trailing "/") will become
        optional.
 
-       All  termcap  variables  no longer supported by terminfo, but which are
-       derivable from other terminfo  variables,  will  be  output.   Not  all
-       terminfo  capabilities  will  be translated; only those variables which
-       were part of termcap will normally be output.  Specifying the -r option
+       All  termcap  variables  no longer supported by terminfo, but which are
+       derivable from other terminfo  variables,  will  be  output.   Not  all
+       terminfo  capabilities  will  be translated; only those variables which
+       were part of termcap will normally be output.  Specifying the -r option
        will  take off this restriction, allowing all capabilities to be output
-       in termcap form.  Normally you would use both the -C  and  -r  options.
+       in termcap form.  Normally you would use both the -C  and  -r  options.
        The  actual  format  used  incorporates  some  improvements for escaped
        characters  from  terminfo  format.   For  a  stricter   BSD-compatible
-       translation, use the -K option rather than -C.
+       translation, use the -K option rather than -C.
 
        Note  that  because  padding  is  collected  to  the  beginning  of the
        capability, not all capabilities are output.  Mandatory padding is  not
-       supported.   Because  termcap  strings  are  not as flexible, it is not
-       always possible  to  convert  a  terminfo  string  capability  into  an
-       equivalent termcap format.  A subsequent conversion of the termcap file
-       back into terminfo format will not necessarily reproduce  the  original
-       terminfo source.
+       supported.   Because  termcap  strings  are  not as flexible, it is not
+       always possible  to  convert  a  terminfo  string  capability  into  an
+       equivalent termcap format.  A subsequent conversion of the termcap file
+       back into terminfo format will not necessarily reproduce  the  original
+       terminfo source.
 
-       Some  common  terminfo  parameter sequences, their termcap equivalents,
+       Some  common  terminfo  parameter sequences, their termcap equivalents,
        and some terminal types which commonly have such sequences, are:
 
-           terminfo                    termcap   Representative Terminals
+           terminfo                    termcap   Representative Terminals
            ---------------------------------------------------------------
-           %p1%c                       %.        adm
-           %p1%d                       %d        hp, ANSI standard, vt100
-           %p1%'x'%+%c                 %+x       concept
-           %i                          %iq       ANSI standard, vt100
-           %p1%?%'x'%>%t%p1%'y'%+%;    %>xy      concept
-           %p2 is printed before %p1   %r        hp
+           %p1%c                       %.        adm
+           %p1%d                       %d        hp, ANSI standard, vt100
+           %p1%'x'%+%c                 %+x       concept
+           %i                          %iq       ANSI standard, vt100
+           %p1%?%'x'%>%t%p1%'y'%+%;    %>xy      concept
+           %p2 is printed before %p1   %r        hp

                      Use= Option [-u]

                      -       The -u option produces a  terminfo  source  description  of  the  first
-       terminal  termname  which  is  relative  to the sum of the descriptions
-       given by the entries for the other terminals termnames.  It  does  this
-       by  analyzing  the differences between the first termname and the other
-       termnames and producing a description with use= fields  for  the  other
+       The -u option produces a  terminfo  source  description  of  the  first
+       terminal  termname  which  is  relative  to the sum of the descriptions
+       given by the entries for the other terminals termnames.  It  does  this
+       by  analyzing  the differences between the first termname and the other
+       termnames and producing a description with use= fields  for  the  other
        terminals.  In this manner, it is possible to retrofit generic terminfo
        entries into a terminal's description.  Or, if  two  similar  terminals
        exist, but were coded at different times or by different people so that
-       each description is a full description, using infocmp  will  show  what
+       each description is a full description, using infocmp  will  show  what
        can be done to change one description to be relative to the other.
 
        A capability will be printed with an at-sign (@) if it no longer exists
-       in the first termname, but one of the other termname entries contains a
+       in the first termname, but one of the other termname entries contains a
        value for it.  A capability's value will be printed if the value in the
-       first termname is not found in any of the other termname entries, or if
-       the  first of the other termname entries that has this capability gives
-       a different value for the capability than that in the first termname.
+       first termname is not found in any of the other termname entries, or if
+       the  first of the other termname entries that has this capability gives
+       a different value for the capability than that in the first termname.
 
-       The order of the other termname  entries  is  significant.   Since  the
-       terminfo  compiler  tic  does a left-to-right scan of the capabilities,
-       specifying two use= entries that contain differing entries for the same
+       The order of the other termname  entries  is  significant.   Since  the
+       terminfo  compiler  tic  does a left-to-right scan of the capabilities,
+       specifying two use= entries that contain differing entries for the same
        capabilities will produce different results depending on the order that
-       the entries are given in.  infocmp will flag any  such  inconsistencies
-       between the other termname entries as they are found.
+       the entries are given in.  infocmp will flag any  such  inconsistencies
+       between the other termname entries as they are found.
 
-       Alternatively, specifying a capability after a use= entry that contains
+       Alternatively, specifying a capability after a use= entry that contains
        that capability will cause the  second  specification  to  be  ignored.
-       Using  infocmp  to recreate a description can be a useful check to make
+       Using  infocmp  to recreate a description can be a useful check to make
        sure that everything was specified correctly  in  the  original  source
        description.
 
        Another  error  that  does not cause incorrect compiled files, but will
-       slow down the compilation time, is specifying extra  use=  fields  that
-       are superfluous.  infocmp will flag any other termname use= fields that
+       slow down the compilation time, is specifying extra  use=  fields  that
+       are superfluous.  infocmp will flag any other termname use= fields that
        were not needed.
 
-   Changing Databases [-A directory] [-B directory]
-       Like  other  ncurses  utilities,  infocmp  looks   for   the   terminal
-       descriptions   in  several  places.   You  can  use  the  TERMINFO  and
-       TERMINFO_DIRS environment variables to override the compiled-in default
-       list of places to search (see curses(3x) for details).
+   Changing Databases [-A directory] [-B directory]
+       Like  other  ncurses  utilities,  infocmp  looks   for   the   terminal
+       descriptions   in  several  places.   You  can  use  the  TERMINFO  and
+       TERMINFO_DIRS environment variables to override the compiled-in default
+       list of places to search (see curses(3X) for details).
 
-       You  can  also use the options -A and -B to override the list of places
+       You  can  also use the options -A and -B to override the list of places
        to search when comparing terminal descriptions:
 
-       o   The -A option sets the location for the first termname
+       o   The -A option sets the location for the first termname
 
-       o   The -B option sets the location for the other termnames.
+       o   The -B option sets the location for the other termnames.
 
        Using these options, it is  possible  to  compare  descriptions  for  a
        terminal  with  the  same name located in two different databases.  For
@@ -235,38 +235,38 @@

                      Other Options

                      -       -0   causes the fields to be printed on one line, without wrapping.
+       -0   causes the fields to be printed on one line, without wrapping.
 
-       -1   causes the fields to be printed out one to a line.  Otherwise, the
+       -1   causes the fields to be printed out one to a line.  Otherwise, the
             fields will be printed several to a line to a maximum width of  60
             characters.
 
-       -a   tells  infocmp  to  retain  commented-out capabilities rather than
+       -a   tells  infocmp  to  retain  commented-out capabilities rather than
             discarding them.  Capabilities are  commented  by  prefixing  them
             with a period.
 
-       -D   tells infocmp to print the database locations that it knows about,
+       -D   tells infocmp to print the database locations that it knows about,
             and exit.
 
-       -E   Dump the capabilities of the given terminal as tables,  needed  in
+       -E   Dump the capabilities of the given terminal as tables,  needed  in
             the   C   initializer  for  a  TERMTYPE  structure  (the  terminal
-            capability structure in the <term.h>).  This option is useful  for
+            capability structure in the <term.h>).  This option is useful  for
             preparing  versions  of  the  curses library hardwired for a given
             terminal type.  The tables are all declared static, and are  named
             according  to  the type and the name of the corresponding terminal
             entry.
 
-            Before ncurses 5.0, the split between the -e and  -E  options  was
+            Before ncurses 5.0, the split between the -e and  -E  options  was
             not  needed;  but  support  for extended names required making the
             arrays  of  terminal  capabilities  separate  from  the   TERMTYPE
             structure.
 
-       -e   Dump the capabilities of the given terminal as a C initializer for
+       -e   Dump the capabilities of the given terminal as a C initializer for
             a TERMTYPE structure (the terminal  capability  structure  in  the
-            <term.h>).   This  option  is useful for preparing versions of the
+            <term.h>).   This  option  is useful for preparing versions of the
             curses library hardwired for a given terminal type.
 
-       -F   compare terminfo files.  This assumes that two following arguments
+       -F   compare terminfo files.  This assumes that two following arguments
             are  filenames.   The  files  are  searched  for  pairwise matches
             between entries, with two entries considered to match  if  any  of
             their  names  do.   The  report  printed  to standard output lists
@@ -274,21 +274,21 @@
             than  one match.  For entries with exactly one match it includes a
             difference report.  Normally, to reduce the volume of the  report,
             use  references  are  not resolved before looking for differences,
-            but resolution can be forced by also specifying -r.
+            but resolution can be forced by also specifying -r.
 
-       -f   Display complex terminfo strings which contain  if/then/else/endif
+       -f   Display complex terminfo strings which contain  if/then/else/endif
             expressions indented for readability.
 
-       -G   Display  constant  literals  in  decimal  form  rather  than their
+       -G   Display  constant  literals  in  decimal  form  rather  than their
             character equivalents.
 
-       -g   Display constant character literals in  quoted  form  rather  than
+       -g   Display constant character literals in  quoted  form  rather  than
             their decimal equivalents.
 
-       -i   Analyze  the  initialization (is1, is2, is3), and reset (rs1, rs2,
-            rs3),  strings  in  the  entry,  as  well  as   those   used   for
-            starting/stopping  cursor-positioning  mode (smcup, rmcup) as well
-            as starting/stopping keymap mode (smkx, rmkx).
+       -i   Analyze  the  initialization (is1, is2, is3), and reset (rs1, rs2,
+            rs3),  strings  in  the  entry,  as  well  as   those   used   for
+            starting/stopping  cursor-positioning  mode (smcup, rmcup) as well
+            as starting/stopping keymap mode (smkx, rmkx).
 
             For each string, the code tries to  analyze  it  into  actions  in
             terms  of  the  other capabilities in the entry, certain X3.64/ISO
@@ -344,18 +344,18 @@
             UNDERLINE, BLINK, and REVERSE.  All but  NORMAL  may  be  prefixed
             with
 
-            o   "+" (turn on) or
+            o   "+" (turn on) or
 
-            o   "-" (turn off).
+            o   "-" (turn off).
 
             An  SGR0  designates  an  empty  highlight sequence (equivalent to
             {SGR:NORMAL}).
 
-       -l   Set output format to terminfo.
+       -l   Set output format to terminfo.
 
-       -p   Ignore padding specifications when comparing strings.
+       -p   Ignore padding specifications when comparing strings.
 
-       -Q n Rather than show source  in  terminfo  (text)  format,  print  the
+       -Q n Rather than show source  in  terminfo  (text)  format,  print  the
             compiled  (binary) format in hexadecimal or base64 form, depending
             on the option's value:
 
@@ -366,92 +366,92 @@
                3  hexadecimal and base64
 
             For example, this prints the compiled terminfo value as  a  string
-            which could be assigned to the TERMINFO environment variable:
+            which could be assigned to the TERMINFO environment variable:
 
                 infocmp -0 -q -Q2
 
-       -q   This makes the output a little shorter:
+       -q   This makes the output a little shorter:
 
-            o   Make  the  comparison listing shorter by omitting subheadings,
+            o   Make  the  comparison listing shorter by omitting subheadings,
                 and using "-" for absent capabilities, "@" for canceled rather
                 than "NULL".
 
-            o   However,   show   differences  between  absent  and  cancelled
+            o   However,   show   differences  between  absent  and  cancelled
                 capabilities.
 
-            o   Omit the "Reconstructed from" comment for source listings.
+            o   Omit the "Reconstructed from" comment for source listings.
 
-       -Rsubset
+       -Rsubset
             Restrict output to a given subset.  This option is  for  use  with
             archaic  versions of terminfo like those on SVr1, Ultrix, or HP/UX
             that do not support the full set of SVR4/XSI Curses terminfo;  and
             variants  such  as AIX that have their own extensions incompatible
             with SVr4/XSI.
 
-            o   Available terminfo subsets are  "SVr1",  "Ultrix",  "HP",  and
-                "AIX"; see terminfo(5) for details.
+            o   Available terminfo subsets are  "SVr1",  "Ultrix",  "HP",  and
+                "AIX"; see terminfo(5) for details.
 
-            o   You  can  also  choose  the  subset  "BSD"  which selects only
+            o   You  can  also  choose  the  subset  "BSD"  which selects only
                 capabilities with termcap equivalents  recognized  by  4.4BSD.
-                The -C option sets the "BSD" subset as a side-effect.
+                The -C option sets the "BSD" subset as a side-effect.
 
-            o   If  you  select  any  other value for -R, it is the same as no
-                subset, i.e.,  all  capabilities  are  used.   The  -I  option
+            o   If  you  select  any  other value for -R, it is the same as no
+                subset, i.e.,  all  capabilities  are  used.   The  -I  option
                 likewise selects no subset as a side-effect.
 
-       -s [d|i|l|c]
-            The  -s  option sorts the fields within each type according to the
+       -s [d|i|l|c]
+            The  -s  option sorts the fields within each type according to the
             argument below:
 
-            d    leave fields in  the  order  that  they  are  stored  in  the
-                 terminfo database.
+            d    leave fields in  the  order  that  they  are  stored  in  the
+                 terminfo database.
 
-            i    sort by terminfo name.
+            i    sort by terminfo name.
 
-            l    sort by the long C variable name.
+            l    sort by the long C variable name.
 
-            c    sort by the termcap name.
+            c    sort by the termcap name.
 
-            If  the  -s  option  is  not given, the fields printed out will be
-            sorted alphabetically by  the  terminfo  name  within  each  type,
-            except  in  the  case of the -C or the -L options, which cause the
-            sorting to be done by the termcap name  or  the  long  C  variable
+            If  the  -s  option  is  not given, the fields printed out will be
+            sorted alphabetically by  the  terminfo  name  within  each  type,
+            except  in  the  case of the -C or the -L options, which cause the
+            sorting to be done by the termcap name  or  the  long  C  variable
             name, respectively.
 
-       -T   eliminates  size-restrictions  on  the  generated  text.   This is
+       -T   eliminates  size-restrictions  on  the  generated  text.   This is
             mainly  useful  for  testing  and  analysis,  since  the  compiled
             descriptions  are  limited  (e.g.,  1023  for  termcap,  4096  for
             terminfo).
 
-       -t   tells tic to discard commented-out  capabilities.   Normally  when
+       -t   tells tic to discard commented-out  capabilities.   Normally  when
             translating  from terminfo to termcap, untranslatable capabilities
             are commented-out.
 
-       -U   tells infocmp to not  post-process  the  data  after  parsing  the
+       -U   tells infocmp to not  post-process  the  data  after  parsing  the
             source  file.   This  feature  helps  when  comparing  the  actual
             contents of two source files, since  it  excludes  the  inferences
-            that infocmp makes to fill in missing data.
+            that infocmp makes to fill in missing data.
 
-       -V   reports the version of ncurses which was used in this program, and
+       -V   reports the version of ncurses which was used in this program, and
             exits.
 
-       -v n prints out tracing information on standard error  as  the  program
+       -v n prints out tracing information on standard error  as  the  program
             runs.
 
-            The  optional  parameter  n  is  a number from 1 to 10, inclusive,
+            The  optional  parameter  n  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.
 
-       -W   By itself, the -w  option  will  not  force  long  strings  to  be
-            wrapped.  Use the -W option to do this.
+       -W   By itself, the -w  option  will  not  force  long  strings  to  be
+            wrapped.  Use the -W option to do this.
 
-       -w width
-            changes the output to width characters.
+       -w width
+            changes the output to width characters.
 
-       -x   print information for user-defined capabilities (see user_caps(5).
+       -x   print information for user-defined capabilities (see user_caps(5).
             These are extensions to  the  terminfo  repertoire  which  can  be
-            loaded using the -x option of tic.
+            loaded using the -x option of tic.

                      FILES

                      @@ -461,60 +461,60 @@

                      HISTORY

                              Although  System  V  Release  2  provided a terminfo library, it had no
        documented tool for decompiling the terminal descriptions.  Tony Hansen
-       (AT&T) wrote the first infocmp in early 1984, for System V Release 3.
+       (AT&T) wrote the first infocmp in early 1984, for System V Release 3.
 
        Eric  Raymond  used  the  AT&T  documentation  in  1995  to  provide an
-       equivalent infocmp for ncurses.   In  addition,  he  added  a  few  new
+       equivalent infocmp for ncurses.   In  addition,  he  added  a  few  new
        features such as:
 
-       o   the   -e   option,   to  support  fallback  (compiled-in)  terminal
+       o   the   -e   option,   to  support  fallback  (compiled-in)  terminal
            descriptions
 
-       o   the -i option, to help with analysis
+       o   the -i option, to help with analysis
 
-       Later, Thomas Dickey added the -x (user-defined  capabilities)  option,
-       and  the  -E  option  to  support  fallback  entries  with user-defined
+       Later, Thomas Dickey added the -x (user-defined  capabilities)  option,
+       and  the  -E  option  to  support  fallback  entries  with user-defined
        capabilities.
 
-       For a complete list, see the EXTENSIONS section.
+       For a complete list, see the EXTENSIONS section.
 
-       In 2010, Roy Marples provided an infocmp program  for  NetBSD.   It  is
+       In 2010, Roy Marples provided an infocmp program  for  NetBSD.   It  is
        less  capable  than  the  SVr4  or ncurses versions (e.g., it lacks the
-       sorting options documented in X/Open), but does include the  -x  option
+       sorting options documented in X/Open), but does include the  -x  option
        adapted from ncurses.

                      PORTABILITY

                      -       X/Open  Curses,  Issue  7 (2009) provides a description of infocmp.  It
+       X/Open  Curses,  Issue  7 (2009) provides a description of infocmp.  It
        does not mention the options used for converting to termcap format.

                      EXTENSIONS

                      -       The -0, -1, -E, -F, -G, -Q, -R, -T, -V, -a, -e, -f, -g, -i, -l, -p,  -q
-       and -t options are not supported in SVr4 curses.
+       The -0, -1, -E, -F, -G, -Q, -R, -T, -V, -a, -e, -f, -g, -i, -l, -p,  -q
+       and -t options are not supported in SVr4 curses.
 
        SVr4   infocmp  does  not  distinguish  between  absent  and  cancelled
-       capabilities.  Also, it shows missing integer capabilities as  -1  (the
+       capabilities.  Also, it shows missing integer capabilities as  -1  (the
        internal   value   used   to   represent   missing   integers).    This
        implementation shows those as  "NULL",  for  consistency  with  missing
        strings.
 
-       The  -r  option's  notion of "termcap" capabilities is System V Release
+       The  -r  option's  notion of "termcap" capabilities is System V Release
        4's.  Actual BSD curses versions will have a more restricted  set.   To
-       see only the 4.4BSD set, use -r -RBSD.
+       see only the 4.4BSD set, use -r -RBSD.

                      BUGS

                      -       The -F option of infocmp(1m) should be a toe(1m) mode.
+       The -F option of infocmp(1M) should be a toe(1M) mode.

                      SEE ALSO

                      -       captoinfo(1m),    infotocap(1m),    tic(1m),    toe(1m),    curses(3x),
-       terminfo(5).  user_caps(5).
+       captoinfo(1M),    infotocap(1M),    tic(1M),    toe(1M),    curses(3X),
+       terminfo(5).  user_caps(5).
 
        https://invisible-island.net/ncurses/tctest.html
 
-       This describes ncurses version 6.2 (patch 20210522).
+       This describes ncurses version 6.2 (patch 20210612).

                      AUTHOR

                      @@ -523,7 +523,7 @@
 
 
 
-                                                                   infocmp(1m)
+                                                                   infocmp(1M)
                        diff --git a/doc/html/man/infotocap.1m.html b/doc/html/man/infotocap.1m.html index c2d1a397..e25458e0 100644 --- a/doc/html/man/infotocap.1m.html +++ b/doc/html/man/infotocap.1m.html @@ -1,4 +1,4 @@ - @@ -41,7 +41,7 @@

                        ncurses6-config 1

                        -ncurses6-config(1)          General Commands Manual         ncurses6-config(1)
+ncurses6-config(1)          General Commands Manual         ncurses6-config(1)
 
 
 
@@ -51,7 +51,7 @@

                        SYNOPSIS

                        -       ncurses6-config [options]
+       ncurses6-config [options]

                        DESCRIPTION

                        @@ -60,64 +60,64 @@

                        OPTIONS

                        -       --prefix
+       --prefix
               echos the package-prefix of ncurses
 
-       --exec-prefix
+       --exec-prefix
               echos the executable-prefix of ncurses
 
-       --cflags
+       --cflags
               echos the C compiler flags needed to compile with ncurses
 
-       --libs echos the libraries needed to link with ncurses
+       --libs echos the libraries needed to link with ncurses
 
-       --version
+       --version
               echos the release+patchdate version of ncurses
 
-       --abi-version
+       --abi-version
               echos the ABI version of ncurses
 
-       --mouse-version
+       --mouse-version
               echos the mouse-interface version of ncurses
 
-       --bindir
+       --bindir
               echos the directory containing ncurses programs
 
-       --datadir
+       --datadir
               echos the directory containing ncurses data
 
-       --includedir
+       --includedir
               echos the directory containing ncurses header files
 
-       --libdir
+       --libdir
               echos the directory containing ncurses libraries
 
-       --mandir
+       --mandir
               echos the directory containing ncurses manpages
 
-       --terminfo
+       --terminfo
               echos the $TERMINFO terminfo database path, e.g.,
               /usr/share/terminfo
 
-       --terminfo-dirs
+       --terminfo-dirs
               echos the $TERMINFO_DIRS directory list, e.g.,
               /usr/share/terminfo
 
-       --termpath
+       --termpath
               echos the $TERMPATH termcap list,  if  support  for  termcap  is
               configured.
 
-       --help prints this message
+       --help prints this message

                        SEE ALSO

                        -       curses(3x)
+       curses(3X)
 
-       This describes ncurses version 6.2 (patch 20210522).
+       This describes ncurses version 6.2 (patch 20210612).
 
 
 
-                                                            ncurses6-config(1)
+                                                            ncurses6-config(1)
                          diff --git a/doc/html/man/new_pair.3x.html b/doc/html/man/new_pair.3x.html index 28c9988c..6702b902 100644 --- a/doc/html/man/new_pair.3x.html +++ b/doc/html/man/new_pair.3x.html @@ -1,6 +1,6 @@ - -new_pair 3x +new_pair 3X -

                          new_pair 3x

                          +

                          new_pair 3X

                          -new_pair(3x)                                                      new_pair(3x)
+new_pair(3X)                                                      new_pair(3X)

                          NAME

                          -       alloc_pair, find_pair, free_pair - new curses color-pair functions
+       alloc_pair, find_pair, free_pair - new curses color-pair functions

                          SYNOPSIS

                          -       #include <curses.h>
+       #include <curses.h>
 
-       int alloc_pair(int fg, int bg);
-       int find_pair(int fg, int bg);
-       int free_pair(int pair);
+       int alloc_pair(int fg, int bg);
+       int find_pair(int fg, int bg);
+       int free_pair(int pair);

                          DESCRIPTION

                          @@ -68,28 +68,28 @@
        The number of colors may be related to the  number  of  possible  color
        pairs for a given terminal, or it may not:
 
-       o   While  almost  all  terminals  allow  setting  the color attributes
+       o   While  almost  all  terminals  allow  setting  the color attributes
            independently, it is unlikely that  your  terminal  allows  you  to
            modify  the  attributes of a given character cell without rewriting
            it.  That is, the foreground and background colors are applied as a
            pair.
 
-       o   Color  pairs  are  the  curses  library's  way  of managing a color
+       o   Color  pairs  are  the  curses  library's  way  of managing a color
            palette on a terminal.  If the library does not keep track  of  the
-           combinations of colors which are displayed, it will be inefficient.
+           combinations of colors which are displayed, it will be inefficient.
 
-       o   For   simple  terminal  emulators  with  only  a  few  dozen  color
+       o   For   simple  terminal  emulators  with  only  a  few  dozen  color
            combinations, it  is  convenient  to  use  the  maximum  number  of
            combinations as the limit on color pairs:
 
-               COLORS * COLORS
+               COLORS * COLORS
 
-       o   Terminals  which support default colors distinct from "ANSI colors"
+       o   Terminals  which support default colors distinct from "ANSI colors"
            add to the possible combinations, producing this total:
 
-               ( COLORS + 1 ) * ( COLORS + 1 )
+               ( COLORS + 1 ) * ( COLORS + 1 )
 
-       o   An application might use up to a few dozen color pairs to implement
+       o   An application might use up to a few dozen color pairs to implement
            a predefined color scheme.
 
            Beyond  that lies in the realm of programs using the foreground and
@@ -105,28 +105,28 @@

                          alloc_pair

                          -       The  alloc_pair  function  accepts  parameters   for   foreground   and
+       The  alloc_pair  function  accepts  parameters   for   foreground   and
        background  color,  and  checks  if  that  color combination is already
        associated with a color pair.
 
-       o   If the combination already exists, alloc_pair returns the  existing
+       o   If the combination already exists, alloc_pair returns the  existing
            pair.
 
-       o   If the combination does not exist, alloc_pair allocates a new color
+       o   If the combination does not exist, alloc_pair allocates a new color
            pair and returns that.
 
-       o   If the table  fills  up,  alloc_pair  discards  the  least-recently
-           allocated entry using free_pair and allocates a new color pair.
+       o   If the table  fills  up,  alloc_pair  discards  the  least-recently
+           allocated entry using free_pair and allocates a new color pair.
 
        All  of  the  color  pairs are allocated from a table of possible color
-       pairs.  The size of the table  is  determined  by  the  terminfo  pairs
-       capability.   The  table  is  shared with init_pair; in fact alloc_pair
-       calls init_pair after updating the ncurses library's fast index to  the
+       pairs.  The size of the table  is  determined  by  the  terminfo  pairs
+       capability.   The  table  is  shared with init_pair; in fact alloc_pair
+       calls init_pair after updating the ncurses library's fast index to  the
        colors versus color pairs.

                          find_pair

                          -       The find_pair function accepts parameters for foreground and background
+       The find_pair function accepts parameters for foreground and background
        color, and checks if that color combination is already associated  with
        a  color  pair,  returning  the  pair  number if it has been allocated.
        Otherwise it returns -1.
@@ -137,15 +137,15 @@

                          RETURN VALUE

                          -       The alloc_pair function returns a color pair  number  in  the  range  1
-       through  COLOR_PAIRS-1, unless it encounters an error updating its fast
+       The alloc_pair function returns a color pair  number  in  the  range  1
+       through  COLOR_PAIRS-1, unless it encounters an error updating its fast
        index to the color pair values, preventing it from allocating  a  color
        pair.  In that case, it returns -1.
 
-       The  find_pair  function returns a color pair number if the given color
+       The  find_pair  function returns a color pair number if the given color
        combination has been associated with a color pair, or -1 if not.
 
-       Likewise, free_pair returns OK unless it encounters an  error  updating
+       Likewise, free_pair returns OK unless it encounters an  error  updating
        the fast index or if no such color pair is in use.
 
 
@@ -156,7 +156,7 @@

                          SEE ALSO

                          -       curs_color(3x).
+       curs_color(3X).

                          AUTHOR

                          @@ -164,7 +164,7 @@
 
 
 
-                                                                  new_pair(3x)
+                                                                  new_pair(3X)
                            diff --git a/doc/html/man/panel.3x.html b/doc/html/man/panel.3x.html index f369f104..0ce53c54 100644 --- a/doc/html/man/panel.3x.html +++ b/doc/html/man/panel.3x.html @@ -1,4 +1,4 @@ - @@ -41,7 +41,7 @@

                            scr_dump 5

                            -scr_dump(5)                   File Formats Manual                  scr_dump(5)
+scr_dump(5)                   File Formats Manual                  scr_dump(5)
 
 
 
@@ -51,25 +51,25 @@

                            SYNOPSIS

                            -       scr_dump
+       scr_dump

                            DESCRIPTION

                                    The  curses library provides applications with the ability to write the
-       contents of a window to an external file using scr_dump or putwin,  and
-       read it back using scr_restore or getwin.
+       contents of a window to an external file using scr_dump or putwin,  and
+       read it back using scr_restore or getwin.
 
-       The  putwin  and  getwin  functions  do  the  work;  while scr_dump and
-       scr_restore conveniently save  and  restore  the  whole  screen,  i.e.,
-       stdscr.
+       The  putwin  and  getwin  functions  do  the  work;  while scr_dump and
+       scr_restore conveniently save  and  restore  the  whole  screen,  i.e.,
+       stdscr.

                            ncurses6

                                    A  longstanding implementation of screen-dump was revised with ncurses6
        to remedy problems with the earlier approach:
 
-       o   A "magic number" is written to the  beginning  of  the  dump  file,
-           allowing  applications  (such  as file(1)) to recognize curses dump
+       o   A "magic number" is written to the  beginning  of  the  dump  file,
+           allowing  applications  (such  as file(1)) to recognize curses dump
            files.
 
            Because ncurses6 uses a new  format,  that  requires  a  new  magic
@@ -82,7 +82,7 @@
 
                0x88888888 (octal "\210\210\210\210")
 
-           This is the pattern  submitted  to  the  maintainers  of  the  file
+           This is the pattern  submitted  to  the  maintainers  of  the  file
            program:
 
                #
@@ -93,21 +93,21 @@
                0    string    \210\210\210\210ncurses    ncurses6 screen image
                #
 
-       o   The screen dumps are written in textual form, so that internal data
+       o   The screen dumps are written in textual form, so that internal data
            sizes are not directly related to the dump-format, and enabling the
            library  to  read  dumps  from  either  narrow-  or wide-character-
            configurations.
 
-           The  narrow  library  configuration  holds  characters  and   video
-           attributes  in  a  32-bit  chtype, while the wide-character library
-           stores this information in the cchar_t  structure,  which  is  much
+           The  narrow  library  configuration  holds  characters  and   video
+           attributes  in  a  32-bit  chtype, while the wide-character library
+           stores this information in the cchar_t  structure,  which  is  much
            larger than 32-bits.
 
-       o   It  is  possible  to  read  a  screen  dump  into a terminal with a
+       o   It  is  possible  to  read  a  screen  dump  into a terminal with a
            different screen-size, because the library truncates or  fills  the
            screen as necessary.
 
-       o   The ncurses6 getwin reads the legacy screen dumps from ncurses5.
+       o   The ncurses6 getwin reads the legacy screen dumps from ncurses5.

                            ncurses5 (legacy)

                            @@ -115,13 +115,13 @@
        were fixes and improvements in succeeding years, the basic  scheme  was
        unchanged:
 
-       o   The WINDOW structure was written in binary form.
+       o   The WINDOW structure was written in binary form.
 
-       o   The WINDOW structure refers to lines of data, which were written as
-           an array of binary data following the WINDOW.
+       o   The WINDOW structure refers to lines of data, which were written as
+           an array of binary data following the WINDOW.
 
-       o   When getwin restored the window, it would  keep  track  of  offsets
-           into  the  array of line-data and adjust the WINDOW structure which
+       o   When getwin restored the window, it would  keep  track  of  offsets
+           into  the  array of line-data and adjust the WINDOW structure which
            was read back into memory.
 
        This is similar to Unix SystemV, but does not write a "magic number" to
@@ -129,45 +129,45 @@

                            PORTABILITY

                            -       There  is  no  standard  format for putwin.  This section gives a brief
+       There  is  no  standard  format for putwin.  This section gives a brief
        description of the existing formats.

                            X/Open Curses

                            -       Refer to X/Open Curses, Issue 7 (2009).
+       Refer to X/Open Curses, Issue 7 (2009).
 
-       X/Open's documentation for enhanced curses says only:
+       X/Open's documentation for enhanced curses says only:
 
-          The getwin( ) function reads window-related data stored in the  file
-          by  putwin( ).   The  function  then  creates  and initializes a new
+          The getwin( ) function reads window-related data stored in the  file
+          by  putwin( ).   The  function  then  creates  and initializes a new
           window using that data.
 
-          The putwin( ) function writes all data associated with win into  the
-          stdio  stream  to  which  filep points, using an unspecified format.
-          This information can be retrieved later using getwin( ).
+          The putwin( ) function writes all data associated with win into  the
+          stdio  stream  to  which  filep points, using an unspecified format.
+          This information can be retrieved later using getwin( ).
 
        In the mid-1990s when the X/Open Curses  document  was  written,  there
        were  still  systems  using older, less capable curses libraries (aside
        from the BSD curses library which was not relevant to X/Open because it
-       did not meet the criteria for base curses).  The document explained the
+       did not meet the criteria for base curses).  The document explained the
        term "enhanced" as follows:
 
-          o   Shading is used to identify  X/Open  Enhanced  Curses  material,
+          o   Shading is used to identify  X/Open  Enhanced  Curses  material,
               relating to interfaces included to provide enhanced capabilities
               for applications originally written to be  compiled  on  systems
               based  on  the  UNIX  operating system.  Therefore, the features
-              described may not be present on systems that conform to XPG4  or
-              to  earlier  XPG  releases.   The  relevant  reference pages may
+              described may not be present on systems that conform to XPG4  or
+              to  earlier  XPG  releases.   The  relevant  reference pages may
               provide additional or more specific portability  warnings  about
               use of the material.
 
-       In  the foregoing, emphasis was added to unspecified format and to XPG4
-       or to earlier XPG releases, for clarity.
+       In  the foregoing, emphasis was added to unspecified format and to XPG4
+       or to earlier XPG releases, for clarity.

                            Unix SystemV

                                    Unix SystemV curses identified the file  format  by  writing  a  "magic
-       number" at the beginning of the dump.  The WINDOW data and the lines of
+       number" at the beginning of the dump.  The WINDOW data and the lines of
        text follow, all in binary form.
 
        The Solaris curses source has these definitions:
@@ -193,23 +193,23 @@
 
             01 35
 
-       After  the magic number, the WINDOW structure and line-data are written
+       After  the magic number, the WINDOW structure and line-data are written
        in binary format.  While the magic number used by the Unix systems  can
-       be seen using od(1), none of the Unix systems documents the format used
+       be seen using od(1), none of the Unix systems documents the format used
        for screen-dumps.
 
        The Unix systems  do  not  use  identical  formats.   While  collecting
-       information  for  for  this  manual  page,  the savescreen test-program
+       information  for  for  this  manual  page,  the savescreen test-program
        produced dumps of different size (all  on  64-bit  hardware,  on  40x80
        screens):
 
-       o   AIX (51817 bytes)
+       o   AIX (51817 bytes)
 
-       o   HPUX (90093 bytes)
+       o   HPUX (90093 bytes)
 
-       o   Solaris 10 (13273 bytes)
+       o   Solaris 10 (13273 bytes)
 
-       o   ncurses5 (12888 bytes)
+       o   ncurses5 (12888 bytes)

                            Solaris

                            @@ -217,12 +217,12 @@
        SVr4 curses.  This is odd since Solaris was the first operating  system
        to pass the SVr4 guidelines.  Solaris has two versions of curses:
 
-       o   The default curses library uses the SVr3 magic number.
+       o   The default curses library uses the SVr3 magic number.
 
-       o   There  is  an  alternate  curses library in /usr/xpg4.  This uses a
+       o   There  is  an  alternate  curses library in /usr/xpg4.  This uses a
            textual format with no magic number.
 
-           According to the copyright notice, the xpg4 Solaris curses  library
+           According to the copyright notice, the xpg4 Solaris curses  library
            was developed by MKS (Mortice Kern Systems) from 1990 to 1995.
 
            Like  ncurses6,  there  is  a  file-header with parameters.  Unlike
@@ -233,7 +233,7 @@

                            PDCurses

                                    PDCurses added support for screen dumps in version  2.7  (2005).   Like
-       Unix  SystemV  and  ncurses5, it writes the WINDOW structure in binary,
+       Unix  SystemV  and  ncurses5, it writes the WINDOW structure in binary,
        but begins the file with its three-byte identifier "PDC", followed by a
        one-byte version, e.g.,
 
@@ -241,21 +241,21 @@

                            NetBSD

                            -       As  of  April  2017,  NetBSD  curses  does  not  support  scr_dump  and
-       scr_restore (or scr_init, scr_set), although it has putwin and getwin.
+       As  of  April  2017,  NetBSD  curses  does  not  support  scr_dump  and
+       scr_restore (or scr_init, scr_set), although it has putwin and getwin.
 
-       Like ncurses5, NetBSD putwin does not identify its dumps with a  useful
+       Like ncurses5, NetBSD putwin does not identify its dumps with a  useful
        magic number.  It writes
 
-       o   the curses shared library major and minor versions as the first two
+       o   the curses shared library major and minor versions as the first two
            bytes (e.g., 7 and 1),
 
-       o   followed by a binary dump of the WINDOW,
+       o   followed by a binary dump of the WINDOW,
 
-       o   some data for wide-characters referenced by the  WINDOW  structure,
+       o   some data for wide-characters referenced by the  WINDOW  structure,
            and
 
-       o   finally, lines as done by other implementations.
+       o   finally, lines as done by other implementations.

                            EXAMPLE

                            @@ -273,13 +273,13 @@
                start_color();
                init_pair(1, COLOR_WHITE, COLOR_BLUE);
                init_pair(2, COLOR_RED, COLOR_BLACK);
-               bkgd(COLOR_PAIR(1));
+               bkgd(COLOR_PAIR(1));
                move(4, 5);
                attron(A_BOLD);
                addstr("Hello");
                move(5, 5);
                attroff(A_BOLD);
-               attrset(A_REVERSE | COLOR_PAIR(2));
+               attrset(A_REVERSE | COLOR_PAIR(2));
                addstr("World!");
                refresh();
                scr_dump("foo.out");
@@ -315,18 +315,18 @@
        The first four octal escapes are actually nonprinting characters, while
        the remainder of the file is printable text.  You may notice:
 
-       o   The actual color pair values are not written to the file.
+       o   The actual color pair values are not written to the file.
 
-       o   All  characters  are  shown  in  printable form; spaces are "\s" to
+       o   All  characters  are  shown  in  printable form; spaces are "\s" to
            ensure they are not overlooked.
 
-       o   Attributes are written in escaped curly  braces,  e.g.,  "\{BOLD}",
+       o   Attributes are written in escaped curly  braces,  e.g.,  "\{BOLD}",
            and may include a color-pair (C1 or C2 in this example).
 
-       o   The  parameters  in  the  header  are  written out only if they are
+       o   The  parameters  in  the  header  are  written out only if they are
            nonzero.  When reading back, order does not matter.
 
-       Running the same program with Solaris xpg4 curses gives this dump:
+       Running the same program with Solaris xpg4 curses gives this dump:
 
            MAX=10,20
            BEG=0,0
@@ -362,8 +362,8 @@
            9,19,0,0,
            CUR=11,5
 
-       Solaris getwin requires that all parameters are  present,  and  in  the
-       same  order.  The xpg4 curses library does not know about the bce (back
+       Solaris getwin requires that all parameters are  present,  and  in  the
+       same  order.  The xpg4 curses library does not know about the bce (back
        color erase) capability, and does not color the window background.
 
        On the other  hand,  the  SVr4  curses  library  does  know  about  the
@@ -395,7 +395,7 @@

                            SEE ALSO

                            -       curs_scr_dump(3x), curs_util(3x).
+       curs_scr_dump(3X), curs_util(3X).

                            AUTHORS

                            @@ -407,7 +407,7 @@
 
 
 
-                                                                   scr_dump(5)
+                                                                   scr_dump(5)
                              diff --git a/doc/html/man/tabs.1.html b/doc/html/man/tabs.1.html index 7a824d95..e8c8e700 100644 --- a/doc/html/man/tabs.1.html +++ b/doc/html/man/tabs.1.html @@ -1,4 +1,4 @@ - -tic 1m +@TIC@ 1M -

                              tic 1m

                              +

                              @TIC@ 1M

                              -tic(1m)                                                                tic(1m)
+tic(1M)                                                                tic(1M)

                              NAME

                              -       tic - the terminfo entry-description compiler
+       tic - the terminfo entry-description compiler

                              SYNOPSIS

                              -       tic  [-01CDGIKLNTUVWacfgqrstx]  [-e names] [-o dir] [-Q[n]] [-R subset]
-       [-v[n]] [-w[n]] file
+       tic  [-01CDGIKLNTUVWacfgqrstx]  [-e names] [-o dir] [-Q[n]] [-R subset]
+       [-v[n]] [-w[n]] file

                              DESCRIPTION

                              -       The tic command translates a terminfo  file  from  source  format  into
+       The tic command translates a terminfo  file  from  source  format  into
        compiled  format.   The  compiled  format is necessary for use with the
-       library routines in ncurses(3x).
+       library routines in ncurses(3X).
 
-       As described in term(5), the database may be either  a  directory  tree
+       As described in term(5), the database may be either  a  directory  tree
        (one  file  per  terminal  entry)  or a hashed database (one record per
-       entry).  The tic command writes only one type of  entry,  depending  on
+       entry).  The tic command writes only one type of  entry,  depending  on
        how it was built:
 
-       o   For    directory    trees,    the    top-level   directory,   e.g.,
+       o   For    directory    trees,    the    top-level   directory,   e.g.,
            /usr/share/terminfo, specifies the location of the database.
 
-       o   For hashed databases, a filename is needed.  If the given  file  is
+       o   For hashed databases, a filename is needed.  If the given  file  is
            not  found  by  that  name,  but  can be found by adding the suffix
            ".db", then that is used.
 
            The default name for the hashed database is the same as the default
            directory name (only adding a ".db" suffix).
 
-       In  either  case  (directory  or  hashed database), tic will create the
+       In  either  case  (directory  or  hashed database), tic will create the
        container if it does not exist.  For a directory,  this  would  be  the
        "terminfo" leaf, versus a "terminfo.db" file.
 
        The  results  are  normally  placed  in  the  system  terminfo database
-       /usr/share/terminfo.  The compiled terminal description can  be  placed
+       /usr/share/terminfo.  The compiled terminal description can  be  placed
        in a different terminfo database.  There are two ways to achieve this:
 
-       o   First,  you  may override the system default either by using the -o
-           option,  or  by  setting  the  variable  TERMINFO  in  your   shell
+       o   First,  you  may override the system default either by using the -o
+           option,  or  by  setting  the  variable  TERMINFO  in  your   shell
            environment to a valid database location.
 
-       o   Secondly,  if  tic  cannot  write  in  /usr/share/terminfo  or  the
+       o   Secondly,  if  tic  cannot  write  in  /usr/share/terminfo  or  the
            location specified using your TERMINFO variable, it looks  for  the
-           directory  $HOME/.terminfo (or hashed database $HOME/.terminfo.db);
+           directory  $HOME/.terminfo (or hashed database $HOME/.terminfo.db);
            if that location exists, the entry is placed there.
 
        Libraries  that  read  terminfo  entries  are  expected  to  check   in
        succession
 
-       o   a location specified with the TERMINFO environment variable,
+       o   a location specified with the TERMINFO environment variable,
 
-       o   $HOME/.terminfo,
+       o   $HOME/.terminfo,
 
-       o   directories listed in the TERMINFO_DIRS environment variable,
+       o   directories listed in the TERMINFO_DIRS environment variable,
 
-       o   a compiled-in list of directories (no default value), and
+       o   a compiled-in list of directories (no default value), and
 
-       o   the system terminfo database (/usr/share/terminfo).
+       o   the system terminfo database (/usr/share/terminfo).

                              ALIASES

                                      This  is the same program as infotocap and captoinfo; usually those are
        linked to, or copied from this program:
 
-       o   When invoked as infotocap, tic sets the -I option.
+       o   When invoked as infotocap, tic sets the -I option.
 
-       o   When invoked as captoinfo, tic sets the -C option.
+       o   When invoked as captoinfo, tic sets the -C option.

                              OPTIONS

                              -       -0     restricts the output to a single line
+       -0     restricts the output to a single line
 
-       -1     restricts the output to a single column
+       -1     restricts the output to a single column
 
-       -a     tells tic  to  retain  commented-out  capabilities  rather  than
+       -a     tells tic  to  retain  commented-out  capabilities  rather  than
               discarding  them.   Capabilities are commented by prefixing them
-              with a period.  This sets the -x option, because it  treats  the
+              with a period.  This sets the -x option, because it  treats  the
               commented-out  entries  as user-defined names.  If the source is
               termcap, accept the 2-character names  required  by  version  6.
               Otherwise these are ignored.
 
-       -C     Force  source translation to termcap format.  Note: this differs
-              from the -C option of infocmp(1m) in that  it  does  not  merely
+       -C     Force  source translation to termcap format.  Note: this differs
+              from the -C option of infocmp(1M) in that  it  does  not  merely
               translate capability names, but also translates terminfo strings
               to termcap format.  Capabilities that are not  translatable  are
               left  in  the entry under their terminfo names but commented out
               with two preceding dots.  The actual  format  used  incorporates
               some  improvements  for escaped characters from terminfo format.
-              For a stricter BSD-compatible translation, add the -K option.
+              For a stricter BSD-compatible translation, add the -K option.
 
-              If this is combined with -c,  tic  makes  additional  checks  to
+              If this is combined with -c,  tic  makes  additional  checks  to
               report  cases  where  the  terminfo  values do not have an exact
               equivalent in termcap form.  For example:
 
-              o   sgr usually will not  convert,  because  termcap  lacks  the
+              o   sgr usually will not  convert,  because  termcap  lacks  the
                   ability  to  work with more than two parameters, and because
                   termcap lacks many of the arithmetic/logical operators  used
                   in terminfo.
 
-              o   capabilities  with more than one delay or with delays before
+              o   capabilities  with more than one delay or with delays before
                   the end of the string will not convert completely.
 
-       -c     tells tic to  only  check  file  for  errors,  including  syntax
-              problems  and  bad  use-links.  If you specify -C (-I) with this
+       -c     tells tic to  only  check  file  for  errors,  including  syntax
+              problems  and  bad  use-links.  If you specify -C (-I) with this
               option, the code will print warnings about entries which,  after
               use  resolution, are more than 1023 (4096) bytes long.  Due to a
               fixed buffer length in older termcap libraries, as well as buggy
@@ -157,58 +157,58 @@
               terminfo),  these  entries  may  cause  core  dumps  with  other
               implementations.
 
-              tic  checks  string  capabilities  to  ensure  that  those  with
+              tic  checks  string  capabilities  to  ensure  that  those  with
               parameters will be valid expressions.  It does this  check  only
               for  the predefined string capabilities; those which are defined
-              with the -x option are ignored.
+              with the -x option are ignored.
 
-       -D     tells tic to print the database locations that it  knows  about,
+       -D     tells tic to print the database locations that it  knows  about,
               and exit.  The first location shown is the one to which it would
-              write compiled terminal descriptions.  If tic  is  not  able  to
+              write compiled terminal descriptions.  If tic  is  not  able  to
               find  a  writable  database  location  according  to  the  rules
               summarized above, it will print a diagnostic and  exit  with  an
               error rather than printing a list of database locations.
 
-       -e names
+       -e names
               Limit  writes  and translations to the following comma-separated
               list of terminals.  If any name or alias of a  terminal  matches
               one  of  the  names  in  the  list, the entry will be written or
               translated as normal.  Otherwise no output will be generated for
               it.   The  option  value is interpreted as a file containing the
               list if it contains a '/'.  (Note:  depending  on  how  tic  was
-              compiled, this option may require -I or -C.)
+              compiled, this option may require -I or -C.)
 
-       -f     Display     complex     terminfo     strings    which    contain
+       -f     Display     complex     terminfo     strings    which    contain
               if/then/else/endif expressions indented for readability.
 
-       -G     Display constant literals in  decimal  form  rather  than  their
+       -G     Display constant literals in  decimal  form  rather  than  their
               character equivalents.
 
-       -g     Display  constant  character literals in quoted form rather than
+       -g     Display  constant  character literals in quoted form rather than
               their decimal equivalents.
 
-       -I     Force source translation to terminfo format.
+       -I     Force source translation to terminfo format.
 
-       -K     Suppress some longstanding ncurses extensions to termcap format,
+       -K     Suppress some longstanding ncurses extensions to termcap format,
               e.g., "\s" for space.
 
-       -L     Force  source  translation  to  terminfo format using the long C
-              variable names listed in <term.h>
+       -L     Force  source  translation  to  terminfo format using the long C
+              variable names listed in <term.h>
 
-       -N     Disable smart defaults.  Normally, when translating from termcap
+       -N     Disable smart defaults.  Normally, when translating from termcap
               to  terminfo,  the  compiler makes a number of assumptions about
-              the   defaults    of    string    capabilities    reset1_string,
-              carriage_return,  cursor_left, cursor_down, scroll_forward, tab,
-              newline, key_backspace, key_left, and key_down, then attempts to
+              the   defaults    of    string    capabilities    reset1_string,
+              carriage_return,  cursor_left, cursor_down, scroll_forward, tab,
+              newline, key_backspace, key_left, and key_down, then attempts to
               use  obsolete termcap capabilities to deduce correct values.  It
               also normally suppresses output of obsolete termcap capabilities
-              such  as bs.  This option forces a more literal translation that
+              such  as bs.  This option forces a more literal translation that
               also preserves the obsolete capabilities.
 
-       -odir  Write compiled entries to given  database  location.   Overrides
+       -odir  Write compiled entries to given  database  location.   Overrides
               the TERMINFO environment variable.
 
-       -Qn    Rather  than  show  source  in terminfo (text) format, print the
+       -Qn    Rather  than  show  source  in terminfo (text) format, print the
               compiled  (binary)  format  in  hexadecimal  or   base64   form,
               depending on the option's value:
 
@@ -218,52 +218,52 @@
 
                3  hexadecimal and base64
 
-       -q     Suppress  comments  and  blank  lines  when  showing  translated
+       -q     Suppress  comments  and  blank  lines  when  showing  translated
               source.
 
-       -Rsubset
+       -Rsubset
               Restrict output to a given subset.  This option is for use  with
               archaic  versions  of  terminfo  like  those on SVr1, Ultrix, or
               HP/UX that do not  support  the  full  set  of  SVR4/XSI  Curses
               terminfo; and outright broken ports like AIX 3.x that have their
               own extensions incompatible with  SVr4/XSI.   Available  subsets
-              are "SVr1", "Ultrix", "HP", "BSD" and "AIX"; see terminfo(5) for
+              are "SVr1", "Ultrix", "HP", "BSD" and "AIX"; see terminfo(5) for
               details.
 
-       -r     Force  entry  resolution  (so  there   are   no   remaining   tc
+       -r     Force  entry  resolution  (so  there   are   no   remaining   tc
               capabilities)  even  when  doing  translation to termcap format.
               This may be needed if you are preparing a  termcap  file  for  a
               termcap  library (such as GNU termcap through version 1.3 or BSD
               termcap  through  4.3BSD)  that  does  not  handle  multiple  tc
               capabilities per entry.
 
-       -s     Summarize  the  compile  by  showing  the database location into
+       -s     Summarize  the  compile  by  showing  the database location into
               which entries are written, and the number of entries  which  are
               compiled.
 
-       -T     eliminates  size-restrictions  on  the  generated text.  This is
+       -T     eliminates  size-restrictions  on  the  generated text.  This is
               mainly useful for  testing  and  analysis,  since  the  compiled
               descriptions  are  limited  (e.g.,  1023  for  termcap, 4096 for
               terminfo).
 
-       -t     tells tic to discard commented-out capabilities.  Normally  when
+       -t     tells tic to discard commented-out capabilities.  Normally  when
               translating    from    terminfo   to   termcap,   untranslatable
               capabilities are commented-out.
 
-       -U   tells tic to not post-process the data after  parsing  the  source
+       -U   tells tic to not post-process the data after  parsing  the  source
             file.  Normally, it infers data which is commonly missing in older
             terminfo data, or in termcaps.
 
-       -V   reports the version of ncurses which was used in this program, and
+       -V   reports the version of ncurses which was used in this program, and
             exits.
 
-       -vn  specifies that (verbose) output be written to standard error trace
-            information showing tic's progress.
+       -vn  specifies that (verbose) output be written to standard error trace
+            information showing tic's progress.
 
-            The optional parameter n is a number  from  1  to  10,  inclusive,
+            The optional parameter n 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  n  is  omitted,  the  default  level is 1.  If n is
+            ignored.   If  n  is  omitted,  the  default  level is 1.  If n is
             specified and greater than 1, the level of detail is increased.
 
             The debug flag levels are as follows:
@@ -282,19 +282,19 @@
 
             9      All values computed in construction of the hash table
 
-            If the debug level n is not given, it is taken to be one.
+            If the debug level n is not given, it is taken to be one.
 
-       -W   By itself, the -w  option  will  not  force  long  strings  to  be
-            wrapped.  Use the -W option to do this.
+       -W   By itself, the -w  option  will  not  force  long  strings  to  be
+            wrapped.  Use the -W option to do this.
 
-            If  you specify both -f and -W options, the latter is ignored when
-            -f has already split the line.
+            If  you specify both -f and -W options, the latter is ignored when
+            -f has already split the line.
 
-       -wn  specifies the width of the output.  The parameter is optional.  If
+       -wn  specifies the width of the output.  The parameter is optional.  If
             it is omitted, it defaults to 60.
 
-       -x   Treat  unknown  capabilities  as  user-defined (see user_caps(5)).
-            That is, if you supply  a  capability  name  which  tic  does  not
+       -x   Treat  unknown  capabilities  as  user-defined (see user_caps(5)).
+            That is, if you supply  a  capability  name  which  tic  does  not
             recognize, it will infer its type (boolean, number or string) from
             the syntax and make an  extended  table  entry  for  that.   User-
             defined  capability strings whose name begins with "k" are treated
@@ -302,29 +302,29 @@

                              PARAMETERS

                              -       file   contains one or more terminfo terminal  descriptions  in  source
-              format   [see   terminfo(5)].   Each  description  in  the  file
+       file   contains one or more terminfo terminal  descriptions  in  source
+              format   [see   terminfo(5)].   Each  description  in  the  file
               describes the capabilities of a particular terminal.
 
-              If file is "-", then the data is read from the  standard  input.
-              The file parameter may also be the path of a character-device.
+              If file is "-", then the data is read from the  standard  input.
+              The file parameter may also be the path of a character-device.

                              PROCESSING

                              -       All  but  one  of  the capabilities recognized by tic are documented in
-       terminfo(5).  The exception is the use capability.
+       All  but  one  of  the capabilities recognized by tic are documented in
+       terminfo(5).  The exception is the use capability.
 
-       When a use=entry-name field is discovered in a terminal entry currently
-       being  compiled,  tic  reads  in the binary from /usr/share/terminfo to
-       complete the entry.  (Entries created from file  will  be  used  first.
-       tic  duplicates  the  capabilities in entry-name for the current entry,
+       When a use=entry-name field is discovered in a terminal entry currently
+       being  compiled,  tic  reads  in the binary from /usr/share/terminfo to
+       complete the entry.  (Entries created from file  will  be  used  first.
+       tic  duplicates  the  capabilities in entry-name for the current entry,
        with the exception of those capabilities that explicitly are defined in
        the current entry.
 
-       When  an  entry, e.g., entry_name_1, contains a use=entry_name_2 field,
-       any  canceled  capabilities  in  entry_name_2  must  also   appear   in
-       entry_name_1  before  use=  for  these  capabilities  to be canceled in
-       entry_name_1.
+       When  an  entry, e.g., entry_name_1, contains a use=entry_name_2 field,
+       any  canceled  capabilities  in  entry_name_2  must  also   appear   in
+       entry_name_1  before  use=  for  these  capabilities  to be canceled in
+       entry_name_1.
 
        Total compiled entries cannot exceed 4096 bytes.  The name field cannot
        exceed  512  bytes.   Terminal names exceeding the maximum alias length
@@ -334,54 +334,54 @@

                              HISTORY

                              -       System V Release 2 provided  a  tic  utility.   It  accepted  a  single
-       option:  -v  (optionally  followed  by  a  number).   According to Ross
-       Ridge's comment in mytinfo, this version of tic was unable to represent
+       System V Release 2 provided  a  tic  utility.   It  accepted  a  single
+       option:  -v  (optionally  followed  by  a  number).   According to Ross
+       Ridge's comment in mytinfo, this version of tic was unable to represent
        cancelled capabilities.
 
-       System  V  Release 3 provided a different tic utility, written by Pavel
-       Curtis, (originally named "compile" in pcurses).  This added an  option
-       -c  to check the file for errors, with the caveat that errors in "use="
+       System  V  Release 3 provided a different tic utility, written by Pavel
+       Curtis, (originally named "compile" in pcurses).  This added an  option
+       -c  to check the file for errors, with the caveat that errors in "use="
        links would not be reported.  System  V  Release  3  documented  a  few
-       warning  messages  which  did not appear in pcurses.  While the program
+       warning  messages  which  did not appear in pcurses.  While the program
        itself was changed  little  as  development  continued  with  System  V
-       Release  4,  the  table  of capabilities grew from 180 (pcurses) to 464
+       Release  4,  the  table  of capabilities grew from 180 (pcurses) to 464
        (Solaris).
 
        In early development of ncurses (1993), Zeyd Ben-Halim used  the  table
-       from  mytinfo  to  extend  the  pcurses  table to 469 capabilities (456
+       from  mytinfo  to  extend  the  pcurses  table to 469 capabilities (456
        matched SVr4, 8 were only in SVr4, 13 were not in SVr4).  Of those  13,
        11  were  ultimately  discarded  (perhaps  to match the draft of X/Open
-       Curses).  The exceptions were memory_lock_above and memory_unlock  (see
-       user_caps(5)).
+       Curses).  The exceptions were memory_lock_above and memory_unlock  (see
+       user_caps(5)).
 
-       Eric  Raymond  incorporated  parts of mytinfo into ncurses to implement
+       Eric  Raymond  incorporated  parts of mytinfo into ncurses to implement
        the termcap-to-terminfo source conversion, and extended that  to  begin
        development of the corresponding terminfo-to-termcap source conversion,
        Thomas Dickey completed that development over  the  course  of  several
        years.
 
-       In  1999,  Thomas  Dickey  added  the -x option to support user-defined
+       In  1999,  Thomas  Dickey  added  the -x option to support user-defined
        capabilities.
 
-       In 2010, Roy Marples provided a tic program and  terminfo  library  for
+       In 2010, Roy Marples provided a tic program and  terminfo  library  for
        NetBSD.   That  implementation  adapts  several  features from ncurses,
-       including tic's -x option.
+       including tic's -x option.
 
-       The -c option tells tic to check for problems in  the  terminfo  source
+       The -c option tells tic to check for problems in  the  terminfo  source
        file.  Continued development provides additional checks:
 
-       o   pcurses had 8 warnings
+       o   pcurses had 8 warnings
 
-       o   ncurses in 1996 had 16 warnings
+       o   ncurses in 1996 had 16 warnings
 
-       o   Solaris (SVr4) curses has 28 warnings
+       o   Solaris (SVr4) curses has 28 warnings
 
-       o   NetBSD tic in 2019 has 19 warnings.
+       o   NetBSD tic in 2019 has 19 warnings.
 
-       o   ncurses in 2019 has 96 warnings
+       o   ncurses in 2019 has 96 warnings
 
-       The checking done in ncurses' tic helps with the conversion to termcap,
+       The checking done in ncurses' tic 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; 128 of  those  are
@@ -389,20 +389,20 @@

                              PORTABILITY

                              -       X/Open  Curses, Issue 7 (2009) provides a brief description of tic.  It
-       lists one option: -c.  The omission of -v is  unexpected.   The  change
+       X/Open  Curses, Issue 7 (2009) provides a brief description of tic.  It
+       lists one option: -c.  The omission of -v is  unexpected.   The  change
        history  states  that  the  description  is  derived  from True64 UNIX.
-       According to its manual  pages,  that  system  also  supported  the  -v
+       According to its manual  pages,  that  system  also  supported  the  -v
        option.
 
        Shortly  after  Issue  7  was  released, Tru64 was discontinued.  As of
-       2019, the surviving implementations of tic are  SVr4  (AIX,  HP-UX  and
-       Solaris), ncurses and NetBSD curses.  The SVr4 tic programs all support
-       the -v option.  The NetBSD tic program follows X/Open's  documentation,
-       omitting the -v option.
+       2019, the surviving implementations of tic are  SVr4  (AIX,  HP-UX  and
+       Solaris), ncurses and NetBSD curses.  The SVr4 tic programs all support
+       the -v option.  The NetBSD tic program follows X/Open's  documentation,
+       omitting the -v option.
 
-       The  X/Open  rationale  states  that  some  implementations of tic read
-       terminal descriptions from the standard input if the file parameter  is
+       The  X/Open  rationale  states  that  some  implementations of tic read
+       terminal descriptions from the standard input if the file parameter  is
        omitted.   None of these implementations do that.  Further, it comments
        that some  may  choose  to  read  from  "./terminfo.src"  but  that  is
        obsolescent  behavior  from SVr2, and is not (for example) a documented
@@ -410,58 +410,58 @@

                              COMPATIBILITY

                              -       There is  some  evidence  that  historic  tic  implementations  treated
+       There is  some  evidence  that  historic  tic  implementations  treated
        description  fields with no whitespace in them as additional aliases or
-       short names.  This tic  does  not  do  that,  but  it  does  warn  when
+       short names.  This tic  does  not  do  that,  but  it  does  warn  when
        description fields may be treated that way and check them for dangerous
        characters.

                              EXTENSIONS

                              -       Unlike the SVr4 tic command, this implementation can  actually  compile
+       Unlike the SVr4 tic command, this implementation can  actually  compile
        termcap  sources.   In fact, entries in terminfo and termcap syntax can
-       be mixed in a single source file.  See  terminfo(5)  for  the  list  of
+       be mixed in a single source file.  See  terminfo(5)  for  the  list  of
        termcap names taken to be equivalent to terminfo names.
 
-       The  SVr4  manual  pages  are not clear on the resolution rules for use
-       capabilities.   This  implementation  of  tic  will  find  use  targets
+       The  SVr4  manual  pages  are not clear on the resolution rules for use
+       capabilities.   This  implementation  of  tic  will  find  use  targets
        anywhere  in  the  source  file, or anywhere in the file tree rooted at
-       TERMINFO (if TERMINFO is defined), or  in  the  user's  $HOME/.terminfo
+       TERMINFO (if TERMINFO is defined), or  in  the  user's  $HOME/.terminfo
        database  (if  it  exists),  or (finally) anywhere in the system's file
        tree of compiled entries.
 
-       The error messages from this tic have the same format as  GNU  C  error
+       The error messages from this tic have the same format as  GNU  C  error
        messages, and can be parsed by GNU Emacs's compile facility.
 
-       Aside from -c and -v, options are not portable:
+       Aside from -c and -v, options are not portable:
 
-       o   Most of tic's options are not supported by SVr4 tic:
+       o   Most of tic's options are not supported by SVr4 tic:
 
-           -0 -1 -C -G -I -N -R -T -V -a -e -f -g -o -r -s -t -x
+           -0 -1 -C -G -I -N -R -T -V -a -e -f -g -o -r -s -t -x
 
-       o   The NetBSD tic  supports a few of the ncurses options
+       o   The NetBSD tic  supports a few of the ncurses options
 
-           -a -o -x
+           -a -o -x
 
-           and  adds  -S  (a feature which does the same thing as infocmp's -e
-           and -E options).
+           and  adds  -S  (a feature which does the same thing as infocmp's -e
+           and -E options).
 
-       The SVr4 -c mode does not report bad "use=" links.
+       The SVr4 -c mode does not report bad "use=" links.
 
        System V does  not  compile  entries  to  or  read  entries  from  your
-       $HOME/.terminfo database unless TERMINFO is explicitly set to it.
+       $HOME/.terminfo database unless TERMINFO is explicitly set to it.

                              FILES

                              -       /usr/share/terminfo/?/*
+       /usr/share/terminfo/?/*
             Compiled terminal description database.

                              SEE ALSO

                              -       captoinfo(1m),   infocmp(1m),   infotocap(1m),   toe(1m),   curses(3x),
-       term(5).  terminfo(5).  user_caps(5).
+       captoinfo(1M),   infocmp(1M),   infotocap(1M),   toe(1M),   curses(3X),
+       term(5).  terminfo(5).  user_caps(5).
 
-       This describes ncurses version 6.2 (patch 20210522).
+       This describes ncurses version 6.2 (patch 20210612).

                              AUTHOR

                              @@ -470,7 +470,7 @@
 
 
 
-                                                                       tic(1m)
+                                                                       tic(1M)
                                diff --git a/doc/html/man/toe.1m.html b/doc/html/man/toe.1m.html index 7b024733..cf0b5981 100644 --- a/doc/html/man/toe.1m.html +++ b/doc/html/man/toe.1m.html @@ -1,6 +1,6 @@ - -toe 1m +@TOE@ 1M -

                                toe 1m

                                +

                                @TOE@ 1M

                                -toe(1m)                                                                toe(1m)
+toe(1M)                                                                toe(1M)

                                NAME

                                -       toe - table of (terminfo) entries
+       toe - table of (terminfo) entries

                                SYNOPSIS

                                -       toe [-v[n]] [-ahsuUV] file...
+       toe [-v[n]] [-ahsuUV] file...

                                DESCRIPTION

                                -       With no options, toe lists all available terminal types by primary name
+       With no options, toe lists all available terminal types by primary name
        with descriptions.   File  arguments  specify  the  directories  to  be
        scanned;  if  no  such  arguments  are  given,  your  default  terminfo
-       directory is scanned.  If you also specify the -h option,  a  directory
+       directory is scanned.  If you also specify the -h option,  a  directory
        header will be issued as each directory is entered.
 
        There are other options intended for use by terminfo file maintainers:
 
-       -a     report  on  all  of  the  terminal databases which ncurses would
+       -a     report  on  all  of  the  terminal databases which ncurses would
               search, rather than only the first one that it finds.
 
-              If the -s is also given,  toe  adds  a  column  to  the  report,
-              showing (like conflict(1)) which entries which belong to a given
+              If the -s is also given,  toe  adds  a  column  to  the  report,
+              showing (like conflict(1)) which entries which belong to a given
               terminal database.  An "*" marks entries which differ,  and  "+"
               marks equivalent entries.
 
-              Without  the -s option, toe does not attempt to merge duplicates
+              Without  the -s option, toe does not attempt to merge duplicates
               in its report
 
-       -s     sort the output by the entry names.
+       -s     sort the output by the entry names.
 
-       -u file
+       -u file
               says  to  write  a  report  to  the  standard  output,   listing
               dependencies  in  the  given  terminfo/termcap source file.  The
               report condenses the "use" relation: each line consists  of  the
@@ -85,7 +85,7 @@
               of all terminals which occur in those use capabilities, followed
               by a newline
 
-       -U file
+       -U file
               says to write a report to the standard output,  listing  reverse
               dependencies  in  the  given  terminfo/termcap source file.  The
               report reverses the "use" relation: each line  consists  of  the
@@ -94,20 +94,20 @@
               primary names of all terminals which depend on it, followed by a
               newline.
 
-       -vn    specifies that (verbose) output be written  to  standard  error,
-              showing toe's progress.
+       -vn    specifies that (verbose) output be written  to  standard  error,
+              showing toe's progress.
 
-              The  optional  parameter n is a number from 1 to 10, interpreted
-              as for tic(1m).  If ncurses is built  without  tracing  support,
+              The  optional  parameter n is a number from 1 to 10, interpreted
+              as for tic(1M).  If ncurses is built  without  tracing  support,
               the optional parameter is ignored.
 
-       -V     reports  the  version of ncurses which was used in this program,
+       -V     reports  the  version of ncurses which was used in this program,
               and exits.

                                EXAMPLES

                                -       Without sorting, the -a option reports all of the names found in all of
-       the   terminal  databases  found  by  the  TERMINFO  and  TERMINFO_DIRS
+       Without sorting, the -a option reports all of the names found in all of
+       the   terminal  databases  found  by  the  TERMINFO  and  TERMINFO_DIRS
        environment variables:
 
            MtxOrb162      16x2 Matrix Orbital LCD display
@@ -124,7 +124,7 @@
            qansi-t        QNX ansi without console writes
            . . .
 
-       Use the -a  and  -s  options  together  to  show  where  each  terminal
+       Use the -a  and  -s  options  together  to  show  where  each  terminal
        description was found:
 
            --> /usr/local/ncurses/share/terminfo
@@ -144,38 +144,38 @@

                                FILES

                                -       /usr/share/terminfo/?/*
+       /usr/share/terminfo/?/*
             Compiled terminal description database.

                                HISTORY

                                        This  utility  is  not  provided by other implementations.  There is no
-       relevant X/Open or POSIX standard for toe.
+       relevant X/Open or POSIX standard for toe.
 
        The program name refers to a developer's pun:
 
-       o   tic,
+       o   tic,
 
-       o   tac (now tack),
+       o   tac (now tack),
 
-       o   toe.
+       o   toe.
 
-       It replaced a -T option which was  briefly  supported  by  the  ncurses
-       infocmp utility in 1995.
+       It replaced a -T option which was  briefly  supported  by  the  ncurses
+       infocmp utility in 1995.
 
-       The  -a  and -s options were added to toe several years later (2006 and
+       The  -a  and -s options were added to toe several years later (2006 and
        2011, respectively).

                                SEE ALSO

                                -       captoinfo(1m),   infocmp(1m),   infotocap(1m),   tic(1m),   curses(3x),
-       terminfo(5).
+       captoinfo(1M),   infocmp(1M),   infotocap(1M),   tic(1M),   curses(3X),
+       terminfo(5).
 
-       This describes ncurses version 6.2 (patch 20210522).
+       This describes ncurses version 6.2 (patch 20210612).
 
 
 
-                                                                       toe(1m)
+                                                                       toe(1M)
                                  diff --git a/doc/html/man/tput.1.html b/doc/html/man/tput.1.html index b0e49b1a..ef21a0d3 100644 --- a/doc/html/man/tput.1.html +++ b/doc/html/man/tput.1.html @@ -1,4 +1,4 @@ - -tput 1 +@TPUT@ 1 -

                                  tput 1

                                  +

                                  @TPUT@ 1

                                  -tput(1)                     General Commands Manual                    tput(1)
+tput(1)                     General Commands Manual                    tput(1)

                                  NAME

                                  -       tput, reset - initialize a terminal or query terminfo database
+       tput, reset - initialize a terminal or query terminfo database

                                  SYNOPSIS

                                  -       tput [-Ttype] capname [parameters]
-       tput [-Ttype] [-x] clear
-       tput [-Ttype] init
-       tput [-Ttype] reset
-       tput [-Ttype] longname
-       tput -S  <<
-       tput -V
+       tput [-Ttype] capname [parameters]
+       tput [-Ttype] [-x] clear
+       tput [-Ttype] init
+       tput [-Ttype] reset
+       tput [-Ttype] longname
+       tput -S  <<
+       tput -V

                                  DESCRIPTION

                                  -       The  tput  utility  uses  the  terminfo  database to make the values of
+       The  tput  utility  uses  the  terminfo  database to make the values of
        terminal-dependent capabilities and information available to the  shell
-       (see  sh(1)),  to  initialize or reset the terminal, or return the long
+       (see  sh(1)),  to  initialize or reset the terminal, or return the long
        name of the requested terminal  type.   The  result  depends  upon  the
        capability's type:
 
           string
-               tput  writes  the  string  to the standard output.  No trailing
+               tput  writes  the  string  to the standard output.  No trailing
                newline is supplied.
 
           integer
-               tput writes the decimal value to the standard  output,  with  a
+               tput writes the decimal value to the standard  output,  with  a
                trailing newline.
 
           boolean
-               tput  simply sets the exit code (0 for TRUE if the terminal has
-               the capability, 1 for FALSE if it does not), and writes nothing
+               tput  simply sets the exit code (0 for TRUE if the terminal has
+               the capability, 1 for FALSE if it does not), and writes nothing
                to the standard output.
 
        Before  using  a value returned on the standard output, the application
-       should test the exit code (e.g., $?, see sh(1)) to be  sure  it  is  0.
-       (See  the EXIT CODES and DIAGNOSTICS sections.)  For a complete list of
-       capabilities and the capname associated with each, see terminfo(5).
+       should test the exit code (e.g., $?, see sh(1)) to be  sure  it  is  0.
+       (See  the EXIT CODES and DIAGNOSTICS sections.)  For a complete list of
+       capabilities and the capname associated with each, see terminfo(5).

                                  Options

                                  -       -S     allows more than one capability per  invocation  of  tput.   The
-              capabilities  must  be  passed  to  tput from the standard input
+       -S     allows more than one capability per  invocation  of  tput.   The
+              capabilities  must  be  passed  to  tput from the standard input
               instead of from  the  command  line  (see  example).   Only  one
-              capname  is allowed per line.  The -S option changes the meaning
-              of the 0 and 1 boolean and string exit codes (see the EXIT CODES
+              capname  is allowed per line.  The -S option changes the meaning
+              of the 0 and 1 boolean and string exit codes (see the EXIT CODES
               section).
 
-              Because  some capabilities may use string parameters rather than
-              numbers, tput uses a table and the presence of parameters in its
-              input  to  decide whether to use tparm(3x), and how to interpret
+              Because  some capabilities may use string parameters rather than
+              numbers, tput uses a table and the presence of parameters in its
+              input  to  decide whether to use tparm(3X), and how to interpret
               the parameters.
 
-       -Ttype indicates  the  type  of  terminal.   Normally  this  option  is
+       -Ttype indicates  the  type  of  terminal.   Normally  this  option  is
               unnecessary,  because  the default is taken from the environment
-              variable TERM.  If -T is specified,  then  the  shell  variables
-              LINES and COLUMNS will also be ignored.
+              variable TERM.  If -T is specified,  then  the  shell  variables
+              LINES and COLUMNS will also be ignored.
 
-       -V     reports  the  version of ncurses which was used in this program,
+       -V     reports  the  version of ncurses which was used in this program,
               and exits.
 
-       -x     do not attempt to clear the terminal's scrollback  buffer  using
+       -x     do not attempt to clear the terminal's scrollback  buffer  using
               the extended "E3" capability.

                                  Commands

                                  -       A few commands (init, reset and longname) are special; they are defined
-       by the tput program.  The others are the names of capabilities from the
-       terminal  database  (see  terminfo(5)  for  a list).  Although init and
-       reset resemble capability names,  tput  uses  several  capabilities  to
+       A few commands (init, reset and longname) are special; they are defined
+       by the tput program.  The others are the names of capabilities from the
+       terminal  database  (see  terminfo(5)  for  a list).  Although init and
+       reset resemble capability names,  tput  uses  several  capabilities  to
        perform these special functions.
 
-       capname
+       capname
               indicates the capability from the terminal database.
 
               If  the  capability  is  a  string  that  takes  parameters, the
@@ -127,393 +127,393 @@
               for the string.
 
               Most  parameters  are numbers.  Only a few terminal capabilities
-              require string parameters; tput uses a table to decide which  to
-              pass  as  strings.   Normally tput uses tparm(3x) to perform the
+              require string parameters; tput uses a table to decide which  to
+              pass  as  strings.   Normally tput uses tparm(3X) to perform the
               substitution.  If no parameters are given  for  the  capability,
-              tput writes the string without performing the substitution.
+              tput writes the string without performing the substitution.
 
-       init   If  the terminal database is present and an entry for the user's
-              terminal exists (see -Ttype, above), the following will occur:
+       init   If  the terminal database is present and an entry for the user's
+              terminal exists (see -Ttype, above), the following will occur:
 
-              (1)  first, tput retrieves the current  terminal  mode  settings
+              (1)  first, tput retrieves the current  terminal  mode  settings
                    for your terminal.  It does this by successively testing
 
-                   o   the standard error,
+                   o   the standard error,
 
-                   o   standard output,
+                   o   standard output,
 
-                   o   standard input and
+                   o   standard input and
 
-                   o   ultimately "/dev/tty"
+                   o   ultimately "/dev/tty"
 
                    to   obtain  terminal  settings.   Having  retrieved  these
-                   settings, tput remembers which file descriptor to use  when
+                   settings, tput remembers which file descriptor to use  when
                    updating settings.
 
               (2)  if  the  window  size cannot be obtained from the operating
                    system, but the terminal description (or environment, e.g.,
-                   LINES  and  COLUMNS  variables  specify  this),  update the
+                   LINES  and  COLUMNS  variables  specify  this),  update the
                    operating system's notion of the window size.
 
               (3)  the terminal modes will be updated:
 
-                   o   any delays (e.g., newline) specified in the entry  will
+                   o   any delays (e.g., newline) specified in the entry  will
                        be set in the tty driver,
 
-                   o   tabs  expansion  will  be turned on or off according to
+                   o   tabs  expansion  will  be turned on or off according to
                        the specification in the entry, and
 
-                   o   if tabs are not expanded, standard  tabs  will  be  set
+                   o   if tabs are not expanded, standard  tabs  will  be  set
                        (every 8 spaces).
 
               (4)  if  present,  the terminal's initialization strings will be
-                   output as detailed in the terminfo(5) section on  Tabs  and
-                   Initialization,
+                   output as detailed in the terminfo(5) section on  Tabs  and
+                   Initialization,
 
               (5)  output is flushed.
 
               If  an  entry does not contain the information needed for any of
               these activities, that activity will silently be skipped.
 
-       reset  This is similar to init, with two differences:
+       reset  This is similar to init, with two differences:
 
               (1)  before any other initialization, the terminal modes will be
                    reset to a "sane" state:
 
-                   o   set cooked and echo modes,
+                   o   set cooked and echo modes,
 
-                   o   turn off cbreak and raw modes,
+                   o   turn off cbreak and raw modes,
 
-                   o   turn on newline translation and
+                   o   turn on newline translation and
 
-                   o   reset  any  unset  special  characters to their default
+                   o   reset  any  unset  special  characters to their default
                        values
 
-              (2)  Instead  of  putting  out   initialization   strings,   the
-                   terminal's  reset  strings  will be output if present (rs1,
-                   rs2, rs3, rf).  If the reset strings are not  present,  but
-                   initialization strings are, the initialization strings will
+              (2)  Instead  of  putting  out   initialization   strings,   the
+                   terminal's  reset  strings  will be output if present (rs1,
+                   rs2, rs3, rf).  If the reset strings are not  present,  but
+                   initialization strings are, the initialization strings will
                    be output.
 
-              Otherwise, reset acts identically to init.
+              Otherwise, reset acts identically to init.
 
-       longname
+       longname
               If the terminal database is present and an entry for the  user's
-              terminal  exists  (see  -Ttype above), then the long name of the
+              terminal  exists  (see  -Ttype above), then the long name of the
               terminal will be put out.  The long name is the last name in the
-              first  line  of  the  terminal's  description  in  the  terminfo
-              database [see term(5)].
+              first  line  of  the  terminal's  description  in  the  terminfo
+              database [see term(5)].

                                  Aliases

                                  -       tput handles the clear, init and reset commands  specially:  it  allows
+       tput handles the clear, init and reset commands  specially:  it  allows
        for the possibility that it is invoked by a link with those names.
 
-       If  tput  is invoked by a link named reset, this has the same effect as
-       tput reset.  The  tset(1)  utility  also  treats  a  link  named  reset
+       If  tput  is invoked by a link named reset, this has the same effect as
+       tput reset.  The  tset(1)  utility  also  treats  a  link  named  reset
        specially.
 
        Before ncurses 6.1, the two utilities were different from each other:
 
-       o   tset  utility  reset the terminal modes and special characters (not
-           done with tput).
+       o   tset  utility  reset the terminal modes and special characters (not
+           done with tput).
 
-       o   On the other hand, tset's repertoire of terminal  capabilities  for
-           resetting  the terminal was more limited, i.e., only reset_1string,
-           reset_2string and reset_file  in  contrast  to  the  tab-stops  and
+       o   On the other hand, tset's repertoire of terminal  capabilities  for
+           resetting  the terminal was more limited, i.e., only reset_1string,
+           reset_2string and reset_file  in  contrast  to  the  tab-stops  and
            margins which are set by this utility.
 
-       o   The  reset  program  is  usually an alias for tset, because of this
+       o   The  reset  program  is  usually an alias for tset, because of this
            difference with resetting terminal modes and special characters.
 
-       With the changes made for ncurses 6.1, the reset  feature  of  the  two
+       With the changes made for ncurses 6.1, the reset  feature  of  the  two
        programs is (mostly) the same.  A few differences remain:
 
-       o   The  tset  program  waits  one  second  when  resetting, in case it
+       o   The  tset  program  waits  one  second  when  resetting, in case it
            happens to be a hardware terminal.
 
-       o   The two programs  write  the  terminal  initialization  strings  to
-           different  streams  (i.e.,  the  standard  error  for  tset and the
-           standard output for tput).
+       o   The two programs  write  the  terminal  initialization  strings  to
+           different  streams  (i.e.,  the  standard  error  for  tset and the
+           standard output for tput).
 
-           Note:  although  these  programs  write   to   different   streams,
+           Note:  although  these  programs  write   to   different   streams,
            redirecting  their output to a file will capture only part of their
            actions.  The changes to the terminal modes  are  not  affected  by
            redirecting the output.
 
-       If  tput  is  invoked by a link named init, this has the same effect as
-       tput init.  Again, you are less likely to use that link because another
-       program named init has a more well-established use.
+       If  tput  is  invoked by a link named init, this has the same effect as
+       tput init.  Again, you are less likely to use that link because another
+       program named init has a more well-established use.

                                  Terminal Size

                                  -       Besides  the  special  commands  (e.g.,  clear),  tput  treats  certain
-       terminfo  capabilities  specially:  lines   and   cols.    tput   calls
-       setupterm(3x) to obtain the terminal size:
+       Besides  the  special  commands  (e.g.,  clear),  tput  treats  certain
+       terminfo  capabilities  specially:  lines   and   cols.    tput   calls
+       setupterm(3X) to obtain the terminal size:
 
-       o   first, it gets the size from the terminal database (which generally
+       o   first, it gets the size from the terminal database (which generally
            is not provided for terminal emulators which do not  have  a  fixed
            window size)
 
-       o   then  it  asks  the operating system for the terminal's size (which
+       o   then  it  asks  the operating system for the terminal's size (which
            generally works, unless connecting via a serial line which does not
-           support NAWS: negotiations about window size).
+           support NAWS: negotiations about window size).
 
-       o   finally,  it  inspects  the environment variables LINES and COLUMNS
+       o   finally,  it  inspects  the environment variables LINES and COLUMNS
            which may override the terminal size.
 
-       If the -T option is given tput ignores  the  environment  variables  by
-       calling   use_tioctl(TRUE),  relying  upon  the  operating  system  (or
+       If the -T option is given tput ignores  the  environment  variables  by
+       calling   use_tioctl(TRUE),  relying  upon  the  operating  system  (or
        finally, the terminal database).

                                  EXAMPLES

                                  -       tput init
+       tput init
             Initialize the terminal according to the type of terminal  in  the
-            environmental  variable  TERM.  This command should be included in
-            everyone's .profile after the environmental variable TERM has been
-            exported, as illustrated on the profile(5) manual page.
+            environmental  variable  TERM.  This command should be included in
+            everyone's .profile after the environmental variable TERM has been
+            exported, as illustrated on the profile(5) manual page.
 
-       tput -T5620 reset
+       tput -T5620 reset
             Reset  an  AT&T  5620 terminal, overriding the type of terminal in
-            the environmental variable TERM.
+            the environmental variable TERM.
 
-       tput cup 0 0
-            Send the sequence to move the cursor to row 0, column 0 (the upper
+       tput cup 0 0
+            Send the sequence to move the cursor to row 0, column 0 (the upper
             left  corner  of  the  screen,  usually known as the "home" cursor
             position).
 
-       tput clear
+       tput clear
             Echo the clear-screen sequence for the current terminal.
 
-       tput cols
+       tput cols
             Print the number of columns for the current terminal.
 
-       tput -T450 cols
+       tput -T450 cols
             Print the number of columns for the 450 terminal.
 
-       bold=`tput smso` offbold=`tput rmso`
-            Set the shell variables bold, to begin  stand-out  mode  sequence,
-            and  offbold,  to  end  standout  mode  sequence,  for the current
-            terminal.  This might be followed by a prompt: echo "${bold}Please
-            type in your name: ${offbold}\c"
+       bold=`tput smso` offbold=`tput rmso`
+            Set the shell variables bold, to begin  stand-out  mode  sequence,
+            and  offbold,  to  end  standout  mode  sequence,  for the current
+            terminal.  This might be followed by a prompt: echo "${bold}Please
+            type in your name: ${offbold}\c"
 
-       tput hc
+       tput hc
             Set  exit  code to indicate if the current terminal is a hard copy
             terminal.
 
-       tput cup 23 4
+       tput cup 23 4
             Send the sequence to move the cursor to row 23, column 4.
 
-       tput cup
+       tput cup
             Send the terminfo string for cursor-movement, with  no  parameters
             substituted.
 
-       tput longname
-            Print  the  long  name  from the terminfo database for the type of
-            terminal specified in the environmental variable TERM.
+       tput longname
+            Print  the  long  name  from the terminfo database for the type of
+            terminal specified in the environmental variable TERM.
 
-            tput -S <<!
-            > clear
-            > cup 10 10
-            > bold
-            > !
+            tput -S <<!
+            > clear
+            > cup 10 10
+            > bold
+            > !
 
-            This example shows tput processing  several  capabilities  in  one
+            This example shows tput processing  several  capabilities  in  one
             invocation.   It  clears  the screen, moves the cursor to position
             10, 10 and turns  on  bold  (extra  bright)  mode.   The  list  is
-            terminated by an exclamation mark (!) on a line by itself.
+            terminated by an exclamation mark (!) on a line by itself.

                                  FILES

                                  -       /usr/share/terminfo
+       /usr/share/terminfo
               compiled terminal description database
 
-       /usr/share/tabset/*
+       /usr/share/tabset/*
               tab  settings  for some terminals, in a format appropriate to be
               output to the terminal (escape sequences that  set  margins  and
-              tabs);  for  more  information, see the Tabs and Initialization,
-              section of terminfo(5)
+              tabs);  for  more  information, see the Tabs and Initialization,
+              section of terminfo(5)

                                  EXIT CODES

                                  -       If the -S option is used, tput checks for errors from each line, and if
+       If the -S option is used, tput checks for errors from each line, and if
        any  errors  are  found, will set the exit code to 4 plus the number of
-       lines with errors.  If no errors are found, the exit  code  is  0.   No
-       indication  of which line failed can be given so exit code 1 will never
-       appear.  Exit codes 2, 3, and 4 retain their usual interpretation.   If
-       the  -S  option  is  not  used,  the  exit  code depends on the type of
-       capname:
-
-          boolean
-                 a value of 0 is set for TRUE and 1 for FALSE.
-
-          string a value of 0 is set  if  the  capname  is  defined  for  this
-                 terminal  type  (the value of capname is returned on standard
-                 output); a value of 1 is set if capname is  not  defined  for
-                 this terminal type (nothing is written to standard output).
-
-          integer
-                 a value of 0 is always set, whether or not capname is defined
-                 for this terminal type.  To determine if capname  is  defined
-                 for  this terminal type, the user must test the value written
-                 to standard output.  A value of -1 means that capname is  not
-                 defined for this terminal type.
-
-          other  reset  or  init  may fail to find their respective files.  In
-                 that case, the exit code is set to 4 + errno.
+       lines with errors.  If no errors are found, the exit  code  is  0.   No
+       indication  of which line failed can be given so exit code 1 will never
+       appear.  Exit codes 2, 3, and 4 retain their usual interpretation.   If
+       the  -S  option  is  not  used,  the  exit  code depends on the type of
+       capname:
+
+          boolean
+                 a value of 0 is set for TRUE and 1 for FALSE.
+
+          string a value of 0 is set  if  the  capname  is  defined  for  this
+                 terminal  type  (the value of capname is returned on standard
+                 output); a value of 1 is set if capname is  not  defined  for
+                 this terminal type (nothing is written to standard output).
+
+          integer
+                 a value of 0 is always set, whether or not capname is defined
+                 for this terminal type.  To determine if capname  is  defined
+                 for  this terminal type, the user must test the value written
+                 to standard output.  A value of -1 means that capname is  not
+                 defined for this terminal type.
+
+          other  reset  or  init  may fail to find their respective files.  In
+                 that case, the exit code is set to 4 + errno.
 
        Any other exit code indicates an error; see the DIAGNOSTICS section.

                                  DIAGNOSTICS

                                  -       tput prints the following error messages  and  sets  the  corresponding
+       tput prints the following error messages  and  sets  the  corresponding
        exit codes.
 
        exit code   error message
        ---------------------------------------------------------------------
-       0           (capname  is a numeric variable that is not specified in
-                   the terminfo(5) database for this  terminal  type,  e.g.
-                   tput -T450 lines and tput -T2621 xmc)
-       1           no error message is printed, see the EXIT CODES section.
-       2           usage error
-       3           unknown terminal type or no terminfo database
-       4           unknown terminfo capability capname
-       >4          error occurred in -S
+       0           (capname  is a numeric variable that is not specified in
+                   the terminfo(5) database for this  terminal  type,  e.g.
+                   tput -T450 lines and tput -T2621 xmc)
+       1           no error message is printed, see the EXIT CODES section.
+       2           usage error
+       3           unknown terminal type or no terminfo database
+       4           unknown terminfo capability capname
+       >4          error occurred in -S
        ---------------------------------------------------------------------

                                  HISTORY

                                  -       The  tput  command  was begun by Bill Joy in 1980.  The initial version
+       The  tput  command  was begun by Bill Joy in 1980.  The initial version
        only cleared the screen.
 
-       AT&T System V provided a different tput command, whose init  and  reset
+       AT&T System V provided a different tput command, whose init  and  reset
        subcommands  (more  than  half  the program) were incorporated from the
-       reset feature of BSD tset written by Eric Allman.
+       reset feature of BSD tset written by Eric Allman.
 
-       Keith Bostic  replaced  the  BSD  tput  command  in  1989  with  a  new
-       implementation  based on the AT&T System V program tput.  Like the AT&T
-       program, Bostic's version accepted some parameters named  for  terminfo
-       capabilities  (clear,  init,  longname and reset).  However (because he
-       had only termcap  available),  it  accepted  termcap  names  for  other
-       capabilities.   Also, Bostic's BSD tput did not modify the terminal I/O
-       modes as the earlier BSD tset had done.
+       Keith Bostic  replaced  the  BSD  tput  command  in  1989  with  a  new
+       implementation  based on the AT&T System V program tput.  Like the AT&T
+       program, Bostic's version accepted some parameters named  for  terminfo
+       capabilities  (clear,  init,  longname and reset).  However (because he
+       had only termcap  available),  it  accepted  termcap  names  for  other
+       capabilities.   Also, Bostic's BSD tput did not modify the terminal I/O
+       modes as the earlier BSD tset had done.
 
        At the same time, Bostic added a shell script named "clear", which used
-       tput to clear the screen.
+       tput to clear the screen.
 
        Both   of   these   appeared  in  4.4BSD,  becoming  the  "modern"  BSD
-       implementation of tput.
+       implementation of tput.
 
-       This implementation of tput began from a different source than AT&T  or
-       BSD:  Ross  Ridge's  mytinfo package, published on comp.sources.unix in
+       This implementation of tput began from a different source than AT&T  or
+       BSD:  Ross  Ridge's  mytinfo package, published on comp.sources.unix in
        December 1992.  Ridge's program made  more  sophisticated  use  of  the
        terminal  capabilities  than  the  BSD program.  Eric Raymond used that
-       tput program (and other parts of mytinfo)  in  ncurses  in  June  1995.
+       tput program (and other parts of mytinfo)  in  ncurses  in  June  1995.
        Using  the  portions  dealing with terminal capabilities almost without
        change,  Raymond  made  improvements  to  the  way   the   command-line
        parameters were handled.

                                  PORTABILITY

                                  -       This  implementation  of  tput  differs from AT&T tput in two important
+       This  implementation  of  tput  differs from AT&T tput in two important
        areas:
 
-       o   tput capname writes to the standard output.  That  need  not  be  a
+       o   tput capname writes to the standard output.  That  need  not  be  a
            regular   terminal.   However,  the  subcommands  which  manipulate
            terminal modes may not use the standard output.
 
-           The AT&T implementation's init  and  reset  commands  use  the  BSD
-           (4.1c)   tset   source,   which  manipulates  terminal  modes.   It
+           The AT&T implementation's init  and  reset  commands  use  the  BSD
+           (4.1c)   tset   source,   which  manipulates  terminal  modes.   It
            successively tries standard output, standard error, standard  input
            before falling back to "/dev/tty" and finally just assumes a 1200Bd
            terminal.  When updating terminal modes, it ignores errors.
 
-           Until changes made after ncurses 6.0, tput did not modify  terminal
-           modes.  tput now uses a similar scheme, using functions shared with
-           tset (and ultimately based on the 4.4BSD tset).  If it is not  able
-           to open a terminal, e.g., when running in cron, tput will return an
+           Until changes made after ncurses 6.0, tput did not modify  terminal
+           modes.  tput now uses a similar scheme, using functions shared with
+           tset (and ultimately based on the 4.4BSD tset).  If it is not  able
+           to open a terminal, e.g., when running in cron, tput will return an
            error.
 
-       o   AT&T tput guesses the type of its capname operands by seeing if all
+       o   AT&T tput guesses the type of its capname operands by seeing if all
            of the characters are numeric, or not.
 
-           Most implementations which provide support for capname operands use
-           the tparm function to  expand  parameters  in  it.   That  function
-           expects  a mixture of numeric and string parameters, requiring tput
+           Most implementations which provide support for capname operands use
+           the tparm function to  expand  parameters  in  it.   That  function
+           expects  a mixture of numeric and string parameters, requiring tput
            to know which type to use.
 
            This implementation uses a table to determine the  parameter  types
-           for the standard capname operands, and an internal library function
-           to analyze nonstandard capname operands.
+           for the standard capname operands, and an internal library function
+           to analyze nonstandard capname operands.
 
-       This  implementation  (unlike  others)  can  accept  both  termcap  and
-       terminfo  names for the capname feature, if termcap support is compiled
-       in.  However, the  predefined  termcap  and  terminfo  names  have  two
-       ambiguities in this case (and the terminfo name is assumed):
+       This  implementation  (unlike  others)  can  accept  both  termcap  and
+       terminfo  names for the capname feature, if termcap support is compiled
+       in.  However, the  predefined  termcap  and  terminfo  names  have  two
+       ambiguities in this case (and the terminfo name is assumed):
 
-       o   The  termcap  name  dl corresponds to the terminfo name dl1 (delete
+       o   The  termcap  name  dl corresponds to the terminfo name dl1 (delete
            one line).
-           The terminfo name dl corresponds to the termcap name DL  (delete  a
+           The terminfo name dl corresponds to the termcap name DL  (delete  a
            given number of lines).
 
-       o   The  termcap  name  ed  corresponds  to the terminfo name rmdc (end
+       o   The  termcap  name  ed  corresponds  to the terminfo name rmdc (end
            delete mode).
-           The terminfo name ed corresponds to the termcap name cd  (clear  to
+           The terminfo name ed corresponds to the termcap name cd  (clear  to
            end of screen).
 
-       The  longname  and  -S options, and the parameter-substitution features
-       used in the cup example,  were  not  supported  in  BSD  curses  before
+       The  longname  and  -S options, and the parameter-substitution features
+       used in the cup example,  were  not  supported  in  BSD  curses  before
        4.3reno (1989) or in AT&T/USL curses before SVr4 (1988).
 
        IEEE   Std   1003.1/The   Open   Group   Base  Specifications  Issue  7
-       (POSIX.1-2008) documents only the operands for clear, init  and  reset.
+       (POSIX.1-2008) documents only the operands for clear, init  and  reset.
        There are a few interesting observations to make regarding that:
 
-       o   In  this implementation, clear is part of the capname support.  The
-           others  (init  and  longname)  do  not   correspond   to   terminal
+       o   In  this implementation, clear is part of the capname support.  The
+           others  (init  and  longname)  do  not   correspond   to   terminal
            capabilities.
 
-       o   Other  implementations  of  tput  on  SVr4-based  systems  such  as
+       o   Other  implementations  of  tput  on  SVr4-based  systems  such  as
            Solaris, IRIX64 and HPUX as well as others such as  AIX  and  Tru64
-           provide support for capname operands.
+           provide support for capname operands.
 
-       o   A few platforms such as FreeBSD recognize termcap names rather than
-           terminfo capability names in their respective tput commands.  Since
-           2010,  NetBSD's  tput  uses  terminfo names.  Before that, it (like
+       o   A few platforms such as FreeBSD recognize termcap names rather than
+           terminfo capability names in their respective tput commands.  Since
+           2010,  NetBSD's  tput  uses  terminfo names.  Before that, it (like
            FreeBSD) recognized termcap names.
 
-           Beginning in 2021, FreeBSD uses the ncurses  tput,  configured  for
+           Beginning in 2021, FreeBSD uses the ncurses  tput,  configured  for
            both terminfo (tested first) and termcap (as a fallback).
 
-       Because (apparently) all of the certified Unix systems support the full
+       Because (apparently) all of the certified Unix systems support the full
        set of capability names, the reasoning for documenting only a  few  may
        not be apparent.
 
-       o   X/Open  Curses Issue 7 documents tput differently, with capname and
+       o   X/Open  Curses Issue 7 documents tput differently, with capname and
            the other features used in this implementation.
 
-       o   That is, there are two standards for tput:  POSIX  (a  subset)  and
+       o   That is, there are two standards for tput:  POSIX  (a  subset)  and
            X/Open  Curses (the full implementation).  POSIX documents a subset
            to avoid the  complication  of  including  X/Open  Curses  and  the
            terminal capabilities database.
 
-       o   While  it  is  certainly  possible  to write a tput program without
+       o   While  it  is  certainly  possible  to write a tput program without
            using  curses,  none  of  the   systems   which   have   a   curses
-           implementation  provide  a  tput utility which does not provide the
-           capname feature.
+           implementation  provide  a  tput utility which does not provide the
+           capname feature.
 
        X/Open  Curses  Issue  7  (2009)  is  the  first  version  to  document
        utilities.  However that part of X/Open Curses does not follow existing
        practice (i.e., Unix features documented in SVID 3):
 
-       o   It assigns exit code 4 to "invalid operand", which may be the  same
-           as  unknown capability.  For instance, the source code for Solaris'
+       o   It assigns exit code 4 to "invalid operand", which may be the  same
+           as  unknown capability.  For instance, the source code for Solaris'
            xcurses uses the term "invalid" in this case.
 
-       o   It assigns exit  code  255  to  a  numeric  variable  that  is  not
+       o   It assigns exit  code  255  to  a  numeric  variable  that  is  not
            specified in the terminfo database.  That likely is a documentation
-           error, confusing the -1 written  to  the  standard  output  for  an
+           error, confusing the -1 written  to  the  standard  output  for  an
            absent or cancelled numeric value versus an (unsigned) exit code.
 
        The  various  Unix systems (AIX, HPUX, Solaris) use the same exit-codes
@@ -524,13 +524,13 @@

                                  SEE ALSO

                                  -       clear(1), stty(1), tabs(1), tset(1), curs_termcap(3x), terminfo(5).
+       clear(1), stty(1), tabs(1), tset(1), curs_termcap(3X), terminfo(5).
 
-       This describes ncurses version 6.2 (patch 20210522).
+       This describes ncurses version 6.2 (patch 20210612).
 
 
 
-                                                                       tput(1)
+                                                                       tput(1)
                                    diff --git a/doc/html/man/tset.1.html b/doc/html/man/tset.1.html index a9526433..72a31023 100644 --- a/doc/html/man/tset.1.html +++ b/doc/html/man/tset.1.html @@ -1,6 +1,6 @@ - -tset 1 +@TSET@ 1 -

                                    tset 1

                                    +

                                    @TSET@ 1

                                    -tset(1)                     General Commands Manual                    tset(1)
+tset(1)                     General Commands Manual                    tset(1)

                                    NAME

                                    -       tset, reset - terminal initialization
+       tset, reset - terminal initialization

                                    SYNOPSIS

                                    -       tset [-IQVcqrsw] [-] [-e ch] [-i ch] [-k ch] [-m mapping] [terminal]
-       reset [-IQVcqrsw] [-] [-e ch] [-i ch] [-k ch] [-m mapping] [terminal]
+       tset [-IQVcqrsw] [-] [-e ch] [-i ch] [-k ch] [-m mapping] [terminal]
+       reset [-IQVcqrsw] [-] [-e ch] [-i ch] [-k ch] [-m mapping] [terminal]

                                    DESCRIPTION

                                    @@ -60,36 +60,36 @@

                                    tset - initialization

                                            This program initializes terminals.
 
-       First,  tset  retrieves  the  current  terminal  mode settings for your
+       First,  tset  retrieves  the  current  terminal  mode settings for your
        terminal.  It does this by successively testing
 
-       o   the standard error,
+       o   the standard error,
 
-       o   standard output,
+       o   standard output,
 
-       o   standard input and
+       o   standard input and
 
-       o   ultimately "/dev/tty"
+       o   ultimately "/dev/tty"
 
-       to obtain terminal settings.  Having  retrieved  these  settings,  tset
+       to obtain terminal settings.  Having  retrieved  these  settings,  tset
        remembers which file descriptor to use when updating settings.
 
-       Next,  tset  determines  the type of terminal that you are using.  This
+       Next,  tset  determines  the type of terminal that you are using.  This
        determination is done as follows, using the first terminal type found.
 
-       1. The terminal argument specified on the command line.
+       1. The terminal argument specified on the command line.
 
-       2. The value of the TERM environmental variable.
+       2. The value of the TERM environmental variable.
 
        3. (BSD systems only.) The terminal type associated with  the  standard
-       error  output  device  in the /etc/ttys file.  (On System-V-like UNIXes
-       and systems using that convention, getty does this job by setting  TERM
-       according to the type passed to it by /etc/inittab.)
+       error  output  device  in the /etc/ttys file.  (On System-V-like UNIXes
+       and systems using that convention, getty does this job by setting  TERM
+       according to the type passed to it by /etc/inittab.)
 
        4. The default terminal type, "unknown".
 
-       If  the  terminal  type  was  not specified on the command-line, the -m
-       option mappings are then applied (see the section TERMINAL TYPE MAPPING
+       If  the  terminal  type  was  not specified on the command-line, the -m
+       option mappings are then applied (see the section TERMINAL TYPE MAPPING
        for  more  information).   Then,  if  the  terminal  type begins with a
        question mark ("?"), the user  is  prompted  for  confirmation  of  the
        terminal  type.   An empty response confirms the type, or, another type
@@ -100,111 +100,111 @@
 
        Once the terminal description is retrieved,
 
-       o   if  the  "-w"  option  is  enabled,  tset may update the terminal's
+       o   if  the  "-w"  option  is  enabled,  tset may update the terminal's
            window size.
 
            If the window size cannot be obtained from  the  operating  system,
-           but  the  terminal  description  (or  environment,  e.g., LINES and
-           COLUMNS variables specify this), use  this  to  set  the  operating
+           but  the  terminal  description  (or  environment,  e.g., LINES and
+           COLUMNS variables specify this), use  this  to  set  the  operating
            system's notion of the window size.
 
-       o   if  the  "-c"  option is enabled, the backspace, interrupt and line
+       o   if  the  "-c"  option is enabled, the backspace, interrupt and line
            kill characters (among many other things) are set
 
-       o   unless  the  "-I"  option  is  enabled,  the   terminal   and   tab
-           initialization  strings  are sent to the standard error output, and
-           tset waits one second (in case a hardware reset was issued).
+       o   unless  the  "-I"  option  is  enabled,  the   terminal   and   tab
+           initialization  strings  are sent to the standard error output, and
+           tset waits one second (in case a hardware reset was issued).
 
-       o   Finally, if the erase, interrupt  and  line  kill  characters  have
+       o   Finally, if the erase, interrupt  and  line  kill  characters  have
            changed,  or  are not set to their default values, their values are
            displayed to the standard error output.

                                    reset - reinitialization

                                    -       When invoked as reset, tset sets the terminal modes to "sane" values:
+       When invoked as reset, tset sets the terminal modes to "sane" values:
 
-       o   sets cooked and echo modes,
+       o   sets cooked and echo modes,
 
-       o   turns off cbreak and raw modes,
+       o   turns off cbreak and raw modes,
 
-       o   turns on newline translation and
+       o   turns on newline translation and
 
-       o   resets any unset special characters to their default values
+       o   resets any unset special characters to their default values
 
        before doing the terminal initialization described above.  Also, rather
-       than  using  the  terminal initialization strings, it uses the terminal
-       reset strings.
+       than  using  the  terminal initialization strings, it uses the terminal
+       reset strings.
 
-       The reset command is useful after a program dies leaving a terminal  in
+       The reset command is useful after a program dies leaving a terminal  in
        an abnormal state:
 
-       o   you may have to type
+       o   you may have to type
 
-               <LF>reset<LF>
+               <LF>reset<LF>
 
            (the line-feed character is normally control-J) to get the terminal
            to work, as carriage-return may no  longer  work  in  the  abnormal
            state.
 
-       o   Also, the terminal will often not echo the command.
+       o   Also, the terminal will often not echo the command.

                                    OPTIONS

                                            The options are as follows:
 
-       -c   Set control characters and modes.
+       -c   Set control characters and modes.
 
-       -e   Set the erase character to ch.
+       -e   Set the erase character to ch.
 
-       -I   Do  not  send  the  terminal  or tab initialization strings to the
+       -I   Do  not  send  the  terminal  or tab initialization strings to the
             terminal.
 
-       -i   Set the interrupt character to ch.
+       -i   Set the interrupt character to ch.
 
-       -k   Set the line kill character to ch.
+       -k   Set the line kill character to ch.
 
-       -m   Specify a mapping from a port type to a terminal.  See the section
-            TERMINAL TYPE MAPPING for more information.
+       -m   Specify a mapping from a port type to a terminal.  See the section
+            TERMINAL TYPE MAPPING for more information.
 
-       -Q   Do  not  display any values for the erase, interrupt and line kill
-            characters.   Normally  tset  displays  the  values  for   control
+       -Q   Do  not  display any values for the erase, interrupt and line kill
+            characters.   Normally  tset  displays  the  values  for   control
             characters which differ from the system's default values.
 
-       -q   The  terminal  type  is  displayed to the standard output, and the
+       -q   The  terminal  type  is  displayed to the standard output, and the
             terminal is not initialized in any way.  The option "-" by  itself
             is equivalent but archaic.
 
-       -r   Print the terminal type to the standard error output.
+       -r   Print the terminal type to the standard error output.
 
-       -s   Print the sequence of shell commands to initialize the environment
-            variable TERM to the standard output.  See the section SETTING THE
-            ENVIRONMENT for details.
+       -s   Print the sequence of shell commands to initialize the environment
+            variable TERM to the standard output.  See the section SETTING THE
+            ENVIRONMENT for details.
 
-       -V   reports the version of ncurses which was used in this program, and
+       -V   reports the version of ncurses which was used in this program, and
             exits.
 
-       -w   Resize the window to match the  size  deduced  via  setupterm(3x).
-            Normally  this  has  no  effect,  unless  setupterm is not able to
+       -w   Resize the window to match the  size  deduced  via  setupterm(3X).
+            Normally  this  has  no  effect,  unless  setupterm is not able to
             detect the window size.
 
-       The arguments for the -e, -i, and -k options may either be  entered  as
+       The arguments for the -e, -i, and -k options may either be  entered  as
        actual  characters  or by using the "hat" notation, i.e., control-h may
        be specified as "^H" or "^h".
 
-       If neither -c or -w is given, both options are assumed.
+       If neither -c or -w is given, both options are assumed.

                                    SETTING THE ENVIRONMENT

                                            It is often desirable to enter the terminal type and information  about
        the terminal's capabilities into the shell's environment.  This is done
-       using the -s option.
+       using the -s option.
 
-       When the -s option is specified, the commands to enter the  information
+       When the -s option is specified, the commands to enter the  information
        into  the  shell's  environment are written to the standard output.  If
-       the SHELL environmental variable ends in "csh", the  commands  are  for
-       csh,  otherwise, they are for sh.  Note, the csh commands set and unset
-       the shell variable noglob, leaving it unset.  The following line in the
-       .login or .profile files will initialize the environment correctly:
+       the SHELL environmental variable ends in "csh", the  commands  are  for
+       csh,  otherwise, they are for sh.  Note, the csh commands set and unset
+       the shell variable noglob, leaving it unset.  The following line in the
+       .login or .profile files will initialize the environment correctly:
 
            eval `tset -s options ... `
 
@@ -212,16 +212,16 @@

                                    TERMINAL TYPE MAPPING

                                            When  the  terminal  is  not  hardwired into the system (or the current
        system information is incorrect) the terminal  type  derived  from  the
-       /etc/ttys  file  or  the TERM environmental variable is often something
-       generic like network, dialup, or unknown.   When  tset  is  used  in  a
+       /etc/ttys  file  or  the TERM environmental variable is often something
+       generic like network, dialup, or unknown.   When  tset  is  used  in  a
        startup  script  it is often desirable to provide information about the
        type of terminal used on such ports.
 
-       The -m options maps from some set of conditions  to  a  terminal  type,
-       that is, to tell tset "If I'm on this port at a particular speed, guess
+       The -m options maps from some set of conditions  to  a  terminal  type,
+       that is, to tell tset "If I'm on this port at a particular speed, guess
        that I'm on that kind of terminal".
 
-       The argument to the -m option consists of an  optional  port  type,  an
+       The argument to the -m option consists of an  optional  port  type,  an
        optional  operator,  an  optional  baud rate specification, an optional
        colon (":") character and a terminal type.  The port type is  a  string
        (delimited  by  either  the  operator  or  the  colon  character).  The
@@ -231,149 +231,149 @@
        compared  with  the speed of the standard error output (which should be
        the control terminal).  The terminal type is a string.
 
-       If the terminal type is not specified  on  the  command  line,  the  -m
+       If the terminal type is not specified  on  the  command  line,  the  -m
        mappings  are  applied to the terminal type.  If the port type and baud
        rate match the mapping, the terminal  type  specified  in  the  mapping
        replaces  the current type.  If more than one mapping is specified, the
        first applicable mapping is used.
 
-       For example, consider the following  mapping:  dialup>9600:vt100.   The
+       For example, consider the following  mapping:  dialup>9600:vt100.   The
        port type is dialup , the operator is >, the baud rate specification is
        9600, and the terminal type is vt100.  The result of this mapping is to
-       specify  that  if  the  terminal  type  is dialup, and the baud rate is
-       greater than 9600 baud, a terminal type of vt100 will be used.
+       specify  that  if  the  terminal  type  is dialup, and the baud rate is
+       greater than 9600 baud, a terminal type of vt100 will be used.
 
        If no baud rate is specified, the terminal type  will  match  any  baud
        rate.   If  no port type is specified, the terminal type will match any
-       port type.  For example, -m dialup:vt100  -m  :?xterm  will  cause  any
+       port type.  For example, -m dialup:vt100  -m  :?xterm  will  cause  any
        dialup port, regardless of baud rate, to match the terminal type vt100,
        and any non-dialup port type to match the terminal type ?xterm.   Note,
        because  of  the  leading  question mark, the user will be queried on a
        default port as to whether they are actually using an xterm terminal.
 
-       No whitespace characters are  permitted  in  the  -m  option  argument.
+       No whitespace characters are  permitted  in  the  -m  option  argument.
        Also,  to avoid problems with meta-characters, it is suggested that the
-       entire -m option argument be placed within single quote characters, and
-       that   csh   users  insert  a  backslash  character  ("\")  before  any
+       entire -m option argument be placed within single quote characters, and
+       that   csh   users  insert  a  backslash  character  ("\")  before  any
        exclamation marks ("!").

                                    HISTORY

                                    -       A reset command appeared in 2BSD (April 1979), written by Kurt  Shoens.
-       This  program set the erase and kill characters to ^H (backspace) and @
+       A reset command appeared in 2BSD (April 1979), written by Kurt  Shoens.
+       This  program set the erase and kill characters to ^H (backspace) and @
        respectively.  Mark Horton improved that in 3BSD (October 1979), adding
-       intr,  quit,  start/stop  and  eof  characters  as well as changing the
+       intr,  quit,  start/stop  and  eof  characters  as well as changing the
        program to avoid modifying any user settings.
 
-       Later in 4.1BSD (December 1980), Mark Horton added a call to  the  tset
-       program  using  the  -I and -Q options, i.e., using that to improve the
-       terminal modes.  With those options, that version of reset did not  use
+       Later in 4.1BSD (December 1980), Mark Horton added a call to  the  tset
+       program  using  the  -I and -Q options, i.e., using that to improve the
+       terminal modes.  With those options, that version of reset did not  use
        the termcap database.
 
-       A separate tset command was provided in 2BSD by Eric Allman.  While the
-       oldest published source (from  1979)  provides  both  tset  and  reset,
+       A separate tset command was provided in 2BSD by Eric Allman.  While the
+       oldest published source (from  1979)  provides  both  tset  and  reset,
        Allman's  comments  in the 2BSD source code indicate that he began work
        in October 1977, continuing development over the next few years.
 
-       In September 1980, Eric Allman modified tset, adding the code from  the
-       existing  "reset"  feature when tset was invoked as reset.  Rather than
-       simply copying the existing program, in this merged version, tset  used
+       In September 1980, Eric Allman modified tset, adding the code from  the
+       existing  "reset"  feature when tset was invoked as reset.  Rather than
+       simply copying the existing program, in this merged version, tset  used
        the  termcap  database  to  do  additional  (re)initialization  of  the
        terminal.  This version appeared in 4.1cBSD, late in 1982.
 
        Other developers (e.g., Keith Bostic and Jim Bloom) continued to modify
-       tset until 4.4BSD was released in 1993.
+       tset until 4.4BSD was released in 1993.
 
-       The  ncurses implementation was lightly adapted from the 4.4BSD sources
+       The  ncurses implementation was lightly adapted from the 4.4BSD sources
        for a terminfo environment by Eric S. Raymond <esr@snark.thyrsus.com>.

                                    COMPATIBILITY

                                            Neither IEEE Std 1003.1/The Open  Group  Base  Specifications  Issue  7
-       (POSIX.1-2008) nor X/Open Curses Issue 7 documents tset or reset.
+       (POSIX.1-2008) nor X/Open Curses Issue 7 documents tset or reset.
 
-       The  AT&T  tput utility (AIX, HPUX, Solaris) incorporated the terminal-
+       The  AT&T  tput utility (AIX, HPUX, Solaris) incorporated the terminal-
        mode manipulation as well as termcap-based features such  as  resetting
-       tabstops  from  tset  in  BSD  (4.1c), presumably with the intention of
-       making tset obsolete.  However, each of those  systems  still  provides
-       tset.   In fact, the commonly-used reset utility is always an alias for
-       tset.
+       tabstops  from  tset  in  BSD  (4.1c), presumably with the intention of
+       making tset obsolete.  However, each of those  systems  still  provides
+       tset.   In fact, the commonly-used reset utility is always an alias for
+       tset.
 
-       The  tset  utility  provides  for   backward-compatibility   with   BSD
-       environments  (under  most modern UNIXes, /etc/inittab and getty(1) can
-       set TERM appropriately for each dial-up line; this  obviates  what  was
-       tset's  most  important  use).  This implementation behaves like 4.4BSD
-       tset, with a few exceptions specified here.
+       The  tset  utility  provides  for   backward-compatibility   with   BSD
+       environments  (under  most modern UNIXes, /etc/inittab and getty(1) can
+       set TERM appropriately for each dial-up line; this  obviates  what  was
+       tset's  most  important  use).  This implementation behaves like 4.4BSD
+       tset, with a few exceptions specified here.
 
-       A few options are different because the TERMCAP variable is  no  longer
-       supported under terminfo-based ncurses:
+       A few options are different because the TERMCAP variable is  no  longer
+       supported under terminfo-based ncurses:
 
-       o   The  -S  option  of  BSD  tset  no longer works; it prints an error
+       o   The  -S  option  of  BSD  tset  no longer works; it prints an error
            message to the standard error and dies.
 
-       o   The -s option only sets TERM, not TERMCAP.
+       o   The -s option only sets TERM, not TERMCAP.
 
-       There was an undocumented 4.4BSD feature that invoking tset via a  link
+       There was an undocumented 4.4BSD feature that invoking tset via a  link
        named  "TSET"  (or  via  any  other  name  beginning with an upper-case
        letter) set the terminal to use upper-case only.  This feature has been
        omitted.
 
-       The -A, -E, -h, -u and -v options were deleted from the tset utility in
+       The -A, -E, -h, -u and -v options were deleted from the tset utility in
        4.4BSD.  None of them were documented in 4.3BSD and all are of  limited
-       utility  at  best.   The  -a,  -d,  and  -p  options  are similarly not
+       utility  at  best.   The  -a,  -d,  and  -p  options  are similarly not
        documented or useful, but  were  retained  as  they  appear  to  be  in
        widespread  use.   It  is  strongly recommended that any usage of these
-       three options be changed to use the -m option instead.  The -a, -d, and
-       -p options are therefore omitted from the usage summary above.
+       three options be changed to use the -m option instead.  The -a, -d, and
+       -p options are therefore omitted from the usage summary above.
 
        Very  old  systems,  e.g., 3BSD, used a different terminal driver which
        was replaced in 4BSD in the early 1980s.  To  accommodate  these  older
-       systems,  the  4BSD  tset  provided a -n option to specify that the new
+       systems,  the  4BSD  tset  provided a -n option to specify that the new
        terminal driver should be used.  This implementation does  not  provide
        that choice.
 
-       It  is  still permissible to specify the -e, -i, and -k options without
+       It  is  still permissible to specify the -e, -i, and -k options without
        arguments, although it is strongly recommended that such usage be fixed
        to explicitly specify the character.
 
-       As  of 4.4BSD, executing tset as reset no longer implies the -Q option.
-       Also, the interaction between the - option and the terminal argument in
-       some historic implementations of tset has been removed.
+       As  of 4.4BSD, executing tset as reset no longer implies the -Q option.
+       Also, the interaction between the - option and the terminal argument in
+       some historic implementations of tset has been removed.
 
-       The  -c  and  -w  options  are  not  found  in earlier implementations.
+       The  -c  and  -w  options  are  not  found  in earlier implementations.
        However, a different window size-change feature was provided in 4.4BSD.
 
-       o   In 4.4BSD, tset uses the window size from the  termcap  description
-           to  set  the  window  size if tset is not able to obtain the window
+       o   In 4.4BSD, tset uses the window size from the  termcap  description
+           to  set  the  window  size if tset is not able to obtain the window
            size from the operating system.
 
-       o   In ncurses, tset obtains the window size using setupterm, which may
-           be  from  the  operating  system, the LINES and COLUMNS environment
+       o   In ncurses, tset obtains the window size using setupterm, which may
+           be  from  the  operating  system, the LINES and COLUMNS environment
            variables or the terminal description.
 
        Obtaining the window size from the terminal description  is  common  to
        both  implementations,  but considered obsolescent.  Its only practical
        use is for hardware terminals.  Generally speaking, a window size would
        be  unset  only if there were some problem obtaining the value from the
-       operating system (and setupterm would still fail).   For  that  reason,
-       the  LINES  and COLUMNS environment variables may be useful for working
+       operating system (and setupterm would still fail).   For  that  reason,
+       the  LINES  and COLUMNS environment variables may be useful for working
        around window-size problems.  Those  have  the  drawback  that  if  the
        window  is  resized, those variables must be recomputed and reassigned.
-       To do this more easily, use the resize(1) program.
+       To do this more easily, use the resize(1) program.

                                    ENVIRONMENT

                                    -       The tset command uses these environment variables:
+       The tset command uses these environment variables:
 
        SHELL
-            tells tset whether to initialize TERM using sh or csh syntax.
+            tells tset whether to initialize TERM using sh or csh syntax.
 
        TERM Denotes your terminal  type.   Each  terminal  type  is  distinct,
             though many are similar.
 
        TERMCAP
             may  denote  the  location of a termcap database.  If it is not an
-            absolute pathname, e.g., begins  with  a  "/",  tset  removes  the
+            absolute pathname, e.g., begins  with  a  "/",  tset  removes  the
             variable  from  the  environment  before  looking for the terminal
             description.
 
@@ -388,14 +388,14 @@

                                    SEE ALSO

                                    -       csh(1),   sh(1),   stty(1),   curs_terminfo(3x),  tty(4),  terminfo(5),
-       ttys(5), environ(7)
+       csh(1),   sh(1),   stty(1),   curs_terminfo(3X),  tty(4),  terminfo(5),
+       ttys(5), environ(7)
 
-       This describes ncurses version 6.2 (patch 20210522).
+       This describes ncurses version 6.2 (patch 20210612).
 
 
 
-                                                                       tset(1)
+                                                                       tset(1)
                                      diff --git a/doc/html/man/user_caps.5.html b/doc/html/man/user_caps.5.html index ce284d30..f241ea03 100644 --- a/doc/html/man/user_caps.5.html +++ b/doc/html/man/user_caps.5.html @@ -1,6 +1,6 @@ - @@ -41,7 +41,7 @@

                                      user_caps 5

                                      -user_caps(5)                  File Formats Manual                 user_caps(5)
+user_caps(5)                  File Formats Manual                 user_caps(5)
 
 
 
@@ -51,40 +51,40 @@

                                      SYNOPSIS

                                      -       tic -x, infocmp -x
+       tic -x, infocmp -x

                                      DESCRIPTION

                                      Background

                                      -       Before  ncurses  5.0,  terminfo  databases  used  a fixed repertoire of
+       Before  ncurses  5.0,  terminfo  databases  used  a fixed repertoire of
        terminal capabilities designed for the SVr2 terminal database in  1984,
        and  extended  in  stages  through SVr4 (1989), and standardized in the
        Single Unix Specification beginning in 1995.
 
-       Most of the extensions in this fixed repertoire were additions  to  the
+       Most of the extensions in this fixed repertoire were additions  to  the
        tables of boolean, numeric and string capabilities.  Rather than change
        the meaning of an existing capability,  a  new  name  was  added.   The
        terminfo  database  uses  a  binary  format;  binary  compatibility was
        ensured by using a header which gave the number of items in the  tables
        for each type of capability.  The standardization was incomplete:
 
-       o   The  binary  format  itself  is  not described in the X/Open Curses
-           documentation.  Only the source format is described.
+       o   The  binary  format  itself  is  not described in the X/Open Curses
+           documentation.  Only the source format is described.
 
            Library developers rely upon the SVr4 documentation,  and  reverse-
            engineering the compiled terminfo files to match the binary format.
 
-       o   Lacking a standard for the binary format, most implementations copy
+       o   Lacking a standard for the binary format, most implementations copy
            the SVr2 binary format, which uses 16-bit signed integers,  and  is
            limited to 4096-byte entries.
 
            The  format  cannot  represent very large numeric capabilities, nor
            can it represent large numbers of special keyboard definitions.
 
-       o   The tables of capability names differ between implementations.
+       o   The tables of capability names differ between implementations.
 
-           Although they may provide all of the standard capability names, the
+           Although they may provide all of the standard capability names, 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.
@@ -95,7 +95,7 @@
            configured with tables which match the terminal databases for  AIX,
            HP-UX or OSF/1, rather than the default Solaris-like configuration.
 
-       o   In  SVr4  curses  and  ncurses, the terminal database is defined at
+       o   In  SVr4  curses  and  ncurses, the terminal database is defined at
            compile-time using a text file which lists the  different  terminal
            capabilities.
 
@@ -115,60 +115,60 @@
                     (box1) box characters primary set
 
            The memory lock/unlock capabilities were included because they were
-           used in  the  X11R6  terminal  description  for  xterm.   The  box1
+           used in  the  X11R6  terminal  description  for  xterm.   The  box1
            capability  is  used  in  tic  to  help  with terminal descriptions
            written for AIX.
 
        During the 1990s, some users were reluctant to use terminfo in spite of
        its performance advantages over termcap:
 
-       o   The  fixed  repertoire  prevented  users  from  adding features for
+       o   The  fixed  repertoire  prevented  users  from  adding features for
            unanticipated terminal improvements  (or  required  them  to  reuse
            existing capabilities as a workaround).
 
-       o   The  limitation  to  16-bit  signed  integers  was  also mentioned.
+       o   The  limitation  to  16-bit  signed  integers  was  also mentioned.
            Because termcap stores everything as a string, it  could  represent
            larger numbers.
 
        Although  termcap's  extensibility  was  rarely  used (it was never the
-       speaker who had actually used the feature), the criticism had a  point.
+       speaker who had actually used the feature), the criticism had a  point.
        ncurses   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 user-defined capabilities because no modifications to the  toolset's
+       as user-defined capabilities because no modifications to the  toolset's
        predefined capability names are needed.
 
-       The  ncurses  utilities tic and infocmp have a command-line option "-x"
+       The  ncurses  utilities tic and infocmp have a command-line option "-x"
        to  control  whether  the  nonstandard  capabilities  are   stored   or
-       retrieved.   A  library function use_extended_names is provided for the
+       retrieved.   A  library function use_extended_names is provided for the
        same purpose.
 
-       When compiling a terminal database, if "-x" is set, tic  will  store  a
+       When compiling a terminal database, if "-x" is set, tic  will  store  a
        user-defined  capability  if  the  capability  name  is  not one of the
        predefined names.
 
        Because ncurses provides  a  termcap  library  interface,  these  user-
        defined capabilities may be visible to termcap applications:
 
-       o   The   termcap  interface  (like  all  implementations  of  termcap)
+       o   The   termcap  interface  (like  all  implementations  of  termcap)
            requires that the capability names are 2-characters.
 
            When  the  capability  is  simple  enough  for  use  in  a  termcap
            application, it is provided as a 2-character name.
 
-       o   There  are  other user-defined capabilities which refer to features
+       o   There  are  other user-defined capabilities which refer to features
            not usable in termcap, e.g., parameterized strings  that  use  more
            than two parameters or use more than the trivial expression support
            provided by termcap.  For these, the terminfo database should  have
            only capability names with 3 or more characters.
 
-       o   Some terminals can send distinct strings for special keys (cursor-,
+       o   Some terminals can send distinct strings for special keys (cursor-,
            keypad-  or  function-keys)  depending  on  modifier  keys  (shift,
            control,  etc.).   While  terminfo  and  termcap  have  a set of 60
            predefined function-key names, 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  xterm to provide
+           ncurses  database  uses  a  convention  based  on  xterm to provide
            extended special-key names.
 
            Fitting that into termcap's limitation of 2-character  names  would
@@ -181,28 +181,28 @@
        terminfo  database  may  have  other extensions, ncurses makes explicit
        checks for these:
 
-          AX boolean, asserts that the terminal interprets SGR 39 and  SGR  49
+          AX boolean, asserts that the terminal interprets SGR 39 and  SGR  49
              by  resetting  the foreground and background color, respectively,
              to the default.
 
-             This is a feature recognized by the screen program as well.
+             This is a feature recognized by the screen program as well.
 
-          E3 string, tells how to  clear  the  terminal's  scrollback  buffer.
-             When present, the clear(1) program sends this before clearing the
+          E3 string, tells how to  clear  the  terminal's  scrollback  buffer.
+             When present, the clear(1) program sends this before clearing the
              terminal.
 
-             The command "tput clear" does the same thing.
+             The command "tput clear" does the same thing.
 
           RGB
-             boolean, number or string, to assert  that  the  set_a_foreground
-             and  set_a_background  capabilities  correspond to direct colors,
+             boolean, number or string, to assert  that  the  set_a_foreground
+             and  set_a_background  capabilities  correspond to direct colors,
              using an RGB (red/green/blue) convention.  This capability allows
-             the  color_content  function to return appropriate values without
-             requiring the application to initialize colors using init_color.
+             the  color_content  function to return appropriate values without
+             requiring the application to initialize colors using init_color.
 
              The capability type determines the values which ncurses sees:
 
-             boolean
+             boolean
                 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,
@@ -212,50 +212,50 @@
                 multiple of three, the blue (and  green)  components  lose  in
                 comparison to red.
 
-             number
+             number
                 tells  ncurses  what result to add to red, green and blue.  If
                 ncurses runs out of bits, blue (and green) lose just as in the
-                boolean case.
+                boolean case.
 
-             string
+             string
                 explicitly  list  the  number  of bits used for red, green and
                 blue components as a slash-separated list of decimal integers.
 
              Because there are several  RGB  encodings  in  use,  applications
              which  make  assumptions  about  the number of bits per color are
              unlikely to work reliably.  As a trivial case, for  example,  one
-             could  define  RGB#1 to represent the standard eight ANSI colors,
+             could  define  RGB#1 to represent the standard eight ANSI colors,
              i.e., one bit per color.
 
-          U8 number, asserts that ncurses must use Unicode  values  for  line-
+          U8 number, asserts that ncurses 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 NCURSES_NO_UTF8_ACS
-             in ncurses(3x).
+             For  more  information, see the discussion of NCURSES_NO_UTF8_ACS
+             in ncurses(3X).
 
              Set this capability to a nonzero value to enable it.
 
-          XM string, override ncurses's built-in string which enables/disables
-             xterm mouse mode.
+          XM string, override ncurses's built-in string which enables/disables
+             xterm mouse mode.
 
              ncurses  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.
 
-             The mouse protocol  is  enabled  when  the  mask  passed  in  the
-             mousemask  function  is nonzero.  By default, ncurses handles the
+             The mouse protocol  is  enabled  when  the  mask  passed  in  the
+             mousemask  function  is nonzero.  By default, ncurses handles the
              responses for the X11 xterm mouse protocol.  It also knows  about
-             the  SGR  1006  xterm mouse protocol, but must to be told to look
+             the  SGR  1006  xterm mouse protocol, but must to be told to look
              for this specifically.  It will not be able to guess  which  mode
              is  used,  because  the  responses  are  enough  alike  that only
              confusion would result.
 
-             The XM capability has a single parameter.  If nonzero, the  mouse
+             The XM 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,
              to  see whether the 1006 protocol is used.  If so, it expects the
-             responses to use the SGR 1006 xterm mouse protocol.
+             responses to use the SGR 1006 xterm mouse protocol.
 
              The xterm mouse protocol is used  by  other  terminal  emulators.
              The  terminal database uses building-blocks for the various xterm
@@ -263,29 +263,29 @@
              descriptions.
 
              The terminal database building blocks for this mouse feature also
-             have  an  experimental  capability  xm.   The   "xm"   capability
+             have  an  experimental  capability  xm.   The   "xm"   capability
              describes  the mouse response.  Currently there is no interpreter
              which would use  this  information  to  make  the  mouse  support
              completely data-driven.
 
-             xm shows the format of the mouse responses.  In this experimental
+             xm shows the format of the mouse responses.  In this experimental
              capability, the parameters are
 
-               p1   y-ordinate
+               p1   y-ordinate
 
-               p2   x-ordinate
+               p2   x-ordinate
 
-               p3   button
+               p3   button
 
-               p4   state, e.g., pressed or released
+               p4   state, e.g., pressed or released
 
-               p5   y-ordinate starting region
+               p5   y-ordinate starting region
 
-               p6   x-ordinate starting region
+               p6   x-ordinate starting region
 
-               p7   y-ordinate ending region
+               p7   y-ordinate ending region
 
-               p8   x-ordinate ending region
+               p8   x-ordinate ending region
 
              Here are  examples  from  the  terminal  database  for  the  most
              commonly used xterm mouse protocols:
@@ -310,17 +310,17 @@
        combinations of modified special keys.  There is no standard  for  what
        those keys can send.
 
-       Since 1999, xterm has supported shift, control, alt, and meta modifiers
+       Since 1999, xterm has supported shift, control, alt, and meta modifiers
        which produce distinct special-key strings.  In a terminal description,
        ncurses  has  no special knowledge of the modifiers used.  Applications
-       can use the naming convention  established  for  xterm  to  find  these
+       can use the naming convention  established  for  xterm  to  find  these
        special keys in the terminal description.
 
-       Starting  with  the curses convention that key names begin with "k" and
+       Starting  with  the curses convention that key names begin with "k" and
        that shifted special keys are  an  uppercase  name,  ncurses'  terminal
        database defines these names to which a suffix is added:
 
-            Name   Description
+            Name   Description
             ---------------------------------------------------------------
             kDC    special form of kdch1 (delete character)
             kDN    special form of kcud1 (cursor down)
@@ -334,7 +334,7 @@
 
        These are the suffixes used to denote the modifiers:
 
-            Value   Description
+            Value   Description
             ----------------------------------
             2       Shift
             3       Alt
@@ -352,32 +352,32 @@
             15      Meta + Ctrl + Alt
             16      Meta + Ctrl + Alt + Shift
 
-       None  of these are predefined; terminal descriptions can refer to names
-       which ncurses will allocate at runtime to key-codes.  To use these keys
+       None  of these are predefined; terminal descriptions can refer to names
+       which ncurses will allocate at runtime to key-codes.  To use these keys
        in an ncurses program, an application could do this:
 
-       o   using  a  list  of  extended  key names, ask tigetstr(3x) for their
+       o   using  a  list  of  extended  key names, ask tigetstr(3X) for their
            values, and
 
-       o   given the list of values,  ask  key_defined(3x)  for  the  key-code
-           which would be returned for those keys by wgetch(3x).
+       o   given the list of values,  ask  key_defined(3X)  for  the  key-code
+           which would be returned for those keys by wgetch(3X).

                                      PORTABILITY

                                      -       The  "-x"  extension  feature  of  tic  and infocmp has been adopted in
+       The  "-x"  extension  feature  of  tic  and infocmp has been adopted in
        NetBSD curses.  That implementation stores  user-defined  capabilities,
        but makes no use of these capabilities itself.

                                      SEE ALSO

                                      -       infocmp(1m), tic(1m).
+       infocmp(1M), tic(1M).
 
-       The  terminal  database  section  NCURSES  USER-DEFINABLE  CAPABILITIES
+       The  terminal  database  section  NCURSES  USER-DEFINABLE  CAPABILITIES
        summarizes commonly-used user-defined capabilities which  are  used  in
        the  terminal  descriptions.   Some  of those features are mentioned in
-       screen(1) or tmux(1).
+       screen(1) or tmux(1).
 
-       XTerm Control Sequences  provides  further  information  on  the  xterm
+       XTerm Control Sequences  provides  further  information  on  the  xterm
        features which are used in these extended capabilities.
 
 
@@ -387,7 +387,7 @@
 
 
 
-                                                                  user_caps(5)
+                                                                  user_caps(5)
                                        diff --git a/doc/html/man/wresize.3x.html b/doc/html/man/wresize.3x.html index 8ddc39bb..d1f3f9be 100644 --- a/doc/html/man/wresize.3x.html +++ b/doc/html/man/wresize.3x.html @@ -1,4 +1,4 @@ -