Jan Vroonhof wrote:
> > > 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.
Yep, that is the case.
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)
Well, XEmacs has no controlling tty. In my case (fvwm2), stdin is
/dev/null and stdout/stderr are ~/.xsession-errors.
Also, a program run from an xterm will generally inherit any
environment settings which are made in /etc/profile, ~/.profile etc,
while a program run from the WM won't. However, my Xsession script
sources both of these files, so there shouldn't be any differences in
the environment in this case.
--
Glynn Clements <glynn(a)sensei.co.uk>