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

[Stefan Monnier]

>> Since lazy-lock is now obsolete, perhaps we should simply redefine
>> turn-on-lazy-lock as a no-op, so that it won't do any harm.

>     I think that making such a change on the basis that lazy-lock is
>     obsolete is a bad idea.

> Apparently it is not merely inferior--it seems it doesn't work at all.

lazy-lock works OK.  The OP's problem has to do with some details of how he
turns it on.


        Stefan