lynx-dev Nitsy "reset" display buglet

[Kim DeVaughn]

When you activate a forms "reset button", the statusline gets
completely blanked, until you move off the button.

A dump of the actual output to the screen, shows that the following
strings actually get written (sequentially) to the screen:

 Resetting form...
 Commands: Use arrow keys to move, '?' for help, 'q' to quit, '<-' to go back.
 __________________________
 Reset to initial text
 Reset to initial text

but when change_form_link() returns to mainloop() after it has set
*refresh_screen = TRUE, the screen refreshes (which is required to
reflect the now "reset" textarea to the screen), and is where the
statusline gets blanked.

Since the refresher can't know why it was invoked, it can't put up a
statusline msg, and since the cursor hasn't moved off the reset button,
there's been no keyboard action that would generate a new statusline
msg.

Anyone have a solution to this rather pathological case?

Making a hack like  *refresh_screen = REFRESH_ALL_EXCEPT_STATUSLINE
and then letting the screen refresher recognize and deal with that
option, is one possibility, but that seems pretty ugly (if it can
even be done with both slang and ncurses at all).

Or, we can live with the blanked statusline, call it a "feature" that
indicates the reset button has done its job, and let it go at that ...

/kim