X-Git-Url: http://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Ftset.1.html;h=0910b4edbadd5cc8e83f9cafa004d31f3c803812;hb=a8987e73ec254703634802b4f7ee30d3a485524d;hp=5d806bda6d44b5f82ebbdc8a1583b173189529b4;hpb=46722468f47c2b77b3987729b4bcf2321cccfd01;p=ncurses.git diff --git a/doc/html/man/tset.1.html b/doc/html/man/tset.1.html index 5d806bda..0910b4ed 100644 --- a/doc/html/man/tset.1.html +++ b/doc/html/man/tset.1.html @@ -1,7 +1,7 @@
@@ -40,6 +40,10 @@+tset(1) tset(1) + + +
@@ -73,7 +77,7 @@ 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 below + line, the -m option mappings are then applied (see below 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 con- @@ -108,36 +112,36 @@ The options are as follows: - -q The terminal type is displayed to the standard out- + -q The terminal type is displayed to the standard out- put, and the terminal is not initialized in any way. The option `-' by itself is equivalent but archaic. - -e Set the erase character to ch. + -e Set the erase character to ch. - -I Do not send the terminal or tab initialization + -I Do not send the terminal or tab initialization strings to the terminal. - -Q Don't display any values for the erase, interrupt and + -Q Don't display any values for the erase, interrupt and line kill characters. -V reports the version of ncurses which was used in this program, and exits. - -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. + -m Specify a mapping from a port type to a terminal. See below for more information. - -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 + -s Print the sequence of shell commands to initialize the environment variable TERM to the standard output. See the section below on setting the environment for details. - The arguments for the -e, -i, and -k options may either be + The arguments for the -e, -i, and -k options may either be entered as actual characters or by using the `hat' nota- tion, i.e. control-h may be specified as ``^H'' or ``^h''. @@ -146,9 +150,9 @@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. + shell's environment. This is done using the -s option. - When the -s option is specified, the commands to enter the + 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 @@ -171,107 +175,107 @@ often desirable to provide information about the type of terminal used on such ports. - The purpose of the -m option is to map from some set of + The purpose of the -m option is to map 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 optional operator, an optional baud rate specifi- - cation, an optional colon (``:'') character and a terminal - type. The port type is a string (delimited by either the - operator or the colon character). The operator may be any - combination of ``>'', ``<'', ``@'', and ``!''; ``>'' means - greater than, ``<'' means less than, ``@'' means equal to - and ``!'' inverts the sense of the test. The baud rate is - specified as a number and is compared with the speed of - the standard error output (which should be the control - terminal). The terminal type is a string. + 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 operator + may be any combination of ``>'', ``<'', ``@'', and ``!''; + ``>'' means greater than, ``<'' means less than, ``@'' + means equal to and ``!'' inverts the sense of the test. + The baud rate is specified as a number and is 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 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 applica- + 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 applica- ble mapping is used. - For example, consider the following mapping: + 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 termi- + is >, the baud rate specification is 9600, and the termi- nal type is vt100. The result of this mapping is to spec- ify that if the terminal type is dialup, and the baud rate - is greater than 9600 baud, a terminal type of vt100 will + 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 + type will match 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 + 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. 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 exclama- + 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 exclama- tion marks (``!'').HISTORY
- The tset command appeared in BSD 3.0. The ncurses imple- - mentation was lightly adapted from the 4.4BSD sources for + The tset command appeared in BSD 3.0. The ncurses imple- + mentation was lightly adapted from the 4.4BSD sources for a terminfo environment by Eric S. Raymond <esr@snark.thyr- sus.com>.COMPATIBILITY
- The tset utility has been provided for backward-compati- - bility 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 + The tset utility has been provided for backward-compati- + bility 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 -S option of BSD tset no longer works; it prints an - error message to stderr and dies. The -s option only sets - TERM, not TERMCAP. Both these changes are because the - TERMCAP variable is no longer supported under terminfo- + The -S option of BSD tset no longer works; it prints an + error message to stderr and dies. The -s option only sets + TERM, not TERMCAP. Both these changes are because the + TERMCAP variable is no longer supported under terminfo- based ncurses, which makes tset -S useless (we made it die noisily rather than silently induce lossage). - There was an undocumented 4.4BSD feature that invoking + There was an undocumented 4.4BSD feature that invoking tset via a link named `TSET` (or via any other name begin- - ning with an upper-case letter) set the terminal to use + ning 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 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 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 -n - option remains, but has no effect. The -adnp options are - therefore omitted from the usage summary above. - - It is still permissible to specify the -e, -i, and -k + 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, -, + and - + 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 -n option + remains, but has no effect. The -adnp options are there- + fore omitted from the usage summary above. + + It is still permissible to specify the -e, -i, and -k options without arguments, although it is strongly recom- mended 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 + the -Q option. Also, the interaction between the - option and the terminal argument in some historic implementations of tset has been removed. -ENVIRONMENT
The tset command uses the SHELL and TERM environment vari- @@ -296,41 +300,7 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + tset(1)