From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
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: Wed, 18 May 2022 01:15:47 +0200 [thread overview]
Message-ID: <87pmkbg38c.fsf@gnus.org> (raw)
In-Reply-To: <jwv5ym37od2.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 17 May 2022 19:10:04 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 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?
lisp-directory
=> "/home/larsi/src/emacs/trunk/lisp/"
<Path_to_emacs> up there is probably a misnomer -- it's just the current
directory.
>> 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.
Right. Then perhaps the error is just in:
(apropos-documentation-check-elc-file "simple.elc")
It assumes a full file name, and doesn't look into the load path, which
it could trivially do.
But before I fix that -- is (aref (symbol-function 'kill-current-buffer)
4) supposed to be the full file name or just the leaf name? I imagined
that #$ was supposed to expand to the full file name... The manual just
says
‘#$’
The current file name in byte-compiled files (*note Docs and
Compilation::). This is not meant to be used in Emacs Lisp source
files.
which isn't very precise.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-17 23:15 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
2022-05-17 23:15 ` Lars Ingebrigtsen [this message]
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=87pmkbg38c.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=55492@debbugs.gnu.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).