X-Git-Url: http://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Ftput.1.html;h=bbc22a4eeed642b453410eeb6c2c370ad3f71e57;hp=f1c67438c4babd797516e164947812b88043846a;hb=5606eb48618dde18a593793e2e5dafadf18d345b;hpb=e2e9c09c48b19b24979cafb2d4864f538b5ddd1c diff --git a/doc/html/man/tput.1.html b/doc/html/man/tput.1.html index f1c67438..bbc22a4e 100644 --- a/doc/html/man/tput.1.html +++ b/doc/html/man/tput.1.html @@ -27,7 +27,7 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: tput.1,v 1.44 2016/08/20 23:40:31 tom Exp @ + * @Id: tput.1,v 1.46 2016/10/22 19:57:25 tom Exp @ --> @@ -170,43 +170,46 @@
- tput handles the init and reset commands specially: it - allows for the possibility that it is invoked by a link + 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 specially: + treats a link named reset specially. - o That utility resets the terminal modes and special - characters (not done here). + Before ncurses 6.1, the two utilities were different from + each other: - o On the other hand, tset's repertoire of terminal capa- - bilities for resetting the terminal is more limited, + o tset utility reset the terminal modes and special + characters (not done with tput). + + o On the other hand, tset's repertoire of terminal capa- + bilities 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, due to - the resetting of terminal modes and special charac- - ters. + o The reset program is usually an alias for tset, + because of this difference with resetting terminal + modes and special characters. 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 + effect as tput init. Again, you are less likely to use + that link because another program named init has a more well-established use.
tput init Initialize the terminal according to the type of ter- - minal in the environmental variable TERM. This com- - mand should be included in everyone's .profile after + minal in the environmental variable TERM. This com- + mand 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 - Reset an AT&T 5620 terminal, overriding the type of + Reset an AT&T 5620 terminal, overriding the type of terminal in the environmental variable TERM. tput cup 0 0 @@ -227,16 +230,16 @@ 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: + for the current terminal. This might be followed by + a prompt: echo "${bold}Please type in your name: ${offbold}\c" tput hc - Set exit code to indicate if the current terminal is + Set exit code to indicate if the current terminal is a hard copy terminal. tput cup 23 4 - Send the sequence to move the cursor to row 23, col- + Send the sequence to move the cursor to row 23, col- umn 4. tput cup @@ -244,8 +247,8 @@ parameters substituted. tput longname - Print the long name from the terminfo database for - the type of terminal specified in the environmental + Print the long name from the terminfo database for + the type of terminal specified in the environmental variable TERM. tput -S <<! @@ -254,10 +257,10 @@ > bold > ! - This example shows tput processing several capabili- - ties 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 + This example shows tput processing several capabili- + ties 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. @@ -267,44 +270,44 @@ /usr/share/tabset/* tab settings for some terminals, in a format appro- - priate to be output to the terminal (escape - sequences that set margins and tabs); for more - information, see the Tabs and Initialization, sec- + priate to be output to the terminal (escape + sequences that set margins and tabs); for more + information, see the Tabs and Initialization, sec- tion of terminfo(5)
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, 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. + 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 + 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 cap- - name is defined for this terminal type. To - determine if capname is defined for this termi- - nal type, the user must test the value written - to standard output. A value of -1 means that + a value of 0 is always set, whether or not cap- + name is defined for this terminal type. To + determine if capname is defined for this termi- + nal 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 + 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 DIAGNOS- + Any other exit code indicates an error; see the DIAGNOS- TICS section. @@ -314,8 +317,8 @@ 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. + 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 @@ -326,119 +329,119 @@
- The tput command was begun by Bill Joy in 1980. The ini- + The tput command was begun by Bill Joy in 1980. The ini- tial version only cleared the screen. - AT&T System V provided a different tput command, whose - init and reset subcommands (more than half the program) + 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 writ- - ten by Eric Allman. Later the corresponding source code - for reset was removed from the BSD tset (in June 1993, + ten by Eric Allman. Later the corresponding source code + for reset was removed from the BSD tset (in June 1993, released in 4.4BSD-Lite a year later). - 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 + 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 + At the same time, Bostic added a shell script named "clear", which used tput to clear the screen. - Both of these appeared in 4.4BSD, becoming the "modern" + Both of these appeared in 4.4BSD, becoming the "modern" BSD implementation of tput.
- This implementation of tput differs from AT&T tput in two + 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 regular terminal. However, the subcommands - which manipulate terminal modes may not use the stan- + 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 stan- dard output. - The AT&T implementation's init and reset commands use + 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, stan- - dard error, standard input before falling back to + modes. It successively tries standard output, stan- + dard 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 ulti- - mately based on the 4.4BSD tset). If it is not able - to open a terminal, e.g., when running in cron, tput + 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 ulti- + mately 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 + 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 + 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 + string parameters, requiring tput to know which type to use. - This implementation uses a table to determine the + This implementation uses a table to determine the parameter types for the standard capname operands, and - an internal library function to analyze nonstandard + an internal library function to analyze nonstandard capname operands. - The longname and -S options, and the parameter-substitu- - tion features used in the cup example, were not supported - in BSD curses before 4.3reno (1989) or in AT&T/USL curses + The longname and -S options, and the parameter-substitu- + tion 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. There are a few interesting observations + IEEE Std 1003.1/The Open Group Base Specifications Issue + 7 (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 + o In this implementation, clear is part of the capname support. The others (init and longname) do not corre- spond to terminal capabilities. - 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 op- + 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 op- erands. - 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) + 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. - Because (apparently) all of the certified Unix systems - support the full set of capability names, the reasoning + 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 the other features used in this implemen- + capname and the other features used in this implemen- tation. - 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 + 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 + curses implementation provide a tput utility which does not provide the capname feature.
- clear(1), stty(1), tabs(1), tset(1), terminfo(5), + clear(1), stty(1), tabs(1), tset(1), terminfo(5), curs_termcap(3x). - This describes ncurses version 6.0 (patch 20160910). + This describes ncurses version 6.0 (patch 20161119).