* sale, use or other dealings in this Software without prior written *
* authorization. *
****************************************************************************
- * @Id: tset.1,v 1.75 2023/11/25 14:32:36 tom Exp @
+ * @Id: tset.1,v 1.77 2023/12/02 20:52:24 tom Exp @
* https://minnie.tuhs.org/cgi-bin/utree.pl?file=1BSD/s6/reset.c
* https://minnie.tuhs.org/cgi-bin/utree.pl?file=3BSD/usr/src/cmd/\
* reset.c
<HEAD>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="generator" content="Manpage converted by man2html - see https://invisible-island.net/scripts/readme.html#others_scripts">
-<TITLE>tset 1 2023-11-25 ncurses 6.4 User commands</TITLE>
+<TITLE>tset 1 2023-12-02 ncurses 6.4 User commands</TITLE>
<link rel="author" href="mailto:bug-ncurses@gnu.org">
</HEAD>
<BODY>
-<H1 class="no-header">tset 1 2023-11-25 ncurses 6.4 User commands</H1>
+<H1 class="no-header">tset 1 2023-12-02 ncurses 6.4 User commands</H1>
<PRE>
<STRONG><A HREF="tset.1.html">tset(1)</A></STRONG> User commands <STRONG><A HREF="tset.1.html">tset(1)</A></STRONG>
1. The <STRONG>terminal</STRONG> argument specified on the command line.
- 2. The value of the <STRONG>TERM</STRONG> environmental variable.
+ 2. The value of the <EM>TERM</EM> environmental variable.
3. (BSD systems only.) The terminal type associated with the standard
- error output device in the <EM>/etc/ttys</EM> file. (On System-V-like Unices
- and systems using that convention, <STRONG>getty(1)</STRONG> does this job by setting
- <STRONG>TERM</STRONG> according to the type passed to it by <EM>/etc/inittab</EM>.)
+ error output device in the <EM>/etc/ttys</EM> file. (On System V hosts and
+ systems using that convention, <STRONG>getty(1)</STRONG> does this job by setting <EM>TERM</EM>
+ according to the type passed to it by <EM>/etc/inittab</EM>.)
4. The default terminal type, "unknown", is not suitable for curses
applications.
window size.
If the window size cannot be obtained from the operating system,
- but the terminal description (or environment, e.g., <STRONG>LINES</STRONG> and
- <STRONG>COLUMNS</STRONG> variables specify this), use this to set the operating
+ but the terminal description (or environment, e.g., <EM>LINES</EM> and
+ <EM>COLUMNS</EM> variables specify this), use this to set the operating
system's notion of the window size.
<STRONG>o</STRONG> if the "<STRONG>-c</STRONG>" option is enabled, the backspace, interrupt and line
When the <STRONG>-s</STRONG> option is specified, the commands to enter the information
into the shell's environment are written to the standard output. If
- the <STRONG>SHELL</STRONG> environmental variable ends in "csh", the commands are for
+ the <EM>SHELL</EM> environmental variable ends in "csh", the commands are for
<STRONG>csh</STRONG>, otherwise, they are for <STRONG>sh(1)</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
</PRE><H3><a name="h3-Terminal-Type-Mapping">Terminal Type Mapping</a></H3><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
+ <EM>/etc/ttys</EM> file or the <EM>TERM</EM> 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.
<STRONG>-r</STRONG> Print the terminal type to the standard error output.
<STRONG>-s</STRONG> Print the sequence of shell commands to initialize the environment
- variable <STRONG>TERM</STRONG> to the standard output; see subsection "Setting the
+ variable <EM>TERM</EM> to the standard output; see subsection "Setting the
Environment".
<STRONG>-V</STRONG> reports the version of ncurses which was used in this program, and
</PRE><H2><a name="h2-ENVIRONMENT">ENVIRONMENT</a></H2><PRE>
The <STRONG>tset</STRONG> command uses these environment variables:
- SHELL
- tells <STRONG>tset</STRONG> whether to initialize <STRONG>TERM</STRONG> using <STRONG>sh(1)</STRONG> or <STRONG>csh(1)</STRONG>
+ <EM>SHELL</EM>
+ tells <STRONG>tset</STRONG> whether to initialize <EM>TERM</EM> using <STRONG>sh(1)</STRONG> or <STRONG>csh(1)</STRONG>
syntax.
- TERM Denotes your terminal type. Each terminal type is distinct,
+ <EM>TERM</EM> Denotes your terminal type. Each terminal type is distinct,
though many are similar.
- TERMCAP
+ <EM>TERMCAP</EM>
may denote the location of a termcap database. If it is not an
absolute pathname, e.g., begins with a "/", <STRONG>tset</STRONG> removes the
variable from the environment before looking for the terminal
</PRE><H2><a name="h2-FILES">FILES</a></H2><PRE>
- /etc/ttys
- system port name to terminal type mapping database (BSD versions
- only).
+ <EM>/etc/ttys</EM>
+ system port name to terminal type mapping database (BSD versions
+ only).
<EM>/usr/share/terminfo</EM>
- compiled terminal description database directory
+ compiled terminal description database directory
</PRE><H2><a name="h2-PORTABILITY">PORTABILITY</a></H2><PRE>
<STRONG>tset</STRONG>. In fact, the commonly-used <STRONG>reset</STRONG> utility is always an alias for
<STRONG>tset</STRONG>.
- The <STRONG>tset</STRONG> utility provides for backward-compatibility with BSD
- environments (under most modern Unices, <STRONG>/etc/inittab</STRONG> and <STRONG>getty(1)</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
- <STRONG>tset</STRONG>, with a few exceptions specified here.
+ The <STRONG>tset</STRONG> utility provides backward compatibility with BSD environments;
+ under most modern Unices, <EM>/etc/inittab</EM> and <STRONG>getty(1)</STRONG> can set <EM>TERM</EM>
+ appropriately for each dial-up line, obviating what was <STRONG>tset</STRONG>'s most
+ important use. This implementation behaves like 4.4BSD <STRONG>tset</STRONG>, with a
+ few exceptions we shall consider now.
- A few options are different because the <STRONG>TERMCAP</STRONG> variable is no longer
+ A few options are different because the <EM>TERMCAP</EM> variable is no longer
supported under terminfo-based <STRONG>ncurses</STRONG>:
<STRONG>o</STRONG> The <STRONG>-S</STRONG> option of BSD <STRONG>tset</STRONG> no longer works; it prints an error
message to the standard error and dies.
- <STRONG>o</STRONG> The <STRONG>-s</STRONG> option only sets <STRONG>TERM</STRONG>, not <STRONG>TERMCAP</STRONG>.
+ <STRONG>o</STRONG> The <STRONG>-s</STRONG> option only sets <EM>TERM</EM>, not <EM>TERMCAP</EM>.
There was an undocumented 4.4BSD feature that invoking <STRONG>tset</STRONG> via a link
named "TSET" (or via any other name beginning with an upper-case
size from the operating system.
<STRONG>o</STRONG> In ncurses, <STRONG>tset</STRONG> obtains the window size using <STRONG>setupterm</STRONG>, which may
- be from the operating system, the <STRONG>LINES</STRONG> and <STRONG>COLUMNS</STRONG> environment
+ be from the operating system, the <EM>LINES</EM> and <EM>COLUMNS</EM> environment
variables or the terminal description.
Obtaining the window size from the terminal description is common to
use is for hardware terminals. Generally speaking, a window size would
be unset only if there were some problem obtaining the value from the
operating system (and <STRONG>setupterm</STRONG> would still fail). For that reason,
- the <STRONG>LINES</STRONG> and <STRONG>COLUMNS</STRONG> environment variables may be useful for working
+ the <EM>LINES</EM> and <EM>COLUMNS</EM> environment variables may be useful for working
around window-size problems. Those have the drawback that if the
window is resized, those variables must be recomputed and reassigned.
To do this more easily, use the <STRONG>resize(1)</STRONG> program.
-ncurses 6.4 2023-1
1-25 <STRONG><A HREF="tset.1.html">tset(1)</A></STRONG>
+ncurses 6.4 2023-1
2-02 <STRONG><A HREF="tset.1.html">tset(1)</A></STRONG>
</PRE>
<div class="nav">
<ul>
projects / ncurses.git / blobdiff