[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??
From: |
Stefan Monnier |
Subject: |
Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error?? |
Date: |
Mon, 29 Aug 2005 10:05:38 -0400 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
> 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.
I think that making such a change on the basis that lazy-lock is obsolete is
a bad idea.
OTOH, I agree with this change because turn-on-lazy-lock is obsolete: the
user should use font-lock-support-mode instead.
Stefan
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, (continued)
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Kim F. Storm, 2005/08/29
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Richard M. Stallman, 2005/08/30
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Stefan Monnier, 2005/08/29
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Richard M. Stallman, 2005/08/30
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Jason Rumney, 2005/08/28
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Stefan Monnier, 2005/08/29
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??,
Stefan Monnier <=
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Richard M. Stallman, 2005/08/30
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Stefan Monnier, 2005/08/30
- Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??, Martin Maechler, 2005/08/31