From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 52400@debbugs.gnu.org
Subject: bug#52400: [PATCH] Don't generate separate autoload file for htmlfontify.el
Date: Fri, 10 Dec 2021 15:37:19 +0200 [thread overview]
Message-ID: <83mtl8shrk.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=fVu3gaXh_ykFEWypDMdAu-nSR+uOibXgSo1BM0tKV8Q@mail.gmail.com> (message from Stefan Kangas on Fri, 10 Dec 2021 13:32:51 +0000)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Fri, 10 Dec 2021 13:32:51 +0000
> Cc: 52400@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I wouldn't touch these issues with a 3-mile pole. They are fragile,
> > and once they work, having an extra file with 3 definitions is a price
> > I take every day. It just isn't worth the effort to awaken these
> > sleeping dogs.
>
> What are the risks in a case like this?
That the build breaks. Two possible variants of breakage:
. the autoloads aren't updated when they should be
. the rule for updating the autoloads is executedevery time you say
"make", even if there was no change anywhere in Emacs
> It seems to me that they are low, in the sense that if we run into
> any problems we can just revert it and live happily ever after.
I say why take the risks, however low, if the problem is not serious
enough?
> The main benefit for me is just a general reduction of complexity, but
> admittedly it is small.
Exactly.
next prev parent reply other threads:[~2021-12-10 13:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 2:07 bug#52400: [PATCH] Don't generate separate autoload file for htmlfontify.el Stefan Kangas
2021-12-10 8:42 ` Eli Zaretskii
2021-12-10 13:32 ` Stefan Kangas
2021-12-10 13:37 ` Eli Zaretskii [this message]
2021-12-10 15:22 ` Stefan Kangas
2021-12-10 16:46 ` Eli Zaretskii
2021-12-10 19:45 ` Stefan Kangas
2022-06-05 16:24 ` 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=83mtl8shrk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52400@debbugs.gnu.org \
--cc=stefan@marxist.se \
/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).