X-Git-Url: https://ncurses.scripts.mit.edu/?a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Ftset.1.html;h=5d806bda6d44b5f82ebbdc8a1583b173189529b4;hb=46722468f47c2b77b3987729b4bcf2321cccfd01;hp=aebef36bf83ca433853b09d4352bca6cd2a6b0cd;hpb=b1f61d9f3aa244512045a6b02e759825d7049d34;p=ncurses.git diff --git a/doc/html/man/tset.1.html b/doc/html/man/tset.1.html index aebef36b..5d806bda 100644 --- a/doc/html/man/tset.1.html +++ b/doc/html/man/tset.1.html @@ -1,36 +1,74 @@ + + +
+- tset - terminal initialization + tset, reset - terminal initialization
- tset [-IQqrs] [-] [-e ch] [-i ch] [-k ch] [-m mapping] - [terminal] - reset [-IQqrs] [-] [-e ch] [-i ch] [-k ch] [-m mapping] - [terminal] + tset [-IQVqrs] [-] [-e ch] [-i ch] [-k ch] [-m mapping] + [terminal] + reset [-IQVqrs] [-] [-e ch] [-i ch] [-k ch] [-m mapping] + [terminal]
- Tset initializes terminals. Tset first determines the + Tset initializes terminals. Tset first determines the type of terminal that you are using. This determination is done as follows, using the first terminal type found. - 1. The terminal argument specified on the command line. + 1. The terminal argument specified on the command line. - 2. The value of the TERM environmental variable. + 2. The value of the TERM environmental variable. 3. (BSD systems only.) The terminal type associated with - the standard error output device in the /etc/ttys file. - (On Linux and System-V-like UNIXes, getty does this job by - setting TERM according to the type passed to it by - /etc/inittab.) + the standard error output device in the /etc/ttys file. + (On Linux and System-V-like UNIXes, getty does this job by + setting TERM according to the type passed to it by + /etc/inittab.) 4. The default terminal type, ``unknown''. @@ -53,7 +91,7 @@ have changed, or are not set to their default values, their values are displayed to the standard error output. - When invoked as reset, tset sets cooked and echo modes, + When invoked as reset, tset sets cooked and echo modes, turns off cbreak and raw modes, turns on newline transla- tion and resets any unset special characters to their default values before doing the terminal initialization @@ -61,7 +99,7 @@ leaving a terminal in an abnormal state. Note, you may have to type - <LF>reset<LF> + <LF>reset<LF> (the line-feed character is normally control-J) to get the terminal to work, as carriage-return may no longer work in @@ -74,46 +112,49 @@ 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 strings to the terminal. - -i Set the interrupt character to ch. + -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. - -k Set the line kill character to ch. + -i Set the interrupt character to ch. + + -k Set the line kill character to ch. -m Specify a mapping from a port type to a terminal. See below for more information. - -Q Don't display any values for the erase, interrupt and - line kill characters. - -r Print the terminal type to the standard error output. - -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 + -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 - entered as actual characters or by using the `hat' nota- + entered as actual characters or by using the `hat' nota- tion, i.e. control-h may be specified as ``^H'' or ``^h''.
- It is often desirable to enter the terminal type and - information about the terminal's capabilities into the + 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. 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 - are for sh. Note, the csh commands set and unset the - shell variable noglob, leaving it unset. The following - line in the .login or .profile files will initialize 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 + are for sh. Note, the csh commands set and unset the + shell variable noglob, leaving it unset. The following + line in the .login or .profile files will initialize the environment correctly: eval `tset -s options ... ` @@ -124,136 +165,133 @@TERMINAL TYPE MAPPING
When the terminal is not hardwired into the system (or the current system information is incorrect) the terminal type - derived from the /etc/ttys file or the TERM environmental - variable is often something generic like network, dialup, - or unknown. When tset is used in a startup script it is - often desirable to provide information about the type of + derived from the /etc/ttys file or the TERM environmental + variable is often something generic like network, dialup, + or unknown. When tset is used in a startup script it is + 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 - 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 + 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 + 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 + 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 + 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: - dialup>9600:vt100. The port type is dialup , the operator - is >, the baud rate specification is 9600, and the termi- + 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- 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 + ify that if the terminal type is dialup, and the baud rate + 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 - dialup:vt100 -m :?xterm will cause any dialup port, + 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 + 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 + 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 + 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 + 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 - options without arguments, although it is strongly recom- - mended that such usage be fixed to explicitly specify the + 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 + As of 4.4BSD, executing tset as reset no longer implies the -Q option. Also, the interaction between the - option - and the terminal argument in some historic implementations - of tset has been removed. + and the terminal argument in some historic implementations + of tset has been removed. +ENVIRONMENT
- The tset command uses the SHELL and TERM environment vari- + The tset command uses the SHELL and TERM environment vari- ables.FILES
/etc/ttys - system port name to terminal type mapping database + system port name to terminal type mapping database (BSD versions only). - @DATADIR@/terminfo + /usr/share/terminfo terminal capability databaseSEE ALSO
- csh(1), sh(1), stty(1), tty(4), termcap(5), ttys(5), envi- - ron(7) - - - - + csh(1), sh(1), stty(1), tty(4), termcap(5), ttys(5), envi- + ron(7)