From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: Reworking loaddefs.el generation
Date: Fri, 27 May 2022 14:17:37 +0200 [thread overview]
Message-ID: <87fskv6ufy.fsf@gnus.org> (raw)
In-Reply-To: <87tu9b9o90.fsf@igel.home> (Andreas Schwab's message of "Fri, 27 May 2022 14:03:07 +0200")
Andreas Schwab <schwab@linux-m68k.org> writes:
>> $ touch lisp/mh-e/mh-e.el
>> $ make
>>
>> The lisp/mh-e/mh-loaddefs.el is not regenerated.
>
> make -C lisp mh-autoloads
But that will make the rule run always (that is, until the
mh-loaddefs.el file gets updated because new autoloads have actually
arrived).
If that's the intention, then I guess I understood the rule -- it's just
very well implemented, which I kinda suspected.
In any case, in the new implementation, I've removed those rules --
"make loaddefs.el" will regenerate all these loaddefs files.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-05-27 12:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:53 Reworking loaddefs.el generation Lars Ingebrigtsen
2022-05-27 12:03 ` Andreas Schwab
2022-05-27 12:17 ` Lars Ingebrigtsen [this message]
2022-05-27 12:43 ` Stefan Monnier
2022-05-27 13:00 ` Lars Ingebrigtsen
2022-05-31 16:10 ` Lars Ingebrigtsen
2022-05-31 16:33 ` Lars Ingebrigtsen
2022-05-31 16:53 ` Lars Ingebrigtsen
2022-05-31 17:32 ` Eli Zaretskii
2022-05-31 17:40 ` Lars Ingebrigtsen
2022-05-31 18:09 ` Lars Ingebrigtsen
2022-05-31 19:24 ` Eli Zaretskii
2022-05-31 19:33 ` Lars Ingebrigtsen
2022-06-01 2:26 ` Eli Zaretskii
2022-06-01 2:29 ` Lars Ingebrigtsen
2022-06-01 11:40 ` Eli Zaretskii
2022-06-01 12:13 ` Lars Ingebrigtsen
2022-06-01 19:02 ` Eli Zaretskii
2022-06-02 9:14 ` Lars Ingebrigtsen
2022-05-31 18:44 ` Alan Mackenzie
2022-05-31 18:47 ` Lars Ingebrigtsen
2022-06-01 3:55 ` Lars Ingebrigtsen
2022-06-01 5:43 ` Lars Ingebrigtsen
2022-06-01 11:16 ` Lars Ingebrigtsen
2022-06-01 11:26 ` Lars Ingebrigtsen
2022-06-01 12:00 ` Andreas Schwab
2022-06-01 12:10 ` Lars Ingebrigtsen
2022-06-01 14:23 ` Lars Ingebrigtsen
2022-06-01 11:47 ` Stefan Monnier
2022-06-01 12:09 ` Lars Ingebrigtsen
2022-05-31 19:04 ` Stefan Monnier
2022-06-01 5:13 ` Lars Ingebrigtsen
2022-06-01 11:07 ` Eli Zaretskii
2022-06-01 12:29 ` Lars Ingebrigtsen
2022-05-31 19:00 ` Lars Ingebrigtsen
2022-05-31 19:12 ` 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=87fskv6ufy.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=schwab@linux-m68k.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 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).