tset.1.html

ncurses-5.4

       the standard output.  If the <STRONG>SHELL</STRONG> environmental  variable
       ends in ``csh'', the commands are for <STRONG>csh</STRONG>, otherwise, they
       are for <STRONG>sh</STRONG>.  Note, the <STRONG>csh</STRONG>  commands  set  and  unset  the
       shell  variable  <STRONG>noglob</STRONG>,  leaving it unset.  The following
       line in the <STRONG>.login</STRONG> or <STRONG>.profile</STRONG> files will  initialize  the
       environment correctly:

           eval `tset -s options ... `



</PRE>
<H2>TERMINAL TYPE MAPPING</H2><PRE>
       When the terminal is not hardwired into the system (or the
       current system information is incorrect) the terminal type
       derived  from the <EM>/etc/ttys</EM> file or the <STRONG>TERM</STRONG> environmental
       variable is often something generic like <STRONG>network</STRONG>,  <STRONG>dialup</STRONG>,
       or  <STRONG>unknown</STRONG>.   When <STRONG>tset</STRONG> 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 <STRONG>-m</STRONG> option is to map from some set of
       conditions to a terminal type, that is, to tell <STRONG>tset</STRONG>  ``If
       I'm  on this port at a particular speed, guess that I'm on
       that kind of terminal''.

       The argument to the <STRONG>-m</STRONG> 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 ``&gt;'', ``&lt;'', ``@'', and ``!'';
       ``&gt;'' means greater than, ``&lt;''  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 <STRONG>-m</STRONG> 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:
       <STRONG>dialup&gt;9600:vt100</STRONG>.  The port type is dialup , the operator
       is &gt;, 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 <STRONG>dialup</STRONG>, and the baud rate
       is  greater  than 9600 baud, a terminal type of <STRONG>vt100</STRONG> 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,   <STRONG>-m</STRONG>
       <STRONG>dialup:vt100</STRONG>  <STRONG>-m</STRONG>  <STRONG>:?xterm</STRONG>  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  <STRONG>-m</STRONG>  option
       argument.   Also,  to avoid problems with meta-characters,
       it is suggested that the  entire  <STRONG>-m</STRONG>  option  argument  be
       placed  within single quote characters, and that <STRONG>csh</STRONG> users
       insert a backslash character (``\'') before  any  exclama-
       tion marks (``!'').


</PRE>
<H2>HISTORY</H2><PRE>
       The  <STRONG>tset</STRONG> command appeared in BSD 3.0.  The <STRONG>ncurses</STRONG> imple-
       mentation was lightly adapted from the 4.4BSD sources  for
       a terminfo environment by Eric S. Raymond &lt;[e-mail]-
       sus.com&gt;.


</PRE>
<H2>COMPATIBILITY</H2><PRE>
       The <STRONG>tset</STRONG> utility has been provided  for  backward-compati-
       bility  with  BSD  environments (under most modern UNIXes,
       <STRONG>/etc/inittab</STRONG> and <STRONG><A HREF="getty.1.html">getty(1)</A></STRONG> can set <STRONG>TERM</STRONG>  appropriately  for
       each  dial-up  line;  this  obviates  what was <STRONG>tset</STRONG>'s most
       important use).  This implementation behaves  like  4.4BSD
       tset, with a few exceptions specified here.

       The  <STRONG>-S</STRONG>  option  of BSD tset no longer works; it prints an
       error message to stderr and dies.  The <STRONG>-s</STRONG> option only sets
       <STRONG>TERM</STRONG>,  not  <STRONG>TERMCAP</STRONG>.   Both  these changes are because the
       <STRONG>TERMCAP</STRONG> variable is no longer  supported  under  terminfo-
       based <STRONG>ncurses</STRONG>, which makes <STRONG>tset</STRONG> <STRONG>-S</STRONG> useless (we made it die
       noisily rather than silently induce lossage).

       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
       upper-case only.  This feature has been omitted.

       The  <STRONG>-A</STRONG>,  <STRONG>-E</STRONG>,  <STRONG>-h</STRONG>, <STRONG>-u</STRONG> and <STRONG>-v</STRONG> options were deleted from the
       <STRONG>tset</STRONG> utility in 4.4BSD.  None of them were  documented  in
       4.3BSD and all are of limited utility at best.  The <STRONG>-a</STRONG>, -,
       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 <STRONG>-m</STRONG> option instead.   The  -n  option
       remains,  but has no effect.  The <STRONG>-adnp</STRONG> options are there-
       fore omitted from the usage summary above.

       It is still permissible to specify  the  <STRONG>-e</STRONG>,  <STRONG>-i</STRONG>,  and  <STRONG>-k</STRONG>
       options  without arguments, although it is strongly recom-
       mended that such usage be fixed to explicitly specify  the
       character.

       As  of  4.4BSD,  executing <STRONG>tset</STRONG> as <STRONG>reset</STRONG> no longer implies
       the <STRONG>-Q</STRONG> option.  Also, the interaction between the - option
       and the <EM>terminal</EM> argument in some historic implementations
       of <STRONG>tset</STRONG> has been removed.


</PRE>
<H2>ENVIRONMENT</H2><PRE>
       The <STRONG>tset</STRONG> command uses the <STRONG>SHELL</STRONG> and <STRONG>TERM</STRONG> environment vari-
       ables.


</PRE>
<H2>FILES</H2><PRE>
       /etc/ttys
            system  port  name  to terminal type mapping database
            (BSD versions only).

       /usr/share/terminfo
            terminal capability database


</PRE>
<H2>SEE ALSO</H2><PRE>
       <STRONG><A HREF="csh.1.html">csh(1)</A></STRONG>, <STRONG><A HREF="sh.1.html">sh(1)</A></STRONG>, <STRONG><A HREF="stty.1.html">stty(1)</A></STRONG>, <STRONG><A HREF="tty.4.html">tty(4)</A></STRONG>, <STRONG><A HREF="termcap.5.html">termcap(5)</A></STRONG>, <STRONG><A HREF="ttys.5.html">ttys(5)</A></STRONG>, envi-
       <STRONG><A HREF="ron.7.html">ron(7)</A></STRONG>




                                                          <STRONG><A HREF="tset.1.html">tset(1)</A></STRONG>
</PRE>
<HR>
<ADDRESS>
Man(1) output converted with
<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
</ADDRESS>
</BODY>
</HTML>