ncurses 5.7 - patch 20100102

[ncurses.git] / man / terminfo.tail

diff --git a/man/terminfo.tail b/man/terminfo.tail
index 00e0c5927943af0458afd82207abe070f48a2a0f..802a6f6b48aa16649e1f6b74fe898c27b0371c75 100644 (file)
--- a/man/terminfo.tail
+++ b/man/terminfo.tail
@@ -1,10 +1,11 @@
-.\" $Id: terminfo.tail,v 1.42 2005/06/25 22:46:03 tom Exp $
+.\" $Id: terminfo.tail,v 1.50 2009/09/19 19:56:15 tom Exp $

 .\" Beginning of terminfo.tail file
 .\" Beginning of terminfo.tail file

+.\" This file is part of ncurses.

 .\" See "terminfo.head" for copyright.
 .ps +1
 .\" See "terminfo.head" for copyright.
 .ps +1

-.PP
+.

 .SS A Sample Entry
 .SS A Sample Entry

-.PP
+.

 The following entry, describing an ANSI-standard terminal, is representative
 of what a \fBterminfo\fR entry for a modern terminal typically looks like.
 .PP
 The following entry, describing an ANSI-standard terminal, is representative
 of what a \fBterminfo\fR entry for a modern terminal typically looks like.
 .PP


@@ -296,7 +297,7 @@ while the Lear Siegler \s-1ADM-3\s0 is described as
 Cursor addressing and other strings requiring parameters
 in the terminal are described by a
 parameterized string capability, with
 Cursor addressing and other strings requiring parameters
 in the terminal are described by a
 parameterized string capability, with

-.IR printf (3S)
+.IR printf (3)

 like escapes \fB%x\fR in it.
 For example, to address the cursor, the
 .B cup
 like escapes \fB%x\fR in it.
 For example, to address the cursor, the
 .B cup


@@ -324,7 +325,9 @@ The \fB%\fR encodings have the following meanings:
 outputs `%'
 .TP
 %\fI[[\fP:\fI]flags][width[.precision]][\fPdoxXs\fI]\fP
 outputs `%'
 .TP
 %\fI[[\fP:\fI]flags][width[.precision]][\fPdoxXs\fI]\fP

