.TH TSET 1
.UC
.SH NAME
tset, reset \- set terminal modes
.SH SYNOPSIS
.B tset
[ options ] [
.B \-m
[ident][test baudrate]:type ] \&... [ type ]
.sp 1
.B reset
\&...
.SH DESCRIPTION
.I Tset
sets up your terminal when you first log in to a UNIX system.
It does terminal dependent processing such as setting
erase and kill characters, setting or resetting delays,
and the like.
It first determines the
.I type
of terminal involved,
and then does necessary initializations and mode settings.
The type of terminal attached to each \s-2UNIX\s0 port is specified in the
.I /etc/ttytype
database.
Type names for terminals may be found in the
.I /etc/termcap
database.
If a port is not wired permanently to a specific terminal (not hardwired)
it will be given an appropriate generic identifier such as
.I dialup.
.PP
In the case where no arguments are specified,
.I tset
simply reads the terminal type out of the environment variable TERM
and reinitializes the terminal.  The rest of this manual concerns
itself with mode and environment initialization,
typically done once at login, and options
used at initialization time to determine the terminal type and set up
terminal modes.
.PP
When used in a startup script (\fI\&.profile\fP for
.IR sh (1)
users or
.I \&.login
for
.IR csh (1)
users) it is desirable to give information about the type of terminal
you will usually use on ports which are not hardwired.
These ports are identified in
.I /etc/ttytype
as
.I dialup
or
.I plugboard
or
.I arpanet,
etc.
To specify
what terminal type you usually use on these ports, the
.B \-m
(map) option flag is followed by the appropriate port type identifier,
an optional baud rate specification,
and the terminal type.
(The effect is to ``map'' from some conditions to a terminal type,
that is, to tell
.I tset
``If I'm on this kind of port, guess that I'm on that kind of terminal''.)
If more than one mapping is specified, the first applicable mapping prevails.
A missing port type identifier matches all identifiers.
Any of the alternate generic names given in
.I termcap
may be used for the identifier.
.PP
A
.I baudrate
is specified as with
.IR stty (1),
and is compared with the
speed of the diagnostic output (which should be the control terminal).
The baud rate
.I test
may be any combination of:
.BR > ,
.BR @ ,
.BR < ,
and
.BR ! ;
.B @
means ``at''
and
.B !
inverts the sense of the test.  To avoid problems with metacharacters, it
is best to place the entire argument to
.B \-m
within ``\''' characters; users of
.IR csh (1)
must also put a ``\e'' before any ``!'' used here.
.PP
.KS
Thus
.IP
.nf
tset \-m \'dialup>300:adm3a\' \-m dialup:dw2 \-m \'plugboard:?adm3a\'
.fi
.KE
.LP
causes the terminal type to be set to an
.I adm3a
if the port in use is a dialup at a speed greater than 300 baud;
to a 
.I dw2
if the port is (otherwise) a dialup (i.e. at 300 baud or less).
(\fBNOTE:\fP the examples given here appear to take up more than
one line, for text processing reasons.  When you type in real
.I tset
commands, you must enter them entirely on one line.)
If the
.I type
finally determined by
.I tset
begins with a question mark,
the user is asked if s/he really wants that type.
A null response means to use that type;
otherwise, another type can be entered which will be used instead.
Thus, in the above case, the user will be queried on a plugboard port
as to whether they are actually using an
.I adm3a.
.PP
If no mapping applies and a final
.I type
option, not preceded by a
.BR \-m ,
is given on the command line
then that type is used;
otherwise the identifier found in the
.I /etc/ttytype
database will be taken to be the terminal type.
This should always be the case for hardwired ports.
.PP
It is usually desirable to return the terminal type, as finally determined by
.I tset,
and information about the terminal's capabilities
to a shell's environment.  This can be done using the
.B \-s
option; using the Bourne shell,
.IR sh (1):
.IP
.nf
eval \`tset \-s \fIoptions...\fP\`
.fi
.LP
or using the C shell,
.IR csh (1):
.IP
.nf
set noglob; eval \`tset \-s \fIoptions...\fP\`
.fi
.PP
If you have an old csh with no eval command, do the following:
.IP
.nf
tset \-s options > /tmp/tset$$ ; source /tmp/tset$$ ; rm /tmp/tset$$
.fi
.PP
In either
.I csh
case, you should probably make an alias in your .cshrc:
.PP
.RS
alias tset \'set noglob; eval \`tset \-s \!*\`\'
.br
or
.br
alias tset \'tset \-s \!* > /tmp/tset$$ ; source /tmp/tset$$ ; rm /tmp/tset$$\'
.RE
Either of these aliases allow the command
.RS
tset 2621
.RE
to be invoked at any time from your login csh.
.B "Note to Bourne Shell users:"
It is
.I not
possible to get this aliasing effect with a 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.)
.PP
These commands cause
.I tset
to generate as output a sequence of shell commands which place the variables
TERM and TERMCAP in the environment; see
.IR environ (5).
.PP
Once the terminal type is known,
.I tset
engages in terminal driver mode setting.
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.
.PP
On terminals that can backspace but not overstrike
(such as a \s-2CRT\s0),
and when the erase character is the default erase character
(`#' on standard systems),
the erase character is changed to \s-2BACKSPACE\s0 (Control-H).
.PP
The options are:
.TP
.B \-\^e\fIc
set the erase character to be the named character
.I c
on all terminals,
the default being the backspace character on the terminal, usually ^H.
The character
.I c
can either be typed directly, or entered using the hat
notation used here.
.TP
.B \-\^k\fIc
is similar to
.B \-e
but for the line kill character rather than the erase character;
.I c
defaults to ^X (for purely historical reasons).
The kill characters is left alone if
.B \-k
is not specified.
The hat notation can also be used for this option.
.TP
.B \-\^n
On systems with the Berkeley 4BSD tty driver,
specifies that the new tty driver modes should be initialized for this terminal.
For a \s-2CRT\s0,
the CRTERASE and CRTKILL
modes are set only if the baud rate is 1200 or greater.
See newtty(4) for more detail.
.TP
.B \-\^v
On systems with CB/UNIX virtual terminals, normally
.I tset
sets up the tty driver modes and the environment TERMCAP variable
to use the virtual terminal.
The
.B \-v
option turns off this processing,
causing tset to not use a virtual terminal.
.TP
.B \-\^I
suppresses transmitting terminal initialization strings.
.TP
.B \-\^Q
supresses printing the
``Erase set to'' and ``Kill set to'' messages.
.TP
.B \-\^S
If your shell is
.IR csh ,
.I tset
will output the strings to be assigned to
TERM and TERMCAP in the environment rather than commands for a shell.
This is mainly useful to avoid the (slow) source command with an
old
.IR csh .
.PP
If
.I tset
is invoked as
.IR reset ,
it will set cooked and echo modes, turn off cbreak and raw modes,
turn on newline translation, and restore special characters
to a sensible state before any terminal dependent processing is done.
Any special character that is found to be \s-2NULL\s0
or ``\-1'' is reset to it's default value.
.PP
This is most useful after a program dies leaving a terminal in a funny
state. You may have to type ``\s-2<LF>\s0reset\s-2<LF>\s0'' to get it to work
since \s-2<CR>\s0 may not work in this state. Often none of this will echo.
.SH EXAMPLES
.PP
These examples all assume the Bourne shell and use the \-s option.
If you use
.IR csh ,
use one of the variations described above.
Note that a typical use of
.I tset
in a .profile or .login will also use the
.B \-e
and
.B \-k
options, and often the
.B \-n
or
.B \-Q
options as well.
These options have not been included here to keep the examples small.
(\fBNOTE:\fP some of the examples given here appear to take up more than
one line, for text processing reasons.  When you type in real
.I tset
commands, you must enter them entirely on one line.)
.PP
At the moment, you are on a 2621.
This is suitable for typing by hand but
not for a .profile, unless you are
.I always
on a 2621.
.IP
.nf
eval \`tset \-s 2621\`
.fi
.PP
You have an h19 at home which you dial up on, but your office terminal
is hardwired and known in /etc/ttytype.
.IP
.nf
eval \`tset \-s \-m dialup:h19\`
.fi
.PP
You have a switch which connects everything to everything, making
it nearly impossible to key on what port you are coming in on.
You use a vt100 in your office at 9600 baud, and dial up to switch
ports at 1200 baud from home on a 2621.
Sometimes you use someone elses terminal at work,
so you want it to ask you to make sure what terminal
type you have at high speeds, but at 1200 baud you are
always on a 2621.
Note the placement of the question mark, and the quotes
to protect the greater than and question mark from
interpretation by the shell.
.IP
.nf
eval \`tset \-s \-m 'switch>1200:?vt100' \-m 'switch<=1200:2621'
.fi
.PP
All of the above entries will fall back on the terminal type
specified in /etc/ttytype if none of the conditions hold.
The following entry is appropriate if
you always dial up, always at the same baud rate,
on many different kinds of terminals.
Your most common terminal is an adm3a.
It always asks you what kind of terminal you are on,
defaulting to adm3a.
.IP
.nf
eval \`tset \-s \?adm3a\`
.fi
.PP
If the file /etc/ttytype is not properly installed and you want to
key entirely on the baud rate, the following can be used:
.IP
.nf
eval \`tset \-s \-m '>1200:vt100' 2621\`
.fi
.PP
Here is a fancy example to illustrate the power of
.I tset
and to hopelessly confuse anyone who has made it this far.
You dial up at 1200 baud or less on a concept100,
sometimes over switch ports and sometimes over regular dialups.
You use various terminals at speeds higher than 1200 over switch ports,
most often the terminal in your office, which is a vt100.
However, sometimes you log in from the university you used to go to,
over the ARPANET; in this case you are on an ALTO emulating a dm2500.
You also often log in on various hardwired ports, such as the console,
all of which are properly entered in /etc/ttytype.
You want your erase character set to control H,
your kill character set to control U,
and don't want
.I tset
to print the ``Erase set to Backspace, Kill set to Control U'' message.
.IP
.nf
eval \`tset \-e \-k^U \-Q \-s \-m 'switch<=1200:concept100' \-m 'switch:?vt100'
	\-m dialup:concept100 \-m arpanet:dm2500\`
.fi
.SH FILES
.ta 2i
/etc/ttytype	port name to terminal type mapping database
.br
/etc/termcap	terminal capability database
.SH SEE\ ALSO
csh(1), sh(1), stty(1), environ(5), termcap(5), ttytype(5)
.SH AUTHOR
Eric Allman
.br
David Wasley
.br
Mark Horton
.SH BUGS
.PP
The
.I 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
.IR login (1)
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.