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.
- 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.
Show replies by date
I have seen this behavior for some time, at least for all XEmacs 21
releases and maybe before that. If I do "gnuclient FILE", gnuclient
waits for the frame to close before terminating. But if I just say
"gnuclient", it exits as soon as the frame appears. Is this different
from what you are seeing?
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: oberman(a)es.net Phone: +1 510 486-8634