>>>> "Horst" == Horst von Brand
<vonbrand(a)inf.utfsm.cl> writes:
Horst> [Progress bar, stops at 2.3 or so] [Stop button]
I doubt it will solve the hanging problem, but you could try
(setq progress-feedback-use-echo-area t)
in init.el to disable the progress bar.
Horst> in the echo area. It becomes totally unresponsive, just the
Horst> buttons at top (File, etc) show their menus, but they don't
Horst> act (i.e., File->New frame does nothing). The kill button
Horst> in the Gnome decoration doesn't work either, fullscreen
Horst> gives fullscreen but the in-xemacs decorations (scrollbar,
Horst> etc) don't adjust to the new frame size, they stay put,
Horst> only the complete frame becomes larger.
All of this happens only when you're in the hung state, right?
The fact that you can call any XEmacs code at all suggests that the
Xt event loop is still running, and the high-priority callbacks
directly from the Xt event loop get run. However, the Lisp event loop
is stuck, apparently. I'm not sure how that can happen....
You don't say, so I'll check: you can't interrupt the hang with
repeated C-g? (One may not be enough, but two or more should be.)
It sounds like one possibility is that there's either a bad regexp in
MH-E or the XEmacs regexp engine is broken. Try setting fontlock to
"off" and see if that helps.
Is it possible to find out what the contents of "+inbox" are by doing
something like "C-x b junk RET C-x i +inbox RET" or "C-x b junk RET C-u
M-! some-mh-command RET"?
Horst> Warning: Error in `pre-idle-hook' (resetting to nil):
Horst> Attempt to throw outside of function:To catch
Horst> `call-process-done' with value `0'
This isn't surprising, given that XEmacs is in a very odd state. I
don't know that it means much, but I'm glad you report it.
--
School of Systems and Information Engineering
http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.