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 13:17:25 +0200 [thread overview]
Message-ID: <87pmkbdr96.fsf@gnus.org> (raw)
In-Reply-To: <jwvsfp760wg.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 17 May 2022 22:19:45 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Looking up the `load-path` should be of last resort because it's not
> reliable (e.g. when you have foo/bar/comp.elc it's not clear if it's
> emacs-lisp/comp.elc or semantic/wisent/comp.elc).
[...]
> The file name should be absolute for all files except the preloaded
> ones, and those should be relative to `lisp-directory` (because the
> preloaded files are loaded before we know where the Lisp files will be
> available at run-time).
Ah, right. I'll adjust the patch to expand to lisp-directory instead
(although it probably doesn't make any practical difference since this
is only about built-in files indeed).
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-05-18 11:17 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
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 [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=87pmkbdr96.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).