Re: Continuous running (was Re: gnuclient *feature* -- crash when frames lose X connection)
Charles G Waldman <cgw(a)alum.mit.edu> writes:
Stephen J. Turnbull writes:
> >>>>> "smikes" == Samuel Mikes <smikes(a)cubane.com>
writes:
>
> smikes> Off topic, is it possible to force XEmacs not to exit
> smikes> when the last device gets deleted?
>
> I don't think so. It would be nice, of course. Then the next thing
> would be to embed the XEmacsServer in a loadable kernel module ;-)
It's not exactly what Samuel was asking, but you can always start it up
as "xemacs -unmapped", which basically gives you the same effect... I
start xemacs this way and do all my edits via gnuclients... when I exit
the last gnuclient frame, the unmapped xemacs frame is still running.
If you combine this with the Xvfb server from XFree86[1], you can do some
pretty spiffy stuff. If you start Xvfb and tell XEmacs to start with
'xemacs -display :2.0 -unmapped', you XEmacs will always be around.
-bp
[1] From the man page: "Xvfb is an X server that can run on machines with
no display hardware and no physical input devices. It emulates a dumb
framebuffer using virtual memory."
--
Ceterum censeo vi esse delendam