-as in \fBprintf\fP, flags are [-+#] and space
+as in \fBprintf\fP, flags are [-+#] and space.
+Use a `:' to allow the next character to be a `-' flag,
+avoiding interpreting "%-" as an operator.

 .TP
 %c
 print pop() like %c in \fBprintf\fP
 .TP
 %c
 print pop() like %c in \fBprintf\fP


@@ -394,7 +397,7 @@ It is possible to form else-if's a la Algol 68:
 .IP
 where c\di\u are conditions, b\di\u are bodies.
 .IP
 .IP
 where c\di\u are conditions, b\di\u are bodies.
 .IP

-Use the \fB-f\fP option of \fBtic\fP or \fBinfocmp\fP to see
+Use the \fB-f\fP option of \fBtic\fP or \fB@INFOCMP@\fP to see

 the structure of if-the-else's.
 Some strings, e.g., \fBsgr\fP can be very complicated when written
 on one line.
 the structure of if-the-else's.
 Some strings, e.g., \fBsgr\fP can be very complicated when written
 on one line.


@@ -756,9 +759,9 @@ For example, the DEC vt220 supports most of the modes:
 .PP
 .TS
 center;
 .PP
 .TS
 center;

-l c c
-l c c
-lw28 lw6 lw2 lw20.
+l l l
+l l l
+lw18 lw14 lw18.

 \fBtparm parameter     attribute       escape sequence\fP
 
 none   none    \\E[0m
 \fBtparm parameter     attribute       escape sequence\fP
 
 none   none    \\E[0m


@@ -791,9 +794,9 @@ Writing out the above sequences, along with their dependencies yields
 .PP
 .TS
 center;
 .PP
 .TS
 center;

-l c c
-l c c
-lw28 lw6 lw2 lw20.
+l l l
+l l l
+lw18 lw14 lw18.

 \fBsequence    when to output  terminfo translation\fP
 
 \\E[0  always  \\E[0
 \fBsequence    when to output  terminfo translation\fP
 
 \\E[0  always  \\E[0


@@ -992,28 +995,36 @@ with the rest of the terminfo description.
 They are normally sent to the terminal, by the
 .I init
 option of the
 They are normally sent to the terminal, by the
 .I init
 option of the

-.IR tput
+.IR @TPUT@

 program, each time the user logs in.
 They will be printed in the following order:
 program, each time the user logs in.
 They will be printed in the following order:

+.RS
+.TP

 run the program
 run the program

-.BR iprog ;
+.BR iprog
+.TP

 output
 output

-.BR is1 ;
-.BR is2 ;
+.BR is1
+.BR is2
+.TP

 set the margins using
 .BR mgc ,
 .BR smgl
 and
 set the margins using
 .BR mgc ,
 .BR smgl
 and

-.BR smgr ;
+.BR smgr
+.TP

 set tabs using
 .B tbc
 and
 set tabs using
 .B tbc
 and

-.BR hts ;
+.BR hts
+.TP

 print the file
 print the file

-.BR if ;
+.BR if
+.TP

 and finally
 output
 .BR is3 .
 and finally
 output
 .BR is3 .

+.RE

 .PP
 Most initialization is done with
 .BR is2 .
 .PP
 Most initialization is done with
 .BR is2 .


@@ -1024,17 +1035,21 @@ and special cases in
 .B is1
 and
 .BR is3 .
 .B is1
 and
 .BR is3 .

-A pair of sequences that does a harder reset from a totally unknown state
-can be analogously given as
+.PP
+A set of sequences that does a harder reset from a totally unknown state
+can be given as

 .BR rs1 ,
 .BR rs2 ,
 .BR rs1 ,
 .BR rs2 ,

-.BR rf ,
+.BR rf

 and
 .BR rs3 ,
 analogous to
 and
 .BR rs3 ,
 analogous to

-.B is2
+.B is1 ,
+.B is2 ,
+.B if

 and
 and

-.BR if .
+.BR is3
+respectively.

 These strings are output by the
 .IR reset
 program, which is used when the terminal gets into a wedged state.
 These strings are output by the
 .IR reset
 program, which is used when the terminal gets into a wedged state.


@@ -1052,6 +1067,28 @@ normally be part of
 but it causes an annoying glitch of the screen and is not normally
 needed since the terminal is usually already in 80 column mode.
 .PP
 but it causes an annoying glitch of the screen and is not normally
 needed since the terminal is usually already in 80 column mode.
 .PP

+The
+.IR reset
+program writes strings
+including
+.BR iprog ,
+etc., in the same order as the
+.IR init
+program, using 
+.BR rs1 ,
+etc., instead of
+.BR is1 ,
+etc.
+If any of
+.BR rs1 ,
+.BR rs2 ,
+.BR rs3 ,
+or
+.BR rf
+reset capability strings are missing, the
+.IR reset
+program falls back upon the corresponding initialization capability string.
+.PP

 If there are commands to set and clear tab stops, they can be given as
 .B tbc
 (clear all tab stops)
 If there are commands to set and clear tab stops, they can be given as
 .B tbc
 (clear all tab stops)


@@ -1137,9 +1174,9 @@ This alternate character set may be specified by the \fBacsc\fR capability.
 .PP
 .TS H
 center expand;
 .PP
 .TS H
 center expand;

-c l l c
-c l l c
-lw28 lw6 lw2 lw20.
+l l l l
+l l l l
+lw25 lw10 lw6 lw6.

 .\".TH
 \fBGlyph       ACS     Ascii   VT100\fR
 \fBName        Name    Default Name\fR
 .\".TH
 \fBGlyph       ACS     Ascii   VT100\fR
 \fBName        Name    Default Name\fR


@@ -1543,7 +1580,7 @@ and the application has only allocated a 1k buffer,
 *
 and the termcap library (like the one in BSD/OS 1.1 and GNU) reads
 the whole entry into the buffer, no matter what its length, to see
 *
 and the termcap library (like the one in BSD/OS 1.1 and GNU) reads
 the whole entry into the buffer, no matter what its length, to see

-if it's the entry it wants,
+if it is the entry it wants,

 .TP 5
 *
 and \fBtgetent()\fP is searching for a terminal type that either is the
 .TP 5
 *
 and \fBtgetent()\fP is searching for a terminal type that either is the


@@ -1564,19 +1601,19 @@ here but will return incorrect data for the terminal.
 .PP
 The "after tc expansion" length will have a similar effect to the
 above, but only for people who actually set TERM to that terminal
 .PP
 The "after tc expansion" length will have a similar effect to the
 above, but only for people who actually set TERM to that terminal

-type, since \fBtgetent()\fP only does "tc" expansion once it's found the
+type, since \fBtgetent()\fP only does "tc" expansion once it is found the

 terminal type it was looking for, not while searching.
 .PP
 In summary, a termcap entry that is longer than 1023 bytes can cause,
 on various combinations of termcap libraries and applications, a core
 dump, warnings, or incorrect operation.
 terminal type it was looking for, not while searching.
 .PP
 In summary, a termcap entry that is longer than 1023 bytes can cause,
 on various combinations of termcap libraries and applications, a core
 dump, warnings, or incorrect operation.

-If it's too long even before
+If it is too long even before

 "tc" expansion, it will have this effect even for users of some other
 terminal types and users whose TERM variable does not have a termcap
 entry.
 .PP
 When in -C (translate to termcap) mode, the \fBncurses\fR implementation of
 "tc" expansion, it will have this effect even for users of some other
 terminal types and users whose TERM variable does not have a termcap
 entry.
 .PP
 When in -C (translate to termcap) mode, the \fBncurses\fR implementation of

-\fBtic\fR(1) issues warning messages when the pre-tc length of a termcap
+\fB@TIC@\fR(1M) issues warning messages when the pre-tc length of a termcap

 translation is too long.
 The -c (check) option also checks resolved (after tc
 expansion) lengths.
 translation is too long.
 The -c (check) option also checks resolved (after tc
 expansion) lengths.


@@ -1650,10 +1687,10 @@ Supports both the SVr4 set and the AIX extensions.
 \*d/?/*
 files containing terminal descriptions
 .SH SEE ALSO
 \*d/?/*
 files containing terminal descriptions
 .SH SEE ALSO

-\fBtic\fR(1M),
-\fBinfocmp\fR(1M),
+\fB@TIC@\fR(1M),
+\fB@INFOCMP@\fR(1M),

 \fBcurses\fR(3X),
 \fBcurses\fR(3X),

-\fBprintf\fR(3S),
+\fBprintf\fR(3),

 \fBterm\fR(\*n).
 .SH AUTHORS
 Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.
 \fBterm\fR(\*n).
 .SH AUTHORS
 Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.