From: Drew Adams <drew.adams@oracle.com>
To: 25794@debbugs.gnu.org
Subject: bug#25794: 24.5; Doc of `Info-selection-hook'
Date: Sun, 19 Feb 2017 09:28:27 -0800 (PST) [thread overview]
Message-ID: <ec257273-f5f6-474f-9006-7fb5c929cfc3@default> (raw)
This is a hook: a variable used by users to automatically invoke
functions when something happens.
Sure, it's true that "when something happens" means, more precisely, at
certain places in the implementation (code). But a hook is a user-level
thing, and hooks should be, first of all, presented to users as such.
Their descriptions should make clear to users when they are used.
That's not really the case for `Info-selection-hook', IMO. Why?
Because users do not know what "when `Info-select-node' is called"
means. They know nothing about non-interactive function
`Info-select-node'.
(Also, the doc string says "Hooks run" - that should be singular.)
`Info-select-node' is an implementation detail. It is not at all clear
to users when that function gets called. The doc for the hook should,
first of all, say when the hook is run in terms of user-observable and
user-understandable behavior. It is fine to ALSO then say something
like "More precisely, the hook is run when `Info-select-node' is called."
That can perhaps help users who consult the code to know better what the
behavior is.
In user-level terms, when is this hook run? Perhaps just say that it is
run whenever an Info node (or page) is visited. Yes, it applies also to
reversion and other revisits of a node, and it applies also to visiting
a TOC, which is not really a node. Still, visiting a node is the best
thing I can think of that describes the behavior to users. Perhaps you
have a better idea?
I think, too, that it would be OK to say that the hook runs _after_ a
node is visited or near the end of visiting a node.
But please say something that is more helpful than just "Hooks run when
`Info-select-node' is called."
In GNU Emacs 24.5.1 (i686-pc-mingw32)
of 2015-04-11 on LEG570
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/usr --host=i686-pc-mingw32'
next reply other threads:[~2017-02-19 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 17:28 Drew Adams [this message]
2017-02-25 8:53 ` bug#25794: 24.5; Doc of `Info-selection-hook' 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=ec257273-f5f6-474f-9006-7fb5c929cfc3@default \
--to=drew.adams@oracle.com \
--cc=25794@debbugs.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).