🚀 go-pugleaf

I've updated Emacs from 18.47 to 18.51 and noticed the following quite
serious problem.  I've managed to hang our whole LAVC while trying out
this new EMACS!  So far it occurs only during a SET HOST session.
I'm using VMS 5.1b but have gone to a 4.7 system and seen exactly the
same behavior.  The following sequence seems to reproduce the problem:

   a)  login on node A
   b)  set host node B		(this is common when using a VAXstation, 
				 and needing to login to another system)
   c)  run the kept or straight gnuemacs 18.51
   d)  start an I-Search  (I've used both a version which searches with
       ^s^r  or ^\^r.)
   e)  type one or two ^G to quit the search and return to the point
       before search began.   

I now find myself one or more keystrokes behind what is happening on
the screen and extremely disconcerted.  Though sometimes I can exit 
and recover from this, sometimes I need to stop/id=xxx.  Once, the 
emacs process got into a MWAST state, refused to die, and no further 
logins to any cluster node were successful!  Note that emacs was not 
INSTALLed in any way.

Anyone else see this?  Any fixes?  We have lots of workstations and
many applications where remote login/file editing is important.


				  Thanks, Bob Stone
                                -----------------------------------------
                                | Rutgers University       201 932-2531 |
                                | RUTHEP::Stone                HEPnet   |
                                | Stone@Ruthep                 Bitnet   |
                                | Stone@Ruthep.Rutgers.Edu     Internet |
                                -----------------------------------------