From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: larsi@gnus.org, 25581@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#25581: 25.1; Incorrect statement in (elisp) `Hooks'
Date: Wed, 26 Aug 2020 11:27:53 -0700 (PDT) [thread overview]
Message-ID: <88261d86-ec91-474a-bcf4-a0be9d80375b@default> (raw)
In-Reply-To: <E1kAka0-0008SS-Sz@fencepost.gnu.org>
> > Some vars are _intended_ to
> > have a value that can be a single function or a list of
> > functions. Some of the latter kind of variables are
> > hooks. (Maybe _all_ of the latter can be treated as
> > hooks; maybe not.)
>
> We could conceivably start a long, slow process of giving them
> new names, and converting them into enitrely regular normal hooks.
Yes. And then (or even before then), we should
update the doc to say that in the past _______ was
allowed. This, to point out that there can be code
out there in the wild that still expects that.
next prev parent reply other threads:[~2020-08-26 18:27 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 16:51 bug#25581: 25.1; Incorrect statement in (elisp) `Hooks' Drew Adams
2017-01-31 3:05 ` npostavs
2017-01-31 3:36 ` Mark Oteiza
2017-01-31 4:06 ` Drew Adams
2017-01-31 3:55 ` Drew Adams
2017-01-31 4:16 ` npostavs
2017-01-31 16:02 ` Drew Adams
2017-02-01 3:35 ` npostavs
2017-02-01 17:01 ` Drew Adams
2017-02-04 21:00 ` npostavs
2017-02-05 2:11 ` Drew Adams
2017-02-10 1:42 ` npostavs
2017-02-10 3:00 ` Drew Adams
2020-10-11 2:26 ` Lars Ingebrigtsen
2020-10-11 14:12 ` Drew Adams
2020-08-24 15:22 ` Lars Ingebrigtsen
2020-08-24 15:54 ` Stefan Kangas
2020-08-24 15:58 ` Lars Ingebrigtsen
2020-08-24 16:20 ` Drew Adams
2020-08-24 16:13 ` Drew Adams
2020-08-24 16:18 ` Drew Adams
2020-08-26 1:50 ` Richard Stallman
2020-08-26 18:27 ` Drew Adams [this message]
2020-08-24 16:01 ` Drew Adams
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=88261d86-ec91-474a-bcf4-a0be9d80375b@default \
--to=drew.adams@oracle.com \
--cc=25581@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
--cc=stefankangas@gmail.com \
/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).