watch(1) uses curses(3), and I thought that library was clever
enough to only update the parts of the screen with actual changes.
And yet, the xterm window with watch(1) flickers when the screen
is updated, even when there are no changes other than the clock,
as if the screen was cleared and repainted ...

Okay, I've captured some output with script(1) and looked over it
with teseq(1), and watch(1) erases and repaints a large and unchanged
_part_ of the screen with each update.  What is going on here??

Anybody familiar enough with curses to make sense of this?

-- 
Christian "naddy" Weisgerber                          [email protected]

Reply via email to