X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_terminfo.3x.html;h=11c211d9ec260c7c664049a53f044974284d6c45;hp=b54484cb865e83cde20256e17582a39554405fc7;hb=643ec2bf782cd02efafe3ccdeaea8920a404645e;hpb=9b51794524995304d8788e42aacb36feede9364f
diff --git a/doc/html/man/curs_terminfo.3x.html b/doc/html/man/curs_terminfo.3x.html
index b54484cb..11c211d9 100644
--- a/doc/html/man/curs_terminfo.3x.html
+++ b/doc/html/man/curs_terminfo.3x.html
@@ -27,7 +27,7 @@
* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
- * @Id: curs_terminfo.3x,v 1.75 2021/06/17 21:11:08 tom Exp @
+ * @Id: curs_terminfo.3x,v 1.76 2021/09/04 19:58:03 tom Exp @
* ***************************************************************************
* ***************************************************************************
* ***************************************************************************
@@ -461,8 +461,15 @@
ters supported by tgoto).
SVr3 introduced the functions for switching between terminal descrip-
- tions, e.g., set_curterm. The various global variables such as bool-
- names were mentioned in the programming manual at this point.
+ tions, e.g., set_curterm. Some of that was incremental improvements to
+ the SVr2 library:
+
+ o The TERMINAL type definition was introduced in SVr3.01, for the
+ term structure provided in SVr2.
+
+ o The various global variables such as boolnames were mentioned in
+ the programming manual at this point, though the variables were
+ provided in SVr2.
SVr4 added the vid_attr and vid_puts functions.
@@ -476,15 +483,15 @@
X/Open notes that vidattr and vidputs may be macros.
- The function setterm is not described by X/Open and must be considered
+ The function setterm is not described by X/Open and must be considered
non-portable. All other functions are as described by X/Open.
- setupterm copies the terminal name to the array ttytype. This is not
+ setupterm copies the terminal name to the array ttytype. This is not
part of X/Open Curses, but is assumed by some applications.
- Other implementions may not declare the capability name arrays. Some
+ Other implementions may not declare the capability name arrays. Some
provide them without declaring them. X/Open does not specify them.
Extended terminal capability names, e.g., as defined by tic -x, are not
@@ -492,14 +499,14 @@
- Older versions of ncurses assumed that the file descriptor passed to
+ Older versions of ncurses assumed that the file descriptor passed to
setupterm from initscr or newterm uses buffered I/O, and would write to
- the corresponding stream. In addition to the limitation that the ter-
- minal was left in block-buffered mode on exit (like System V curses),
- it was problematic because ncurses did not allow a reliable way to
+ the corresponding stream. In addition to the limitation that the ter-
+ minal was left in block-buffered mode on exit (like System V curses),
+ it was problematic because ncurses did not allow a reliable way to
cleanup on receiving SIGTSTP.
- The current version (ncurses6) uses output buffers managed directly by
+ The current version (ncurses6) uses output buffers managed directly by
ncurses. Some of the low-level functions described in this manual page
write to the standard output. They are not signal-safe. The high-lev-
el functions in ncurses use alternate versions of these functions using
@@ -508,69 +515,69 @@
The X/Open Curses prototypes are based on the SVr4 curses header decla-
- rations, which were defined at the same time the C language was first
+ rations, which were defined at the same time the C language was first
standardized in the late 1980s.
- o X/Open Curses uses const less effectively than a later design
- might, in some cases applying it needlessly to values are already
- constant, and in most cases overlooking parameters which normally
- would use const. Using constant parameters for functions which do
+ o X/Open Curses uses const less effectively than a later design
+ might, in some cases applying it needlessly to values are already
+ constant, and in most cases overlooking parameters which normally
+ would use const. Using constant parameters for functions which do
not use const may prevent the program from compiling. On the other
hand, writable strings are an obsolescent feature.
- As an extension, this implementation can be configured to change
- the function prototypes to use the const keyword. The ncurses ABI
+ As an extension, this implementation can be configured to change
+ the function prototypes to use the const keyword. The ncurses ABI
6 enables this feature by default.
- o X/Open Curses prototypes tparm with a fixed number of parameters,
+ o X/Open Curses prototypes tparm with a fixed number of parameters,
rather than a variable argument list.
- This implementation uses a variable argument list, but can be con-
- figured to use the fixed-parameter list. Portable applications
- should provide 9 parameters after the format; zeroes are fine for
+ This implementation uses a variable argument list, but can be con-
+ figured to use the fixed-parameter list. Portable applications
+ should provide 9 parameters after the format; zeroes are fine for
this purpose.
- In response to review comments by Thomas E. Dickey, X/Open Curses
+ In response to review comments by Thomas E. Dickey, X/Open Curses
Issue 7 proposed the tiparm function in mid-2009.
If configured to use the terminal-driver, e.g., for the MinGW port,
- o setupterm interprets a missing/empty TERM variable as the special
+ o setupterm interprets a missing/empty TERM variable as the special
value "unknown".
- o setupterm allows explicit use of the the windows console driver by
- checking if $TERM is set to "#win32con" or an abbreviation of that
+ o setupterm allows explicit use of the the windows console driver by
+ checking if $TERM is set to "#win32con" or an abbreviation of that
string.
- In System V Release 4, set_curterm has an int return type and returns
+ In System V Release 4, set_curterm has an int return type and returns
OK or ERR. We have chosen to implement the X/Open Curses semantics.
- In System V Release 4, the third argument of tputs has the type int
+ In System V Release 4, the third argument of tputs has the type int
(*putc)(char).
- At least one implementation of X/Open Curses (Solaris) returns a value
- other than OK/ERR from tputs. That returns the length of the string,
+ At least one implementation of X/Open Curses (Solaris) returns a value
+ other than OK/ERR from tputs. That returns the length of the string,
and does no error-checking.
- X/Open notes that after calling mvcur, the curses state may not match
+ X/Open notes that after calling mvcur, the curses state may not match
the actual terminal state, and that an application should touch and re-
fresh the window before resuming normal curses calls. Both ncurses and
- System V Release 4 curses implement mvcur using the SCREEN data allo-
- cated in either initscr or newterm. So though it is documented as a
- terminfo function, mvcur is really a curses function which is not well
+ System V Release 4 curses implement mvcur using the SCREEN data allo-
+ cated in either initscr or newterm. So though it is documented as a
+ terminfo function, mvcur is really a curses function which is not well
specified.
- X/Open states that the old location must be given for mvcur. This im-
- plementation allows the caller to use -1's for the old ordinates. In
+ X/Open states that the old location must be given for mvcur. This im-
+ plementation allows the caller to use -1's for the old ordinates. In
that case, the old location is unknown.
- curses(3x), curs_initscr(3x), curs_kernel(3x), curs_termcap(3x),
+ curses(3x), curs_initscr(3x), curs_kernel(3x), curs_termcap(3x),
curs_variables(3x), term_variables(3x), putc(3), terminfo(5)