diff options
Diffstat (limited to 'man/tset.1')
| -rw-r--r-- | man/tset.1 | 101 |
1 files changed, 59 insertions, 42 deletions
diff --git a/man/tset.1 b/man/tset.1 index 9743f5b5a7c8..e151e7532f41 100644 --- a/man/tset.1 +++ b/man/tset.1 @@ -1,5 +1,5 @@ .\"*************************************************************************** -.\" Copyright (c) 1998-2008,2010 Free Software Foundation, Inc. * +.\" Copyright (c) 1998-2011,2013 Free Software Foundation, Inc. * .\" * .\" Permission is hereby granted, free of charge, to any person obtaining a * .\" copy of this software and associated documentation files (the * @@ -26,12 +26,16 @@ .\" authorization. * .\"*************************************************************************** .\" -.\" $Id: tset.1,v 1.25 2010/12/04 18:38:55 tom Exp $ +.\" $Id: tset.1,v 1.29 2013/12/21 22:15:53 tom Exp $ .TH @TSET@ 1 "" +.ie \n(.g .ds `` \(lq +.el .ds `` `` +.ie \n(.g .ds '' \(rq +.el .ds '' '' .SH NAME -\fBtset\fR, \fBreset\fR \- terminal initialization +\fB@TSET@\fR, \fBreset\fR \- terminal initialization .SH SYNOPSIS -\fBtset\fR [\fB\-IQVcqrsw\fR] [\fB\-\fR] [\fB\-e\fR \fIch\fR] [\fB\-i\fR \fIch\fR] [\fB\-k\fR \fIch\fR] [\fB\-m\fR \fImapping\fR] [\fIterminal\fR] +\fB@TSET@\fR [\fB\-IQVcqrsw\fR] [\fB\-\fR] [\fB\-e\fR \fIch\fR] [\fB\-i\fR \fIch\fR] [\fB\-k\fR \fIch\fR] [\fB\-m\fR \fImapping\fR] [\fIterminal\fR] .br \fBreset\fR [\fB\-IQVcqrsw\fR] [\fB\-\fR] [\fB\-e\fR \fIch\fR] [\fB\-i\fR \fIch\fR] [\fB\-k\fR \fIch\fR] [\fB\-m\fR \fImapping\fR] [\fIterminal\fR] .SH DESCRIPTION @@ -49,13 +53,13 @@ error output device in the \fI/etc/ttys\fR file. \fIgetty\fR does this job by setting \fBTERM\fR according to the type passed to it by \fI/etc/inittab\fR.) .PP -4. The default terminal type, ``unknown''. +4. The default terminal type, \*(``unknown\*(''. .PP If the terminal type was not specified on the command-line, the \fB\-m\fR option mappings are then applied (see the section .B TERMINAL TYPE MAPPING for more information). -Then, if the terminal type begins with a question mark (``?''), the +Then, if the terminal type begins with a question mark (\*(``?\*(''), the user is prompted for confirmation of the terminal 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 @@ -72,7 +76,7 @@ Use the \fB\-c\fP or \fB\-w\fP option to select only the window sizing versus the other initialization. If neither option is given, both are assumed. .PP -When invoked as \fBreset\fR, \fBtset\fR sets cooked and echo modes, +When invoked as \fBreset\fR, \fB@TSET@\fR sets cooked and echo modes, turns off cbreak and raw modes, turns on newline translation and resets any unset special characters to their default values before doing the terminal initialization described above. This is useful @@ -89,6 +93,7 @@ The options are as follows: .TP 5 .B \-c Set control characters and modes. +.TP 5 .B \-e Set the erase character to \fIch\fR. .TP @@ -109,7 +114,7 @@ for more information. .TP .B \-Q Do not display any values for the erase, interrupt and line kill characters. -Normally \fBtset\fR displays the values for control characters which +Normally \fB@TSET@\fR displays the values for control characters which differ from the system's default values. .TP .B \-q @@ -137,7 +142,7 @@ unless \fBsetupterm\fP is not able to detect the window size. .PP The arguments for the \fB\-e\fR, \fB\-i\fR, and \fB\-k\fR options may either be entered as actual characters or by using the `hat' -notation, i.e., control-h may be specified as ``^H'' or ``^h''. +notation, i.e., control-h may be specified as \*(``^H\*('' or \*(``^h\*(''. . .SH SETTING THE ENVIRONMENT It is often desirable to enter the terminal type and information about @@ -146,35 +151,41 @@ This is done using the \fB\-s\fR option. .PP When the \fB\-s\fR option is specified, the commands to enter the information into the shell's environment are written to the standard output. If -the \fBSHELL\fR environmental variable ends in ``csh'', the commands +the \fBSHELL\fR environmental variable ends in \*(``csh\*('', the commands are for \fBcsh\fR, otherwise, they are for \fBsh\fR. Note, the \fBcsh\fR commands set and unset the shell variable \fBnoglob\fR, leaving it unset. The following line in the \fB.login\fR or \fB.profile\fR files will initialize the environment correctly: .sp - eval \`tset \-s options ... \` + eval \`@TSET@ \-s options ... \` . .SH TERMINAL TYPE MAPPING When the terminal is not hardwired into the system (or the current system information is incorrect) the terminal type derived from the \fI/etc/ttys\fR file or the \fBTERM\fR environmental variable is often something generic like \fBnetwork\fR, \fBdialup\fR, or \fBunknown\fR. -When \fBtset\fR is used in a startup script it is often desirable to +When \fB@TSET@\fR is used in a startup script it is often desirable to provide information about the type of terminal used on such ports. .PP The purpose of the \fB\-m\fR option is to map from some set of conditions to a terminal type, that is, to -tell \fBtset\fR -``If I'm on this port at a particular speed, guess that I'm on that -kind of terminal''. +tell \fB@TSET@\fR +\*(``If I'm on this port at a particular speed, +guess that I'm on that kind of terminal\*(''. .PP The argument to the \fB\-m\fR 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 ``>'', ``<'', ``@'', and ``!''; ``>'' -means greater than, ``<'' means less than, ``@'' means equal to -and ``!'' inverts the sense of the test. +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 +\*(``!\*('' 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. @@ -204,53 +215,57 @@ terminal. No whitespace characters are permitted in the \fB\-m\fR option argument. Also, to avoid problems with meta-characters, it is suggested that the entire \fB\-m\fR option argument be placed within single quote characters, -and that \fBcsh\fR users insert a backslash character (``\e'') before -any exclamation marks (``!''). +and that \fBcsh\fR users insert a backslash character (\*(``\e\*('') before +any exclamation marks (\*(``!\*(''). .SH HISTORY -The \fBtset\fR command appeared in BSD 3.0. The \fBncurses\fR implementation +The \fB@TSET@\fR command appeared in BSD 3.0. The \fBncurses\fR implementation was lightly adapted from the 4.4BSD sources for a terminfo environment by Eric S. Raymond <esr@snark.thyrsus.com>. .SH COMPATIBILITY -The \fBtset\fR utility has been provided for backward-compatibility with BSD +The \fB@TSET@\fR utility has been provided for backward-compatibility with BSD environments (under most modern UNIXes, \fB/etc/inittab\fR and \fIgetty\fR(1) can set \fBTERM\fR appropriately for each dial-up line; this obviates what was -\fBtset\fR's most important use). This implementation behaves like 4.4BSD +\fB@TSET@\fR's most important use). This implementation behaves like 4.4BSD tset, with a few exceptions specified here. .PP -The \fB\-S\fR option of BSD tset no longer works; it prints an error message to stderr -and dies. The \fB\-s\fR option only sets \fBTERM\fR, not \fBTERMCAP\fP. Both these -changes are because the \fBTERMCAP\fR variable is no longer supported under -terminfo-based \fBncurses\fR, which makes \fBtset \-S\fR useless (we made it die -noisily rather than silently induce lossage). +The \fB\-S\fR option of BSD tset no longer works; +it prints an error message to stderr and dies. +The \fB\-s\fR option only sets \fBTERM\fR, not \fBTERMCAP\fP. +Both of these changes are because the \fBTERMCAP\fR variable +is no longer supported under terminfo-based \fBncurses\fR, +which makes \fB@TSET@ \-S\fR useless +(we made it die noisily rather than silently induce lossage). .PP There was an undocumented 4.4BSD feature that invoking tset via a link named `TSET` (or via any other name beginning with an upper-case letter) set the terminal to use upper-case only. This feature has been omitted. .PP The \fB\-A\fR, \fB\-E\fR, \fB\-h\fR, \fB\-u\fR and \fB\-v\fR -options were deleted from the \fBtset\fR +options were deleted from the \fB@TSET@\fR utility in 4.4BSD. None of them were documented in 4.3BSD and all are of limited utility at best. The \fB\-a\fR, \fB\-d\fR, and \fB\-p\fR 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 \fB\-m\fR option instead. The -\fB\-n\fP option remains, but has no effect. The \fB\-adnp\fR options are therefore -omitted from the usage summary above. +three options be changed to use the \fB\-m\fR option instead. +The \fB\-n\fP option remains, but has no effect. +The \fB\-adnp\fR options are therefore omitted from the usage summary above. .PP -It is still permissible to specify the \fB\-e\fR, \fB\-i\fR, and \fB\-k\fR options without -arguments, although it is strongly recommended that such usage be fixed to +It is still permissible to specify the \fB\-e\fR, \fB\-i\fR, +and \fB\-k\fR options without arguments, +although it is strongly recommended that such usage be fixed to explicitly specify the character. .PP -As of 4.4BSD, executing \fBtset\fR as \fBreset\fR no longer implies the \fB\-Q\fR -option. Also, the interaction between the \- option and the \fIterminal\fR -argument in some historic implementations of \fBtset\fR has been removed. +As of 4.4BSD, +executing \fB@TSET@\fR as \fBreset\fR no longer implies the \fB\-Q\fR option. +Also, the interaction between the \- option and the \fIterminal\fR +argument in some historic implementations of \fB@TSET@\fR has been removed. .SH ENVIRONMENT -The \fBtset\fR command uses these environment variables: +The \fB@TSET@\fR command uses these environment variables: .TP 5 SHELL -tells \fBtset\fP whether to initialize \fBTERM\fP using \fBsh\fP or +tells \fB@TSET@\fP whether to initialize \fBTERM\fP using \fBsh\fP or \fBcsh\fP syntax. .TP 5 TERM @@ -260,7 +275,7 @@ Each terminal type is distinct, though many are similar. TERMCAP may denote the location of a termcap database. If it is not an absolute pathname, e.g., begins with a `/', -\fBtset\fP removes the variable from the environment before looking +\fB@TSET@\fP removes the variable from the environment before looking for the terminal description. .SH FILES .TP 5 @@ -270,6 +285,7 @@ system port name to terminal type mapping database (BSD versions only). @TERMINFO@ terminal capability database .SH SEE ALSO +.hy 0 csh(1), sh(1), stty(1), @@ -278,6 +294,7 @@ tty(4), terminfo(5), ttys(5), environ(7) +.hy .PP This describes \fBncurses\fR version @NCURSES_MAJOR@.@NCURSES_MINOR@ (patch @NCURSES_PATCH@). |