Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!romp!auschs!awdprime!sandino.austin.ibm.com!jeffe
From: jeffe@sandino.austin.ibm.com (Peter Jeffe 512.823.4091)
Newsgroups: comp.unix.aix
Subject: Re: More Problems with Curses
Keywords: curses, aix, delay
Message-ID: <3286@awdprime.UUCP>
Date: 28 Aug 90 21:40:42 GMT
References: <1990Aug24.175432.26025@eplrx7.uucp>
Sender: news@awdprime.UUCP
Organization: IBM AWD, Austin, TX
Lines: 24

In article <1990Aug24.175432.26025@eplrx7.uucp> mroz@eplrx7.uucp (Peter Mroz) writes:
>The problem is that because of the way I'm
>connected in to the RS/6000, sometimes there is a delay in sending the three
>bytes for a cursor strike (ESC [ A, ESC [ B, etc.), so that I get back
>three characters instead of "one" (KEY_xxxx).  
>
>Called IBM Software Support and was told that this was not a defect; we would
>have to get curses to understand the delay.
>
>Is there some stty setting or curses call that will alleviate this problem?

The curses library has dealt with this issue by allowing you to redefine the
maximum delay between the escape character and succeeding ones in an escape
sequence.  You can do this with the ESCDELAY environment variable, which
specifies the number of 200 microsecond intervals to wait after an escape
character is seen.  The default value is 100000 usecs, or an ESCDELAY value
of 500.  I've found that a value of 1000 does the trick with an rlogin over
one gateway.

This feature is avaliable in the July update.
-------------------------------------------------------------------------------
Peter Jeffe   ...uunet!cs.utexas.edu!ibmaus!auschs!sandino.austin.ibm.com!jeffe
        first they want a disclaimer, then they make you pee in a jar,
                   then they come for you in the night