From: Stefan Kangas <stefan@marxist.se>
To: Drew Adams <drew.adams@oracle.com>
Cc: Roland Winkler <winkler@gnu.org>, 21563@debbugs.gnu.org
Subject: bug#21563: 24.5; discourage load-hook variables
Date: Thu, 16 Jan 2020 14:33:19 +0100 [thread overview]
Message-ID: <87tv4vy19c.fsf@marxist.se> (raw)
In-Reply-To: <80b979c0-0fdf-4b84-bf1b-cde0a596f8bb@default> (Drew Adams's message of "Wed, 15 Jan 2020 19:56:09 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> So is the argument now that the existence of load
> hooks makes maintenance too complicated? What will
> be the next argument?
To summarize what has come up in this thread so far, the load-hook
convention has the following problems:
1. They are never called if set by a user after a library is loaded.
2. They can lead to issues like Bug#24491.
3. They require every package (that wants to use them) to add boiler
plate code.
They are also redundant since we have eval-after-load and
with-eval-after-load, which do not have any of the above problems.
Best regards,
Stefan Kangas
next prev parent reply other threads:[~2020-01-16 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 18:57 bug#21563: 24.5; discourage load-hook variables Roland Winkler
2020-01-15 19:32 ` Stefan Kangas
2020-01-15 20:21 ` Drew Adams
2020-01-15 20:42 ` Stefan Kangas
2020-01-16 0:27 ` Roland Winkler
2020-01-15 22:06 ` Glenn Morris
2020-01-16 0:03 ` Stefan Kangas
2020-01-16 0:24 ` Drew Adams
2020-01-16 0:54 ` Stefan Kangas
2020-01-16 3:56 ` Drew Adams
2020-01-16 13:33 ` Stefan Kangas [this message]
2020-01-16 16:15 ` Drew Adams
2020-01-16 20:30 ` Stefan Kangas
2020-01-16 21:08 ` Drew Adams
2020-01-16 0:31 ` Stefan Kangas
2020-04-16 4:14 ` Stefan Kangas
2020-04-16 9:07 ` Roland Winkler
2020-04-26 14:33 ` Stefan Kangas
2020-10-20 17:16 ` Stefan Kangas
2020-01-16 11:49 ` Mauro Aranda
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tv4vy19c.fsf@marxist.se \
--to=stefan@marxist.se \
--cc=21563@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=winkler@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.