</PRE>
<H2>NAME</H2><PRE>
- <B>tset</B> - terminal initialization
+ <B>tset</B>, <B>reset</B> - terminal initialization
</PRE>
<H2>SYNOPSIS</H2><PRE>
- tset [-IQqrs] [-] [-e <I>ch</I>] [-i <I>ch</I>] [-k <I>ch</I>] [-m <I>mapping</I>]
+ tset [-IQVqrs] [-] [-e <I>ch</I>] [-i <I>ch</I>] [-k <I>ch</I>] [-m <I>mapping</I>]
[<I>terminal</I>]
- reset [-IQqrs] [-] [-e <I>ch</I>] [-i <I>ch</I>] [-k <I>ch</I>] [-m <I>mapping</I>]
+ reset [-IQVqrs] [-] [-e <I>ch</I>] [-i <I>ch</I>] [-k <I>ch</I>] [-m <I>mapping</I>]
[<I>terminal</I>]
-I Do not send the terminal or tab initialization
strings to the terminal.
+ -Q Don't display any values for the erase, interrupt and
+ line kill characters.
+
+ <B>-V</B> reports the version of ncurses which was used in this
+ program, and exits.
+
-i Set the interrupt character to <I>ch</I>.
-k Set the line kill character to <I>ch</I>.
-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
+ -s Print the sequence of shell commands to initialize
the environment variable <B>TERM</B> to the standard output.
- See the section below on setting the environment for
+ 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''.
</PRE>
<H2>SETTING THE ENVIRONMENT</H2><PRE>
- 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 <B>SHELL</B> environmental variable
+ information into the shell's environment are written to
+ the standard output. If the <B>SHELL</B> environmental variable
ends in ``csh'', the commands are for <B>csh</B>, otherwise, they
- are for <B>sh</B>. Note, the <B>csh</B> commands set and unset the
- shell variable <B>noglob</B>, leaving it unset. The following
- line in the <B>.login</B> or <B>.profile</B> files will initialize the
+ are for <B>sh</B>. Note, the <B>csh</B> commands set and unset the
+ shell variable <B>noglob</B>, leaving it unset. The following
+ line in the <B>.login</B> or <B>.profile</B> files will initialize the
environment correctly:
eval `tset -s options ... `
<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 <I>/etc/ttys</I> file or the <B>TERM</B> environmental
- variable is often something generic like <B>network</B>, <B>dialup</B>,
- or <B>unknown</B>. When <B>tset</B> is used in a startup script it is
- often desirable to provide information about the type of
+ derived from the <I>/etc/ttys</I> file or the <B>TERM</B> environmental
+ variable is often something generic like <B>network</B>, <B>dialup</B>,
+ or <B>unknown</B>. When <B>tset</B> 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 <B>tset</B> ``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 <B>tset</B> ``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:
+ For example, consider the following mapping:
<B>dialup>9600:vt100</B>. The port type is dialup , the operator
- is >, the baud rate specification is 9600, and the termi-
+ 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 <B>dialup</B>, and the baud rate
- is greater than 9600 baud, a terminal type of <B>vt100</B> will
+ is greater than 9600 baud, a terminal type of <B>vt100</B> 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, <B>-m</B>
+ type will match any port type. For example, <B>-m</B>
<B>dialup:vt100</B> <B>-m</B> <B>:?xterm</B> 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 <B>csh</B> 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 <B>csh</B> users
+ insert a backslash character (``\'') before any exclama-
tion marks (``!'').
</PRE>
<H2>HISTORY</H2><PRE>
- The <B>tset</B> command appeared in BSD 3.0. The <B>ncurses</B> imple-
- mentation was lightly adapted from the 4.4BSD sources for
+ The <B>tset</B> command appeared in BSD 3.0. The <B>ncurses</B> imple-
+ mentation was lightly adapted from the 4.4BSD sources for
a terminfo environment by Eric S. Raymond <esr@snark.thyr-
sus.com>.
</PRE>
<H2>COMPATIBILITY</H2><PRE>
- The <B>tset</B> utility has been provided for backward-compati-
- bility with BSD environments (under most modern UNIXes,
- <B>/etc/inittab</B> and <B><A HREF="getty.1.html">getty(1)</A></B> can set <B>TERM</B> appropriately for
- each dial-up line; this obviates what was <B>tset</B>'s most
- important use). This implementation behaves like 4.4BSD
+ The <B>tset</B> utility has been provided for backward-compati-
+ bility with BSD environments (under most modern UNIXes,
+ <B>/etc/inittab</B> and <B><A HREF="getty.1.html">getty(1)</A></B> can set <B>TERM</B> appropriately for
+ each dial-up line; this obviates what was <B>tset</B>'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
- <B>TERM</B>, not <B>TERMCAP</B>. Both these changes are because the
- <B>TERMCAP</B> variable is no longer supported under terminfo-
+ <B>TERM</B>, not <B>TERMCAP</B>. Both these changes are because the
+ <B>TERMCAP</B> variable is no longer supported under terminfo-
based <B>ncurses</B>, which makes <B>tset</B> <B>-S</B> 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
- <B>tset</B> utility in 4.4BSD. None of them were documented in
+ The -A, -E, -h, -u and -v options were deleted from the
+ <B>tset</B> 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 <B>tset</B> as <B>reset</B> no longer implies
+ As of 4.4BSD, executing <B>tset</B> as <B>reset</B> no longer implies
the -Q option. Also, the interaction between the - option
and the <I>terminal</I> argument in some historic implementations
of <B>tset</B> has been removed.
+
</PRE>
<H2>ENVIRONMENT</H2><PRE>
The <B>tset</B> command uses the <B>SHELL</B> and <B>TERM</B> environment vari-
</PRE>
<H2>FILES</H2><PRE>
/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 database
-
-
-
-
projects / ncurses.git / blobdiff