From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52400@debbugs.gnu.org
Subject: bug#52400: [PATCH] Don't generate separate autoload file for htmlfontify.el
Date: Fri, 10 Dec 2021 15:22:12 +0000 [thread overview]
Message-ID: <CADwFkm=dZ7TNVCQAn6w5s0BwGDYjhoHRTqKM50t7OVCV9_y3FA@mail.gmail.com> (raw)
In-Reply-To: <83mtl8shrk.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Dec 2021 15:37:19 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> 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
FWIW, I didn't see any of those issues in my testing.
> I say why take the risks, however low, if the problem is not serious
> enough?
Cruft inevitably adds to cognitive load. A lot of it adds more, little
adds little. We have a lot of it, IMO, so every little bit helps.
The problem is that if it exists, you will sometimes happen to look at
it and think "hmm, why is this file here". I think this is the second
(or third?) time I stumble upon this particular file.
next prev parent reply other threads:[~2021-12-10 15:22 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
2021-12-10 15:22 ` Stefan Kangas [this message]
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='CADwFkm=dZ7TNVCQAn6w5s0BwGDYjhoHRTqKM50t7OVCV9_y3FA@mail.gmail.com' \
--to=stefan@marxist.se \
--cc=52400@debbugs.gnu.org \
--cc=eliz@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).