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

[Martin Maechler]

>>>>> "Jason" == Jason Rumney <address@hidden>
>>>>>     on Sun, 28 Aug 2005 20:45:09 +0100 writes:

    Jason> "Richard M. Stallman" <address@hidden> writes:
    >> 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.

    Jason> If we do that, we might as well delete lazy-lock.el
    Jason> and fast-lock.el rather than leave them in obsolete.

Yes, or rather leave a stub ?

Remember that I started this thread because our local (pretty long and
involved) default.el somewhere had

        (autoload 'turn-on-lazy-lock "lazy-lock")
        (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)

which lead to an infinite loop.
As a user, I'd like to get a decent error message {``lazy-lock
is past; please use jit-lock-mode ...''} from the
above - which is perfectly working in 21.4 - not just an error 
because "lazy-lock" is n't found anymore.