From: Lars Ingebrigtsen <larsi@gnus.org>
To: 53024@debbugs.gnu.org
Cc: monnier@iro.umontreal.ca
Subject: bug#53024: 29.0.50; Wishlist: Byte-compile loaddefs.el?
Date: Sun, 31 Jul 2022 12:47:59 +0200 [thread overview]
Message-ID: <87k07t36e8.fsf@gnus.org> (raw)
In-Reply-To: <87o7x537pd.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 31 Jul 2022 12:19:42 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> So now we just need a way to direct `documentation' to look into the
> correct loaddefs.elc file for the doc string. But... do we know which
> loaddefs file the `autoload' form comes from?
Never mind -- it was just because I'd forgotten to adjust loadup.el to
actually load the .elc file.
So this seems to work well now, as far as I can see, so we can indeed
byte-compile the loaddefs files in the Emacs tree. But not the ones
from packages because of the #$ problem.
next prev parent reply other threads:[~2022-07-31 10:47 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-05 15:53 bug#53024: 29.0.50; Wishlist: Byte-compile loaddefs.el? Lars Ingebrigtsen
2022-01-22 12:27 ` Lars Ingebrigtsen
2022-07-31 10:02 ` Lars Ingebrigtsen
2022-07-31 10:19 ` Lars Ingebrigtsen
2022-07-31 10:47 ` Lars Ingebrigtsen [this message]
2022-07-31 16:35 ` Lars Ingebrigtsen
2022-07-31 17:06 ` Andreas Schwab
2022-08-01 12:33 ` Lars Ingebrigtsen
2022-08-01 13:06 ` Eli Zaretskii
2022-08-02 9:52 ` Lars Ingebrigtsen
2022-08-02 11:17 ` Eli Zaretskii
2022-08-02 11:19 ` Lars Ingebrigtsen
2022-08-03 12:24 ` Lars Ingebrigtsen
2022-08-03 12:41 ` Lars Ingebrigtsen
2022-08-04 6:07 ` Lars Ingebrigtsen
2022-08-04 21:45 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 11:46 ` Lars Ingebrigtsen
2022-08-05 12:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-05 12:22 ` Lars Ingebrigtsen
2022-08-05 13:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-06 12:10 ` Lars Ingebrigtsen
2022-08-04 16:31 ` Andreas Schwab
2022-08-04 16:37 ` Lars Ingebrigtsen
2022-08-04 17:10 ` Eli Zaretskii
2022-08-04 17:14 ` Lars Ingebrigtsen
2022-08-04 17:22 ` Eli Zaretskii
2022-08-05 11:44 ` Lars Ingebrigtsen
2022-08-05 12:57 ` Eli Zaretskii
2022-08-06 12:09 ` Lars Ingebrigtsen
2022-08-06 12:16 ` Eli Zaretskii
2022-08-06 12:20 ` Lars Ingebrigtsen
2022-08-04 18:08 ` Andreas Schwab
2022-08-04 18:11 ` Lars Ingebrigtsen
2022-08-04 19:15 ` Andreas Schwab
2022-08-04 19:20 ` Lars Ingebrigtsen
2022-08-04 20:17 ` Andreas Schwab
2022-08-04 20:31 ` Lars Ingebrigtsen
2022-08-04 20:57 ` Lars Ingebrigtsen
2022-08-05 5:44 ` Eli Zaretskii
2022-08-05 11:51 ` 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=87k07t36e8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=53024@debbugs.gnu.org \
--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).