.\"***************************************************************************.\" Copyright (c) 1998-2002,2003 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            *.\" "Software"), to deal in the Software without restriction, including      *.\" without limitation the rights to use, copy, modify, merge, publish,      *.\" distribute, distribute with modifications, sublicense, and/or sell       *.\" copies of the Software, and to permit persons to whom the Software is    *.\" furnished to do so, subject to the following conditions:                 *.\"                                                                          *.\" The above copyright notice and this permission notice shall be included  *.\" in all copies or substantial portions of the Software.                   *.\"                                                                          *.\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS  *.\" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF               *.\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.   *.\" IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,   *.\" DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR    *.\" OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR    *.\" THE USE OR OTHER DEALINGS IN THE SOFTWARE.                               *.\"                                                                          *.\" Except as contained in this notice, the name(s) of the above copyright   *.\" holders shall not be used in advertising or otherwise to promote the     *.\" sale, use or other dealings in this Software without prior written       *.\" authorization.                                                           *.\"***************************************************************************.\".\" $Id: curs_termcap.3x,v 1.18 2003/02/08 22:25:47 tom Exp $.TH curs_termcap 3X "".ds n 5.SH NAME\fBtgetent\fR,\fBtgetflag\fR,\fBtgetnum\fR,\fBtgetstr\fR,\fBtgoto\fR,\fBtputs\fR - direct \fBcurses\fR interface to the terminfo capability database.SH SYNOPSIS\fB#include <curses.h>\fR.br\fB#include <term.h>\fR.br\fBextern char PC;\fR\fBextern char * UP;\fR\fBextern char * BC;\fR\fBextern @NCURSES_OSPEED@ ospeed;\fR.br\fBint tgetent(char *bp, const char *name);\fR.br\fBint tgetflag(char *id);\fR.br\fBint tgetnum(char *id);\fR.br\fBchar *tgetstr(char *id, char **area);\fR.br\fBchar *tgoto(const char *cap, int col, int row);\fR.br\fBint tputs(const char *str, int affcnt, int (*putc)(int));\fR.br.SH DESCRIPTIONThese routines are included as a conversion aid for programs that usethe \fItermcap\fR library.  Their parameters are the same and theroutines are emulated using the \fIterminfo\fR database.  Thus, theycan only be used to query the capabilities of entries for which aterminfo entry has been compiled.The \fBtgetent\fR routine loads the entry for \fIname\fR.It returns 1 on success, 0 if there is no such entry, and -1 if theterminfo database could not be found.The emulation ignores the buffer pointer \fIbp\fR.The \fBtgetflag\fR routine gets the boolean entry for \fIid\fR,or zero if it is not available.The \fBtgetnum\fR routine gets the numeric entry for \fIid\fR,or -1 if it is not available.The \fBtgetstr\fR routine returns the string entry for \fIid\fR,or zero if it is not available.Use \fBtputs\fR to output the returned string.The return value will also be copied to the buffer pointed to by \fIarea\fR,and the \fIarea\fR value will be updated to point past the null endingthis value.Only the first two characters of the \fBid\fR parameter of\fBtgetflag\fR,\fBtgetnum\fR and\fBtgetstr\fR are compared in lookups.The \fBtgoto\fR routine instantiates the parameters into the given capability.The output from this routine is to be passed to \fBtputs\fR.The \fBtputs\fR routine is described on the \fBcurs_terminfo\fR(3X) manualpage.  It can retrieve capabilities by either termcap or terminfo name.The variables\fBPC\fR,\fBUP\fR and\fBBC\fRare set by \fBtgetent\fR to the terminfo entry's data for\fBpad_char\fR,\fBcursor_up\fR and\fBbackspace_if_not_bs\fR,respectively.\fBUP\fR is not used by ncurses.\fBPC\fR is used in the \fBtdelay_output\fR function.\fBBC\fR is used in the \fBtgoto\fR emulation.The variable \fBospeed\fR is set by ncurses in a system-specific codingto reflect the terminal speed..SH RETURN VALUEExcept where explicitly noted,routines that return an integer return \fBERR\fR upon failure and \fBOK\fR(SVr4 only specifies "an integer value other than \fBERR\fR") upon successfulcompletion.Routines that return pointers return \fBNULL\fR on error..SH BUGSIf you call \fBtgetstr\fR to fetch \fBca\fR or any other parameterized string,be aware that it will be returned in terminfo notation, not the older andnot-quite-compatible termcap notation.  This won't cause problems if allyou do with it is call \fBtgoto\fR or \fBtparm\fR, which both expandterminfo-style strings as terminfo.(The \fBtgoto\fR function, if configured to support termcap, will checkif the string is indeed terminfo-style by looking for "%p" parameters or"$<..>" delays, and invoke a termcap-style parser if the string does notappear to be terminfo).Because terminfo conventions for representing padding in string capabilitiesdiffer from termcap's, \fBtputs("50");\fR will put out a literal "50" ratherthan busy-waiting for 50 milliseconds.  Cope with it.Note that termcap has nothing analogous to terminfo's \fBsgr\fR string.One consequence of this is that termcap applications assume \fRme\fR(terminfo \fBsgr0\fR) does not reset the alternate character set.This implementation checks for, and modifies the data shown to thetermcap interface to accommodate termcap's limitation in this respect..SH PORTABILITYThe XSI Curses standard, Issue 4 describes these functions.  However, theyare marked TO BE WITHDRAWN and may be removed in future versions.Neither the XSI Curses standard nor the SVr4 man pages documented the returnvalues of \fBtgetent\fR correctly, though all three were in fact returned eversince SVr1.In particular, an omission in the XSI Curses documentation has beenmisinterpreted to mean that \fBtgetent\fR returns \fBOK\fR or \fBERR\fR.Because the purpose of these functions is to provide compatibility withthe \fItermcap\fR library, that is a defect in XCurses, Issue 4, Version 2rather than in ncurses.External variables are provided for support of certain termcap applications.However, termcap applications' use of those variables is poorly documented,e.g., not distinguishing between input and output.In particular, some applications are reported to declare and/ormodify \fBospeed\fR..SH SEE ALSO\fBcurses\fR(3X), \fBterminfo\fR(\*n), \fBputc\fR(3S)..\"#.\"# The following sets edit modes for GNU EMACS.\"# Local Variables:.\"# mode:nroff.\"# fill-column:79.\"# End: