scr_dump(), scr_restore(), scr_init(), scr_set() - read or write a curses screen from or to a file
#include <curses.h>
int scr_dump(const char *filename);
int scr_restore(const char *filename);
int scr_init(const char *filename);
int scr_set(const char *filename);
The scr_dump(3) routine dumps the current contents of the virtual screen to the file filename.
The scr_restore(3) routine sets the virtual screen to the contents of filename, which must have been written using scr_dump(3). The next call to doupdate(3) restores the screen to the way it looked in the dump file.
The scr_init(3) routine reads in the contents of filename and uses them to initialize the curses data structures about what the terminal currently has on its screen. If the data is determined to be valid, curses bases its next update of the screen on this information rather than clearing the screen and starting from scratch. scr_init(3) is used after initscr(3) or a system(3) call to share the screen with another process which has done a scr_dump(3) after its endwin(3) call. The data is declared invalid if the terminfo capabilities rmcup and nrrmc exist; also if the terminal has been written to since the preceding scr_dump(3) call.
The scr_set(3) routine is a combination of scr_restore(3) and scr_init(3). It tells the program that the information in filenameis what is currently on the screen, and also what the program wants on the screen. This can be thought of as a screen inheritance function.
To read (write) a window from (to) a file, use the getwin(3) and putwin(3) routines (see the curs_util(3) reference page).
All routines return the integer ERR upon failure and OK upon success.
Scr_init(3), scr_set(3), and scr_restore(3) may be macros.
The XSI Curses standard, Issue 4, describes these functions (adding the const qualifiers).
The SVr4 docs merely say under scr_init(3) that the dump data is also considered invalid "if the time-stamp of the tty is old" but don't define "old".
curses(3)
curs_initscr(3)
curs_refresh(3)
curs_util(3)
system(3)