From: Stefan Kangas <stefankangas@gmail.com>
To: Tomas Nordin <tomasn@posteo.net>, 72915@debbugs.gnu.org
Subject: bug#72915: Docstrings of add-hook and remove-hook improvement?
Date: Sat, 31 Aug 2024 15:35:44 -0700 [thread overview]
Message-ID: <CADwFkm=5A0rCU5kCS4Ro_Le91GwAjL6+8A3EBHvBr-sC1u3POA@mail.gmail.com> (raw)
In-Reply-To: <87v7zgrhrt.fsf@posteo.net>
Tomas Nordin <tomasn@posteo.net> writes:
> diff --git a/lisp/subr.el b/lisp/subr.el
> index 28ba30f584e..e60c4119c60 100644
> --- a/lisp/subr.el
> +++ b/lisp/subr.el
> @@ -2090,6 +2090,10 @@ add-hook
> "Add to the value of HOOK the function FUNCTION.
> FUNCTION is not added if already present.
>
> +HOOK should be a symbol. If HOOK is void, or if HOOK's value is a
> +single function, it is changed to a list of functions (containing only
> +FUNCTION in the void case).
> +
> The place where the function is added depends on the DEPTH
> parameter. DEPTH defaults to 0. By convention, it should be
> a number between -100 and 100 where 100 means that the function
> @@ -2108,10 +2112,6 @@ add-hook
> buffer-local value. That acts as a flag to run the hook
> functions of the global value as well as in the local value.
>
> -HOOK should be a symbol. If HOOK is void, it is first set to
> -nil. If HOOK's value is a single function, it is changed to a
> -list of functions.
> -
> FUNCTION may be any valid function, but it's recommended to use a
> function symbol and not a lambda form. Using a symbol will
> ensure that the function is not re-added if the function is
> @@ -2179,7 +2179,7 @@ remove-hook
> "Remove from the value of HOOK the function FUNCTION.
> HOOK should be a symbol, and FUNCTION may be any valid function. If
> FUNCTION isn't the value of HOOK, or, if FUNCTION doesn't appear in the
> -list of hooks to run in HOOK, then nothing is done. See `add-hook'.
> +list of functions to run in HOOK, then nothing is done. See `add-hook'.
>
> The optional third argument, LOCAL, if non-nil, says to modify
> the hook's buffer-local value rather than its default value.
LGTM.
next prev parent reply other threads:[~2024-08-31 22:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 12:36 bug#72915: Docstrings of add-hook and remove-hook improvement? Tomas Nordin
2024-08-31 22:35 ` Stefan Kangas [this message]
2024-09-01 4:57 ` Eli Zaretskii
2024-09-01 7:15 ` Stefan Kangas
2024-09-01 7:18 ` Stefan Kangas
2024-09-01 14:17 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-01 15:47 ` Tomas Nordin
2024-09-14 13:31 ` Stefan Kangas
2024-09-01 14:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-14 23:24 ` Stefan Kangas
2024-09-15 11:17 ` Tomas Nordin
2024-09-15 13:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-15 13:49 ` Tomas Nordin
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='CADwFkm=5A0rCU5kCS4Ro_Le91GwAjL6+8A3EBHvBr-sC1u3POA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=72915@debbugs.gnu.org \
--cc=tomasn@posteo.net \
/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.