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

[Jason Rumney]

"Richard M. Stallman" <address@hidden> writes:

> 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."

We should probably also change the doc string for
font-lock-support-mode. Currently it lists fast-lock-mode,
lazy-lock-mode and jit-lock-mode in that order, with no mention of any
being obsolete.