X-Git-Url: https://ncurses.scripts.mit.edu/?p=ncurses.git;a=blobdiff_plain;f=doc%2Fhtml%2Fman%2Fcurs_termcap.3x.html;h=f62fc0ca997feb1b010cd70ce4b7388651de4b2c;hp=f510812b7f29a254c4434e85a61ec7ccdc45178b;hb=f86cbeb5f9bd96ab041d34039c35749a14965039;hpb=46722468f47c2b77b3987729b4bcf2321cccfd01
diff --git a/doc/html/man/curs_termcap.3x.html b/doc/html/man/curs_termcap.3x.html
index f510812b..f62fc0ca 100644
--- a/doc/html/man/curs_termcap.3x.html
+++ b/doc/html/man/curs_termcap.3x.html
@@ -1,7 +1,7 @@
@@ -40,19 +40,28 @@
+curs_termcap(3x) curs_termcap(3x)
+
+
+
NAME
- tgetent, tgetflag, tgetnum, tgetstr, tgoto, tputs - direct
- curses interface to the terminfo capability database
+ PC, UP, BC, ospeed, tgetent, tgetflag, tgetnum, tgetstr,
+ tgoto, tputs - direct curses interface to the terminfo
+ capability database
SYNOPSIS
#include <curses.h>
#include <term.h>
- extern char PC; extern char * UP; extern char * BC; extern
- short ospeed;
+
+ extern char PC;
+ extern char * UP;
+ extern char * BC;
+ extern short ospeed;
+
int tgetent(char *bp, const char *name);
int tgetflag(char *id);
int tgetnum(char *id);
@@ -72,18 +81,18 @@
The tgetent routine loads the entry for name. It returns
1 on success, 0 if there is no such entry, and -1 if the
- terminfo database could not be found. The emulation
- ignores the buffer pointer bp.
+ terminfo database could not be found. The emulation ig-
+ nores the buffer pointer bp.
- The tgetflag routine gets the boolean entry for id, or
- zero if it is not available.
+ The tgetflag routine gets the boolean entry for id, or ze-
+ ro if it is not available.
The tgetnum routine gets the numeric entry for id, or -1
if it is not available.
The tgetstr routine returns the string entry for id, or
- zero if it is not available. Use tputs to output the
- returned string. The return value will also be copied to
+ zero if it is not available. Use tputs to output the re-
+ turned string. The return value will also be copied to
the buffer pointed to by area, and the area value will be
updated to point past the null ending this value.
@@ -107,13 +116,12 @@
minal speed.
-
RETURN VALUE
- Except where explicitly noted, routines that return an
- integer return ERR upon failure and OK (SVr4 only speci-
- fies "an integer value other than ERR") upon successful
- completion.
+ Except where explicitly noted, routines that return an in-
+ teger return ERR upon failure and OK (SVr4 only specifies
+ "an integer value other than ERR") upon successful comple-
+ tion.
Routines that return pointers return NULL on error.
@@ -121,47 +129,58 @@
BUGS
If you call tgetstr to fetch ca or any other parameterized
- string, be aware that it will be returned in terminfo
- notation, not the older and not-quite-compatible termcap
- notation. This won't cause problems if all you do with it
- is call tgoto or tparm, which both expand terminfo-style
- strings as terminfo. (The tgoto function, if configured
- to support termcap, will check if the string is indeed
- terminfo-style by looking for "%p" parameters or "$<..>"
- delays, and invoke a termcap-style parser if the string
- does not appear to be terminfo).
+ string, be aware that it will be returned in terminfo no-
+ tation, not the older and not-quite-compatible termcap no-
+ tation. This will not cause problems if all you do with
+ it is call tgoto or tparm, which both expand terminfo-
+ style strings as terminfo. (The tgoto function, if con-
+ figured to support termcap, will check if the string is
+ indeed terminfo-style by looking for "%p" parameters or
+ "$<..>" delays, and invoke a termcap-style parser if the
+ string does not appear to be terminfo).
Because terminfo conventions for representing padding in
string capabilities differ from termcap's, tputs("50");
will put out a literal "50" rather than busy-waiting for
50 milliseconds. Cope with it.
+ Note that termcap has nothing analogous to terminfo's sgr
+ string. One consequence of this is that termcap applica-
+ tions assume me (terminfo sgr0) does not reset the alter-
+ nate character set. This implementation checks for, and
+ modifies the data shown to the termcap interface to accom-
+ modate termcap's limitation in this respect.
+
PORTABILITY
- The XSI Curses standard, Issue 4 describes these func-
- tions. However, they are marked TO BE WITHDRAWN and may
+ The XSI Curses standard, Issue 4 describes these func-
+ tions. However, they are marked TO BE WITHDRAWN and may
be removed in future versions.
- Neither the XSI Curses standard nor the SVr4 man pages
- documented the return values of tgetent correctly, though
- all three were in fact returned ever since SVr1. In par-
- ticular, an omission in the XSI Curses documentation has
- been misinterpreted to mean that tgetent returns OK or
+ Neither the XSI Curses standard nor the SVr4 man pages
+ documented the return values of tgetent correctly, though
+ all three were in fact returned ever since SVr1. In par-
+ ticular, an omission in the XSI Curses documentation has
+ been misinterpreted to mean that tgetent returns OK or
ERR. Because the purpose of these functions is to provide
- compatibility with the termcap library, that is a defect
+ compatibility with the termcap library, that is a defect
in XCurses, Issue 4, Version 2 rather than in ncurses.
- External variables are provided for support of certain
- termcap applications. However, termcap applications' use
+ External variables are provided for support of certain
+ termcap applications. However, termcap applications' use
of those variables is poorly documented, e.g., not distin-
- guishing between input and output. In particular, some
+ guishing between input and output. In particular, some
applications are reported to declare and/or modify ospeed.
SEE ALSO
- curses(3x), terminfo(5), putc(3S).
+ curses(3x), terminfo(5), term_variables(3x), putc(3).
+
+
+
+ curs_termcap(3x)