> Well, I've taken the time and have succeeded:
> The following reproducibly produces the bug
>
> emacs-22.0.50 -q -l emacs-22.0-bug.el &
>
> where I've attached the emacs-22.0-bug.el file (in text/plain)
I can confirm that I see an error with that file. And here's a
command line that needs no external .el file to show the bug:
emacs -Q --eval="
(progn (setq debug-on-error t)
(add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
(global-font-lock-mode t))"
The infinite recursion looks like this in the debugger:
Debugger entered--Lisp error: (error "Lisp nesting exceeds
`max-lisp-eval-depth'")
lazy-lock-mode(t)
turn-on-lazy-lock()
run-hooks(font-lock-mode-hook font-lock-mode-off-hook)
font-lock-mode(t)
lazy-lock-mode(t)
turn-on-lazy-lock()
run-hooks(font-lock-mode-hook font-lock-mode-off-hook)
One thing I noticed is that lazy-lock.el is in .../lisp/obsolete/ -
perhaps you're not supposed to use lazy-lock any more, although
font-lock.el still mentions lazy-lock-mode in several places.
I believe the 'proper' way of using lazy-lock is to:
(setq font-lock-support-mode 'lazy-lock-mode)
See the documentation for font-lock-support-mode for more information.
The default value of font-lock-support-mode is 'jit-lock-mode and
works very well for me. Perhaps the creation of jit-lock-mode is what
obsoleted lazy-lock-mode.
Chris.
_______________________________________________
Emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
