Re: [Crash] gnuclient -nw
SL Baur <steve(a)xemacs.org> writes:
> Glynn Clements <glynn(a)sensei.co.uk> writes:
>> Using `gnuclient -nw <filename>' kills XEmacs, but only when started
>> from the WM. If it is started from an xterm or the console, it works
>> fine.
Why should we care? When I tried this I got (with olvwm on Linux
linked with libc6 and libgpm):
I think you are misunderstanding Glynn, or I am.
I think he starts XEmacs from his WM but is running gnuclient in an
xterm.
Jan
This second case where it matter whether XEmacs is started from the WM
or otherwise, I cannot figure out why it should make a differnce. The
other guys bug is even more weird but reprodable (if XEmacs is started
from mwm, (gnuserv-start) is in .emacs THEN (and only then) XEmacs does not
see second request to edit files (although gnuserv writes it on
STDOUT, XEmacs never calls the process filter), using gnuclient -batch
twice works.). It is so complicated that I agreed with him to wait for
21.0 in the hope that all the process and stream fixups magically fix
it.
Anybody have a clue about what is typically different between a WM
environment and say a shell in Xterm? (Note the unix environment is
more-or-less the same in each case)