"gnuclient -nw" just exits
Karl Kleinpaste writes:
When using gnuclient to instantiate a new X frame, I expect
gnuclient
merely to exit, having done all the job it can be expected to do.
But when using "gnclient -nw", I kinda expect gnuclient to stay the
heck out of the way while XEmacs running elsewhere takes control of
the tty. As it is in -b26, however, "gnuclient -nw" still simply
exits immediately. And it's exiting status zero, for that matter,
which is curious, considering that the only exit() calls in
lib-src/gnuclient.c are "exit(1);".
main() does a return 0. I tested gnuclient -nw attaching to an
XEmacs already running on a tty and that worked OK. gnuclient
hung around until I did C-x 5 0 on the new frame.
If you look at disconnect_from_server you'll see that it reads
from the server until the read() call returns no data or has a
fatal error. So it looks like something happens to either the
socket or the server if gnuclient is dying early.