@@ -374,7 +374,7 @@
---------------------------------------------------------------------
0 (capname is a numeric variable that is not specified in
the terminfo(5) database for this terminal type, e.g.
- tput-T450lines and tput-T2621xmc)
+ tput-T450lines and tput-Thp2621xmc)
1 no error message is printed, see the EXITCODES section.
2 usage error
3 unknown terminal type or no terminfo database
@@ -399,14 +399,14 @@
incorporated from the reset feature of BSD tset written by Eric
Allman.
- o SVr4 added color initialization using the orig_colors and
- orig_pairs capabilities in the init subcommand.
+ o SVr4 added color initialization using the orig_colors and orig_pair
+ capabilities in the init subcommand.
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 termcapnames for other
+ 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.
@@ -443,14 +443,14 @@
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.
+ to open a terminal, e.g., when running in cron(1), tput will return
+ an error.
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
+ 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.
@@ -458,6 +458,14 @@
for the standard capname operands, and an internal library function
to analyze nonstandard capname operands.
+ Besides providing more reliable operation than AT&T's utility, a
+ portability problem is introduced by this analysis: An OpenBSD
+ developer adapted the internal library function from ncurses to
+ port NetBSD's termcap-based tput to terminfo. That had been
+ modified to interpret multiple commands on a line. Portable
+ applications should not rely upon this feature; ncurses provides it
+ to support applications written specifically for OpenBSD.
+
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
@@ -537,7 +545,7 @@