Openbox: A lightweight window manager (Linux.com)

Openbox: A lightweight window manager (Linux.com)

Okay, so I tried starting xemacs like this, inside screen.

xemacs -unmapped -eval "(gnuserv-start)"

This correctly started it without creating a window, and I was able to run gnuclient to connect to it and create windows. However, still when the X server goes away, the xemacs process dies with a traceback (appended). Too bad.

Fatal error (13).

Your files have been auto-saved.
Use `M-x recover-session' to recover them.

Your version of XEmacs was distributed with a PROBLEMS file that may describe
your crash, and with luck a workaround. Please check it first, but do report
the crash anyway. Please report this bug by invoking M-x report-emacs-bug,
or by selecting `Send Bug Report' from the Help menu. If necessary, send
ordinary email to `xemacs-beta@xemacs.org'. *MAKE SURE* to include the XEmacs
configuration from M-x describe-installation, or equivalently the file
Installation in the top of the build tree.

*Please* try *hard* to obtain a C stack backtrace; without it, we are unlikely
to be able to analyze the problem. Locate the core file produced as a result
of this crash (often called `core' or `core.<process-id>', and located in
the directory in which you started XEmacs or your home directory), and type

gdb /usr/bin/xemacs core

then type `where' at the debugger prompt. No GDB on your system? You may
have DBX, or XDB, or SDB. (Ask your system administrator if you need help.)
If no core file was produced, enable them (often with `ulimit -c unlimited'
in case of future recurrance of the crash.

Lisp backtrace follows:

# (condition-case ... . error)
# (catch top-level ...)