Jerry James writes:
Unless someone knows a reason why that history is incorrect, the
right
thing to do here is to kill off the first 3 definitions in
mule-util.el. I'll whip up a patch to do that in a bit.
Please do; that's the right thing to do. That doesn't mean we won't
get further problems in Mule, though. We should be prepared for
weirdness.
However, there's also the question of how Lisp code can crash at all.
Do you understand that mechanism?
Please take the minimal reproducer, add it to
tests/reproduce-crashes.el, and make sure it crashes there. Add an
XEmacs bug pointing to this thread and that test. Or I can do it, but
without a tracker entry my memory has been rather fallible of late.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta