From: Tomas Nordin <tomasn@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>,
Stefan Kangas <stefankangas@gmail.com>,
72915@debbugs.gnu.org
Subject: bug#72915: Docstrings of add-hook and remove-hook improvement?
Date: Sun, 15 Sep 2024 13:49:15 +0000 [thread overview]
Message-ID: <87frq1m3hg.fsf@posteo.net> (raw)
In-Reply-To: <jwvr09ldpuo.fsf-monnier+emacs@gnu.org>
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The `add-hook` part was OK for me, indeed.
>
> [ I'm no great fan of that paragraph (neither the original nor the one
> you replace it with), tho, because it's a bit "too detailed" for my
> taste. E.g. the value *always* ends up being a list of functions, and
> the parenthesis states something which sounds to me like it should be
> inferrable from the rest of the docstring. ]
I think I agree, the parenthesized part could be discarded, shortening
the paragraph to
"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."
prev parent reply other threads:[~2024-09-15 13:49 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
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 [this message]
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=87frq1m3hg.fsf@posteo.net \
--to=tomasn@posteo.net \
--cc=72915@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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 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.