GNU bug report logs -
#72811
28.2; global-display-line-numbers-mode with debbugs package cause Lisp nesting exceeds ‘max-lisp-eval-depth’
Previous Next
Reported by: Mats Lidell <mats.lidell <at> lidells.se>
Date: Sun, 25 Aug 2024 22:21:01 UTC
Severity: normal
Found in version 28.2
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
> Cc: Robert Weiner <rswgnu <at> gmail.com>
> Date: Mon, 26 Aug 2024 00:19:16 +0200
> From: Mats Lidell via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>
> With Emacs 27.2 and 28.2 using global-display-line-numbers-mode after fetching a bug with debbugs leads to Lisp nesting exceeds ‘max-lisp-eval-depth’. With Emacs 29.4 or Emacs 30 there is no error.
I guess we already fixed this, so we could close this bug. Still...
> debbugs-gnu-rescan()
> run-hooks(tabulated-list-revert-hook)
> tabulated-list-revert()
> run-hooks(display-line-numbers-mode-hook display-line-numbers-mode-on-hook)
> display-line-numbers-mode()
> display-line-numbers--turn-on()
> global-display-line-numbers-mode()
...can you figure out which Lisp caused display-line-numbers-mode or
display-line-numbers-mode-on-hook to run tabulated-list-revert? I
couldn't find that anywhere in Emacs, and also not in debbugs. I do
see that debbugs-gnu adds to tabulated-list-revert-hook the function
debbugs-gnu-rescan, which then changes the major mode, which causes
display-line-numbers-mode to be turned on again, so what happens after
that is clear: infinite recursion. But I cannot understand why was
tabulated-list-revert called in the first place.
This bug report was last modified 250 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.