all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mats Lidell via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rswgnu@gmail.com, 72811@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: Thu, 29 Aug 2024 22:12:16 +0200	[thread overview]
Message-ID: <87v7zj84wv.fsf@lidells.se> (raw)
In-Reply-To: <86h6b3fsj5.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Aug 2024 15:00:14 +0300")

> 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/

%% Mats





  reply	other threads:[~2024-08-29 20:12 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 [this message]
2024-09-14  7:31     ` Eli Zaretskii

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87v7zj84wv.fsf@lidells.se \
    --to=bug-gnu-emacs@gnu.org \
    --cc=72811@debbugs.gnu.org \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.