I reported in -b26 that gnuclient was exiting immediately after being started, which confused me especially because it departed with status zero, but I saw no exit of that sort. Kyle pointed out that gnuclient's main() actually does "return 0;", which makes sense as far as that goes. So I just walked through gnuclient with gdb, and I simply don't understand the path taken. My short summary of gnuclient's path is: - initialize a bunch of general state/option variables. - check for batch operations and window suppression ("-nw"). - connect to xemacs via connect_to_unix_server(). - get xemacs' pid. - disconnect. - set signal state (in the -nw case). - connect to xemacs again. - ship over a gnuserv-edit-files command. - ...and then immediately disconnect and exit. Where in this logic path does the possibility of having gnuclient wait for `C-x 5 0' even exist? I feel I must be missing something obvious. 21.2.27, Linux RH6.0. --karl