Re: Lazy-lock errors.

Casper> At 18 Jan 2002 12:37:06 +0100, Casper> Adrian Aichner wrote: Casper> I did, but the backtraces didn't become more meaningful, Casper> so I simply renamed the byte-compiled version of Casper> lazy-lock. I then happened to get a backtrace on another Casper> lazy-lock error that's been bothering me. I fixed that (a Casper> failure to check for division by zero, which led to an Casper> error when lazy-lock traversed an empty (mini-)buffer), Casper> and it looks as if this has removed my other problem as Casper> well. Great! Casper> I'll put my fix through its paces, and if nothing crops Casper> up, I'll be submitting my first XEmacs patch soon. Thanks Casper> for pointing me in the right direction! You're welcome. Please see item 6 of http://www.xemacs.org/Develop/ before creating your patch. Looking forward to it ... Adrian Casper> - Kvan. -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/