"gnuclient -nw" oddity (was "[COMMIT] gnuclient bug on Ben's part")

Mike> What's more confusing is that I'm suddenly having problems getting Mike> "gnuclient -nw" to start up at all. When I run it, instead of Mike> getting an XEmacs frame, it hangs. If I C-z it, I get Mike> ^Z[2] + Stopped (SIGTSTP) /usr/local/bin/gnuclient -nw [1] - Mike> Stopped (SIGTTOU) xemacs & Mike> Putting job 1 (xemacs) into the foreground gives me my tty frame. Mike> But then I can't get out with C-x 5 0. The tty frame is cleared, Mike> but I don't get my shell back. Mike> This is on Solaris, a recent development build of 5.11, using ksh Mike> as my shell. I can reproduce this on Linux. It appears to result from running "gnuclient -nw" from the same shell that I started XEmacs in. If I run "gnuclient -nw" from a different shell, things work normally. Want me to file a formal bug report (M-x report-xemacs-bug)? mike