X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Ftset.1.html;h=d76c27d8368511b40b423d6f19a438531b876e4f;hp=4c5ad2fd46604ee4e56a9888775edbbd98d528e6;hb=f344f8539c1543f8cd65a5bb142dbaf23b9421d2;hpb=62ca6190a9a8ddccb2c4d5ca7b2ef9f88432da65
diff --git a/doc/html/man/tset.1.html b/doc/html/man/tset.1.html
index 4c5ad2fd..d76c27d8 100644
--- a/doc/html/man/tset.1.html
+++ b/doc/html/man/tset.1.html
@@ -1,6 +1,6 @@
@@ -99,35 +99,66 @@
("?"), the user is prompted for confirmation of the termi-
nal type. An empty response confirms the type, or,
another type can be entered to specify a new type. Once
- the terminal type has been determined, the terminfo entry
- for the terminal is retrieved. If no terminfo entry is
- found for the type, the user is prompted for another ter-
- minal type.
+ the terminal type has been determined, the terminal
+ description for the terminal is retrieved. If no terminal
+ description is found for the type, the user is prompted
+ for another terminal type.
- Once the terminfo entry is retrieved, the window size,
- backspace, interrupt and line kill characters (among many
- other things) are set and the terminal and tab initializa-
- tion strings are sent to the standard error output.
- Finally, if the erase, interrupt and line kill characters
- have changed, or are not set to their default values,
- their values are displayed to the standard error output.
+ Once the terminal description is retrieved,
+
+ o if the "-w" option is enabled, tset may update the
+ terminal's window size.
+
+ If the window size cannot be obtained from the operat-
+ ing system, but the terminal description (or environ-
+ ment, e.g., LINES and COLUMNS variables specify this),
+ use this to set the operating system's notion of the
+ window size.
+
+ o if the "-c" option is enabled, the backspace, inter-
+ rupt and line kill characters (among many other
+ things) are set
+
+ o unless the "-I" option is enabled, the terminal and
+ tab initialization strings are sent to the standard
+ error output, and tset waits one second (in case a
+ hardware reset was issued).
+
+ o Finally, if the erase, interrupt and line kill charac-
+ ters have changed, or are not set to their default
+ values, their values are displayed to the standard
+ error output.
- When invoked as reset, tset sets cooked and echo modes,
- turns off cbreak and raw modes, turns on newline transla-
- tion and resets any unset special characters to their
- default values before doing the terminal initialization
- described above. This is useful after a program dies
- leaving a terminal in an abnormal state. Note, you may
- have to type
+ When invoked as reset, tset sets the terminal modes to
+ "sane" values:
+
+ o sets cooked and echo modes,
+
+ o turns off cbreak and raw modes,
+
+ o turns on newline translation and
- <LF>reset<LF>
+ o resets any unset special characters to their default
+ values
- (the line-feed character is normally control-J) to get the
- terminal to work, as carriage-return may no longer work in
- the abnormal state. Also, the terminal will often not
- echo the command.
+ before doing the terminal initialization described above.
+ Also, rather than using the terminal initialization
+ strings, it uses the terminal reset strings.
+
+ The reset command is useful after a program dies leaving a
+ terminal in an abnormal state:
+
+ o you may have to type
+
+ <LF>reset<LF>
+
+ (the line-feed character is normally control-J) to get
+ the terminal to work, as carriage-return may no longer
+ work in the abnormal state.
+
+ o Also, the terminal will often not echo the command.
@@ -144,51 +175,51 @@
-k Set the line kill character to ch.
- -m Specify a mapping from a port type to a terminal.
+ -m Specify a mapping from a port type to a terminal.
See the section TERMINAL TYPE MAPPING for more infor-
mation.
- -Q Do not display any values for the erase, interrupt
+ -Q Do not display any values for the erase, interrupt
and line kill characters. Normally tset displays the
- values for control characters which differ from the
+ values for control characters which differ from the
system's default values.
- -q The terminal type is displayed to the standard out-
- put, and the terminal is not initialized in any way.
+ -q The terminal type is displayed to the standard out-
+ put, and the terminal is not initialized in any way.
The option "-" by itself is equivalent but archaic.
-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 TERM to the standard output.
See the section SETTING THE ENVIRONMENT for details.
-V reports the version of ncurses which was used in this
program, and exits.
- -w Resize the window to match the size deduced via
- setupterm. Normally this has no effect, unless
+ -w Resize the window to match the size deduced via
+ setupterm(3x). Normally this has no effect, unless
setupterm is not able to detect the window size.
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".
If neither -c or -w is given, both options are assumed.
- 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 SHELL environmental variable
- ends in "csh", the commands are for csh, otherwise, they
- are for sh. Note, the csh commands set and unset the
- shell variable noglob, leaving it unset. The following
- line in the .login or .profile files will initialize the
+ information into the shell's environment are written to
+ the standard output. If the SHELL environmental variable
+ ends in "csh", the commands are for csh, otherwise, they
+ are for sh. Note, the csh commands set and unset the
+ shell variable noglob, leaving it unset. The following
+ line in the .login or .profile files will initialize the
environment correctly:
eval `tset -s options ... `
@@ -197,74 +228,91 @@
When the terminal is not hardwired into the system (or the
current system information is incorrect) the terminal type
- derived from the /etc/ttys file or the TERM environmental
- variable is often something generic like network, dialup,
- or unknown. When tset is used in a startup script it is
- often desirable to provide information about the type of
+ derived from the /etc/ttys file or the TERM environmental
+ variable is often something generic like network, dialup,
+ or unknown. When tset is used in a startup script it is
+ often desirable to provide information about the type of
terminal used on such ports.
- The -m options maps from some set of conditions to a ter-
- minal type, that is, to tell tset "If I'm on this port at
- a particular speed, guess that I'm on that kind of termi-
+ The -m options maps from some set of conditions to a ter-
+ minal type, that is, to tell tset "If I'm on this port at
+ a particular speed, guess that I'm on that kind of termi-
nal".
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
+ cation, 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 ">", "<", "@", and "!"; ">" means greater
- than, "<" means less than, "@" means equal to and "!"
+ combination of ">", "<", "@", and "!"; ">" means 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 terminal). The
+ 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:
dialup>9600:vt100. 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 dialup, and the baud rate
- is greater than 9600 baud, a terminal type of vt100 will
+ is greater than 9600 baud, a terminal type of vt100 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, -m
+ type will match any port type. For example, -m
dialup:vt100 -m :?xterm 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 csh users
- insert a backslash character ("\") before any exclamation
+ 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 csh users
+ insert a backslash character ("\") before any exclamation
marks ("!").
- A reset command appeared in 2BSD (1979), written by Kurt
- Shoens.
-
- A separate tset command was provided in 2BSD by Eric All-
- man. While the oldest published source (from 1979) pro-
- vides both programs, Allman's comments in the 2BSD source
- code indicate that he began work in October 1977, continu-
- ing development over the next few years.
-
- In 1980, Eric Allman modified tset to provide a "reset"
- feature when the program was invoked as reset.
+ A reset command appeared in 2BSD (April 1979), written by
+ Kurt Shoens. This program set the erase and kill charac-
+ ters to ^H (backspace) and @ respectively. Mark Horton
+ improved that in 3BSD (October 1979), adding intr, quit,
+ start/stop and eof characters as well as changing the pro-
+ gram to avoid modifying any user settings.
+
+ Later in 4.1BSD (December 1980), Mark Horton added a call
+ to the tset program using the -I and -Q options, i.e.,
+ using that to improve the terminal modes. With those
+ options, that version of reset did not use the termcap
+ database.
+
+ A separate tset command was provided in 2BSD by Eric All-
+ man. While the oldest published source (from 1979) pro-
+ vides both tset and reset, Allman's comments in the 2BSD
+ source code indicate that he began work in October 1977,
+ continuing development over the next few years.
+
+ In September 1980, Eric Allman modified tset, adding the
+ code from the existing "reset" feature when tset was
+ invoked as reset. Rather than simply copying the existing
+ program, in this merged version, tset used the termcap
+ database to do additional (re)initialization of the termi-
+ nal. This version appeared in 4.1cBSD, late in 1982.
+
+ Other developers (e.g., Keith Bostic and Jim Bloom) con-
+ tinued to modify tset until 4.4BSD was released in 1993.
The ncurses implementation was lightly adapted from the
4.4BSD sources for a terminfo environment by Eric S. Ray-
@@ -387,7 +435,7 @@
csh(1), sh(1), stty(1), curs_terminfo(3x), tty(4),
terminfo(5), ttys(5), environ(7)
- This describes ncurses version 6.0 (patch 20161224).
+ This describes ncurses version 6.0 (patch 20170114).