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

[Richard M. Stallman]

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

Why bother the users with it?   jit-lock is the only real option now,
and it's used by default.

    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.

Thanks for noticig that.  I will get rid of those options, and also
make fast-lock-mode and lazy-lock-mode aliases for jit-lock-mode.