From: Stefan Monnier 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: 55492@debbugs.gnu.org, "Daniel Martín" <mardani29@yahoo.es>
Subject: bug#55492: 29.0.50; apropos-documentation with universal argument shows an error
Date: Tue, 17 May 2022 19:10:04 -0400 [thread overview]
Message-ID: <jwv5ym37od2.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87tu9ng3yg.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 18 May 2022 01:00:07 +0200")
Lars Ingebrigtsen [2022-05-18 01:00:07] wrote:
> Daniel Martín via "Bug reports for GNU Emacs, the Swiss army knife of
> text editors" <bug-gnu-emacs@gnu.org> writes:
>> emacs -Q
>> C-u C-h d window RET
>>
>> Actual result:
>>
>> An error is shown:
>>
>> apropos-documentation-check-elc-file: Opening input file: No such file
>> or directory, <Path_to_emacs>/simple.elc
>
> I see the same if I start Emacs now, and the root cause is
>
> (apropos-safe-documentation 'kill-current-buffer)
>
> which again is because of this
>
> (aref (symbol-function 'kill-current-buffer) 4)
> => ("simple.elc" . 202401)
What is the value of `lisp-directory` when you get that error?
What is the actual "<Path_to_emacs>" printed above?
Where should Emacs find the `simple.elc` file instead?
> Now, in my Emacs that's been running for a few hours, I instead get:
>
> (aref (symbol-function 'kill-current-buffer) 4)
> => ("/home/larsi/src/emacs/trunk/lisp/simple.elc" . 202401)
I suspect that this is because the `simple.elc` was reloaded for some
reason, which happens to hide the problem.
> I think Stefan changed the format of byte compiled functions a while
> ago? Or do I misremember? Anyway, added to the CCs.
Not really, no, but the docstrings of preloaded packages (like
`simple.el`) used to be (stored in and) fetched from `etc/DOC` and is
now fetched from the elc files instead.
The relevant change (and hence likely culprit here) is
59732a83c8875c8986d2221600d559a24d8309cc
Stefan
next prev parent reply other threads:[~2022-05-17 23:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m1tu9nztpn.fsf.ref@yahoo.es>
2022-05-17 22:21 ` bug#55492: 29.0.50; apropos-documentation with universal argument shows an error Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-17 23:00 ` Lars Ingebrigtsen
2022-05-17 23:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-05-17 23:15 ` Lars Ingebrigtsen
2022-05-17 23:23 ` Lars Ingebrigtsen
2022-05-18 8:50 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-18 2:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-18 11:17 ` Lars Ingebrigtsen
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=jwv5ym37od2.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=55492@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mardani29@yahoo.es \
--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).