X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=man%2Fterminfo.tail;h=26aa6856b89d349fb2bb1a6c62f7d043840fab54;hp=8d73593cb8534ed2a3ce649227fd98d01e83e3d9;hb=b0916ab669030bac5c8590c0d66e36e1b9b34e9b;hpb=f70db18a0c3c6a828d8a5999be37239f01c9d98a diff --git a/man/terminfo.tail b/man/terminfo.tail index 8d73593c..26aa6856 100644 --- a/man/terminfo.tail +++ b/man/terminfo.tail @@ -1,4 +1,4 @@ -.\" $Id: terminfo.tail,v 1.47 2006/12/24 18:14:22 tom Exp $ +.\" $Id: terminfo.tail,v 1.57 2012/03/01 12:02:54 tom Exp $ .\" Beginning of terminfo.tail file .\" This file is part of ncurses. .\" See "terminfo.head" for copyright. @@ -25,7 +25,7 @@ of what a \fBterminfo\fR entry for a modern terminal typically looks like. kf11=\\E[W, kf12=\\E[X, kf2=\\E[N, kf3=\\E[O, kf4=\\E[P, kf5=\\E[Q, kf6=\\E[R, kf7=\\E[S, kf8=\\E[T, kf9=\\E[U, kich1=\\E[L, mc4=\\E[4i, mc5=\\E[5i, nel=\\r\\E[S, - op=\\E[37;40m, rep=%p1%c\\E[%p2%{1}%-%db, + op=\\E[37;40m, rep=%p1%c\\E[%p2%{1}%\-%db, rin=\\E[%p1%dT, s0ds=\\E(B, s1ds=\\E)B, s2ds=\\E*B, s3ds=\\E+B, setab=\\E[4%p1%dm, setaf=\\E[3%p1%dm, setb=\\E[4%?%p1%{1}%=%t4%e%p1%{3}%=%t6%e%p1%{4}%=%t1%e%p1%{6}%=%t3%e%p1%d%;m, @@ -75,14 +75,29 @@ map to an \s-1ESCAPE\s0 character, \fB^x\fR maps to a control-x for any appropriate x, and the sequences \fB\en \el \er \et \eb \ef \es\fR give a newline, line-feed, return, tab, backspace, form-feed, and space. -Other escapes include \fB\e^\fR for \fB^\fR, +Other escapes include +.bP +\fB\e^\fR for \fB^\fR, +.bP \fB\e\e\fR for \fB\e\fR, +.bP \fB\e\fR, for comma, +.bP \fB\e:\fR for \fB:\fR, +.bP and \fB\e0\fR for null. -(\fB\e0\fR will produce \e200, which does not terminate a string but behaves +.IP +\fB\e0\fR will produce \e200, which does not terminate a string but behaves as a null character on most terminals, providing CS7 is specified. -See stty(1).) +See stty(1). +.IP +The reason for this quirk is to maintain binary compatibility of the +compiled terminfo files with other implementations, +e.g., the SVr4 systems, which document this. +Compiled terminfo files use null-terminated strings, with no lengths. +Modifying this would require a new binary format, +which would not work with other implementations. +.PP Finally, characters may be given as three octal digits after a \fB\e\fR. .PP A delay in milliseconds may appear anywhere in a string capability, enclosed in @@ -125,8 +140,8 @@ will instead look in the directory \fB$HOME/.terminfo\fR for a compiled description. If it fails to find one there, and the environment variable TERMINFO_DIRS is set, it will interpret the contents of that variable as a list of colon- -separated directories to be searched (an empty entry is interpreted as a -command to search \fI\*d\fR). +separated directories (or database files) to be searched +(an empty entry is interpreted as a command to search \fI\*d\fR). If no description is found in any of the TERMINFO_DIRS directories, the fetch fails. .PP @@ -325,7 +340,9 @@ The \fB%\fR encodings have the following meanings: 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 @@ -333,20 +350,20 @@ print pop() like %c in \fBprintf\fP %s print pop() like %s in \fBprintf\fP .TP -%p[1-9] +%p[1\-9] push \fIi\fP'th parameter .TP -%P[a-z] -set dynamic variable [a-z] to pop() +%P[a\-z] +set dynamic variable [a\-z] to pop() .TP -%g[a-z] -get dynamic variable [a-z] and push it +%g[a\-z] +get dynamic variable [a\-z] and push it .TP -%P[A-Z] -set static variable [a-z] to pop() +%P[A\-Z] +set static variable [a\-z] to pop() .TP -%g[A-Z] -get static variable [a-z] and push it +%g[A\-Z] +get static variable [a\-z] and push it .IP The terms "static" and "dynamic" are misleading. Historically, these are simply two different sets of variables, @@ -363,7 +380,7 @@ integer constant \fInn\fP %l push strlen(pop) .TP -%+ %- %* %/ %m +%+ %\- %* %/ %m arithmetic (%m is mod): push(pop() op pop()) .TP %& %| %^ @@ -395,14 +412,14 @@ 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 -Use the \fB-f\fP option of \fBtic\fP or \fB@INFOCMP@\fP to see -the structure of if-the-else's. +Use the \fB\-f\fP option of \fB@TIC@\fP or \fB@INFOCMP@\fP to see +the structure of if-then-else's. Some strings, e.g., \fBsgr\fP can be very complicated when written on one line. -The \fB-f\fP option splits the string into lines with the parts indented. +The \fB\-f\fP option splits the string into lines with the parts indented. .PP Binary operations are in postfix form with the operands in the usual order. -That is, to get x-5 one would use "%gx%{5}%-". +That is, to get x\-5 one would use "%gx%{5}%-". %P and %g variables are persistent across escape-string evaluations. .PP @@ -540,7 +557,7 @@ automatically, so you need not compose insert/delete strings for an entry with \fBcsr\fR). .PP Yet another way to construct insert and delete might be to use a combination of -index with the memory-lock feature found on some terminals (like the HP-700/90 +index with the memory-lock feature found on some terminals (like the HP\-700/90 series, which however also has insert/delete). .PP Inserting lines at the top or bottom of the screen can also be @@ -591,6 +608,7 @@ Other terminals, such as the Concept 100 and the Perkin Elmer Owl, make a distinction between typed and untyped blanks on the screen, shifting upon an insert or delete only to an untyped blank on the screen which is either eliminated, or expanded to two untyped blanks. +.PP You can determine the kind of terminal you have by clearing the screen and then typing text separated by cursor motions. @@ -606,6 +624,7 @@ shifts over to the \*(lqdef\*(rq which then move together around the end of the current line and onto the next as you insert, you have the second type of terminal, and should give the capability \fBin\fR, which stands for \*(lqinsert null\*(rq. +.PP While these are two logically separate attributes (one line versus multi-line insert mode, and special treatment of untyped spaces) we have seen no terminals whose insert mode cannot be described with the single attribute. @@ -757,9 +776,9 @@ For example, the DEC vt220 supports most of the modes: .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 @@ -792,9 +811,9 @@ Writing out the above sequences, along with their dependencies yields .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 @@ -972,7 +991,7 @@ the numeric parameter .B it is given, showing the number of spaces the tabs are set to. This is normally used by the -.IR tset +.IR @TSET@ command to determine whether to set the mode for hardware tab expansion, and whether to set the tab stops. If the terminal has tab stops that can be saved in non-volatile memory, @@ -1172,9 +1191,9 @@ This alternate character set may be specified by the \fBacsc\fR capability. .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 @@ -1182,7 +1201,7 @@ UK pound sign ACS_STERLING f } arrow pointing down ACS_DARROW v . arrow pointing left ACS_LARROW < , arrow pointing right ACS_RARROW > + -arrow pointing up ACS_UARROW ^ - +arrow pointing up ACS_UARROW ^ \- board of squares ACS_BOARD # h bullet ACS_BULLET o ~ checker board (stipple) ACS_CKBOARD : a @@ -1190,7 +1209,7 @@ degree symbol ACS_DEGREE \e f diamond ACS_DIAMOND + ` greater-than-or-equal-to ACS_GEQUAL > z greek pi ACS_PI * { -horizontal line ACS_HLINE - q +horizontal line ACS_HLINE \- q lantern symbol ACS_LANTERN # i large plus or crossover ACS_PLUS + n less-than-or-equal-to ACS_LEQUAL < y @@ -1199,8 +1218,8 @@ lower right corner ACS_LRCORNER + j not-equal ACS_NEQUAL ! | plus/minus ACS_PLMINUS # g scan line 1 ACS_S1 ~ o -scan line 3 ACS_S3 - p -scan line 7 ACS_S7 - r +scan line 3 ACS_S3 \- p +scan line 7 ACS_S7 \- r scan line 9 ACS_S9 \&_ s solid square block ACS_BLOCK # 0 tee pointing down ACS_TTEE + w @@ -1225,7 +1244,7 @@ Most color terminals are either `Tektronix-like' or `HP-like'. Tektronix-like terminals have a predefined set of N colors (where N usually 8), and can set character-cell foreground and background characters independently, mixing them -into N * N color-pairs. +into N\ *\ N color-pairs. On HP-like terminals, the use must set each color pair up separately (foreground and background are not independently settable). Up to M color-pairs may be set up from 2*M different colors. @@ -1310,7 +1329,7 @@ which color pair is current. On a Tektronix-like terminal, the capability \fBccc\fR may be present to indicate that colors can be modified. If so, the \fBinitc\fR capability will -take a color number (0 to \fBcolors\fR - 1)and three more parameters which +take a color number (0 to \fBcolors\fR \- 1)and three more parameters which describe the color. These three parameters default to being interpreted as RGB (Red, Green, Blue) values. @@ -1322,7 +1341,7 @@ terminal-dependent. On an HP-like terminal, \fBinitp\fR may give a capability for changing a color-pair value. It will take seven parameters; a color-pair number (0 to -\fBmax_pairs\fR - 1), and two triples describing first background and then +\fBmax_pairs\fR \- 1), and two triples describing first background and then foreground colors. These parameters must be (Red, Green, Blue) or (Hue, Lightness, Saturation) depending on \fBhls\fR. @@ -1523,9 +1542,9 @@ A capability can be canceled by placing \fBxx@\fR to the left of the use reference that imports it, where \fIxx\fP is the capability. For example, the entry .PP - 2621-nl, smkx@, rmkx@, use=2621, + 2621\-nl, smkx@, rmkx@, use=2621, .PP -defines a 2621-nl that does not have the \fBsmkx\fR or \fBrmkx\fR capabilities, +defines a 2621\-nl that does not have the \fBsmkx\fR or \fBrmkx\fR capabilities, and hence does not turn on the function key labels when in visual mode. This is useful for different modes for a terminal, or for different user preferences. @@ -1542,7 +1561,7 @@ The man pages for 4.3BSD and older versions of \fBtgetent()\fP instruct the user allocate a 1024-byte buffer for the termcap entry. The entry gets null-terminated by the termcap library, so that makes the maximum safe length for a termcap entry -1k-1 (1023) bytes. +1k\-1 (1023) bytes. Depending on what the application and the termcap library being used does, and where in the termcap file the terminal type that \fBtgetent()\fP is searching for is, several bad things can happen. @@ -1568,19 +1587,15 @@ length of the entry as it exists in /etc/termcap, minus the backslash-newline pairs, which \fBtgetent()\fP strips out while reading it. Some termcap libraries strip off the final newline, too (GNU termcap does not). Now suppose: -.TP 5 -* +.bP a termcap entry before expansion is more than 1023 bytes long, -.TP 5 -* +.bP and the application has only allocated a 1k buffer, -.TP 5 -* +.bP 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, -.TP 5 -* +if it is the entry it wants, +.bP and \fBtgetent()\fP is searching for a terminal type that either is the long entry, appears in the termcap file after the long entry, or does not appear in the file at all (so that \fBtgetent()\fP has to search @@ -1599,27 +1614,27 @@ 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 -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. -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 +When in \-C (translate to termcap) mode, the \fBncurses\fR implementation of \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 +The \-c (check) option also checks resolved (after tc expansion) lengths. .SS Binary Compatibility It is not wise to count on portability of binary terminfo entries between commercial UNIX versions. The problem is that there are at least two versions -of terminfo (under HP-UX and AIX) which diverged from System V terminfo after +of terminfo (under HP\-UX and AIX) which diverged from System V terminfo after SVr1, and have added extension capabilities to the string table that (in the binary format) collide with System V and XSI Curses extensions. .SH EXTENSIONS @@ -1655,30 +1670,30 @@ the XSI Curses standard and (in some cases) different extension sets. Here is a summary, accurate as of October 1995: .PP -\fBSVR4, Solaris, ncurses\fR -- +\fBSVR4, Solaris, ncurses\fR \-\- These support all SVr4 capabilities. .PP -\fBSGI\fR -- +\fBSGI\fR \-\- Supports the SVr4 set, adds one undocumented extended string capability (\fBset_pglen\fR). .PP -\fBSVr1, Ultrix\fR -- +\fBSVr1, Ultrix\fR \-\- These support a restricted subset of terminfo capabilities. The booleans end with \fBxon_xoff\fR; the numerics with \fBwidth_status_line\fR; and the strings with \fBprtr_non\fR. .PP -\fBHP/UX\fR -- +\fBHP/UX\fR \-\- Supports the SVr1 subset, plus the SVr[234] numerics \fBnum_labels\fR, \fBlabel_height\fR, \fBlabel_width\fR, plus function keys 11 through 63, plus \fBplab_norm\fR, \fBlabel_on\fR, and \fBlabel_off\fR, plus some incompatible extensions in the string table. .PP -\fBAIX\fR -- +\fBAIX\fR \-\- Supports the SVr1 subset, plus function keys 11 through 63, plus a number of incompatible string table extensions. .PP -\fBOSF\fR -- +\fBOSF\fR \-\- Supports both the SVr4 set and the AIX extensions. .SH FILES .TP 25 @@ -1690,12 +1705,7 @@ files containing terminal descriptions \fBcurses\fR(3X), \fBprintf\fR(3), \fBterm\fR(\*n). +\fBterm_variables\fR(3X). .SH AUTHORS Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey. Based on pcurses by Pavel Curtis. -.\"# -.\"# The following sets edit modes for GNU EMACS -.\"# Local Variables: -.\"# mode:nroff -.\"# fill-column:79 -.\"# End: