path: root/contrib/ncurses/man/terminfo.tail
diff options
authorRong-En Fan <rafan@FreeBSD.org>2007-12-30 11:08:14 +0000
committerRong-En Fan <rafan@FreeBSD.org>2007-12-30 11:08:14 +0000
commit5ca44d1c915a0e0c87f8f347e61f7bfa65d609af (patch)
tree319eb1471eaf8c0c9cfc606e7cb8987ca9167507 /contrib/ncurses/man/terminfo.tail
parent01b82453a3d0c6d76d4afc340c07cfc2be4a6b7a (diff)
Import ncurses 5.6-20071222 snapshot onto the vender branch
Notes: svn path=/vendor/ncurses/dist/; revision=174993
Diffstat (limited to 'contrib/ncurses/man/terminfo.tail')
1 files changed, 11 insertions, 11 deletions
diff --git a/contrib/ncurses/man/terminfo.tail b/contrib/ncurses/man/terminfo.tail
index fa9a90d86654..60d0b70d170a 100644
--- a/contrib/ncurses/man/terminfo.tail
+++ b/contrib/ncurses/man/terminfo.tail
@@ -1,11 +1,11 @@
-.\" $Id: terminfo.tail,v 1.44 2006/04/01 22:47:01 tom Exp $
+.\" $Id: terminfo.tail,v 1.48 2007/06/02 20:30:40 tom Exp $
.\" Beginning of terminfo.tail file
.\" This file is part of ncurses.
.\" See "terminfo.head" for copyright.
.ps +1
.SS A Sample Entry
The following entry, describing an ANSI-standard terminal, is representative
of what a \fBterminfo\fR entry for a modern terminal typically looks like.
@@ -297,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
-.IR printf (3S)
+.IR printf (3)
like escapes \fB%x\fR in it.
For example, to address the cursor, the
.B cup
@@ -395,7 +395,7 @@ It is possible to form else-if's a la Algol 68:
where c\di\u are conditions, b\di\u are bodies.
-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.
@@ -993,7 +993,7 @@ with the rest of the terminfo description.
They are normally sent to the terminal, by the
.I init
option of the
-.IR tput
program, each time the user logs in.
They will be printed in the following order:
@@ -1578,7 +1578,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
-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
@@ -1599,19 +1599,19 @@ here but will return incorrect data for the terminal.
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.
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
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.
@@ -1688,7 +1688,7 @@ files containing terminal descriptions
Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey.