From xemacs-m  Thu Jun  5 13:19:48 1997
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id NAA13497
	for <xemacs-beta@xemacs.org>; Thu, 5 Jun 1997 13:19:47 -0500 (CDT)
Received: from Corp.Sun.COM ([129.145.35.78]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id LAA02632 for <xemacs-beta@xemacs.org>; Thu, 5 Jun 1997 11:38:01 -0700
Received: from legba.Corp.Sun.COM by Corp.Sun.COM (SMI-8.6/SMI-5.3)
	id LAA17127; Thu, 5 Jun 1997 11:20:09 -0700
Received: by legba.Corp.Sun.COM (SMI-8.6/SMI-SVR4)
	id LAA17472; Thu, 5 Jun 1997 11:20:10 -0700
To: xemacs-beta@xemacs.org
Subject: more gnuserv stuff
X-Attribution: GDF
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: Gary.Foster@Corp.Sun.COM (Gary D. Foster)
Date: 05 Jun 1997 11:20:09 -0700
Message-ID: <bcipvu0oqsm.fsf@corp.Sun.COM>
Lines: 21
X-Mailer: Gnus v5.4.55/XEmacs 20.3(beta3)

Has anyone had any success running gnuclient, displaying a new X
frame, and attaching to a remotely running xemacs via
MIT-MAGIC-COOKIE-1?

Something like:

legba:$ gnuclient -h xem-host -p 9994

(with GNU_PORT set in the remote xemacs environment as 9994, and
gnuserv verified listening on port 9994, and .Xauthority information
all set up for display 999 as needed)

When I try it, I get an error signaled in the warning buffer (a void
variable error) and gnuclient drops me right back to my shell prompt.
After that, I can no longer connect at all from that pty, which leads
me to believe that the root of the problem might be the same one that
I mentioned before (and that Hrvoje and Kyle posted fixes for).

Just wanted to make sure, though.

-- Gary F.

