all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kevin Layer via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 55177@debbugs.gnu.org
Subject: bug#55177: 28.1; run-mode-hooks recursion in 28.1, not in 27.2
Date: Fri, 29 Apr 2022 07:48:29 -0700	[thread overview]
Message-ID: <27273.1651243709@gremlin.franz.com> (raw)
In-Reply-To: <874k2ci50d.fsf@gnus.org>

Lars Ingebrigtsen wrote:

>> Kevin Layer <layer@franz.com> writes:
>> 
>> > My method of building is in a docker container from a .tar.xz file.
>> > Can you tell me how to generate that from the emacs-28 branch?  I will
>> > be happy to test it tomorrow.
>> 
>> Sorry, don't know anything about docker.

No worries, seems moot now.  Also, now I know how to download a tar.gz
of a branch HEAD.

>> But I've now tested your test case, and I can reproduce the problem in
>> Emacs 28.1 (we enter an infinite loop), but not on the emacs-28 branch,
>> so this has been fixed for Emacs 28.2.

Thanks.

I want to point out that this is a workaround for 28.1, replacing the
defun for common-lisp-mode with this:

(defalias 'common-lisp-mode 'fi:common-lisp-mode)

That seems like the better way to do it anyway.

Thanks everyone.







      reply	other threads:[~2022-04-29 14:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-28 20:41 bug#55177: 28.1; run-mode-hooks recursion in 28.1, not in 27.2 Kevin Layer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-28 23:02 ` Lars Ingebrigtsen
2022-04-29  0:29   ` Kevin Layer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-29  6:31     ` Eli Zaretskii
2022-04-29  6:44     ` Eli Zaretskii
2022-04-29 10:00     ` Lars Ingebrigtsen
2022-04-29 14:48       ` Kevin Layer via Bug reports for GNU Emacs, the Swiss army knife of text editors [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

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

  git send-email \
    --in-reply-to=27273.1651243709@gremlin.franz.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=55177@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=layer@franz.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.