From: Eli Zaretskii <eliz@gnu.org>
To: German Pacenza <germanp82@hotmail.com>,
Andrea Corallo <acorallo@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 64494@debbugs.gnu.org
Subject: bug#64494: 30.0.50; Recursive load error with native-compile
Date: Thu, 06 Jul 2023 18:09:47 +0300 [thread overview]
Message-ID: <83ttuhgjpg.fsf@gnu.org> (raw)
In-Reply-To: <DM5PR2201MB1161EF3E42C4A2CB6CB5AEBAA72CA@DM5PR2201MB1161.namprd22.prod.outlook.com> (message from German Pacenza on Thu, 06 Jul 2023 08:45:10 -0300)
> From: German Pacenza <germanp82@hotmail.com>
> Date: Thu, 06 Jul 2023 08:45:10 -0300
>
>
> Steps to reproduce:
> clean native compile cache
> emacs -Q
> C-x r b (bookmark-jump)
>
> Error message appears:
> emacs-lisp-compilation-mode: Recursive load: "/home/german/repos/emacs/lisp/progmodes/compile.elc", "/home/german/repos/emacs/lisp/emacs-lisp/ring.elc", "/home/german/repos/emacs/lisp/comint.elc", "/home/german/repos/emacs/lisp/progmodes/compile.elc", "/home/german/repos/emacs/lisp/emacs-lisp/ring.elc", "/home/german/repos/emacs/lisp/comint.elc", "/home/german/repos/emacs/lisp/progmodes/compile.elc", "/home/german/repos/emacs/lisp/emacs-lisp/ring.elc", "/home/german/repos/emacs/lisp/comint.elc", "/home/german/repos/emacs/lisp/progmodes/compile.elc", "/home/german/repos/emacs/lisp/emacs-lisp/ring.elc", "/home/german/repos/emacs/lisp/comint.elc", "/home/german/repos/emacs/lisp/progmodes/compile.elc", "/home/german/repos/emacs/lisp/emacs-lisp/cl-lib.elc", "/home/german/repos/emacs/lisp/emac
s-lisp/pp.elc", "/home/german/repos/emacs/lisp/bookmark.elc"
>
> Reverting commit 40492581f96626e405e4b453456b8c9b83822c97 fixes the issue.
Thanks, I've reverted that commit for now.
Andrea, Stefan: any ideas for how to allow emacs-lisp-compilation-mode
in async compilation buffers without triggering this recursive-load
nastiness?
next prev parent reply other threads:[~2023-07-06 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 11:45 bug#64494: 30.0.50; Recursive load error with native-compile German Pacenza
2023-07-06 15:09 ` Eli Zaretskii [this message]
2023-07-07 17:02 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-07 18:23 ` Eli Zaretskii
2023-07-07 20:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-08 1:22 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-14 1:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=83ttuhgjpg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64494@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=germanp82@hotmail.com \
--cc=monnier@iro.umontreal.ca \
/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).