Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!mips!prls!pyramid!infmx!davek From: davek@informix.com (David Kosenko) Newsgroups: comp.databases Subject: Re: Using Informix remotely Keywords: Informix Message-ID: <1990Oct29.145247.6137@informix.com> Date: 29 Oct 90 14:52:47 GMT References: <53593@unix.cis.pitt.edu> Sender: news@informix.com (Usenet News) Organization: Informix Software, Inc. Lines: 25 In article <53593@unix.cis.pitt.edu> smfst2@unix.cis.pitt.edu (Seth M Fuller) writes: >Informix 4.00 >is supposed to have a parameter that can be tuned that determines how >long Informix waits to make sure it has gotten a complete key-sequence. It does. The parameter is set via an environment variable, DBESCWT. The value you set for that specifies in seconds how long to wait after an escape is entered to see if there are subsequent characters in the sequence. The maximum value for this is 60. As setting this value higher will result in a noticeable delay when an escape alone is typed (the default ACCEPT key), you may want to remap the ACCEPT key using the OPTIONS command. We in the field have found that setting this value to 2 (i.e. wait 2 seconds after an escape to see if any other characters come in) seems to clear up the "misinterpretation" problem while not affecting the ACCEPT process too noticeably. Dave -- Disclaimer: These opinions blah blah blah. ************************************************************************** Up on the watershed, standing at a fork in the road; you can stand there and agonize, 'til your agony's your heaviest load. -E. Saliers