Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Behaviour of setjmp/longjmp and registers
Message-ID: <9597@smoke.BRL.MIL>
Date: 5 Feb 89 05:04:49 GMT
References: <25@torsqnt.UUCP> <8867@bloom-beacon.MIT.EDU> <9480@smoke.BRL.MIL> <3112@xyzzy.UUCP> <483@maxim.ERBE.SE>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 13

In article <483@maxim.ERBE.SE> prc@maxim.ERBE.SE (Robert Claeson) writes:
>Does this really work that good? A function key (control) character
>sequence can be of arbitrary length. The up-arrow  key on my keyboard
>sends three characters, whereas a typical F-key sends 5 characters.

The character sequence should follow ANSI X3.64, meaning that it begins
with an ESC character and continues through an alpha.  That can be
parsed without any timeouts at all.

What probably is contributing to the confusion is that you bought
keyboards that have an ESC key the user can press that violates the
X3.64 standard.  Remove the key or tell your users how to recover
from it (treating a second consecutive ESC specially is one way).