| From: Thomas Dickey <[EMAIL PROTECTED]>

| I just tried again, but still no runaway.  But it's a couple years old:
| 
| Linux bloatware 2.2.16 #8 SMP Fri Dec 8 18:02:22 EST 2000 i686 unknown
| 
| -rwxr-xr-x   1 root     root      1013224 Mar 21  2000 libc-2.1.3.so
| 
| (I recall seeing some discussion over the past few years regarding differing
| implementation of select/poll, so perhaps it's an improvement ;-)

Might be worth doing an strace.  On RHL8.0, I get:

select(5, [3 4], [], NULL, {0, 0})      = 1 (in [3], left {0, 0})
select(4, [3], [], [], {0, 0})          = 1 (in [3], left {0, 0})
select(4, [3], [], [], {0, 0})          = 1 (in [3], left {0, 0})
select(4, [3], [], [], {0, 0})          = 1 (in [3], left {0, 0})

Notice that each of these select calls has a timeout specified, and
that timeout is 0 seconds.  So these calls never block.  Besides that,
there is something available on file descriptor 3 but it is never
being accessed.

What does strace show on your older system?

| > |   I'm using
| > | a test-screen in vttest to exercise this feature.
| > 
| > Do you mean the feature of hanging, or the feature used properly?
| 
| the latter.  With Redhat 8.0, I was able to make it run away with a few
| dozen clicks in that test screen.  

That sounds bad.  I have used JOVE full time for almost 20 years and
usually hit this problem when I lose contact with the machine running
JOVE (think ssh in an xterm).

On the other hand, the ugly echo & click hangs xterm on my machines
first time every time.

| > What do you think about the approach I suggested (act as if a default
| > CSI...T sequence had been received until the real one is)?  Perhaps
| > the default should only be used after some timeout.
| 
| it's not entirely clear to me what the sequence would be here.

Two obvious ones: the whole xterm region, or an empty region at the
point of the cursor.  I'd vote for the empty region: no information
about a subsequent click is lost (the answer will be forced to be the
long form).

Clearly func should be non zero in either case: we don't want to
cancel the mode.
        
I do suggest that the default only be installed after a brief timeout.
How long?  A tenth of a second feels about right.

I also suggest that the default be replaced if and when the explicit
CSI...T sequence is received.

There are other ways to skin this cat.  For example, after a longer
timeout, just exit the mode.

Thanks for looking at this,

Hugh Redelmeier
[EMAIL PROTECTED]  voice: +1 416 482-8253

_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Reply via email to