- what the terminal currently has on its screen. If the
- data is determined to be valid, <STRONG>curses</STRONG> bases its next
- update of the screen on this information rather than
- clearing the screen and starting from scratch. <STRONG>scr_init</STRONG>
- is used after <STRONG>initscr</STRONG> or a <STRONG>system</STRONG> [see <STRONG>system</STRONG>(BA_LIB)]
- call to share the screen with another process which has
- done a <STRONG>scr_dump</STRONG> after its <STRONG>endwin</STRONG> call. The data is
- declared invalid if the terminfo capabilities <STRONG>rmcup</STRONG> and
- <STRONG>nrrmc</STRONG> exist; also if the terminal has been written to
- since the preceding <STRONG>scr_dump</STRONG> call.
-
- 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
+ what the terminal currently has on its screen. If the da-
+ ta is determined to be valid, <STRONG>curses</STRONG> bases its next update
+ of the screen on this information rather than clearing the
+ screen and starting from scratch. <STRONG>scr_init</STRONG> is used after
+ <STRONG>initscr</STRONG> or a <STRONG>system</STRONG> call to share the screen with another
+ process which has done a <STRONG>scr_dump</STRONG> after its <STRONG>endwin</STRONG> call.
+ The data is declared invalid if the terminfo capabilities
+ <STRONG>rmcup</STRONG> and <STRONG>nrrmc</STRONG> exist; also if the terminal has been writ-
+ ten to since the preceding <STRONG>scr_dump</STRONG> call.
+
+ 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