Re: Lazy-lock errors.
At 18 Jan 2002 12:37:06 +0100,
Adrian Aichner wrote:
please
M-x load-library RET lazy-lock RET
This should give you a meaningful Lisp Backtrace when the problem
happens again.
I did, but the backtraces didn't become more meaningful, so I simply
renamed the byte-compiled version of lazy-lock. I then happened to get
a backtrace on another lazy-lock error that's been bothering me. I
fixed that (a failure to check for division by zero, which led to an
error when lazy-lock traversed an empty (mini-)buffer), and it looks
as if this has removed my other problem as well.
I'll put my fix through its paces, and if nothing crops up, I'll be
submitting my first XEmacs patch soon. Thanks for pointing me in the
right direction!
- Kvan.