HP-UX Reference (11i v1 00/12) - 3 Library Functions N-Z (vol 7)

ManualsBrandsHP ManualsSoftwareHP-UX Reference Manuals

241

242

243

244

245

246

247

248

249

250

__________________________________________________________________________________________________________________________________________________________________________________________________

STANDARD Printed by: Nora Chuang [nchuang] STANDARD

/build/1111/BRICK/man3/nan.3m

________________________________________________________________

___ ___

putp(3X) putp(3X)

(ENHANCED CURSES)

NAME

putp, tputs — output commands to the terminal

SYNOPSIS

#include <term.h>

int putp(const char *str);

int tputs(const char *str, int affcnt, int (*putfunc)(int));

DESCRIPTION

These functions output commands contained in the terminfo database to the terminal.

The putp() function is equivalent to tputs(str,1,putchar). The output of putp() always goes to

stdout, not to the ﬁldes speciﬁed in setupterm() .

The tputs() function outputs str to the terminal. The str argument must be a terminfo string variable

or the return value from tgetstr(), tgoto(), tigetstr() or tparm(). The affcnt argument is

the number of lines affected, or 1 if not applicable. If the terminfo database indicates that the terminal in

use requires padding after any command in the generated string,

tputs() inserts pad characters into the

string that is sent to the terminal, at positions indicated by the terminfo database. The

tputs() func-

tion outputs each character of the generated string by calling the user-supplied function putfunc (see

below).

The user-supplied function putfunc (speciﬁed as an argument to

tputs) is either putchar() or some

other function with the same prototype. The

tputs() function ignores the return value of putfunc .

RETURN VALUE

Upon successful completion, these functions return OK. Otherwise, they return ERR.

ERRORS

No errors are deﬁned.

APPLICATION USAGE

After use of any of these functions, the model Curses maintains of the state of the terminal might not

match the actual state of the terminal. The application should touch and refresh the window before resum-

ing conventional use of Curses.

Use of these functions requires that the application contain so much information about a particular class of

terminal that it defeats the purpose of using Curses.

On some terminals, a command to change rendition conceptually occupies space in the screen buffer (with

or without width). Thus, a command to set the terminal to a new rendition would change the rendition of

some characters already displayed.