X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=man%2Fterminfo.tail;h=ef064ed949b0fe9fad405f01bbf85c50ae9ef5f5;hp=152297c12830185bf4dd406a83b9f989c472d7bf;hb=eccca377f55c70b12e3e92621d94d1e1c1fcfb7d;hpb=a8e3f06ac309504143cd56ac9ec55889bfdf4914 diff --git a/man/terminfo.tail b/man/terminfo.tail index 152297c1..ef064ed9 100644 --- a/man/terminfo.tail +++ b/man/terminfo.tail @@ -1,4 +1,4 @@ -.\" $Id: terminfo.tail,v 1.85 2017/04/22 18:59:02 tom Exp $ +.\" $Id: terminfo.tail,v 1.90 2019/01/20 20:21:46 tom Exp $ .\" Beginning of terminfo.tail file .\" This file is part of ncurses. .\" See "terminfo.head" for copyright. @@ -370,7 +370,7 @@ it may still be possible to craft a working .B nel out of one or both of them. .PP -These capabilities suffice to describe hard-copy and \*(lqglass-tty\*(rq terminals. +These capabilities suffice to describe hard-copy and \*(``glass-tty\*('' terminals. Thus the model 33 teletype is described as .PP .DT @@ -428,9 +428,9 @@ The \fB%\fR encodings have the following meanings: outputs \*(``%\*('' .TP \fB%\fP\fI[[\fP:\fI]flags][width[.precision]][\fP\fBdoxXs\fP\fI]\fP -as in \fBprintf\fP, flags are \fI[\-+#]\fP and \fIspace\fP. +as in \fBprintf\fP(3), flags are \fI[\-+#]\fP and \fIspace\fP. Use a \*(``:\*('' to allow the next character to be a \*(``\-\*('' flag, -avoiding interpreting "%\-" as an operator. +avoiding interpreting \*(``%\-\*('' as an operator. .TP \f(CW%c\fP print \fIpop()\fP like %c in \fBprintf\fP @@ -516,12 +516,12 @@ to be sent \eE&a12c03Y padded for 6 milliseconds. Note that the order of the rows and columns is inverted here, and that the row and column are printed as two digits. -Thus its \fBcup\fR capability is \*(lqcup=6\eE&%p2%2dc%p1%2dY\*(rq. +Thus its \fBcup\fR capability is \*(``cup=6\eE&%p2%2dc%p1%2dY\*(''. .PP The Microterm \s-1ACT-IV\s0 needs the current row and column sent preceded by a \fB^T\fR, with the row and column simply encoded in binary, -\*(lqcup=^T%p1%c%p2%c\*(rq. -Terminals which use \*(lq%c\*(rq need to be able to +\*(``cup=^T%p1%c%p2%c\*(''. +Terminals which use \*(``%c\*('' need to be able to backspace the cursor (\fBcub1\fR), and to move the cursor up one line on the screen (\fBcuu1\fR). This is necessary because it is not always safe to transmit \fB\en\fR @@ -531,7 +531,7 @@ tabs are never expanded, so \et is safe to send. This turns out to be essential for the Ann Arbor 4080.) .PP A final example is the \s-1LSI ADM\s0-3a, which uses row and column -offset by a blank character, thus \*(lqcup=\eE=%p1%' '%+%c%p2%' '%+%c\*(rq. +offset by a blank character, thus \*(``cup=\eE=%p1%' '%+%c%p2%' '%+%c\*(''. After sending \*(``\eE=\*('', this pushes the first parameter, pushes the ASCII value for a space (32), adds them (pushing the sum on the stack in place of the two previous values) and outputs that value as a character. @@ -569,7 +569,7 @@ spaces to the right) these can be given as .BR cub , .BR cuf , and -.BR cuu +.B cuu with a single parameter indicating how many spaces to move. These are primarily useful if the terminal does not have .BR cup , @@ -700,18 +700,18 @@ either eliminated, or expanded to two untyped blanks. You can determine the kind of terminal you have by clearing the screen and then typing text separated by cursor motions. -Type \*(lqabc\ \ \ \ def\*(rq using local -cursor motions (not spaces) between the \*(lqabc\*(rq and the \*(lqdef\*(rq. -Then position the cursor before the \*(lqabc\*(rq and put the terminal in insert +Type \*(``abc\ \ \ \ def\*('' using local +cursor motions (not spaces) between the \*(``abc\*('' and the \*(``def\*(''. +Then position the cursor before the \*(``abc\*('' and put the terminal in insert mode. If typing characters causes the rest of the line to shift rigidly and characters to fall off the end, then your terminal does not distinguish between blanks and untyped positions. -If the \*(lqabc\*(rq -shifts over to the \*(lqdef\*(rq which then move together around the end of the +If the \*(``abc\*('' +shifts over to the \*(``def\*('' 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. +\*(``insert null\*(''. .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 @@ -959,7 +959,7 @@ give this sequence as If there is a way to make the cursor completely invisible, give that as .BR civis . The capability -.BR cnorm +.B cnorm should be given which undoes the effects of both of these modes. .PP If your terminal correctly generates underlined characters @@ -1128,25 +1128,25 @@ They will be printed in the following order: .RS .TP run the program -.BR iprog +.B iprog .TP output -.BR is1 -.BR is2 +.B is1 +.B is2 .TP set the margins using .BR mgc , -.BR smgl +.B smgl and -.BR smgr +.B smgr .TP set tabs using .B tbc and -.BR hts +.B hts .TP print the file -.BR if +.B if .TP and finally output @@ -1167,7 +1167,7 @@ A set of sequences that does a harder reset from a totally unknown state can be given as .BR rs1 , .BR rs2 , -.BR rf +.B rf and .BR rs3 , analogous to @@ -1175,13 +1175,13 @@ analogous to .B is2 , .B if and -.BR is3 +.B is3 respectively. These strings are output by the \fB@RESET@\fP program, which is used when the terminal gets into a wedged state. Commands are normally placed in .BR rs1 , -.BR rs2 +.B rs2 .B rs3 and .B rf @@ -1196,7 +1196,7 @@ needed since the terminal is usually already in 80 column mode. The \fB@RESET@\fP program writes strings including .BR iprog , etc., in the same order as the -.IR init +.I init program, using .BR rs1 , etc., instead of @@ -1207,7 +1207,7 @@ If any of .BR rs2 , .BR rs3 , or -.BR rf +.B rf reset capability strings are missing, the \fB@RESET@\fP program falls back upon the corresponding initialization capability string. .PP @@ -1290,7 +1290,8 @@ They are documented here in case they ever become important. .SS Line Graphics .PP Many terminals have alternate character sets useful for forms-drawing. -Terminfo and \fBcurses\fR built-in support for the drawing characters +Terminfo and \fBcurses\fR have built-in support +for most of the drawing characters supported by the VT100, with some characters from the AT&T 4410v1 added. This alternate character set may be specified by the \fBacsc\fR capability. .PP @@ -1301,8 +1302,8 @@ l l l l l _ _ _ _ _ lw25 lw10 lw6 lw6 lw6. .\".TH -\fBGlyph ACS Ascii VT100 VT100\fR -\fBName Name Default Char Code\fR +\fBGlyph ACS Ascii acsc acsc\fR +\fBName Name Default Char Value\fR arrow pointing right ACS_RARROW > + 0x2b arrow pointing left ACS_LARROW < , 0x2c arrow pointing up ACS_UARROW ^ \- 0x2d @@ -1345,9 +1346,17 @@ lowercase \*(``i\*('' mapping. .bP The DEC VT100 implemented graphics using the alternate character set feature, temporarily switching \fImodes\fP and sending characters -in the range 0x60 (96) to 0x7e (126). +in the range 0x60 (96) to 0x7e (126) +(the \fBacsc Value\fP column in the table). .bP The AT&T terminal added graphics characters outside that range. +.IP +Some of the characters within the range do not match the VT100; +presumably they were used in the AT&T terminal: +\fIboard of squares\fP replaces the VT100 \fInewline\fP symbol, while +\fIlantern symbol\fP replaces the VT100 \fIvertical tab\fP symbol. +The other VT100 symbols for control characters (\fIhorizontal tab\fP, +\fIcarriage return\fP and \fIline-feed\fP) are not (re)used in curses. .PP The best way to define a new device's graphics set is to add a column to a copy of this table for your terminal, giving the character which @@ -1834,6 +1843,7 @@ files containing terminal descriptions \fBprintf\fR(3), \fBterm\fR(\*n). \fBterm_variables\fR(3X). +\fBuser_caps\fR(5). .SH AUTHORS Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey. Based on pcurses by Pavel Curtis.