System: Solaris 2.5.1, X11R6, gcc 2.7.2.x.
I tried using gnuclient for the first time since b46 or so. It
doesn't seem to work anymore. I start "xemacs -vanilla", "M-x
gnuserv-start". Then "gnuclient /tmp/junk". This works fine.
Start up a new xemacs and gnuserv-start. Now, if I try "gnuclient".
It pops up a new frame with the current buffer in it. C-X #, of
course, doesn't work because the buffer is a server buffer. Should
gnuclient create a new server buffer in this case?
Start another xemacs and gnuserv-start. Then try "gnuclient -nw
/tmp/junk". gnuclient hangs, and so does that xemacs. No response to
any key stroke. I kill gnuclient and xemacs is still hung. If I then
kill xemacs, I get this:
Lisp backtrace follows:
# (unwind-protect ...)
make-device(tty "/dev/pts/4" (terminal-type "xterm"
controlling-process 3734))
# bind (controlling-process terminal-type tty)
make-tty-device("/dev/pts/4" "xterm" 3734)
apply(make-tty-device ("/dev/pts/4" "xterm" 3734))
# bind (dest-frame new-frame old-device-num quick view flags list type)
gnuserv-edit-files((tty "/dev/pts/4" "xterm" 3734) ((1 .
"/tmp/junk")))
eval((gnuserv-edit-files (quote (tty "/dev/pts/4" "xterm" 3734))
(quote (...))))
byte-code("..." [eval read-from-string gnuserv-string header] 4)
# (condition-case ... . ((error (byte-code "ÀÂ
\"ÅÆ
@
A\"" ... 3)) (quit
(byte-code "ÀÂ
\"ÅÆÇÅ\"" ... 3))))
# bind (header string proc)
gnuserv-process-filter(#<process "gnuserv" pid 3733 state:run> "7
(gnuserv-edit-files '(tty \"/dev/pts/4\" \"xterm\" 3734) '((1
. \"/tmp/junk\")))")
# (condition-case ... . error)
# bind (inhibit-quit)
# (condition-case ... . error)
# (catch top-level ...)
Apparently, xemacs is having troubles connecting to my xterm.
This used to work in earlier betas.
Where do I go from here?
Ray