Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??

[Jason Rumney]

Chris Moore wrote:

> Perhaps the creation of jit-lock-mode is what
> obsoleted lazy-lock-mode.
>  
Correct. When variable font support was added, some of the assumptions 
lazy-lock makes about what needs fontifying became invalid. A completely 
different strategy involving hooks into the low level display code was 
needed, so jit-lock was created.