Neal Becker writes:
Sort of works, but I'm getting millions of messages:
Fontifying region...(invalid-function 0)
Strangely, setting debug-on-error doesn't seem to trap the message.
If it were a debuggable error, I have to admire your stamina. You
only get one error per command, so you tried it millions of times! :-)
Now, debug-on-error hooks into the process *later* than condition-case
does, so if the error is handled in code you'll never see it. What
you need here is debug-on-signal, which drops you into the debugger
before condition-case gets its hands on it.
You could also just look for condition-cases in the code.
XEmacs-Beta mailing list