| curs_initscr(3X) | Library calls | curs_initscr(3X) |
initscr, newterm, endwin, isendwin, set_term, delscreen - initialize, manipulate, or tear down curses terminal interface
#include <ncurses/curses.h>
WINDOW * initscr(void); int endwin(void);
bool isendwin(void);
SCREEN * newterm(const char * type, FILE * outf, FILE * inf); SCREEN * set_term(SCREEN * new); void delscreen(SCREEN * sp);
initscr determines the terminal type and initializes the library's SCREEN, WINDOW, and other data structures. It is normally the first curses function call a program performs. However, an application with unusual needs might employ a few other curses functions beforehand:
Further, a curses program might call newterm prior to or instead of initscr in two specialized cases described in its subsection below.
initscr causes the first refresh(3X) call to clear the screen. If errors occur, initscr writes an appropriate diagnostic message to the standard error stream and exits; otherwise, it returns a pointer to stdscr.
An application that manages multiple terminals should call newterm once for each such device instead of initscr. newterm's arguments are
newterm returns a variable of pointer-to-SCREEN type, which should be saved for later use with set_term and delscreen.
newterm passes the file descriptor of the output stream to the terminfo function setupterm(3X), which returns a pointer to a TERMINAL structure that newterm stores in the SCREEN it returns to the application.
An application that needs to inspect a terminal type's capabilities, so that it can continue to run in a line-oriented mode if the terminal type does not support capabilities the application demands, would also use newterm. If at most one terminal connection is needed, the programmer could perform such a capability test, decide the mode in which to operate, then call delscreen on the pointer returned by newterm, and proceed with either initscr or a non-curses interface.
The program must also call endwin for each terminal being used before exiting from curses. If newterm is called more than once for the same terminal, the first terminal referred to must be the last one for which endwin is called.
A program should always call endwin before exiting the application or temporarily suspending curses's management of the terminal. endwin:
Calling refresh(3X) or doupdate(3X) after a temporary suspension causes curses to resume managing the terminal.
isendwin returns TRUE if wrefresh(3X) has not been called since the most recent endwin call, and FALSE otherwise.
set_term re-orients the curses library's operations to another terminal when the application has arranged to manage more than one with newterm. set_term expects a SCREEN pointer previously returned by newterm as an argument, and returns the previous one. set_term is the only standard curses API function that manipulates SCREEN pointers; all others affect only the current terminal (but see curs_sp_funcs(3X)).
delscreen frees the storage backing the supplied SCREEN pointer argument. endwin does not, so that an application can resume managing a terminal with curses after a (possibly conditional or temporary) suspension; see curs_kernel(3X). Use delscreen after endwin when the application has no more need of a terminal device but will not soon exit.
delscreen returns no value. endwin returns OK on success and ERR on failure. isendwin returns TRUE or FALSE as described above.
In ncurses,
Functions that return pointers return null pointers on error. In ncurses, set_term does not fail, and initscr exits the application if it does not operate successfully.
ncurses establishes signal handlers when a function that initializes a SCREEN, either initscr or newterm, is first called. Applications that wish to handle the following signals themselves should set up their corresponding handlers after initializing the screen.
X/Open Curses Issue 4 describes these functions. It specifies no error conditions for them.
X/Open Curses specifies that portable applications must not call initscr more than once.
initscr in BSD, from its inception (1980) through the Net/2 release (1991) returned ERR cast to a WINDOW pointer when detecting an error. 4.4BSD (1995) instead returned a null pointer. Neither exited the application. It is safe but redundant to check the return value of initscr in X/Open Curses.
Calling endwin does not dispose of the memory allocated by initscr or newterm. Deleting a SCREEN provides a way to do this.
Implementations disagree regarding the level of abstraction applicable to a function or property. For example, SCREEN (returned by newterm) and TERMINAL (returned by setupterm(3X)) hold file descriptors for the output stream. If an application switches screens using set_term, or switches terminals using set_curterm(3X), applications using the output file descriptor can behave differently depending on the structure holding the corresponding descriptor.
If the TERM variable is not set in the environment or has an empty value, initscr uses the value “unknown”, which normally corresponds to a terminal entry with the generic (gn) capability. Generic entries are detected by setupterm(3X) and cannot be used for full-screen operation. Other implementations may handle a missing or empty TERM variable differently.
Quoting X/Open Curses Issue 7, section 3.1.1:
Curses implementations may provide for special handling of the SIGINT, SIGQUIT, and SIGTSTP signals if their disposition is SIG_DFL at the time initscr() is called...
Any special handling for these signals may remain in effect for the life of the process or until the process changes the disposition of the signal.
None of the Curses functions are required to be safe with respect to signals...
Section “NOTES” above discusses ncurses's signal handlers.
4BSD (1980) introduced initscr and endwin.
SVr2 (1984) added newterm and set_term.
SVr3.1 (1987) supplied delscreen and isendwin.
curses(3X), curs_kernel(3X), curs_refresh(3X), curs_slk(3X), curs_terminfo(3X), curs_util(3X), curs_variables(3X)
| 2025-08-23 | ncurses 6.6 |