From: Eli Zaretskii <eliz@gnu.org>
To: Mats Lidell <mats.lidell@lidells.se>
Cc: rswgnu@gmail.com, 72811-done@debbugs.gnu.org
Subject: bug#72811: 28.2; global-display-line-numbers-mode with debbugs package cause Lisp nesting exceeds ‘max-lisp-eval-depth’
Date: Sat, 14 Sep 2024 10:31:00 +0300 [thread overview]
Message-ID: <86ldzuite3.fsf@gnu.org> (raw)
In-Reply-To: <87v7zj84wv.fsf@lidells.se> (message from Mats Lidell on Thu, 29 Aug 2024 22:12:16 +0200)
> From: Mats Lidell <mats.lidell@lidells.se>
> Cc: 72811@debbugs.gnu.org, rswgnu@gmail.com
> Date: Thu, 29 Aug 2024 22:12:16 +0200
>
> > Eli Zaretskii writes:
> > I guess we already fixed this, so we could close this bug. Still...
>
> Yes. But I was curious since I could not find any commit in Emacs that looked
> related to fixing this.
>
> > ...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.
>
> I could not either so I filed the bug report. ;-) And hoped someone could
> figure it out. \o/
No further comments, so I'm closing this bug.
prev parent reply other threads:[~2024-09-14 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-25 22:19 bug#72811: 28.2; global-display-line-numbers-mode with debbugs package cause Lisp nesting exceeds ‘max-lisp-eval-depth’ Mats Lidell via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-29 12:00 ` Eli Zaretskii
2024-08-29 20:12 ` Mats Lidell via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 7:31 ` Eli Zaretskii [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ldzuite3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72811-done@debbugs.gnu.org \
--cc=mats.lidell@lidells.se \
--cc=rswgnu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).