X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Ftput.1.html;h=bd3ff9b1977a0f16856e3a2df25468c602a9b1b1;hp=fcdaf71619ee4363a6e984769c972258ca8f5be4;hb=d30f99439fcc8d4bb4c38e5c4afb4f6555fc6ad4;hpb=61790aa3ac9e0dff2b443ac567b174fc4d235b86
diff --git a/doc/html/man/tput.1.html b/doc/html/man/tput.1.html
index fcdaf716..bd3ff9b1 100644
--- a/doc/html/man/tput.1.html
+++ b/doc/html/man/tput.1.html
@@ -1,7 +1,7 @@
@@ -483,37 +483,40 @@
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
+ both terminfo (tested first) and termcap (as a fallback).
+
Because (apparently) all of the certified Unix systems support the full
- set of capability names, the reasoning for documenting only a few may
+ 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
- X/Open Curses (the full implementation). POSIX documents a subset
- to avoid the complication of including X/Open Curses and the
+ 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
- using curses, none of the systems which have a curses
- implementation provide a tput utility which does not provide the
+ 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.
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
+ The various Unix systems (AIX, HPUX, Solaris) use the same exit-codes
as ncurses.
NetBSD curses documents different exit codes which do not correspond to
@@ -523,7 +526,7 @@
clear(1), stty(1), tabs(1), tset(1), curs_termcap(3x), terminfo(5).
- This describes ncurses version 6.2 (patch 20210102).
+ This describes ncurses version 6.2 (patch 20210403).