X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=man%2Fterminfo.tail;h=d06d3a963a63105363eaf1f1bd62cefff7e1aa4a;hp=8d73593cb8534ed2a3ce649227fd98d01e83e3d9;hb=37babca07fea18b480155ef60ef302ca09fca152;hpb=f70db18a0c3c6a828d8a5999be37239f01c9d98a diff --git a/man/terminfo.tail b/man/terminfo.tail index 8d73593c..d06d3a96 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.49 2008/02/16 20:57:43 tom Exp $ .\" Beginning of terminfo.tail file .\" This file is part of ncurses. .\" See "terminfo.head" for copyright. @@ -325,7 +325,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 @@ -1578,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 -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,13 +1601,13 @@ 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.