From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, 36618@debbugs.gnu.org
Subject: bug#36618: 26.2; Misnamed `*-hooks' variables
Date: Sat, 13 Jul 2019 10:46:12 -0700 (PDT) [thread overview]
Message-ID: <8f219892-9cd8-4742-90d1-6eeff84f4dc6@default> (raw)
In-Reply-To: <<83o91xzvm3.fsf@gnu.org>>
> > A user looking for hooks will fall upon these misleading
> > names of non-hooks using completion (e.g. substring).
>
> Not necessarily: we have a section in the ELisp manual that lists all
> the standard hooks.
A user looking for hooks is not necessarily looking
for _standard_ hooks, and she is not necessarily
looking for coverage of hooks in the manual.
As one simple example, `C-h v' with various types
of completion (substring is one example, but there
are others) can match such non-hook variables.
Similarly, searches.
Hook naming conventions are documented. And hook
names have been improved over the years to better
reflect the conventions. There are a few functions
that mislead by their names. That misleading is
not needed - it doesn't help anything.
next parent reply other threads:[~2019-07-13 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<aed10b21-f313-4fd1-ac95-64d5f2f49451@default>
[not found] ` <<87d0ievxm5.fsf@mouse.gnus.org>
[not found] ` <<2b8f5747-6d20-494a-b727-fdd0b9245299@default>
[not found] ` <<83o91xzvm3.fsf@gnu.org>
2019-07-13 17:46 ` Drew Adams [this message]
2019-07-13 17:50 ` bug#36618: 26.2; Misnamed `*-hooks' variables Eli Zaretskii
2019-07-12 15:16 Drew Adams
2019-07-13 14:05 ` Lars Ingebrigtsen
2019-07-13 17:23 ` Drew Adams
2019-07-13 17:34 ` Eli Zaretskii
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=8f219892-9cd8-4742-90d1-6eeff84f4dc6@default \
--to=drew.adams@oracle.com \
--cc=36618@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).