- The <B>scr_dump</B> routine dumps the current contents of the <I>virtual</I> <I>screen</I>
- to the file <I>filename</I>.
-
- The <B>scr_restore</B> routine sets the <I>virtual</I> <I>screen</I> to the contents of
- <I>filename</I>, which must have been written using <B>scr_dump</B>. The next call
- to <B>doupdate</B> restores the <I>physical</I> <I>screen</I> to the way it looked in the
- dump file.
-
- The <B>scr_init</B> routine reads in the contents of <I>filename</I> and uses them to
- initialize the <B>curses</B> data structures about what the terminal currently
- has on its screen. If the data is determined to be valid, <B>curses</B> bases
- its next update of the screen on this information rather than clearing
- the screen and starting from scratch. <B>scr_init</B> is used after <B>initscr</B>
- or a <B>system</B> call to share the screen with another process which has
- done a <B>scr_dump</B> after its <B><A HREF="curs_initscr.3X.html">endwin(3X)</A></B> call. The data is declared in-
- valid
-
- <B>o</B> if the terminfo capabilities <B>rmcup</B> and <B>nrrmc</B> exist, also
-
- <B>o</B> if the terminal has been written to since the preceding <B>scr_dump</B>
- call.
-
- The <B>scr_set</B> routine is a combination of <B>scr_restore</B> and <B>scr_init</B>. It
- tells the program that the information in <I>filename</I> is what is currently
+ <EM>curses</EM> provides applications the ability to write the contents of the
+ screen to a file and read them back. To read/write a window (rather
+ than the whole screen) from/to a file, use <STRONG><A HREF="curs_util.3x.html">getwin(3x)</A></STRONG> and <STRONG><A HREF="curs_util.3x.html">putwin(3x)</A></STRONG>,
+ respectively.
+
+
+</PRE><H3><a name="h3-scr_dump">scr_dump</a></H3><PRE>
+ <STRONG>scr_dump</STRONG> writes to <EM>filename</EM> the contents of the virtual screen; see
+ <STRONG><A HREF="curs_variables.3x.html">curscr(3x)</A></STRONG>.
+
+
+</PRE><H3><a name="h3-scr_restore">scr_restore</a></H3><PRE>
+ <STRONG>scr_restore</STRONG> updates the virtual screen to contain the contents of
+ <EM>filename</EM> (if it was validly written with <STRONG>scr_dump</STRONG>). No refresh is
+ performed; after performing any further desired updates, call
+ <STRONG><A HREF="curs_refresh.3x.html">doupdate(3x)</A></STRONG> or similar.
+
+
+</PRE><H3><a name="h3-scr_init">scr_init</a></H3><PRE>
+ <STRONG>scr_init</STRONG> reads <EM>filename</EM>, using it to initialize <EM>curses</EM> data structures
+ describing the state of the terminal screen. If these data are valid,
+ <EM>curses</EM> bases its next update of the screen on this information rather
+ than clearing it and starting from scratch.
+
+ The data fail the validity check
+
+ <STRONG>o</STRONG> if the terminal employs <EM>terminfo</EM> capabilities <STRONG>exit_ca_mode</STRONG> (<STRONG>rmcup</STRONG>)
+ or <STRONG>non_rev_rmcup</STRONG> (<STRONG>nrrmc</STRONG>) are defined, or
+
+ <STRONG>o</STRONG> if <EM>curses</EM> knows that the terminal has been written to since the
+ preceding <STRONG>scr_dump</STRONG> call.
+
+ <STRONG>scr_init</STRONG> could be used after <STRONG><A HREF="curs_initscr.3x.html">initscr(3x)</A></STRONG> or <STRONG>system(3)</STRONG> to share the
+ screen with another process that has done a <STRONG>scr_dump</STRONG> after <STRONG><A HREF="curs_initscr.3x.html">endwin(3x)</A></STRONG>.
+
+
+</PRE><H3><a name="h3-scr_set">scr_set</a></H3><PRE>
+ The <STRONG>scr_set</STRONG> routine is a combination of <STRONG>scr_restore</STRONG> and <STRONG>scr_init</STRONG>. It
+ tells the program that the information in <EM>filename</EM> is what is currently