|
From: | Stefan Monnier |
Subject: | Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error?? |
Date: | Tue, 30 Aug 2005 22:50:47 -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. > Apparently it is not merely inferior--it seems it doesn't work at all. lazy-lock works OK. The OP's problem has to do with some details of how he turns it on. Stefan
[Prev in Thread] | Current Thread | [Next in Thread] |