From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: wavexx@thregr.org, emacs-devel@gnu.org
Subject: Re: "make autoloads" signals an error
Date: Fri, 03 Jun 2022 08:57:05 +0300 [thread overview]
Message-ID: <834k12e1ce.fsf@gnu.org> (raw)
In-Reply-To: <87y1yebfsv.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 03 Jun 2022 05:13:04 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: wavexx@thregr.org, emacs-devel@gnu.org
> Date: Fri, 03 Jun 2022 05:13:04 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Hm, yes. But... would just prepending the build/lisp/* directories to
> >> load-path fix that issue? I.e., use the .elc files from build/lisp and
> >> fall back on lisp-directory otherwise?
> >
> > How do you prepend it? The setting of load-path is done early during
> > startup, see init_lread.
>
> We'd have to add some facility to Emacs to do so (perhaps via a new
> command line option).
My point was to say it wouldn't be trivial.
> As I said, I'm not sure this is worth doing at all -- but if
> somebody does this, it doesn't sound like it's a major practical
> problem to make this work.
>
> Probably.
I can go with "probably" ;-)
next prev parent reply other threads:[~2022-06-03 5:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 12:10 "make autoloads" signals an error Eli Zaretskii
2022-06-01 12:26 ` Lars Ingebrigtsen
2022-06-01 12:44 ` Eli Zaretskii
2022-06-01 12:46 ` Lars Ingebrigtsen
2022-06-01 12:50 ` Lars Ingebrigtsen
2022-06-01 12:56 ` Lars Ingebrigtsen
2022-06-01 17:51 ` Ergus
2022-06-01 18:21 ` Ergus
2022-06-02 9:16 ` Lars Ingebrigtsen
2022-06-02 10:01 ` Yuri D'Elia
2022-06-02 10:08 ` Lars Ingebrigtsen
2022-06-02 10:48 ` Lars Ingebrigtsen
2022-06-02 10:55 ` Eli Zaretskii
2022-06-02 11:20 ` Lars Ingebrigtsen
2022-06-02 11:53 ` Eli Zaretskii
2022-06-02 11:59 ` Lars Ingebrigtsen
2022-06-02 12:05 ` Eli Zaretskii
2022-06-03 3:13 ` Lars Ingebrigtsen
2022-06-03 5:57 ` Eli Zaretskii [this message]
2022-06-02 12:54 ` Andreas Schwab
2022-06-02 11:55 ` Lars Ingebrigtsen
2022-06-01 13:11 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834k12e1ce.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=wavexx@thregr.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.