![[Go to CFHT Home Page]](/images/cfht-icon.gif){kind=icon}
Man Pages 
Back to Software Index 
Manpage Top Level
reset [ - ] [ -ec ] [ -I ] [ -kc ] [ -n ] [ -Q ] [ -r ] [ -s ] [ -m [ indent ] [ test baudrate ]: type ] ... [ type ]
SUNWscpu
tset sets up your terminal, typically when you first log in. It does terminal dependent processing such as setting erase and kill characters, setting or resetting delays, sending any sequences needed to properly initialized the terminal, and the like. tset first determines the type of terminal involved, and then does necessary initializations and mode settings. If a port is not wired permanently to a specific terminal (not hardwired) it is given an appropriate generic identifier such as dialup.
reset clears the terminal settings by turning off CBREAK and RAW modes, output delays and parity checking, turns on NEWLINE translation, echo and TAB expansion, and restores undefined special characters to their default state. It then sets the modes as usual, based on the terminal type (which will probably override some of the above). See stty(1) for more information. All arguments to tset may be used with reset. reset also uses rs= and rf= to reset the initialization string and file. This is useful after a program dies and leaves the terminal in a funny state. Often in this situation, characters will not echo as you type them. You may have to type LINEFEED reset LINEFEED since RETURN may not work.
When no arguments are specified, tset reads the terminal type from the TERM environment variable and re-initializes the terminal, and performs initialization of mode, environment and other options at login time to determine the terminal type and set up terminal modes.
When used in a startup script (.profile for sh(1) users or .login for csh(1) users) it is desirable to give information about the type of terminal you will usually use on ports that are not hardwired. Any of the alternate generic names given in the file /etc/termcap are possible identifiers. Refer to the -m option below for more information. If no mapping applies and a final type option, not preceded by a -m, is given on the command line then that type is used.
It is usually desirable to return the terminal type, as finally
determined by tset, and information about the terminal’s capabilities, to
a shell’s environment. This can be done using the -, -s, or -S options.
For the Bourne shell, put this command in your .profile file:
or using the C shell, put these commands in your .login file:
With the C shell, it is also convenient to make an alias in your .cshrc file:
This also allows the command:
to be invoked at any time to set the terminal and environment. It is not possible to get this aliasing effect with a Bourne shell script, because shell scripts cannot set the environment of their parent. If a process could set its parent’s environment, none of this nonsense would be necessary in the first place.
Once the terminal type is known, tset sets the terminal driver mode. This normally involves sending an initialization sequence to the terminal, setting the single character erase (and optionally the line-kill (full line erase)) characters, and setting special character delays. TAB and NEWLINE expansion are turned off during transmission of the terminal initialization sequence.
On terminals that can backspace but not overstrike (such as a CRT ), and when the erase character is ‘#’, the erase character is changed as if -e had been used.
set noglob eval ‘tset -s ...‘ unset noglob
To prevent interpretation as metacharacters, the entire argument to -m should be enclosed in single quotes. When using the C shell, exclamation points should be preceded by a backslash (\).
To select a 2621, you might put the following sequence of commands in your .login file (or .profile for Bourne shell users).
set noglob eval ‘tset -s 2621‘ unset noglob
If you have a switch which connects to various ports (making it impractical
to identify which port you may be connected to), and use various terminals
from time to time, you can select from among those terminals according
to the speed or baud rate. In the example below, tset will prompt you for
a terminal type if the baud rate is greater than 1200 (say, 9600 for a
terminal connected by an RS-232 line), and use a Wyse 50 by default. If
the baud rate is less than or equal to 1200, it will select a 2621. Note
the placement of the question mark, and the quotes to protect the > and
? from interpretation by the shell.
set noglob eval ‘tset -s -m ’switch>1200:?wy’ -m ’switch<=1200:2621’‘ unset noglob
The following entry is appropriate if you always dial up, always at the same baud rate, on many different kinds of terminals, and the terminal you use most often is an adm3a.
If you want to make the selection based only on the baud rate, you might use the following:
set noglob eval ‘tset -s ?adm3a‘ unset noglob
set noglob eval ‘tset -s -m ’>1200:wy’ 2621‘ unset noglob
The following example quietly sets the erase character to BACKSPACE, and kill to CTRL-U . If the port is switched, it selects a Concepttm 100 for speeds less than or equal to 1200, and asks for the terminal type otherwise (the default in this case is a Wyse 50). If the port is a direct dialup, it selects Concept 100 as the terminal type. If logging in over the ARPANET , the terminal type selected is a Datamedia 2500 terminal or emulator. Note the backslash escaping the NEWLINE at the end of the first line in the example.
set noglob eval ‘tset -e -k^U -Q -s -m ’switch<=1200:concept100’ -m \ ’switch:?wy’ -m dialup:concept100 -m arpanet:dm2500‘ unset noglob
The tset command is one of the first commands a user must master when getting started on a UNIX system. Unfortunately, it is one of the most complex, largely because of the extra effort the user must go through to get the environment of the login shell set. Something needs to be done to make all this simpler, either the login program should do this stuff, or a default shell alias should be made, or a way to set the environment of the parent should exist.
This program cannot intuit personal choices for erase, interrupt and line kill characters, so it leaves these set to the local system standards.
It could well be argued that the shell should be responsible for ensuring that the terminal remains in a sane state; this would eliminate the need for the reset program.