Thank you for your report!
On Tue, May 1, 2012 at 7:06 AM, Jirina Stone <j.stone1(a)physics.ox.ac.uk> wrote:
The error was
Window hight 0 too small (after splitting).
This is likely a bug in some Lisp program you are using. It's not
likely to be directly connected to the crash. I'll do some archive
research; I know I've seen similar reports but I don't recall window
height ZERO cases (the actual too small limit is usually 2 or 3 lines,
so 1 or 2 is "too small").
# (condition-case ... . ((nil)))
This is almost certainly a known bug, but it hasn't been localized
yet, there is no fix yet. Please check and see if the crash occurs
$ xemacs -vanilla no-such-file.tex
(it should not). Then try with "xemacs -vanilla existing-file.tex"
(obviously substitute the name of a real file). If that does cause
the crash, and you can send me the file, please do. If you are
uncomfortable posting it to a public mailing list, but are willing to
send it to me personally, you can send it to me at
If you can't reproduce the crash with "xemacs -vanilla", but can
reliably elicit the crash with your normal XEmacs, then there is a
more tedious procedure we can follow to try to localize the defect.
But that's going depend on your time and effort, so it's up to you.
So that you can get your work done, there is a workaround. Put
(setq progress-feedback-use-echo-area t)
in your init.el. That will prevent XEmacs from using the GUI progress
gauge, and the crash shouldn't recur. Then we can try to diagnose and
fix the window-height issue.
XEmacs-Beta mailing list