From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 39823@debbugs.gnu.org, rms@gnu.org, maxim.cournoyer@gmail.com,
npostavs@gmail.com
Subject: bug#39823: 26.3; update-directory-autoloads regression from Emacs 26 to Emacs 27
Date: Thu, 01 Oct 2020 20:54:07 +0300 [thread overview]
Message-ID: <83blhlhlxc.fsf@gnu.org> (raw)
In-Reply-To: <87h7rdq2wu.fsf@gnus.org> (message from Lars Ingebrigtsen on Thu, 01 Oct 2020 19:20:01 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Thu, 01 Oct 2020 19:20:01 +0200
> Cc: 39823@debbugs.gnu.org, rms@gnu.org, Noam Postavsky <npostavs@gmail.com>
>
> Lars Ingebrigtsen <larsi@gnus.org> writes:
>
> > I think it would make more sense to introduce a new function, say,
> > `make-directory-autoloads' (because it doesn't so much update the
> > autoloads as create an autoload file, I think?) with a sane function
> > signature, and then deprecate update-directory-autoloads (which is only
> > used a handful of place in the Emacs tree).
>
> Man, that was a lot more invasive than I thought, because the
> dynamically bound variable was used all over the place.
>
> But with the following patch
>
> (make-directory-autoloads "~/src/emacs/trunk/lisp/calc" "/tmp/autofoo.el")
>
> works. Emacs builds after applying the patch, and starts, and no tests
> fail.
>
> Does this look OK to everybody?
Before we go and make all these changes, how about considering the
solution I proposed up-thread, i.e. leave this alone? I mean, is it
really worth all this? It's an obscure use case with a very easy
solution/workaround.
But feel free to ignore me.
next prev parent reply other threads:[~2020-10-01 17:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 15:11 bug#39823: 26.3; update-directory-autoloads regression from Emacs 26 to Emacs 27 Maxim Cournoyer
2020-03-13 0:43 ` Noam Postavsky
2020-03-13 8:30 ` Eli Zaretskii
2020-03-14 2:06 ` Maxim Cournoyer
2020-03-13 23:01 ` Michael Heerdegen
2020-03-14 2:03 ` Maxim Cournoyer
2020-03-17 11:48 ` Noam Postavsky
2020-03-14 3:34 ` Richard Stallman
2020-03-17 2:16 ` Maxim Cournoyer
2020-03-19 1:46 ` Richard Stallman
2020-04-08 3:55 ` Maxim Cournoyer
2020-04-08 6:31 ` Eli Zaretskii
2020-04-08 16:41 ` Maxim Cournoyer
2020-04-08 19:09 ` Eli Zaretskii
2020-04-19 3:13 ` Maxim Cournoyer
2020-04-19 12:19 ` Noam Postavsky
2020-06-22 4:10 ` Maxim Cournoyer
2020-06-22 15:07 ` Noam Postavsky
2020-06-23 20:42 ` Maxim Cournoyer
2020-09-30 15:23 ` Lars Ingebrigtsen
2020-10-01 17:20 ` Lars Ingebrigtsen
2020-10-01 17:54 ` Eli Zaretskii [this message]
2020-10-01 18:06 ` Lars Ingebrigtsen
2020-10-02 2:36 ` Lars Ingebrigtsen
2020-10-02 17:54 ` Maxim Cournoyer
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=83blhlhlxc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39823@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=maxim.cournoyer@gmail.com \
--cc=npostavs@gmail.com \
--cc=rms@gnu.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).