Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!paperboy!hsdndev!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Escape sequences over Telnet/TCP
Message-ID: <17189:May722:02:2791@kramden.acf.nyu.edu>
Date: 7 May 91 22:02:27 GMT
References: <9105040208.AA21383@WLV.IMSD.CONTEL.COM>
Organization: IR
Lines: 14

In article <9105040208.AA21383@WLV.IMSD.CONTEL.COM> mcc@WLV.IMSD.CONTEL.COM (Merton Campbell Crockett) writes:
> If this is the case, the fault lies in the implementation of
> the TELNET client software which is not handling escape sequences correctly in
> this particular environment.

No. The fault lies entirely in a keyboard code convention that produces
streams that can't be uniquely decoded without timing information. In a
better world, no valid key combination would produce a proper prefix of
another, and these problems would disappear.

(One would think that a virtual terminal protocol would address these
issues. SUPDUP does, anyway.)

---Dan