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 19:45:35 +0000 [thread overview]
Message-ID: <CADwFkmm7=ZCi0+qpkZeWTUp-kP=LGZgZzAFvCWYfqGwHqmx6cA@mail.gmail.com> (raw)
In-Reply-To: <83fsr0s8zu.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 10 Dec 2021 18:46:45 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> But it isn't cruft. You tend to declare something "cruft" too easily.
This file is the result of an old optimization (some autoloads) that
were subsequently cleaned up. (The non-optimized version would have
been to just require hfy-cmap.el.) However, the clean-up didn't go far
enough, and thus we ended up with a file that I think can be accurately
described as cruft.
> No, we don't. Please don't consider cruft anything that you think is
> not right; there's more than one way to skin a fish. People who
> worked on Emacs before us weren't exactly incompetent, you know.
I don't think saying that some things have outgrown their usefulness or
could be done better reflects negatively on previous authors.
> Just get used to it being there, I say. It doesn't do any harm,
> although you seem to think it does.
The "harm" here is exactly having to get used to it. IOW, you may argue
that this is a very minor cleanup, but on the other hand the cost of
doing nothing is also non-zero. Hackers will have to look at this for
another couple of decades, or until someone else thinks to install a
patch like the one I wrote.
However, since you seem to feel strongly about it, I won't insist.
next prev parent reply other threads:[~2021-12-10 19:45 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
2021-12-10 16:46 ` Eli Zaretskii
2021-12-10 19:45 ` Stefan Kangas [this message]
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='CADwFkmm7=ZCi0+qpkZeWTUp-kP=LGZgZzAFvCWYfqGwHqmx6cA@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).