Re: Gnuclient -nw strangeness
Robert_Pluim(a)BayNetworks.COM (Robert Pluim) writes:
if I do: xemacs -vanilla & (which creates an X frame)
and then: gnuclient -nw from the same xterm, gnuclient hangs. I can ^Z
it, and then bring xemacs to the foreground, and I'll get a tty frame.
If I do the gnuclient -nw from a different xterm, everything works as
expected.
Unfortunately this a known problem. It is basically the unix terminal
group mechanism which is getting our way here.
The problem could be avoid if you could do
'xemacs -unmapped </dev/null &' or XEmacs could itself detach from its
terminal. However this cannot currently be as XEmacs needs stdin to be
a tty. This could be solved by -batch like mode (which has a stream
device[1] and thus does not need a tty) that does not exit when some flag
is set. Gnuserv-start could then set this flag.
Alternatively 'gnuclient' could be me made to proxy the stuff to its
own pseudo terminal like 'script' does. This would also make the
signal forwarding a lot cleaner.
Nobody has done the coding yet however.
Jan
Footnotes:
[1] Unix XEmacs has 3! device types: X, tty, stream.