Newsgroups: comp.unix.sysv386 Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uunet!kithrup!sef From: sef@kithrup.COM (Sean Eric Fagan) Subject: Re: vi and rlogin Organization: Kithrup Enterprises, Ltd. Distribution: usa Date: Sat, 08 Jun 1991 06:58:16 GMT Message-ID: <1991Jun08.065816.11472@kithrup.COM> References: <852@tiamat.fsc.com> <1991Jun07.012603.4449@virtech.uucp> In article <1991Jun07.012603.4449@virtech.uucp> cpcahil@virtech.uucp (Conor P. Cahill) writes: >Rlogin does not eat ESCs. The problem with using multi-byte keys over >a network is that there may be enough of a delay between the characters >in the sequence that a program sees them as separate sequences. No, I guarantee there is at least one version of rlogin that SCO shipped that ate ESC's. A friend of mine fixed it, after finding out, during one session (in which he'd rlogin'd to one machine, and rlogin'd from there to a third, and then ran emacs on the third) that he had to press *27 times* to get one across. (Each rlogin [not rlogind] ate three escapes, and spit out one in return; thus, 3 esc's on localhost to get one esc to host1; 9 esc's on localhost to get three esc's to host1 to get 1 esc to host2; and 27 esc's on localhost to get 9 esc's to host1 to get 3 esc's to host2 to get 1 esc to host3.) There may be a problem with function keys over the network, but emacs doesn't *care* about that, so there aren't any timing problems. -- Sean Eric Fagan | "I made the universe, but please don't blame me for it; sef@kithrup.COM | I had a bellyache at the time." -----------------+ -- The Turtle (Stephen King, _It_) Any opinions expressed are my own, and generally unpopular with others.