Michael,
I now realize that my initial test was bogus because I started xemacs
from the shell in which I ran gnuclient, and it therefore had all of
the context it needed to work properly. In a more rigorous test, I
am unable to make it work :-( Sorry for the false positive.
Michael Sperber [Mr. Preprocessor] may have said:
Right. But for the connection to carry the cookie, it needs access
to
the cookie. In the setup out here, ssh stores it in a file referenced
by the XAUTHORITY environment variable.
Version 3 apparently no longer uses the XAUTHORITY environment
variable:
server> ssh client
client> printenv XAUTHORITY
client> xlogo [works]
The only variables it appears to set (aside from DISPLAY) are
SSH_CLIENT and SSH_TTY, neither of which appears to be necessary:
client> unsetenv SSH_CLIENT
client> unsetenv SSH_TTY
client> xlogo [works]
It appears that the X authentication information is stored on the host
on which the pseudo-server is running, and I can launch clients from
any shell which connect to the pseudo-server. That said, when I try
to execute (make-frame-on-display "client:10.0"), xemacs just hangs.
Cheers,
-Ted