Xref: utzoo gnu.misc.discuss:3089 comp.misc:12555 comp.dcom.modems:9728 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!sun-barr!newstop!central!csccat!ncmicro!ltf From: ltf@ncmicro.lonestar.org (Lance Franklin) Newsgroups: gnu.misc.discuss,comp.misc,comp.dcom.modems Subject: Re: hayes lawsuit Message-ID: <370@ncmicro.lonestar.org> Date: 14 May 91 19:17:29 GMT References: <1991May13.044909.3617@netdev.comsys.com> <-i5Hsdq3@cs.psu.edu> Followup-To: gnu.misc.discuss Organization: NC Microproducts, Inc. Richardson, Tx Lines: 26 In article <-i5Hsdq3@cs.psu.edu> schwartz@groucho.cs.psu.edu (Scott Schwartz) writes: } }tmb@ai.mit.edu (Thomas M. Breuel) writes: } If you can think of uses prior to the mid-1980's of timeouts or timing } to transmit out-of-band commands or data to a computer or communications } device, please drop me a note, and I can put you in touch with the } attorneys handling the case. } }Isn't that how vi handles function keys? Anyone know vi's inception }date? I beleive that Wordstar used to use a timeout on it's two-key functions. If you didn't hit the second key within a certain period of time, a help screen would pop up giving you a list of applicable keys. This was, I beleive, to efficiently work with slow terminals, where expert users could hit the second key quickly and avoid taking up the time to display the help. Since the terminal could be considered a communications device in this case, perhaps this would be helpful to your case? Lance -- Lance T. Franklin +----------------------------------------------+ (ltf@ncmicro.lonestar.org) | "You want I should bop you with this here | NC Microproducts, Inc. | Lollipop?!?" The Fat Fury | Richardson, Texas +----------------------------------------------+