curs_terminfo.3x.html 21 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354
  1. <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
  2. <!--
  3. ****************************************************************************
  4. * Copyright (c) 1999-2007,2008 Free Software Foundation, Inc. *
  5. * *
  6. * Permission is hereby granted, free of charge, to any person obtaining a *
  7. * copy of this software and associated documentation files (the *
  8. * "Software"), to deal in the Software without restriction, including *
  9. * without limitation the rights to use, copy, modify, merge, publish, *
  10. * distribute, distribute with modifications, sublicense, and/or sell *
  11. * copies of the Software, and to permit persons to whom the Software is *
  12. * furnished to do so, subject to the following conditions: *
  13. * *
  14. * The above copyright notice and this permission notice shall be included *
  15. * in all copies or substantial portions of the Software. *
  16. * *
  17. * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS *
  18. * OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF *
  19. * MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. *
  20. * IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, *
  21. * DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR *
  22. * OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR *
  23. * THE USE OR OTHER DEALINGS IN THE SOFTWARE. *
  24. * *
  25. * Except as contained in this notice, the name(s) of the above copyright *
  26. * holders shall not be used in advertising or otherwise to promote the *
  27. * sale, use or other dealings in this Software without prior written *
  28. * authorization. *
  29. ****************************************************************************
  30. * @Id: curs_terminfo.3x,v 1.30 2008/08/16 20:53:27 tom Exp @
  31. -->
  32. <HTML>
  33. <HEAD>
  34. <TITLE>curs_terminfo 3x</TITLE>
  35. <link rev=made href="mailto:bug-ncurses@gnu.org">
  36. <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
  37. </HEAD>
  38. <BODY>
  39. <H1>curs_terminfo 3x</H1>
  40. <HR>
  41. <PRE>
  42. <!-- Manpage converted by man2html 3.0.1 -->
  43. <STRONG><A HREF="curs_terminfo.3x.html">curs_terminfo(3x)</A></STRONG> <STRONG><A HREF="curs_terminfo.3x.html">curs_terminfo(3x)</A></STRONG>
  44. </PRE>
  45. <H2>NAME</H2><PRE>
  46. <STRONG>del_curterm</STRONG>, <STRONG>mvcur</STRONG>, <STRONG>putp</STRONG>, <STRONG>restartterm</STRONG>, <STRONG>set_curterm</STRONG>,
  47. <STRONG>setterm</STRONG>, <STRONG>setupterm</STRONG>, <STRONG>tigetflag</STRONG>, <STRONG>tigetnum</STRONG>, <STRONG>tigetstr</STRONG>, <STRONG>tparm</STRONG>,
  48. <STRONG>tputs</STRONG>, <STRONG>vid_attr</STRONG>, <STRONG>vid_puts</STRONG>, <STRONG>vidattr</STRONG>, <STRONG>vidputs</STRONG> - <STRONG>curses</STRONG>
  49. interfaces to terminfo database
  50. </PRE>
  51. <H2>SYNOPSIS</H2><PRE>
  52. <STRONG>#include</STRONG> <STRONG>&lt;curses.h&gt;</STRONG>
  53. <STRONG>#include</STRONG> <STRONG>&lt;term.h&gt;</STRONG>
  54. <STRONG>int</STRONG> <STRONG>setupterm(char</STRONG> <STRONG>*</STRONG><EM>term</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <EM>fildes</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <STRONG>*</STRONG><EM>errret</EM><STRONG>);</STRONG>
  55. <STRONG>int</STRONG> <STRONG>setterm(char</STRONG> <STRONG>*</STRONG><EM>term</EM><STRONG>);</STRONG>
  56. <STRONG>TERMINAL</STRONG> <STRONG>*set_curterm(TERMINAL</STRONG> <STRONG>*</STRONG><EM>nterm</EM><STRONG>);</STRONG>
  57. <STRONG>int</STRONG> <STRONG>del_curterm(TERMINAL</STRONG> <STRONG>*</STRONG><EM>oterm</EM><STRONG>);</STRONG>
  58. <STRONG>int</STRONG> <STRONG>restartterm(char</STRONG> <STRONG>*</STRONG><EM>term</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <EM>fildes</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <STRONG>*</STRONG><EM>errret</EM><STRONG>);</STRONG>
  59. <STRONG>char</STRONG> <STRONG>*tparm(char</STRONG> <STRONG>*</STRONG><EM>str</EM><STRONG>,</STRONG> <STRONG>...);</STRONG>
  60. <STRONG>int</STRONG> <STRONG>tputs(const</STRONG> <STRONG>char</STRONG> <STRONG>*</STRONG><EM>str</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <EM>affcnt</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <STRONG>(*</STRONG><EM>putc</EM><STRONG>)(int));</STRONG>
  61. <STRONG>int</STRONG> <STRONG>putp(const</STRONG> <STRONG>char</STRONG> <STRONG>*</STRONG><EM>str</EM><STRONG>);</STRONG>
  62. <STRONG>int</STRONG> <STRONG>vidputs(chtype</STRONG> <EM>attrs</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <STRONG>(*</STRONG><EM>putc</EM><STRONG>)(int));</STRONG>
  63. <STRONG>int</STRONG> <STRONG>vidattr(chtype</STRONG> <EM>attrs</EM><STRONG>);</STRONG>
  64. <STRONG>int</STRONG> <STRONG>vid_puts(attr_t</STRONG> <EM>attrs</EM><STRONG>,</STRONG> <STRONG>short</STRONG> <EM>pair</EM><STRONG>,</STRONG> <STRONG>void</STRONG> <STRONG>*</STRONG><EM>opts</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <STRONG>(*</STRONG><EM>putc</EM><STRONG>)(char));</STRONG>
  65. <STRONG>int</STRONG> <STRONG>vid_attr(attr_t</STRONG> <EM>attrs</EM><STRONG>,</STRONG> <STRONG>short</STRONG> <EM>pair</EM><STRONG>,</STRONG> <STRONG>void</STRONG> <STRONG>*</STRONG><EM>opts</EM><STRONG>);</STRONG>
  66. <STRONG>int</STRONG> <STRONG>mvcur(int</STRONG> <EM>oldrow</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <EM>oldcol</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <EM>newrow</EM>, int <EM>newcol</EM><STRONG>);</STRONG>
  67. <STRONG>int</STRONG> <STRONG>tigetflag(char</STRONG> <STRONG>*</STRONG><EM>capname</EM><STRONG>);</STRONG>
  68. <STRONG>int</STRONG> <STRONG>tigetnum(char</STRONG> <STRONG>*</STRONG><EM>capname</EM><STRONG>);</STRONG>
  69. <STRONG>char</STRONG> <STRONG>*tigetstr(char</STRONG> <STRONG>*</STRONG><EM>capname</EM><STRONG>);</STRONG>
  70. </PRE>
  71. <H2>DESCRIPTION</H2><PRE>
  72. These low-level routines must be called by programs that
  73. have to deal directly with the <STRONG>terminfo</STRONG> database to handle
  74. certain terminal capabilities, such as programming func-
  75. tion keys. For all other functionality, <STRONG>curses</STRONG> routines
  76. are more suitable and their use is recommended.
  77. Initially, <STRONG>setupterm</STRONG> should be called. Note that <STRONG>se-</STRONG>
  78. <STRONG>tupterm</STRONG> is automatically called by <STRONG>initscr</STRONG> and <STRONG>newterm</STRONG>.
  79. This defines the set of terminal-dependent variables
  80. [listed in <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>]. The <STRONG>terminfo</STRONG> variables <STRONG>lines</STRONG> and
  81. <STRONG>columns</STRONG> are initialized by <STRONG>setupterm</STRONG> as follows:
  82. If <STRONG>use_env(FALSE)</STRONG> has been called, values for <STRONG>lines</STRONG>
  83. and <STRONG>columns</STRONG> specified in <STRONG>terminfo</STRONG> are used.
  84. Otherwise, if the environment variables <STRONG>LINES</STRONG> and
  85. <STRONG>COLUMNS</STRONG> exist, their values are used. If these en-
  86. vironment variables do not exist and the program is
  87. running in a window, the current window size is
  88. used. Otherwise, if the environment variables do
  89. not exist, the values for <STRONG>lines</STRONG> and <STRONG>columns</STRONG> speci-
  90. fied in the <STRONG>terminfo</STRONG> database are used.
  91. The header files <STRONG>curses.h</STRONG> and <STRONG>term.h</STRONG> should be included
  92. (in this order) to get the definitions for these strings,
  93. numbers, and flags. Parameterized strings should be
  94. passed through <STRONG>tparm</STRONG> to instantiate them. All <STRONG>terminfo</STRONG>
  95. strings [including the output of <STRONG>tparm</STRONG>] should be printed
  96. with <STRONG>tputs</STRONG> or <STRONG>putp</STRONG>. Call the <STRONG>reset_shell_mode</STRONG> to restore
  97. the tty modes before exiting [see <STRONG><A HREF="curs_kernel.3x.html">curs_kernel(3x)</A></STRONG>]. Pro-
  98. grams which use cursor addressing should output <STRONG>en-</STRONG>
  99. <STRONG>ter_ca_mode</STRONG> upon startup and should output <STRONG>exit_ca_mode</STRONG>
  100. before exiting. Programs desiring shell escapes should
  101. call
  102. <STRONG>reset_shell_mode</STRONG> and output <STRONG>exit_ca_mode</STRONG> before the shell
  103. is called and should output <STRONG>enter_ca_mode</STRONG> and call <STRONG>re-</STRONG>
  104. <STRONG>set_prog_mode</STRONG> after returning from the shell.
  105. The <STRONG>setupterm</STRONG> routine reads in the <STRONG>terminfo</STRONG> database, ini-
  106. tializing the <STRONG>terminfo</STRONG> structures, but does not set up the
  107. output virtualization structures used by <STRONG>curses</STRONG>. The ter-
  108. minal type is the character string <EM>term</EM>; if <EM>term</EM> is null,
  109. the environment variable <STRONG>TERM</STRONG> is used. All output is to
  110. file descriptor <STRONG>fildes</STRONG> which is initialized for output.
  111. If <EM>errret</EM> is not null, then <STRONG>setupterm</STRONG> returns <STRONG>OK</STRONG> or <STRONG>ERR</STRONG>
  112. and stores a status value in the integer pointed to by <EM>er-</EM>
  113. <EM>rret</EM>. A return value of <STRONG>OK</STRONG> combined with status of <STRONG>1</STRONG> in
  114. <EM>errret</EM> is normal. If <STRONG>ERR</STRONG> is returned, examine <EM>errret</EM>:
  115. <STRONG>1</STRONG> means that the terminal is hardcopy, cannot be
  116. used for curses applications.
  117. <STRONG>0</STRONG> means that the terminal could not be found, or
  118. that it is a generic type, having too little
  119. information for curses applications to run.
  120. <STRONG>-1</STRONG> means that the <STRONG>terminfo</STRONG> database could not be
  121. found.
  122. If <EM>errret</EM> is null, <STRONG>setupterm</STRONG> prints an error message upon
  123. finding an error and exits. Thus, the simplest call is:
  124. <STRONG>setupterm((char</STRONG> <STRONG>*)0,</STRONG> <STRONG>1,</STRONG> <STRONG>(int</STRONG> <STRONG>*)0);</STRONG>,
  125. which uses all the defaults and sends the output to <STRONG>std-</STRONG>
  126. <STRONG>out</STRONG>.
  127. The <STRONG>setterm</STRONG> routine is being replaced by <STRONG>setupterm</STRONG>. The
  128. call:
  129. <STRONG>setupterm(</STRONG><EM>term</EM><STRONG>,</STRONG> <STRONG>1,</STRONG> <STRONG>(int</STRONG> <STRONG>*)0)</STRONG>
  130. provides the same functionality as <STRONG>setterm(</STRONG><EM>term</EM><STRONG>)</STRONG>. The
  131. <STRONG>setterm</STRONG> routine is included here for BSD compatibility,
  132. and is not recommended for new programs.
  133. The <STRONG>set_curterm</STRONG> routine sets the variable <STRONG>cur_term</STRONG> to
  134. <EM>nterm</EM>, and makes all of the <STRONG>terminfo</STRONG> boolean, numeric, and
  135. string variables use the values from <EM>nterm</EM>. It returns
  136. the old value of <STRONG>cur_term</STRONG>.
  137. The <STRONG>del_curterm</STRONG> routine frees the space pointed to by
  138. <EM>oterm</EM> and makes it available for further use. If <EM>oterm</EM> is
  139. the same as <STRONG>cur_term</STRONG>, references to any of the <STRONG>terminfo</STRONG>
  140. boolean, numeric, and string variables thereafter may re-
  141. fer to invalid memory locations until another <STRONG>setupterm</STRONG>
  142. has been called.
  143. The <STRONG>restartterm</STRONG> routine is similar to <STRONG>setupterm</STRONG> and
  144. <STRONG>initscr</STRONG>, except that it is called after restoring memory
  145. to a previous state (for example, when reloading a game
  146. saved as a core image dump). It assumes that the windows
  147. and the input and output options are the same as when mem-
  148. ory was saved, but the terminal type and baud rate may be
  149. different. Accordingly, it saves various tty state bits,
  150. calls <STRONG>setupterm</STRONG>, and then restores the bits.
  151. The <STRONG>tparm</STRONG> routine instantiates the string <EM>str</EM> with parame-
  152. ters <EM>pi</EM>. A pointer is returned to the result of <EM>str</EM> with
  153. the parameters applied.
  154. The <STRONG>tputs</STRONG> routine applies padding information to the
  155. string <EM>str</EM> and outputs it. The <EM>str</EM> must be a terminfo
  156. string variable or the return value from <STRONG>tparm</STRONG>, <STRONG>tgetstr</STRONG>,
  157. or <STRONG>tgoto</STRONG>. <EM>affcnt</EM> is the number of lines affected, or 1 if
  158. not applicable. <EM>putc</EM> is a <STRONG>putchar</STRONG>-like routine to which
  159. the characters are passed, one at a time.
  160. The <STRONG>putp</STRONG> routine calls <STRONG>tputs(</STRONG><EM>str</EM><STRONG>,</STRONG> <STRONG>1,</STRONG> <STRONG>putchar)</STRONG>. Note that
  161. the output of <STRONG>putp</STRONG> always goes to <STRONG>stdout</STRONG>, not to the
  162. <EM>fildes</EM> specified in <STRONG>setupterm</STRONG>.
  163. The <STRONG>vidputs</STRONG> routine displays the string on the terminal in
  164. the video attribute mode <EM>attrs</EM>, which is any combination
  165. of the attributes listed in <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>. The characters
  166. are passed to the <STRONG>putchar</STRONG>-like routine <EM>putc</EM>.
  167. The <STRONG>vidattr</STRONG> routine is like the <STRONG>vidputs</STRONG> routine, except
  168. that it outputs through <STRONG>putchar</STRONG>.
  169. The <STRONG>vid_attr</STRONG> and <STRONG>vid_puts</STRONG> routines correspond to vidattr
  170. and vidputs, respectively. They use a set of arguments
  171. for representing the video attributes plus color, i.e.,
  172. one of type attr_t for the attributes and one of short for
  173. the color_pair number. The <STRONG>vid_attr</STRONG> and <STRONG>vid_puts</STRONG> routines
  174. are designed to use the attribute constants with the <EM>WA</EM><STRONG>_</STRONG>
  175. prefix. The opts argument is reserved for future use.
  176. Currently, applications must provide a null pointer for
  177. that argument.
  178. The <STRONG>mvcur</STRONG> routine provides low-level cursor motion. It
  179. takes effect immediately (rather than at the next re-
  180. fresh).
  181. The <STRONG>tigetflag</STRONG>, <STRONG>tigetnum</STRONG> and <STRONG>tigetstr</STRONG> routines return the
  182. value of the capability corresponding to the <STRONG>terminfo</STRONG> <EM>cap-</EM>
  183. <EM>name</EM> passed to them, such as <STRONG>xenl</STRONG>.
  184. The <STRONG>tigetflag</STRONG> routine returns the value <STRONG>-1</STRONG> if <EM>capname</EM> is
  185. not a boolean capability, or <STRONG>0</STRONG> if it is canceled or absent
  186. from the terminal description.
  187. The <STRONG>tigetnum</STRONG> routine returns the value <STRONG>-2</STRONG> if <EM>capname</EM> is
  188. not a numeric capability, or <STRONG>-1</STRONG> if it is canceled or ab-
  189. sent from the terminal description.
  190. The <STRONG>tigetstr</STRONG> routine returns the value <STRONG>(char</STRONG> <STRONG>*)-1</STRONG> if <EM>cap-</EM>
  191. <EM>name</EM> is not a string capability, or <STRONG>0</STRONG> if it is canceled or
  192. absent from the terminal description.
  193. The <EM>capname</EM> for each capability is given in the table col-
  194. umn entitled <EM>capname</EM> code in the capabilities section of
  195. <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>.
  196. <STRONG>char</STRONG> <STRONG>*boolnames[]</STRONG>, <STRONG>*boolcodes[]</STRONG>, <STRONG>*boolfnames[]</STRONG>
  197. <STRONG>char</STRONG> <STRONG>*numnames[]</STRONG>, <STRONG>*numcodes[]</STRONG>, <STRONG>*numfnames[]</STRONG>
  198. <STRONG>char</STRONG> <STRONG>*strnames[]</STRONG>, <STRONG>*strcodes[]</STRONG>, <STRONG>*strfnames[]</STRONG>
  199. These null-terminated arrays contain the <EM>capnames</EM>, the
  200. <STRONG>termcap</STRONG> codes, and the full C names, for each of the <STRONG>ter-</STRONG>
  201. <STRONG>minfo</STRONG> variables.
  202. </PRE>
  203. <H2>RETURN VALUE</H2><PRE>
  204. Routines that return an integer return <STRONG>ERR</STRONG> upon failure
  205. and <STRONG>OK</STRONG> (SVr4 only specifies "an integer value other than
  206. <STRONG>ERR</STRONG>") upon successful completion, unless otherwise noted
  207. in the preceding routine descriptions.
  208. Routines that return pointers always return <STRONG>NULL</STRONG> on error.
  209. X/Open defines no error conditions. In this implementa-
  210. tion
  211. <STRONG>del_curterm</STRONG>
  212. returns an error if its terminal parameter is
  213. null.
  214. <STRONG>putp</STRONG> calls <STRONG>tputs</STRONG>, returning the same error-codes.
  215. <STRONG>restartterm</STRONG>
  216. returns an error if the associated call to <STRONG>se-</STRONG>
  217. <STRONG>tupterm</STRONG> returns an error.
  218. <STRONG>setupterm</STRONG>
  219. returns an error if it cannot allocate enough
  220. memory, or create the initial windows (stdscr,
  221. curscr, newscr). Other error conditions are
  222. documented above.
  223. <STRONG>tputs</STRONG>
  224. returns an error if the string parameter is
  225. null. It does not detect I/O errors: X/Open
  226. states that <STRONG>tputs</STRONG> ignores the return value of
  227. the output function <EM>putc</EM>.
  228. </PRE>
  229. <H2>NOTES</H2><PRE>
  230. The <STRONG>setupterm</STRONG> routine should be used in place of <STRONG>setterm</STRONG>.
  231. It may be useful when you want to test for terminal capa-
  232. bilities without committing to the allocation of storage
  233. involved in <STRONG>initscr</STRONG>.
  234. Note that <STRONG>vidattr</STRONG> and <STRONG>vidputs</STRONG> may be macros.
  235. </PRE>
  236. <H2>PORTABILITY</H2><PRE>
  237. The function <STRONG>setterm</STRONG> is not described by X/Open and must
  238. be considered non-portable. All other functions are as
  239. described by X/Open.
  240. <STRONG>setupterm</STRONG> copies the terminal name to the array <STRONG>ttytype</STRONG>.
  241. This is not part of X/Open Curses, but is assumed by some
  242. applications.
  243. In System V Release 4, <STRONG>set_curterm</STRONG> has an <STRONG>int</STRONG> return type
  244. and returns <STRONG>OK</STRONG> or <STRONG>ERR</STRONG>. We have chosen to implement the
  245. X/Open Curses semantics.
  246. In System V Release 4, the third argument of <STRONG>tputs</STRONG> has the
  247. type <STRONG>int</STRONG> <STRONG>(*putc)(char)</STRONG>.
  248. At least one implementation of X/Open Curses (Solaris) re-
  249. turns a value other than OK/ERR from <STRONG>tputs</STRONG>. That returns
  250. the length of the string, and does no error-checking.
  251. X/Open Curses prototypes <STRONG>tparm</STRONG> with a fixed number of pa-
  252. rameters, rather than a variable argument list. This im-
  253. plementation uses a variable argument list. Portable ap-
  254. plications should provide 9 parameters after the format;
  255. zeroes are fine for this purpose.
  256. X/Open notes that after calling <STRONG>mvcur</STRONG>, the curses state
  257. may not match the actual terminal state, and that an ap-
  258. plication should touch and refresh the window before re-
  259. suming normal curses calls. Both ncurses and System V Re-
  260. lease 4 curses implement <STRONG>mvcur</STRONG> using the SCREEN data allo-
  261. cated in either <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG>. So though it is docu-
  262. mented as a terminfo function, <STRONG>mvcur</STRONG> is really a curses
  263. function which is not well specified.
  264. X/Open states that the old location must be given for
  265. <STRONG>mvcur</STRONG>. This implementation allows the caller to use -1's
  266. for the old ordinates. In that case, the old location is
  267. unknown.
  268. Extended terminal capability names, e.g., as defined by
  269. <STRONG>tic</STRONG> <STRONG>-x</STRONG>, are not stored in the arrays described in this
  270. section.
  271. </PRE>
  272. <H2>SEE ALSO</H2><PRE>
  273. <STRONG><A HREF="ncurses.3x.html">curses(3x)</A></STRONG>, <STRONG><A HREF="curs_initscr.3x.html">curs_initscr(3x)</A></STRONG>, <STRONG><A HREF="curs_kernel.3x.html">curs_kernel(3x)</A></STRONG>, <STRONG>curs_term-</STRONG>
  274. <STRONG><A HREF="curs_termcap.3x.html">cap(3x)</A></STRONG>, <STRONG><A HREF="putc.3.html">putc(3)</A></STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>
  275. <STRONG><A HREF="curs_terminfo.3x.html">curs_terminfo(3x)</A></STRONG>
  276. </PRE>
  277. <HR>
  278. <ADDRESS>
  279. Man(1) output converted with
  280. <a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a>
  281. </ADDRESS>
  282. </BODY>
  283. </HTML>