|TSET(1)||General Commands Manual||TSET(1)|
tsetfirst determines the type of terminal that you are using. This determination is done as follows, using the first terminal type found:
-moption mappings are then applied (see the TERMINAL TYPE MAPPING section 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 confirms the type, or another type can be entered to specify a new type. Once the terminal type has been determined, the terminfo entry for the terminal is retrieved. If no terminfo entry is found for the type, the user is prompted for another terminal type. Once the terminfo entry is retrieved, the window size, backspace, interrupt, and line kill characters (among many other things) are set and the terminal and tab initialization strings are sent to the standard error output. Finally, if the erase, interrupt and line kill characters have changed, or are not set to their default values, their values are displayed to the standard error output. Use the
-woption to select only the window sizing versus the other initialization. If neither option is given, both are assumed. When invoked as
tsetsets cooked and echo modes, turns off cbreak and raw modes, turns on newline translation and resets any unset special characters to their default values before doing the terminal initialization described above. This is useful after a program dies leaving a terminal in an abnormal state. Note, you may have to type “<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 the abnormal state. Also, the terminal will often not echo the command. The options are as follows:
tsetdisplays the values for control characters which differ from the system's default values.
TERMto the standard output. See the SETTING THE ENVIRONMENT section below for details.
-koptions may either be entered as actual characters or by using the “hat” notation, i.e., control-H may be specified as “^H” or “^h”.
-soption. When the
-soption is specified, the commands to enter the information into the shell's environment are written to the standard output. If the
SHELLenvironment variable ends in “csh”, the commands are for csh(1), otherwise, they are for sh(1). Note, the csh(1) 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 ... `
TERMenvironment variable is often something generic like “network”, “dialup”, or “unknown”. When
tsetis used in a startup script (.profile for sh(1) users or .login for csh(1) users) it is often desirable to provide information about the type of terminal used on such ports. The purpose of the
-moption 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
-moption 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
-mmappings 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 applicable 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 terminal type is “vt100”. The result of this mapping is to specify 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 port type is specified, the terminal 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 are actually using an xterm terminal. No whitespace characters are permitted in the
-moption argument. Also, to avoid problems with meta-characters, it is suggested that the entire
-moption argument be placed within single quote characters, and that csh(1) users insert a backslash character (‘
\’) before any exclamation marks (‘
tsetcommand utilizes the
tsetcommand now uses the terminfo(5) database where previous versions used termcap(5). Historic versions of the termcap(3) library limited entries to 1023 bytes. Modern terminfo(3) entries are often much larger, making it impossible to store the full entry in the
TERMCAPenvironment variable. Because of this, the
-Soption is no longer supported (it prints an error message to the standard error and exits) and the
-soption only sets
-voptions have been deleted from the
tsetutility. None of them were documented in 4.3BSD and all are of limited utility at best. The
-poptions 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
-moption instead. The
-noption remains, but has no effect. It is still permissible to specify the
-koptions without arguments, although it is strongly recommended that such usage be fixed to explicitly specify the character. Executing
resetno longer implies the
-Qoption. Also, the interaction between the
-option and the terminal argument in some historic implementations of
tsethas been removed. Finally, the
tsetimplementation has been completely redone (as part of the addition to the system of a IEEE Std 1003.1-1988 (“POSIX.1”) compliant terminal interface) and will no longer compile on systems with older terminal interfaces.
resetutilities first appeared in 1BSD.
tsetwas written by Eric P. Allman in October 1977, and
resetwas originally written by Kurt Shoens. The current version also contains code by Zeyd M. Ben-Halim, Eric S. Raymond, and Thomas E. Dickey.
|December 3, 2015||OpenBSD-current|