Remove readline legacy input function 'winch' and replace its functionality with an event handler function. Once again make the null keybinding do nothing. There are various sitauations where you want to perform a repaint at just the right time, and more or less by luck it worked very well to do this on null, but this really shouldn't happen and no longer does. Hopefully if new repainting issues turn up, they can be fixed at the root instead of once again reapplying this broken bandaid.

darcs-hash:20070930225354-75c98-8e2b518aa0ef694cee889c1c599ff4f158d9eb7f.gz

1 files changed, 13 insertions, 3 deletions

diff --git a/screen.h b/screen.h
index 581fce39..19b12f7f 100644
--- a/screen.h
+++ b/screen.h
@@ -102,9 +102,19 @@ void s_write( screen_t *s,
 			  int cursor_pos );
 
 /** 
-	This function resets the screen buffers internal knowledge about
-	the contents of the screen. Use this function when some other
-	function than s_write has written to the screen.
+    This function resets the screen buffers internal knowledge about
+    the contents of the screen. Use this function when some other
+    function than s_write has written to the screen.
+
+    \param s the screen to reset
+    \param reset_cursor whether the line on which the curor has changed should be assumed to have changed. If \c reset_cursor is set to 0, the library will attempt to make sure that the screen area does not seem to move up or down on repaint. 
+
+    If reset_cursor is incorreclt set to 0, this may result in screen
+    contents being erased. If it is incorrectly set to one, it may
+    result in one or more lines of garbage on screen on the next
+    repaint. If this happens during a loop, such as an interactive
+    resizing, there will be one line of garbage for every repaint,
+    which will quicly fill the screen.
 */
 void s_reset( screen_t *s, int reset_cursor );