giacomo boffi <giacomo.boffi(a)polimi.it> writes:
Stephen J. Turnbull writes:
> XEmacs can use up big hunks of VM; even if it's swapped out, that's
> not desirable.
if a few hundred kb more are not a problem...
> AFAIK gnuserv connections aren't really first class citizens; XEmacs
> has to connect to some device.
Since posting my problem to the debian bug tracking system, and
discovering this is evidently a FAQ...
... one could
1. start xemacs in a "screen session"
% screen xemacs -nw -f gnuserv-start
That's a nifty workaround which I have been using for a few weeks. I
tried the -unmapped one first, but when gnuserv crashed one day, and
the xemacs process stayed alive, I thought it would be nice to be able
to reconncect to xemacs and tell it to start gnuserv once again -
hence using screen
2. immediately detach from the session (usually it's C-a d), and
Or just use:
screen -m -d /usr/X11R6/bin/xemacs -nw -f gnuserv-start
But it is only a workaround, and when one of the clients die, it kills
them all. I'll see what I can code up, but I do know nothing about X,
and littel about elisp :)
TimC -- http://astronomy.swin.edu.au/staff/tconnors/
Whip me. Beat me. Make me maintain AIX.