On 2007-06-26 09:24:44 -0400, Thomas Dickey wrote: > On Tue, Jun 26, 2007 at 02:58:31PM +0200, Vincent Lefevre wrote: > > A naive replay won't work: you need (triple-)clicks while the output > > occurs to be able to reproduce the bug (such clicks more or less > > freeze xterm's output). > > I would take that into account. The main thing that a reply would > do would be to set the screen up as it was when you clicked on it, > e.g., erasures, wrapping-marks, etc.
But clicks are not logged, so it would not be the same state (clicks shouldn't affect the buffer state, but the present bug is that they seem to affect this state). -- Vincent Lefèvre <[EMAIL PROTECTED]> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
