1 .\"***************************************************************************
2 .\" Copyright (c) 1998-2007,2010 Free Software Foundation, Inc. *
4 .\" Permission is hereby granted, free of charge, to any person obtaining a *
5 .\" copy of this software and associated documentation files (the *
6 .\" "Software"), to deal in the Software without restriction, including *
7 .\" without limitation the rights to use, copy, modify, merge, publish, *
8 .\" distribute, distribute with modifications, sublicense, and/or sell *
9 .\" copies of the Software, and to permit persons to whom the Software is *
10 .\" furnished to do so, subject to the following conditions: *
12 .\" The above copyright notice and this permission notice shall be included *
13 .\" in all copies or substantial portions of the Software. *
15 .\" THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS *
16 .\" OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF *
17 .\" MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. *
18 .\" IN NO EVENT SHALL THE ABOVE COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, *
19 .\" DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR *
20 .\" OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR *
21 .\" THE USE OR OTHER DEALINGS IN THE SOFTWARE. *
23 .\" Except as contained in this notice, the name(s) of the above copyright *
24 .\" holders shall not be used in advertising or otherwise to promote the *
25 .\" sale, use or other dealings in this Software without prior written *
27 .\"***************************************************************************
29 .\" $Id: curs_termcap.3x,v 1.26 2010/12/04 18:38:55 tom Exp $
30 .TH curs_termcap 3X ""
44 \fBtputs\fR \- direct \fBcurses\fR interface to the terminfo capability database
48 \fB#include <curses.h>\fR
50 \fB#include <term.h>\fR
54 \fBextern char * UP;\fR
56 \fBextern char * BC;\fR
58 \fBextern @NCURSES_OSPEED@ ospeed;\fR
60 \fBint tgetent(char *bp, const char *name);\fR
62 \fBint tgetflag(char *id);\fR
64 \fBint tgetnum(char *id);\fR
66 \fBchar *tgetstr(char *id, char **area);\fR
68 \fBchar *tgoto(const char *cap, int col, int row);\fR
70 \fBint tputs(const char *str, int affcnt, int (*putc)(int));\fR
73 These routines are included as a conversion aid for programs that use
74 the \fItermcap\fR library. Their parameters are the same and the
75 routines are emulated using the \fIterminfo\fR database. Thus, they
76 can only be used to query the capabilities of entries for which a
77 terminfo entry has been compiled.
79 The \fBtgetent\fR routine loads the entry for \fIname\fR.
80 It returns 1 on success, 0 if there is no such entry, and \-1 if the
81 terminfo database could not be found.
82 The emulation ignores the buffer pointer \fIbp\fR.
84 The \fBtgetflag\fR routine gets the boolean entry for \fIid\fR,
85 or zero if it is not available.
87 The \fBtgetnum\fR routine gets the numeric entry for \fIid\fR,
88 or \-1 if it is not available.
90 The \fBtgetstr\fR routine returns the string entry for \fIid\fR,
91 or zero if it is not available.
92 Use \fBtputs\fR to output the returned string.
93 The return value will also be copied to the buffer pointed to by \fIarea\fR,
94 and the \fIarea\fR value will be updated to point past the null ending
97 Only the first two characters of the \fBid\fR parameter of
100 \fBtgetstr\fR are compared in lookups.
102 The \fBtgoto\fR routine instantiates the parameters into the given capability.
103 The output from this routine is to be passed to \fBtputs\fR.
105 The \fBtputs\fR routine is described on the \fBcurs_terminfo\fR(3X) manual
106 page. It can retrieve capabilities by either termcap or terminfo name.
112 are set by \fBtgetent\fR to the terminfo entry's data for
115 \fBbackspace_if_not_bs\fR,
117 \fBUP\fR is not used by ncurses.
118 \fBPC\fR is used in the \fBtdelay_output\fR function.
119 \fBBC\fR is used in the \fBtgoto\fR emulation.
120 The variable \fBospeed\fR is set by ncurses in a system-specific coding
121 to reflect the terminal speed.
124 Except where explicitly noted,
125 routines that return an integer return \fBERR\fR upon failure and \fBOK\fR
126 (SVr4 only specifies "an integer value other than \fBERR\fR") upon successful
129 Routines that return pointers return \fBNULL\fR on error.
131 If you call \fBtgetstr\fR to fetch \fBca\fR or any other parameterized string,
132 be aware that it will be returned in terminfo notation, not the older and
133 not-quite-compatible termcap notation. This will not cause problems if all
134 you do with it is call \fBtgoto\fR or \fBtparm\fR, which both expand
135 terminfo-style strings as terminfo.
136 (The \fBtgoto\fR function, if configured to support termcap, will check
137 if the string is indeed terminfo-style by looking for "%p" parameters or
138 "$<..>" delays, and invoke a termcap-style parser if the string does not
139 appear to be terminfo).
141 Because terminfo conventions for representing padding in string capabilities
142 differ from termcap's, \fBtputs("50");\fR will put out a literal "50" rather
143 than busy-waiting for 50 milliseconds. Cope with it.
145 Note that termcap has nothing analogous to terminfo's \fBsgr\fR string.
146 One consequence of this is that termcap applications assume \fRme\fR
147 (terminfo \fBsgr0\fR) does not reset the alternate character set.
148 This implementation checks for, and modifies the data shown to the
149 termcap interface to accommodate termcap's limitation in this respect.
151 The XSI Curses standard, Issue 4 describes these functions. However, they
152 are marked TO BE WITHDRAWN and may be removed in future versions.
154 Neither the XSI Curses standard nor the SVr4 man pages documented the return
155 values of \fBtgetent\fR correctly, though all three were in fact returned ever
157 In particular, an omission in the XSI Curses documentation has been
158 misinterpreted to mean that \fBtgetent\fR returns \fBOK\fR or \fBERR\fR.
159 Because the purpose of these functions is to provide compatibility with
160 the \fItermcap\fR library, that is a defect in XCurses, Issue 4, Version 2
161 rather than in ncurses.
163 External variables are provided for support of certain termcap applications.
164 However, termcap applications' use of those variables is poorly documented,
165 e.g., not distinguishing between input and output.
166 In particular, some applications are reported to declare and/or
171 \fBterm_variables\fR(3X),