Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!cs.utexas.edu!sun-barr!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Re: Remote xterm strategy
Message-ID: <43510@lll-winken.LLNL.GOV>
Date: 8 Jan 90 01:43:37 GMT
References: <90Jan6.054031est.2293@neat.cs.toronto.edu> <6517@ogicse.ogc.edu> <32711@news.Think.COM> <1990Jan7.213940.11542@smsc.sony.com>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 31

| From: dce@Sony.COM (David Elliott)
| 
| [With] standard BSD rlogin, -e is followed immediately by the character
| to use, and if none is given, the escape feature is turned off.  In other
| words, just use -e with no character and it will do what you expect.

  "-e" by itself won't turn off the rlogin escape character.  It sets the
escape character to '\0'.  You can still escape out of the rlogin with
^@^Z, for instance.  The following patch to the 4.3BSD rlogin client will
implement the semantics you've described (I've been using this patch for
the last six months with no problems):

*** rlogin.c-dist	Sun Mar 30 16:39:06 1986
--- rlogin.c	Thu Jun 29 18:25:22 1989
***************
*** 289,295 ****
  		 */
  		if (bol) {
  			bol = 0;
! 			if (c == cmdchar) {
  				bol = 0;
  				local = 1;
  				continue;
--- 289,295 ----
  		 */
  		if (bol) {
  			bol = 0;
! 			if (cmdchar && c == cmdchar) {
  				bol = 0;
  				local = 1;
  				continue;