emacs-pretest-bug
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


From: Jason Rumney
Subject: Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??
Date: Sun, 28 Aug 2005 20:38:11 +0100
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (windows-nt)

"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.
>
> Why bother the users with it?   jit-lock is the only real option now,
> and it's used by default.

I didn't realise it was used by default. I guess I can remove the
font-lock-support-mode setting from my .emacs then (it probably dates
back to when Gerd was still working on it and asked developers to test
it).




reply via email to

[Prev in Thread] Current Thread [Next in Thread]