diff options
Diffstat (limited to 'doc/html/man/curs_terminfo.3x.html')
| -rw-r--r-- | doc/html/man/curs_terminfo.3x.html | 310 |
1 files changed, 188 insertions, 122 deletions
diff --git a/doc/html/man/curs_terminfo.3x.html b/doc/html/man/curs_terminfo.3x.html index 9a640e9..dd85e35 100644 --- a/doc/html/man/curs_terminfo.3x.html +++ b/doc/html/man/curs_terminfo.3x.html @@ -1,7 +1,7 @@ -<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <!-- **************************************************************************** - * Copyright (c) 1999-2008,2010 Free Software Foundation, Inc. * + * Copyright (c) 1999-2011,2013 Free Software Foundation, Inc. * * * * Permission is hereby granted, free of charge, to any person obtaining a * * copy of this software and associated documentation files (the * @@ -27,7 +27,12 @@ * sale, use or other dealings in this Software without prior written * * authorization. * **************************************************************************** - * @Id: curs_terminfo.3x,v 1.35 2010/12/04 18:38:55 tom Exp @ + * @Id: curs_terminfo.3x,v 1.43 2013/07/20 19:29:59 tom Exp @ + * *************************************************************************** + * *************************************************************************** + * *************************************************************************** + * *************************************************************************** + * *************************************************************************** --> <HTML> <HEAD> @@ -68,7 +73,7 @@ <STRONG>int</STRONG> <STRONG>putp(const</STRONG> <STRONG>char</STRONG> <STRONG>*</STRONG><EM>str</EM><STRONG>);</STRONG> <STRONG>int</STRONG> <STRONG>vidputs(chtype</STRONG> <EM>attrs</EM><STRONG>,</STRONG> <STRONG>int</STRONG> <STRONG>(*</STRONG><EM>putc</EM><STRONG>)(int));</STRONG> <STRONG>int</STRONG> <STRONG>vidattr(chtype</STRONG> <EM>attrs</EM><STRONG>);</STRONG> - <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> + <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>)(int));</STRONG> <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> <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> <STRONG>int</STRONG> <STRONG>tigetflag(char</STRONG> <STRONG>*</STRONG><EM>capname</EM><STRONG>);</STRONG> @@ -85,38 +90,51 @@ tion keys. For all other functionality, <STRONG>curses</STRONG> routines are more suitable and their use is recommended. + <STRONG>Initialization</STRONG> Initially, <STRONG>setupterm</STRONG> should be called. Note that <STRONG>se-</STRONG> <STRONG>tupterm</STRONG> is automatically called by <STRONG>initscr</STRONG> and <STRONG>newterm</STRONG>. This defines the set of terminal-dependent variables - [listed in <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>]. The <STRONG>terminfo</STRONG> variables <STRONG>lines</STRONG> and - <STRONG>columns</STRONG> are initialized by <STRONG>setupterm</STRONG> as follows: - - If <STRONG>use_env(FALSE)</STRONG> has been called, values for <STRONG>lines</STRONG> - and <STRONG>columns</STRONG> specified in <STRONG>terminfo</STRONG> are used. - - Otherwise, if the environment variables <STRONG>LINES</STRONG> and - <STRONG>COLUMNS</STRONG> exist, their values are used. If these en- - vironment variables do not exist and the program is - running in a window, the current window size is - used. Otherwise, if the environment variables do - not exist, the values for <STRONG>lines</STRONG> and <STRONG>columns</STRONG> speci- - fied in the <STRONG>terminfo</STRONG> database are used. - - The header files <STRONG>curses.h</STRONG> and <STRONG>term.h</STRONG> should be included - (in this order) to get the definitions for these strings, - numbers, and flags. Parameterized strings should be - passed through <STRONG>tparm</STRONG> to instantiate them. All <STRONG>terminfo</STRONG> - strings [including the output of <STRONG>tparm</STRONG>] should be printed - with <STRONG>tputs</STRONG> or <STRONG>putp</STRONG>. Call the <STRONG>reset_shell_mode</STRONG> to restore - the tty modes before exiting [see <STRONG><A HREF="curs_kernel.3x.html">curs_kernel(3x)</A></STRONG>]. Pro- - grams which use cursor addressing should output <STRONG>en-</STRONG> - <STRONG>ter_ca_mode</STRONG> upon startup and should output <STRONG>exit_ca_mode</STRONG> - before exiting. Programs desiring shell escapes should - call - - <STRONG>reset_shell_mode</STRONG> and output <STRONG>exit_ca_mode</STRONG> before the shell - is called and should output <STRONG>enter_ca_mode</STRONG> and call <STRONG>re-</STRONG> - <STRONG>set_prog_mode</STRONG> after returning from the shell. + [listed in <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>]. + + Each initialization routine provides applications with the + terminal capabilities either directly (via header defini- + tions), or by special functions. The header files <STRONG>curs-</STRONG> + <STRONG>es.h</STRONG> and <STRONG>term.h</STRONG> should be included (in this order) to get + the definitions for these strings, numbers, and flags. + + The <STRONG>terminfo</STRONG> variables <STRONG>lines</STRONG> and <STRONG>columns</STRONG> are initialized + by <STRONG>setupterm</STRONG> as follows: + + <STRONG>o</STRONG> If <STRONG>use_env(FALSE)</STRONG> has been called, values for <STRONG>lines</STRONG> + and <STRONG>columns</STRONG> specified in <STRONG>terminfo</STRONG> are used. + + <STRONG>o</STRONG> Otherwise, if the environment variables <STRONG>LINES</STRONG> and <STRONG>COL-</STRONG> + <STRONG>UMNS</STRONG> exist, their values are used. If these environ- + ment variables do not exist and the program is running + in a window, the current window size is used. Other- + wise, if the environment variables do not exist, the + values for <STRONG>lines</STRONG> and <STRONG>columns</STRONG> specified in the <STRONG>terminfo</STRONG> + database are used. + + Parameterized strings should be passed through <STRONG>tparm</STRONG> to + instantiate them. All <STRONG>terminfo</STRONG> strings [including the + output of <STRONG>tparm</STRONG>] should be printed with <STRONG>tputs</STRONG> or <STRONG>putp</STRONG>. + Call <STRONG>reset_shell_mode</STRONG> to restore the tty modes before ex- + iting [see <STRONG><A HREF="curs_kernel.3x.html">curs_kernel(3x)</A></STRONG>]. + + Programs which use cursor addressing should + + <STRONG>o</STRONG> output <STRONG>enter_ca_mode</STRONG> upon startup and + + <STRONG>o</STRONG> output <STRONG>exit_ca_mode</STRONG> before exiting. + + Programs which execute shell subprocesses should + + <STRONG>o</STRONG> call <STRONG>reset_shell_mode</STRONG> and output <STRONG>exit_ca_mode</STRONG> before + the shell is called and + + <STRONG>o</STRONG> output <STRONG>enter_ca_mode</STRONG> and call <STRONG>reset_prog_mode</STRONG> after + returning from the shell. The <STRONG>setupterm</STRONG> routine reads in the <STRONG>terminfo</STRONG> database, ini- tializing the <STRONG>terminfo</STRONG> structures, but does not set up the @@ -129,54 +147,74 @@ <EM>rret</EM>. A return value of <STRONG>OK</STRONG> combined with status of <STRONG>1</STRONG> in <EM>errret</EM> is normal. If <STRONG>ERR</STRONG> is returned, examine <EM>errret</EM>: - <STRONG>1</STRONG> means that the terminal is hardcopy, cannot be - used for curses applications. + <STRONG>1</STRONG> means that the terminal is hardcopy, cannot be used + for curses applications. + + <STRONG>setupterm</STRONG> determines if the entry is a hardcopy type + by checking the <EM>hc</EM> (<EM>hardcopy</EM>) capability. - <STRONG>0</STRONG> means that the terminal could not be found, or - that it is a generic type, having too little - information for curses applications to run. + <STRONG>0</STRONG> means that the terminal could not be found, or that + it is a generic type, having too little information + for curses applications to run. - <STRONG>-1</STRONG> means that the <STRONG>terminfo</STRONG> database could not be - found. + <STRONG>setupterm</STRONG> determines if the entry is a generic type + by checking the <EM>gn</EM> (<EM>generic</EM>) capability. - If <EM>errret</EM> is null, <STRONG>setupterm</STRONG> prints an error message upon + <STRONG>-1</STRONG> means that the <STRONG>terminfo</STRONG> database could not be found. + + If <EM>errret</EM> is null, <STRONG>setupterm</STRONG> prints an error message upon finding an error and exits. Thus, the simplest call is: <STRONG>setupterm((char</STRONG> <STRONG>*)0,</STRONG> <STRONG>1,</STRONG> <STRONG>(int</STRONG> <STRONG>*)0);</STRONG>, - which uses all the defaults and sends the output to <STRONG>std-</STRONG> + which uses all the defaults and sends the output to <STRONG>std-</STRONG> <STRONG>out</STRONG>. - The <STRONG>setterm</STRONG> routine is being replaced by <STRONG>setupterm</STRONG>. The - call: + The <STRONG>setterm</STRONG> routine was replaced by <STRONG>setupterm</STRONG>. The call: <STRONG>setupterm(</STRONG><EM>term</EM><STRONG>,</STRONG> <STRONG>1,</STRONG> <STRONG>(int</STRONG> <STRONG>*)0)</STRONG> provides the same functionality as <STRONG>setterm(</STRONG><EM>term</EM><STRONG>)</STRONG>. The - <STRONG>setterm</STRONG> routine is included here for BSD compatibility, - and is not recommended for new programs. - - The <STRONG>set_curterm</STRONG> routine sets the variable <STRONG>cur_term</STRONG> to - <EM>nterm</EM>, and makes all of the <STRONG>terminfo</STRONG> boolean, numeric, and - string variables use the values from <EM>nterm</EM>. It returns - the old value of <STRONG>cur_term</STRONG>. - - The <STRONG>del_curterm</STRONG> routine frees the space pointed to by + <STRONG>setterm</STRONG> routine is provided for BSD compatibility, and is + not recommended for new programs. + + <STRONG>The</STRONG> <STRONG>Terminal</STRONG> <STRONG>State</STRONG> + The <STRONG>setupterm</STRONG> routine stores its information about the + terminal in a <STRONG>TERMINAL</STRONG> structure pointed to by the global + variable <STRONG>cur_term</STRONG>. If it detects an error, or decides + that the terminal is unsuitable (hardcopy or generic), it + discards this information, making it not available to ap- + plications. + + If <STRONG>setupterm</STRONG> is called repeatedly for the same terminal + type, it will reuse the information. It maintains only + one copy of a given terminal's capabilities in memory. If + it is called for different terminal types, <STRONG>setupterm</STRONG> allo- + cates new storage for each set of terminal capabilities. + + The <STRONG>set_curterm</STRONG> routine sets <STRONG>cur_term</STRONG> to <EM>nterm</EM>, and makes + all of the <STRONG>terminfo</STRONG> boolean, numeric, and string variables + use the values from <EM>nterm</EM>. It returns the old value of + <STRONG>cur_term</STRONG>. + + The <STRONG>del_curterm</STRONG> routine frees the space pointed to by <EM>oterm</EM> and makes it available for further use. If <EM>oterm</EM> is - the same as <STRONG>cur_term</STRONG>, references to any of the <STRONG>terminfo</STRONG> - boolean, numeric, and string variables thereafter may re- - fer to invalid memory locations until another <STRONG>setupterm</STRONG> + the same as <STRONG>cur_term</STRONG>, references to any of the <STRONG>terminfo</STRONG> + boolean, numeric, and string variables thereafter may re- + fer to invalid memory locations until another <STRONG>setupterm</STRONG> has been called. The <STRONG>restartterm</STRONG> routine is similar to <STRONG>setupterm</STRONG> and - <STRONG>initscr</STRONG>, except that it is called after restoring memory - to a previous state (for example, when reloading a game - saved as a core image dump). It assumes that the windows - and the input and output options are the same as when mem- - ory was saved, but the terminal type and baud rate may be - different. Accordingly, it saves various tty state bits, - calls <STRONG>setupterm</STRONG>, and then restores the bits. - + <STRONG>initscr</STRONG>, except that it is called after restoring memory + to a previous state (for example, when reloading a game + saved as a core image dump). <STRONG>restartterm</STRONG> assumes that the + windows and the input and output options are the same as + when memory was saved, but the terminal type and baud rate + may be different. Accordingly, <STRONG>restartterm</STRONG> saves various + tty state bits, calls <STRONG>setupterm</STRONG>, and then restores the + bits. + + <STRONG>Formatting</STRONG> <STRONG>Output</STRONG> The <STRONG>tparm</STRONG> routine instantiates the string <EM>str</EM> with parame- ters <EM>pi</EM>. A pointer is returned to the result of <EM>str</EM> with the parameters applied. @@ -185,6 +223,7 @@ rather than a fixed-parameter list. Its numeric parame- ters are integers (int) rather than longs. + <STRONG>Output</STRONG> <STRONG>Functions</STRONG> The <STRONG>tputs</STRONG> routine applies padding information to the string <EM>str</EM> and outputs it. The <EM>str</EM> must be a terminfo string variable or the return value from <STRONG>tparm</STRONG>, <STRONG>tgetstr</STRONG>, @@ -218,36 +257,48 @@ takes effect immediately (rather than at the next re- fresh). + <STRONG>Terminal</STRONG> <STRONG>Capability</STRONG> <STRONG>Functions</STRONG> The <STRONG>tigetflag</STRONG>, <STRONG>tigetnum</STRONG> and <STRONG>tigetstr</STRONG> routines return the value of the capability corresponding to the <STRONG>terminfo</STRONG> <EM>cap-</EM> - <EM>name</EM> passed to them, such as <STRONG>xenl</STRONG>. + <EM>name</EM> passed to them, such as <STRONG>xenl</STRONG>. The <EM>capname</EM> for each + capability is given in the table column entitled <EM>capname</EM> + code in the capabilities section of <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>. + + These routines return special values to denote errors. + + The <STRONG>tigetflag</STRONG> routine returns + + <STRONG>-1</STRONG> if <EM>capname</EM> is not a boolean capability, or - The <STRONG>tigetflag</STRONG> routine returns the value <STRONG>-1</STRONG> if <EM>capname</EM> is - not a boolean capability, or <STRONG>0</STRONG> if it is canceled or absent - from the terminal description. + <STRONG>0</STRONG> if it is canceled or absent from the terminal de- + scription. - The <STRONG>tigetnum</STRONG> routine returns the value <STRONG>-2</STRONG> if <EM>capname</EM> is - not a numeric capability, or <STRONG>-1</STRONG> if it is canceled or ab- - sent from the terminal description. + The <STRONG>tigetnum</STRONG> routine returns - The <STRONG>tigetstr</STRONG> routine returns the value <STRONG>(char</STRONG> <STRONG>*)-1</STRONG> if <EM>cap-</EM> - <EM>name</EM> is not a string capability, or <STRONG>0</STRONG> if it is canceled or - absent from the terminal description. + <STRONG>-2</STRONG> if <EM>capname</EM> is not a numeric capability, or - The <EM>capname</EM> for each capability is given in the table col- - umn entitled <EM>capname</EM> code in the capabilities section of - <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG>. + <STRONG>-1</STRONG> if it is canceled or absent from the terminal de- + scription. + The <STRONG>tigetstr</STRONG> routine returns + + <STRONG>(char</STRONG> <STRONG>*)-1</STRONG> + if <EM>capname</EM> is not a string capability, or + + <STRONG>0</STRONG> if it is canceled or absent from the terminal de- + scription. + + <STRONG>Terminal</STRONG> <STRONG>Capability</STRONG> <STRONG>Names</STRONG> + These null-terminated arrays contain the short terminfo + names ("codes"), the <STRONG>termcap</STRONG> names, and the long terminfo + names ("fnames") for each of the predefined <STRONG>terminfo</STRONG> vari- + ables: <STRONG>char</STRONG> <STRONG>*boolnames[]</STRONG>, <STRONG>*boolcodes[]</STRONG>, <STRONG>*boolfnames[]</STRONG> <STRONG>char</STRONG> <STRONG>*numnames[]</STRONG>, <STRONG>*numcodes[]</STRONG>, <STRONG>*numfnames[]</STRONG> <STRONG>char</STRONG> <STRONG>*strnames[]</STRONG>, <STRONG>*strcodes[]</STRONG>, <STRONG>*strfnames[]</STRONG> - These null-terminated arrays contain the <EM>capnames</EM>, the - <STRONG>termcap</STRONG> codes, and the full C names, for each of the <STRONG>ter-</STRONG> - <STRONG>minfo</STRONG> variables. - </PRE> <H2>RETURN VALUE</H2><PRE> @@ -261,49 +312,64 @@ X/Open defines no error conditions. In this implementa- tion - <STRONG>del_curterm</STRONG> - returns an error if its terminal parameter is - null. + <STRONG>del_curterm</STRONG> + returns an error if its terminal parameter is + null. - <STRONG>putp</STRONG> calls <STRONG>tputs</STRONG>, returning the same error-codes. + <STRONG>putp</STRONG> calls <STRONG>tputs</STRONG>, returning the same error-codes. - <STRONG>restartterm</STRONG> - returns an error if the associated call to <STRONG>se-</STRONG> - <STRONG>tupterm</STRONG> returns an error. + <STRONG>restartterm</STRONG> + returns an error if the associated call to <STRONG>se-</STRONG> + <STRONG>tupterm</STRONG> returns an error. - <STRONG>setupterm</STRONG> - returns an error if it cannot allocate enough - memory, or create the initial windows (stdscr, - curscr, newscr). Other error conditions are - documented above. + <STRONG>setupterm</STRONG> + returns an error if it cannot allocate enough + memory, or create the initial windows (stdscr, + curscr, newscr). Other error conditions are + documented above. - <STRONG>tputs</STRONG> - returns an error if the string parameter is - null. It does not detect I/O errors: X/Open - states that <STRONG>tputs</STRONG> ignores the return value of - the output function <EM>putc</EM>. - - -</PRE> -<H2>NOTES</H2><PRE> - The <STRONG>setupterm</STRONG> routine should be used in place of <STRONG>setterm</STRONG>. - It may be useful when you want to test for terminal capa- - bilities without committing to the allocation of storage - involved in <STRONG>initscr</STRONG>. - - Note that <STRONG>vidattr</STRONG> and <STRONG>vidputs</STRONG> may be macros. + <STRONG>tputs</STRONG> + returns an error if the string parameter is + null. It does not detect I/O errors: X/Open + states that <STRONG>tputs</STRONG> ignores the return value of + the output function <EM>putc</EM>. </PRE> <H2>PORTABILITY</H2><PRE> - The function <STRONG>setterm</STRONG> is not described by X/Open and must - be considered non-portable. All other functions are as + X/Open notes that <STRONG>vidattr</STRONG> and <STRONG>vidputs</STRONG> may be macros. + + The function <STRONG>setterm</STRONG> is not described by X/Open and must + be considered non-portable. All other functions are as described by X/Open. - <STRONG>setupterm</STRONG> copies the terminal name to the array <STRONG>ttytype</STRONG>. - This is not part of X/Open Curses, but is assumed by some + <STRONG>setupterm</STRONG> copies the terminal name to the array <STRONG>ttytype</STRONG>. + This is not part of X/Open Curses, but is assumed by some applications. + If configured to use the terminal-driver, e.g., for the + MinGW port, + + <STRONG>o</STRONG> <STRONG>setupterm</STRONG> interprets a missing/empty TERM variable as + the special value "unknown". + + <STRONG>o</STRONG> <STRONG>setupterm</STRONG> allows explicit use of the the windows con- + sole driver by checking if $TERM is set to "#win32con" + or an abbreviation of that string. + + Older versions of <STRONG>ncurses</STRONG> assumed that the file descriptor + passed to <STRONG>setupterm</STRONG> from <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG> uses buffered + I/O, and would write to the corresponding stream. In ad- + dition to the limitation that the terminal was left in + block-buffered mode on exit (like SystemV curses), it was + problematic because <STRONG>ncurses</STRONG> did not allow a reliable way + to cleanup on receiving SIGTSTP. The current version uses + output buffers managed directly by <STRONG>ncurses</STRONG>. Some of the + low-level functions described in this manual page write to + the standard output. They are not signal-safe. The high- + level functions in <STRONG>ncurses</STRONG> use alternate versions of these + functions using the more reliable buffering scheme. + In System V Release 4, <STRONG>set_curterm</STRONG> has an <STRONG>int</STRONG> return type and returns <STRONG>OK</STRONG> or <STRONG>ERR</STRONG>. We have chosen to implement the X/Open Curses semantics. @@ -323,12 +389,12 @@ zeroes are fine for this purpose. In response to comments by Thomas E. Dickey, X/Open Curses - Issue 7 proposed the <STRONG>tiparam</STRONG> function in mid-2009. + Issue 7 proposed the <STRONG>tiparm</STRONG> function in mid-2009. X/Open notes that after calling <STRONG>mvcur</STRONG>, the curses state may not match the actual terminal state, and that an ap- plication should touch and refresh the window before re- - suming normal curses calls. Both ncurses and System V Re- + suming normal curses calls. Both <STRONG>ncurses</STRONG> and System V Re- lease 4 curses implement <STRONG>mvcur</STRONG> using the SCREEN data allo- cated in either <STRONG>initscr</STRONG> or <STRONG>newterm</STRONG>. So though it is docu- mented as a terminfo function, <STRONG>mvcur</STRONG> is really a curses @@ -339,15 +405,18 @@ for the old ordinates. In that case, the old location is unknown. + Other implementions may not declare the capability name + arrays. Some provide them without declaring them. X/Open + does not specify them. + Extended terminal capability names, e.g., as defined by - <STRONG>tic</STRONG> <STRONG>-x</STRONG>, are not stored in the arrays described in this - section. + <STRONG>tic</STRONG> <STRONG>-x</STRONG>, are not stored in the arrays described here. </PRE> <H2>SEE ALSO</H2><PRE> - <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> - <STRONG><A HREF="curs_termcap.3x.html">cap(3x)</A></STRONG>, <STRONG><A HREF="curs_variables.3x.html">curs_variables(3x)</A></STRONG>, <STRONG><A HREF="term_variables.3x.html">term_variables(3x)</A></STRONG>, <STRONG><A HREF="putc.3.html">putc(3)</A></STRONG>, + <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> + <STRONG><A HREF="curs_termcap.3x.html">cap(3x)</A></STRONG>, <STRONG><A HREF="curs_variables.3x.html">curs_variables(3x)</A></STRONG>, <STRONG><A HREF="term_variables.3x.html">term_variables(3x)</A></STRONG>, <STRONG>putc(3)</STRONG>, <STRONG><A HREF="terminfo.5.html">terminfo(5)</A></STRONG> @@ -355,9 +424,6 @@ <STRONG><A HREF="curs_terminfo.3x.html">curs_terminfo(3x)</A></STRONG> </PRE> <HR> -<ADDRESS> -Man(1) output converted with -<a href="http://www.oac.uci.edu/indiv/ehood/man2html.html">man2html</a> -</ADDRESS> +Man(1) output converted with <a href="http://invisible-island.net/scripts/readme.html#others_scripts">man2html</a> </BODY> </HTML> |