ncurses 6.2 - patch 20210213

[ncurses.git] / man / tset.1

diff --git a/man/tset.1 b/man/tset.1
index c011f792c9ba759b3317306da6d4b24ee153b2d8..65b1ef2299672fe637fdaf9c052eba12e8646134 100644 (file)
--- a/man/tset.1
+++ b/man/tset.1
@@ -1,5 +1,6 @@
 .\"***************************************************************************
 .\"***************************************************************************

-.\" Copyright (c) 1998-2016,2017 Free Software Foundation, Inc.              *
+.\" Copyright 2018,2020 Thomas E. Dickey                                     *
+.\" Copyright 1998-2016,2017 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            *
 .\"                                                                          *
 .\" Permission is hereby granted, free of charge, to any person obtaining a  *
 .\" copy of this software and associated documentation files (the            *


@@ -26,14 +27,15 @@
 .\" authorization.                                                           *
 .\"***************************************************************************
 .\"
 .\" authorization.                                                           *
 .\"***************************************************************************
 .\"

-.\" $Id: tset.1,v 1.49 2017/04/16 21:30:15 tom Exp $
+.\" $Id: tset.1,v 1.55 2020/02/02 23:34:34 tom Exp $

 .TH @TSET@ 1 ""
 .ie \n(.g .ds `` \(lq
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
 .el       .ds '' ''
 .de bP
 .TH @TSET@ 1 ""
 .ie \n(.g .ds `` \(lq
 .el       .ds `` ``
 .ie \n(.g .ds '' \(rq
 .el       .ds '' ''
 .de bP

-.IP \(bu 4
+.ie n  .IP \(bu 4
+.el    .IP \(bu 2

 ..
 .SH NAME
 \fB@TSET@\fR, \fB@RESET@\fR \- terminal initialization
 ..
 .SH NAME
 \fB@TSET@\fR, \fB@RESET@\fR \- terminal initialization


@@ -55,7 +57,7 @@ standard output,
 .bP
 standard input and
 .bP
 .bP
 standard input and
 .bP

-ultimately \*(lq/dev/tty\*(rq
+ultimately \*(``/dev/tty\*(''

 .PP
 to obtain terminal settings.
 Having retrieved these settings, \fB@TSET@\fP remembers which
 .PP
 to obtain terminal settings.
 Having retrieved these settings, \fB@TSET@\fP remembers which


@@ -81,7 +83,8 @@ 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
 .B TERMINAL TYPE MAPPING
 for more information).
 Then, if the terminal type begins with a question mark (\*(``?\*(''), the

-user is prompted for confirmation of the terminal type.  An empty
+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,
 response confirms the type, or, another type can be entered to specify
 a new type.
 Once the terminal type has been determined,


@@ -100,7 +103,8 @@ and \fBCOLUMNS\fP variables specify this),
 use this to set the operating system's notion of the window size.
 .bP
 if the \*(``\fB\-c\fP\*('' option is enabled,
 use this to set the operating system's notion of the window size.
 .bP
 if the \*(``\fB\-c\fP\*('' option is enabled,

-the backspace, interrupt and line kill characters (among many other things) are set
+the backspace, interrupt and line kill characters
+(among many other things) are set

 .bP
 unless the \*(``\fB\-I\fP\*('' option is enabled,
 the terminal
 .bP
 unless the \*(``\fB\-I\fP\*('' option is enabled,
 the terminal


@@ -205,11 +209,13 @@ the terminal's capabilities into the shell's environment.
 This is done using the \fB\-s\fR option.
 .PP
 When the \fB\-s\fR option is specified, the commands to enter the information
 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
+into the shell's environment are written to the standard output.
+If

 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
 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
+\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 ... \`
 or \fB.profile\fR files will initialize the environment correctly:
 .sp
     eval \`@TSET@ \-s options ... \`


@@ -230,7 +236,8 @@ 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
 .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
+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
 \*(``>\*('',
 string (delimited by either the operator or the colon character).
 The operator may be any combination of
 \*(``>\*('',


@@ -246,14 +253,17 @@ of the standard error output (which should be the control terminal).
 The terminal type is a string.
 .PP
 If the terminal type is not specified on the command line, the \fB\-m\fR
 The terminal type is a string.
 .PP
 If the terminal type is not specified on the command line, the \fB\-m\fR

-mappings are applied to the terminal type.  If the port type and baud
+mappings are applied to the terminal type.
+If the port type and baud

 rate match the mapping, the terminal type specified in the mapping
 rate match the mapping, the terminal type specified in the mapping

-replaces the current type.  If more than one mapping is specified, the
+replaces the current type.
+If more than one mapping is specified, the

 first applicable mapping is used.
 .PP
 For example, consider the following mapping: \fBdialup>9600:vt100\fR.
 The port type is dialup , the operator is >, the baud rate
 first applicable mapping is used.
 .PP
 For example, consider the following mapping: \fBdialup>9600:vt100\fR.
 The port type is dialup , the operator is >, the baud rate

-specification is 9600, and the terminal type is vt100.  The result of
+specification is 9600, and the terminal type is vt100.
+The result of

 this mapping is to specify that if the terminal type is \fBdialup\fR,
 and the baud rate is greater than 9600 baud, a terminal type of
 \fBvt100\fR will be used.
 this mapping is to specify that if the terminal type is \fBdialup\fR,
 and the baud rate is greater than 9600 baud, a terminal type of
 \fBvt100\fR will be used.


@@ -296,7 +306,7 @@ that he began work in October 1977,
 continuing development over the next few years.
 .PP
 In September 1980, Eric Allman modified \fBtset\fP,
 continuing development over the next few years.
 .PP
 In September 1980, Eric Allman modified \fBtset\fP,

-adding the code from the existing \*(lqreset\*(rq
+adding the code from the existing \*(``reset\*(''

 feature when \fBtset\fP was invoked as \fBreset\fP.
 Rather than simply copying the existing program,
 in this merged version, \fBtset\fP used the termcap database
 feature when \fBtset\fP was invoked as \fBreset\fP.
 Rather than simply copying the existing program,
 in this merged version, \fBtset\fP used the termcap database


@@ -324,9 +334,10 @@ In fact, the commonly-used \fBreset\fP utility
 is always an alias for \fBtset\fP.
 .PP
 The \fB@TSET@\fR utility provides for backward-compatibility with BSD
 is always an alias for \fBtset\fP.
 .PP
 The \fB@TSET@\fR utility provides for backward-compatibility with BSD

-environments (under most modern UNIXes, \fB/etc/inittab\fR and \fIgetty\fR(1)
+environments (under most modern UNIXes, \fB/etc/inittab\fR and \fBgetty\fR(1)

 can set \fBTERM\fR appropriately for each dial-up line; this obviates what was
 can set \fBTERM\fR appropriately for each dial-up line; this obviates what was

-\fB@TSET@\fR's most important use).  This implementation behaves like 4.4BSD
+\fB@TSET@\fR's most important use).
+This implementation behaves like 4.4BSD

 \fBtset\fP, with a few exceptions specified here.
 .PP
 A few options are different
 \fBtset\fP, with a few exceptions specified here.
 .PP
 A few options are different


@@ -351,9 +362,11 @@ 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
 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
+widespread use.
+It is strongly recommended that any usage of these

 three options be changed to use the \fB\-m\fR option instead.
 three options be changed to use the \fB\-m\fR option instead.

-The \fB\-a\fP, \fB\-d\fP, and \fB\-p\fR options are therefore omitted from the usage summary above.
+The \fB\-a\fP, \fB\-d\fP, and \fB\-p\fR options
+are therefore omitted from the usage summary above.

 .PP
 Very old systems, e.g., 3BSD, used a different terminal driver which
 was replaced in 4BSD in the early 1980s.
 .PP
 Very old systems, e.g., 3BSD, used a different terminal driver which
 was replaced in 4BSD in the early 1980s.