X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fterminfo.5.html;h=becb62195bc697a2d8b2afc53b7fae7f11cbabd0;hp=be06a7044aa5c80aa0704ba97899b2c415dba80a;hb=62ca6190a9a8ddccb2c4d5ca7b2ef9f88432da65;hpb=acc28c6418f43cbf15187f2f1fd9a562d5d96535 diff --git a/doc/html/man/terminfo.5.html b/doc/html/man/terminfo.5.html index be06a704..becb6219 100644 --- a/doc/html/man/terminfo.5.html +++ b/doc/html/man/terminfo.5.html @@ -1,4 +1,3 @@ - +
+ +- terminfo(5) File Formats terminfo(5) --
+
terminfo - terminal capability data base --
+
/usr/share/terminfo/*/* --
+
Terminfo is a data base describing terminals, used by screen-oriented programs such as nvi(1), rogue(1) and libraries such as curses(3x). Terminfo describes termi- nals by giving a set of capabilities which they have, by specifying how to perform screen operations, and by speci- fying padding requirements and initialization sequences. - This describes ncurses version 5.9 (patch 20140809). + This describes ncurses version 6.0 (patch 20161224). Entries in terminfo consist of a sequence of `,' separated fields (embedded commas may be escaped with a backslash or @@ -132,7 +129,8 @@ For more on terminal naming conventions, see the term(7) manual page. - Predefined Capabilities + +
The following is a complete table of the capabilities included in a terminfo description block and available to terminfo-using code. In each line of the table, @@ -256,7 +254,7 @@ status_line_esc_ok eslok es escape can be used on the status line tilde_glitch hz hz cannot print ~'s - (hazeltine) + (Hazeltine) transparent_underline ul ul underline character @@ -292,7 +290,7 @@ color-pairs on the screen maximum_windows wnum MW maximum number of - defineable windows + definable windows no_color_video ncv NC video attributes that cannot be used with colors @@ -928,9 +926,8 @@ multiple codesets color_names colornm Yw Give name for color #1 - define_bit_image_region defbi Yx Define rectan- - gualar bit image - region + define_bit_image_region defbi Yx Define rectangular + bit image region device_type devt dv Indicate lan- guage/codeset sup- port @@ -985,17 +982,18 @@ set_page_length slines YZ Set page length to #1 lines + set_tb_margin smgtb MT Sets both top and bottom margins to #1, #2 - The XSI Curses standard added these hardcopy capabili- + The XSI Curses standard added these hardcopy capabili- ties. They were used in some post-4.1 versions of System V curses, e.g., Solaris 2.5 and IRIX 6.x. Except for YI, the ncurses termcap names for them are invented. Accord- - ing to the XSI Curses standard, they have no termcap + ing to the XSI Curses standard, they have no termcap names. If your compiled terminfo entries use these, they - may not be binary-compatible with System V terminfo + may not be binary-compatible with System V terminfo entries after SVr4.1; beware! @@ -1022,51 +1020,53 @@ tations use sL for termcap). - User-Defined Capabilities - The preceding section listed the predefined capabilities. - They deal with some special features for terminals no - longer (or possibly never) produced. Occasionally there - are special features of newer terminals which are awkward + +
+ The preceding section listed the predefined capabilities. + They deal with some special features for terminals no + longer (or possibly never) produced. Occasionally there + are special features of newer terminals which are awkward or impossible to represent by reusing the predefined capa- bilities. ncurses addresses this limitation by allowing user-defined capabilities. The tic and infocmp programs provide the -x - option for this purpose. When -x is set, tic treats - unknown capabilities as user-defined. That is, if tic - encounters a capability name which it does not recognize, - it infers its type (boolean, number or string) from the + option for this purpose. When -x is set, tic treats + unknown capabilities as user-defined. That is, if tic + encounters a capability name which it does not recognize, + it infers its type (boolean, number or string) from the syntax and makes an extended table entry for that capabil- - ity. The use_extended_names function makes this informa- + ity. The use_extended_names function makes this informa- tion conditionally available to applications. The ncurses - library provides the data leaving most of the behavior to + library provides the data leaving most of the behavior to applications: o User-defined capability strings whose name begins with "k" are treated as function keys. - o The types (boolean, number, string) determined by tic + o The types (boolean, number, string) determined by tic can be inferred by successful calls on tigetflag, etc. - o If the capability name happens to be two characters, - the capability is also available through the termcap + o If the capability name happens to be two characters, + the capability is also available through the termcap interface. While termcap is said to be extensible because it does not - use a predefined set of capabilities, in practice it has - been limited to the capabilities defined by terminfo - implementations. As a rule, user-defined capabilities + use a predefined set of capabilities, in practice it has + been limited to the capabilities defined by terminfo + implementations. As a rule, user-defined capabilities intended for use by termcap applications should be limited - to booleans and numbers to avoid running past the 1023 - byte limit assumed by termcap implementations and their - applications. In particular, providing extended sets of - function keys (past the 60 numbered keys and the handful + to booleans and numbers to avoid running past the 1023 + byte limit assumed by termcap implementations and their + applications. In particular, providing extended sets of + function keys (past the 60 numbered keys and the handful of special named keys) is best done using the longer names available using terminfo. - A Sample Entry + +
The following entry, describing an ANSI-standard terminal, - is representative of what a terminfo entry for a modern + is representative of what a terminfo entry for a modern terminal typically looks like. ansi|ansi/pc-term compatible with color, @@ -1100,43 +1100,44 @@ smul=\E[4m, tbc=\E[3g, u6=\E[%i%d;%dR, u7=\E[6n, u8=\E[?%[;0123456789]c, u9=\E[c, vpa=\E[%i%p1%dd, - Entries may continue onto multiple lines by placing white - space at the beginning of each line except the first. - Comments may be included on lines beginning with "#". + Entries may continue onto multiple lines by placing white + space at the beginning of each line except the first. + Comments may be included on lines beginning with "#". Capabilities in terminfo are of three types: - o Boolean capabilities which indicate that the terminal + o Boolean capabilities which indicate that the terminal has some particular feature, - o numeric capabilities giving the size of the terminal + o numeric capabilities giving the size of the terminal or the size of particular delays, and - o string capabilities, which give a sequence which can + o string capabilities, which give a sequence which can be used to perform particular terminal operations. - Types of Capabilities - All capabilities have names. For instance, the fact that - ANSI-standard terminals have automatic margins (i.e., an - automatic return and line-feed when the end of a line is - reached) is indicated by the capability am. Hence the + +
+ All capabilities have names. For instance, the fact that + ANSI-standard terminals have automatic margins (i.e., an + automatic return and line-feed when the end of a line is + reached) is indicated by the capability am. Hence the description of ansi includes am. Numeric capabilities are - followed by the character "#" and then a positive value. - Thus cols, which indicates the number of columns the ter- - minal has, gives the value "80" for ansi. Values for + followed by the character "#" and then a positive value. + Thus cols, which indicates the number of columns the ter- + minal has, gives the value "80" for ansi. Values for numeric capabilities may be specified in decimal, octal or - hexadecimal, using the C programming language conventions + hexadecimal, using the C programming language conventions (e.g., 255, 0377 and 0xff or 0xFF). - Finally, string valued capabilities, such as el (clear to + Finally, string valued capabilities, such as el (clear to end of line sequence) are given by the two-character code, - an "=", and then a string ending at the next following + an "=", and then a string ending at the next following ",". - A number of escape sequences are provided in the string + A number of escape sequences are provided in the string valued capabilities for easy encoding of characters there. - Both \E and \e map to an ESCAPE character, ^x maps to a - control-x for any appropriate x, and the sequences \n \l - \r \t \b \f \s give a newline, line-feed, return, tab, + Both \E and \e map to an ESCAPE character, ^x maps to a + control-x for any appropriate x, and the sequences \n \l + \r \t \b \f \s give a newline, line-feed, return, tab, backspace, form-feed, and space. Other escapes include o \^ for ^, @@ -1149,43 +1150,51 @@ o and \0 for null. - \0 will produce \200, which does not terminate a - string but behaves as a null character on most termi- + \0 will produce \200, which does not terminate a + string but behaves as a null character on most termi- nals, providing CS7 is specified. See stty(1). - The reason for this quirk is to maintain binary com- - patibility of the compiled terminfo files with other - implementations, e.g., the SVr4 systems, which docu- - ment this. Compiled terminfo files use null-termi- - nated strings, with no lengths. Modifying this would + The reason for this quirk is to maintain binary com- + patibility of the compiled terminfo files with other + implementations, e.g., the SVr4 systems, which docu- + ment this. Compiled terminfo files use null-termi- + nated strings, with no lengths. Modifying this would require a new binary format, which would not work with other implementations. - Finally, characters may be given as three octal digits + Finally, characters may be given as three octal digits after a \. - A delay in milliseconds may appear anywhere in a string - capability, enclosed in $<..> brackets, as in el=\EK$<5>, - and padding characters are supplied by tputs to provide - this delay. The delay must be a number with at most one - decimal place of precision; it may be followed by suffixes - "*" or "/" or both. A "*" indicates that the padding - required is proportional to the number of lines affected - by the operation, and the amount given is the per- - affected-unit padding required. (In the case of insert - character, the factor is still the number of lines - affected.) Normally, padding is advisory if the device - has the xon capability; it is used for cost computation - but does not trigger delays. A "/" suffix indicates that - the padding is mandatory and forces a delay of the given - number of milliseconds even on devices for which xon is - present to indicate flow control. + A delay in milliseconds may appear anywhere in a string + capability, enclosed in $<..> brackets, as in el=\EK$<5>, + and padding characters are supplied by tputs to provide + this delay. + + o The delay must be a number with at most one decimal + place of precision; it may be followed by suffixes "*" + or "/" or both. + + o A "*" indicates that the padding required is propor- + tional to the number of lines affected by the opera- + tion, and the amount given is the per-affected-unit + padding required. (In the case of insert character, + the factor is still the number of lines affected.) + + Normally, padding is advisory if the device has the + xon capability; it is used for cost computation but + does not trigger delays. + + o A "/" suffix indicates that the padding is mandatory + and forces a delay of the given number of milliseconds + even on devices for which xon is present to indicate + flow control. Sometimes individual capabilities must be commented out. To do this, put a period before the capability name. For example, see the second ind in the example above. - Fetching Compiled Descriptions + +
The ncurses library searches for terminal descriptions in several places. It uses only the first description found. The library has a compiled-in list of places to search @@ -1208,7 +1217,7 @@ database files) to be searched. An empty directory name (i.e., if the variable begins - or ends with a colon, or contains adacent colons) is + or ends with a colon, or contains adjacent colons) is interpreted as the system location /usr/share/ter- minfo. @@ -1221,7 +1230,8 @@ o the system terminfo directory, /usr/share/terminfo (the compiled-in default). - Preparing Descriptions + +
We now outline how to prepare descriptions of terminals. The most effective way to prepare a terminal description is by imitating the description of a similar terminal in @@ -1240,7 +1250,8 @@ ally needed. A similar test can be used for insert char- acter. - Basic Capabilities + +
The number of columns on each line for the terminal is given by the cols numeric capability. If the terminal is a CRT, then the number of lines on the screen is given by @@ -1317,7 +1328,8 @@ am, bel=^G, clear=^Z, cols#80, cr=^M, cub1=^H, cud1=^J, ind=^J, lines#24, - Parameterized Strings + +
Cursor addressing and other strings requiring parameters in the terminal are described by a parameterized string capability, with printf-like escapes such as %x in it. @@ -1345,15 +1357,15 @@ to allow the next character to be a "-" flag, avoid- ing interpreting "%-" as an operator. - %c print pop() like %c in printf + %c print pop() like %c in printf - %s print pop() like %s in printf + %s print pop() like %s in printf %p[1-9] push i'th parameter %P[a-z] - set dynamic variable [a-z] to pop() + set dynamic variable [a-z] to pop() %g[a-z]/ get dynamic variable [a-z] and push it @@ -1379,7 +1391,7 @@ %l push strlen(pop) %+, %-, %*, %/, %m - arithmetic (%m is mod): push(pop() op pop()) + arithmetic (%m is mod): push(pop() op pop()) %&, %|, %^ bit operations (AND, OR and exclusive-OR): push(pop() @@ -1393,7 +1405,7 @@ %!, %~ unary operations (logical and bit complement): - push(op pop()) + push(op pop()) %i add 1 to first two parameters (for ANSI terminals) @@ -1446,7 +1458,8 @@ ter. Then the same is done for the second parameter. More complex arithmetic is possible using the stack. - Cursor Motions + +
If the terminal has a fast way to home the cursor (to very upper left corner of screen) then this can be given as home; similarly a fast way of getting to the lower left- @@ -1485,7 +1498,8 @@ rmcup sequence is output (to the state prior to outputting rmcup), specify nrrmc. - Area Clears + +
If the terminal can clear from the current position to the end of the line, leaving the cursor where it is, this should be given as el. If the terminal can clear from the @@ -1497,7 +1511,8 @@ (Thus, it can be simulated by a request to delete a large number of lines, if a true ed is not available.) - Insert/delete line and vertical motions + +
If the terminal can open a new blank line before the line where the cursor is, this should be given as il1; this is done only from the first position of a line. The cursor @@ -1544,7 +1559,7 @@ late destructive scrolling; their documentation cautions you not to define csr unless this is true. This curses implementation is more liberal and will do explicit erases - after scrolling if ndstr is defined. + after scrolling if ndsrc is defined. If the terminal has the ability to define a window as part of memory, which all commands affect, it should be given @@ -1559,7 +1574,8 @@ lines up from below or that scrolling back with ri may bring down non-blank lines. - Insert/Delete Character + +
There are two basic kinds of intelligent terminals with respect to insert/delete character which can be described using terminfo. The most common insert/delete character @@ -1647,7 +1663,8 @@ n blanks without moving the cursor) can be given as ech with one parameter. - Highlighting, Underlining, and Visible Bells + +
If your terminal has one or more kinds of display attributes, these can be represented in a number of dif- ferent ways. You should choose one display form as stand- @@ -1774,7 +1791,8 @@ erasable with a blank, then this should be indicated by giving eo. - Keypad and Function Keys + +
If the terminal has a keypad that transmits codes when the keys are pressed, this information can be given. Note that it is not possible to handle terminals where the key- @@ -1854,7 +1872,8 @@ or more pln sequences to make sure that the change becomes visible. - Tabs and Initialization + +
If the terminal has hardware tabs, the command to advance to the next tab stop can be given as ht (usually control I). A "back-tab" command which moves leftward to the pre- @@ -1867,7 +1886,7 @@ initially set every n spaces when the terminal is powered up, the numeric parameter it is given, showing the number of spaces the tabs are set to. This is normally used by - the tset command to determine whether to set the mode for + the 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, the terminfo description can assume that @@ -1880,7 +1899,7 @@ These strings are expected to set the terminal into modes consistent with the rest of the terminfo description. They are normally sent to the terminal, by the init option - of the tput program, each time the user logs in. They + of the tput program, each time the user logs in. They will be printed in the following order: run the program @@ -1908,7 +1927,7 @@ A set of sequences that does a harder reset from a totally unknown state can be given as rs1, rs2, rf and rs3, analo- gous to is1 , is2 , if and is3 respectively. These - strings are output by the reset program, which is used + strings are output by the reset program, which is used when the terminal gets into a wedged state. Commands are normally placed in rs1, rs2 rs3 and rf only if they pro- duce annoying effects on the screen and are not necessary @@ -1918,10 +1937,10 @@ normally needed since the terminal is usually already in 80 column mode. - The reset program writes strings including iprog, etc., in + The reset program writes strings including iprog, etc., in the same order as the init program, using rs1, etc., instead of is1, etc. If any of rs1, rs2, rs3, or rf reset - capability strings are missing, the reset program falls + capability strings are missing, the reset program falls back upon the corresponding initialization capability string. @@ -1932,7 +1951,8 @@ described by this, the sequence can be placed in is2 or if. - Delays and Padding + +
Many older and slower terminals do not support either XON/XOFF or DTR handshaking, including hard copy terminals and some very archaic CRTs (including, for example, DEC @@ -1958,7 +1978,8 @@ ter as a pad, then this can be given as pad. Only the first character of the pad string is used. - Status Lines + +
Some terminals have an extra "status line" which is not normally used by software (and thus not counted in the terminal's lines capability). @@ -1993,7 +2014,8 @@ capabilities. They are documented here in case they ever become important. - Line Graphics + +
Many terminals have alternate character sets useful for forms-drawing. Terminfo and curses build in support for the drawing characters supported by the VT100, with some @@ -2043,42 +2065,59 @@ acter pairs right to left in sequence; these become the ACSC string. - Color Handling - 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. 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. - ANSI-compatible terminals are Tektronix-like. + +
+ The curses library functions init_pair and init_color + manipulate the color pairs and color values discussed in + this section (see curs_color(3x) for details on these and + related functions). + + Most color terminals are either "Tektronix-like" or "HP- + like": + + o Tektronix-like terminals have a predefined set of N + colors (where N is usually 8), and can set character- + cell foreground and background characters indepen- + dently, mixing them into N * N color-pairs. + + o On HP-like terminals, the user 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. ANSI-compatible + terminals are Tektronix-like. Some basic color capabilities are independent of the color method. The numeric capabilities colors and pairs specify - the maximum numbers of colors and color-pairs that can be - displayed simultaneously. The op (original pair) string - resets foreground and background colors to their default - values for the terminal. The oc string resets all colors - or color-pairs to their default values for the terminal. - Some terminals (including many PC terminal emulators) - erase screen areas with the current background color - rather than the power-up default background; these should + the maximum numbers of colors and color-pairs that can be + displayed simultaneously. The op (original pair) string + resets foreground and background colors to their default + values for the terminal. The oc string resets all colors + or color-pairs to their default values for the terminal. + Some terminals (including many PC terminal emulators) + erase screen areas with the current background color + rather than the power-up default background; these should have the boolean capability bce. - To change the current foreground or background color on a - Tektronix-type terminal, use setaf (set ANSI foreground) - and setab (set ANSI background) or setf (set foreground) - and setb (set background). These take one parameter, the - color number. The SVr4 documentation describes only - setaf/setab; the XPG4 draft says that "If the terminal - supports ANSI escape sequences to set background and fore- - ground, they should be coded as setaf and setab, respec- - tively. If the terminal supports other escape sequences - to set background and foreground, they should be coded as - setf and setb, respectively. The vidputs() function and - the refresh functions use setaf and setab if they are - defined." + While the curses library works with color pairs (reflect- + ing the inability of some devices to set foreground and + background colors independently), there are separate capa- + bilities for setting these features: + + o To change the current foreground or background color + on a Tektronix-type terminal, use setaf (set ANSI + foreground) and setab (set ANSI background) or setf + (set foreground) and setb (set background). These + take one parameter, the color number. The SVr4 docu- + mentation describes only setaf/setab; the XPG4 draft + says that "If the terminal supports ANSI escape + sequences to set background and foreground, they + should be coded as setaf and setab, respectively. + + o If the terminal supports other escape sequences to set + background and foreground, they should be coded as + setf and setb, respectively. The vidputs and the + refresh functions use the setaf and setab capabilities + if they are defined. The setaf/setab and setf/setb capabilities take a single numeric argument each. Argument values 0-7 of setaf/setab @@ -2118,21 +2157,25 @@ On an HP-like terminal, use scp with a color-pair number parameter to set which color pair is current. - On a Tektronix-like terminal, the capability ccc may be - present to indicate that colors can be modified. If so, - the initc capability will take a color number (0 to colors - - 1)and three more parameters which describe the color. - These three parameters default to being interpreted as RGB - (Red, Green, Blue) values. If the boolean capability hls - is present, they are instead as HLS (Hue, Lightness, Satu- - ration) indices. The ranges are terminal-dependent. - - On an HP-like terminal, initp may give a capability for - changing a color-pair value. It will take seven parame- - ters; a color-pair number (0 to max_pairs - 1), and two - triples describing first background and then foreground - colors. These parameters must be (Red, Green, Blue) or - (Hue, Lightness, Saturation) depending on hls. + Some terminals allow the color values to be modified: + + o On a Tektronix-like terminal, the capability ccc may + be present to indicate that colors can be modified. + If so, the initc capability will take a color number + (0 to colors - 1)and three more parameters which + describe the color. These three parameters default to + being interpreted as RGB (Red, Green, Blue) values. + If the boolean capability hls is present, they are + instead as HLS (Hue, Lightness, Saturation) indices. + The ranges are terminal-dependent. + + o On an HP-like terminal, initp may give a capability + for changing a color-pair value. It will take seven + parameters; a color-pair number (0 to max_pairs - 1), + and two triples describing first background and then + foreground colors. These parameters must be (Red, + Green, Blue) or (Hue, Lightness, Saturation) depending + on hls. On some color terminals, colors collide with highlights. You can register these collisions with the ncv capability. @@ -2166,7 +2209,8 @@ SVr4 curses does nothing with ncv, ncurses recognizes it and optimizes the output in favor of colors. - Miscellaneous + +
If the terminal requires other than a null (zero) charac- ter as a pad, then this can be given as pad. Only the first character of the pad string is used. If the termi- @@ -2239,7 +2283,8 @@ text, including mc4, is transparently passed to the printer while an mc5p is in effect. - Glitches and Braindamage + +
Hazeltine terminals, which do not allow "~" characters to be displayed should indicate hz. @@ -2271,7 +2316,8 @@ Other specific terminal problems may be corrected by adding more capabilities of the form xx. - Similar Terminals + +
If there are two very similar terminals, one (the variant) can be defined as being just like the other (the base) with certain exceptions. In the definition of the vari- @@ -2295,7 +2341,8 @@ labels when in visual mode. This is useful for different modes for a terminal, or for different user preferences. - Pitfalls of Long Entries + +
Long terminfo entries are unlikely to be a problem; to date, no entry has even approached terminfo's 4096-byte string-table maximum. Unfortunately, the termcap transla- @@ -2303,13 +2350,13 @@ termcap translations of long terminfo entries can cause problems. - The man pages for 4.3BSD and older versions of tgetent() + The man pages for 4.3BSD and older versions of tgetent instruct the user to 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. Depending on what the application and the termcap library being used does, and - where in the termcap file the terminal type that tgetent() + where in the termcap file the terminal type that tgetent is searching for is, several bad things can happen. Some termcap libraries print a warning message or exit if @@ -2329,7 +2376,7 @@ one, because it affects more than just users of that par- ticular terminal. This is the length of the entry as it exists in /etc/termcap, minus the backslash-newline pairs, - which tgetent() strips out while reading it. Some termcap + which tgetent strips out while reading it. Some termcap libraries strip off the final newline, too (GNU termcap does not). Now suppose: @@ -2343,28 +2390,28 @@ matter what its length, to see if it is the entry it wants, - o and tgetent() is searching for a terminal type that + o and tgetent 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 tgetent() has to search the whole - termcap file). - - Then tgetent() will overwrite memory, perhaps its stack, - and probably core dump the program. Programs like telnet - are particularly vulnerable; modern telnets pass along - values like the terminal type automatically. The results - are almost as undesirable with a termcap library, like - SunOS 4.1.3 and Ultrix 4.4, that prints warning messages - when it reads an overly long termcap entry. If a termcap - library truncates long entries, like OSF/1 3.0, it is - immune to dying here but will return incorrect data for - the terminal. + at all (so that tgetent has to search the whole term- + cap file). + + Then tgetent will overwrite memory, perhaps its stack, and + probably core dump the program. Programs like telnet are + particularly vulnerable; modern telnets pass along values + like the terminal type automatically. The results are + almost as undesirable with a termcap library, like SunOS + 4.1.3 and Ultrix 4.4, that prints warning messages when it + reads an overly long termcap entry. If a termcap library + truncates long entries, like OSF/1 3.0, it is immune to + dying here but will return incorrect data for the termi- + nal. 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 tgetent() only does "tc" expan- - sion once it is found the terminal type it was looking - for, not while searching. + that terminal type, since tgetent 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 @@ -2380,7 +2427,8 @@ (check) option also checks resolved (after tc expansion) lengths. - 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 @@ -2390,8 +2438,7 @@ and XSI Curses extensions. --
+
Searching for terminal descriptions in $HOME/.terminfo and TERMINFO_DIRS is not supported by older implementations. @@ -2460,20 +2507,17 @@ OSF -- Supports both the SVr4 set and the AIX extensions. --
+
/usr/share/terminfo/?/* files containing terminal descriptions --
- tic(1m), infocmp(1m), curses(3x), printf(3), term(5). - term_variables(3x). +
+ tic(1m), infocmp(1m), curses(3x), curs_color(3x), + printf(3), term(5). term_variables(3x). --
+
Zeyd M. Ben-Halim, Eric S. Raymond, Thomas E. Dickey. Based on pcurses by Pavel Curtis. @@ -2481,10 +2525,43 @@ terminfo(5)-