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.

> It might be more useful to print a message. Something like
> "lazy-lock is obsolete since Emacs 21. jit-lock is the recommended
> replacement. See `font-lock-support-mode' for more info, including how
> to enable lazy-lock if you really want to continue using it."

Calling turn-on-lazy-lock *should* already display a message about
lazy-lock.el being obsolete.  This message is displayed any time a file is
loaded from the obsolete subdirectory.
Of course maybe the message flashes by without being noticed.


        Stefan