From: joseph--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Stefan Monnier" <monnier@iro.umontreal.ca>,
"Eli Zaretskii" <eliz@gnu.org>
Cc: 60346@debbugs.gnu.org
Subject: bug#60346: jka-compre.el.gz "Recursive load"
Date: Fri, 06 Jan 2023 01:23:26 +0000 [thread overview]
Message-ID: <5e76c7f0060cb81ed8f96a8f7a6559c1@breatheoutbreathe.in> (raw)
In-Reply-To: <jwvk02c7tit.fsf-monnier+emacs@gnu.org>
Thank you for your feedback! Yes, this seems like a case of the XY problem. If the problem comes up again for me, I'll ask for helping stepping into byte-compiled functions.
Joseph
December 27, 2022 7:42 AM, "Stefan Monnier" <monnier@iro.umontreal.ca> wrote:
>>> I wanted to ignore byte-compiled files because edebug was refusing to
>>> step into byte-compiled functions.
>
> Ignoring byte-compiled files is definitely not the best solution to
> your problem.
>
>>> I ran the following:
>>>
>>> emacs -Q --eval="(setq load-suffixes '(\".el\"))"
>>>
>>> This broke basic functionality, throwing a "Recursive load" error. For
>>> example, `M-x find-file ~/.emacs.d/init.el` gives:
>>>
>>> VC refresh error: (error "Recursive load"
>>> "/gnu/store/x8nykb09aqmp2j6k74dpgc4jvbk8c2bl-emacs-next-29.0.50-3.22e8a77/share/emacs/29.0.50/lisp/j
>>> a-compr.el.gz"
>
> Loading a compressed file can be done only after we load `jka-compr`
> (since that's the package which implement this feature).
> So clearly, there's a bootstrap problem if that package is
> itself compressed.
>
> Distributions which compress their `.el` files get away with it because
> `jka-compr.elc` isn't compressed, but if you remove `.elc` from
> `load-suffixes` then you reintroduce the circularity. Same thing if you
> move it to after `.el`.
>
> Maybe `gunzip .../jka-compr.el.gz` is all it takes to make it work, tho.
>
>> I'm not sure we want to support this kind of changes in the order or
>> contents of load-suffixes.
>
> It might work when `.el` files aren't compressed.
>
>> It sounds to me like the order is there for as reason, and no part of
>> Emacs expects these lists to be reordered, let alone have some
>> extensions removed from them. I think the only valid changes are
>> adding extensions to the end.
>
> I'm not sure what I'd consider valid or not, but the present use-case
> isn't a good justification to go and try and make that use work.
>
> Stefan
prev parent reply other threads:[~2023-01-06 1:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 21:26 bug#60346: VC refresh error "Recursive load" Joseph Turner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-27 14:05 ` Eli Zaretskii
2022-12-27 15:42 ` bug#60346: jka-compre.el.gz " Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-06 1:23 ` joseph--- 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
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=5e76c7f0060cb81ed8f96a8f7a6559c1@breatheoutbreathe.in \
--to=bug-gnu-emacs@gnu.org \
--cc=60346@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=joseph@breatheoutbreathe.in \
--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).