From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: "51930@debbugs.gnu.org" <51930@debbugs.gnu.org>
Subject: bug#51930: 27.2; Buffer-local functions? Buffers specified buffer-locally?
Date: Tue, 20 Sep 2022 15:58:25 +0000 [thread overview]
Message-ID: <SJ0PR10MB548895C6693206D88C719E60F34C9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <877d1ycbom.fsf@gnus.org>
> > This is a very dramatic description of a problem ("can't make heads or
> > tails", "I have no idea what is meant", etc.), so I'm not sure whether
> > a simple cross-reference to the documentation of add-hook, which
> > explains what is meant by "buffer-local" in this case, will solve the
> > problem. If it will, doing that is very easy. In fact, I just did.
>
> I think the section is clear after that clarification, so I'm closing
> this bug report.
Nope, it's not clear. The doc of `add-hook' does
not at all talk about buffer-local functions. It
talks about buffer-local hooks and a buffer-local
hook list. A buffer-local function is neither
defined nor described anywhere.
If what is meant is the use of the function on
a hook buffer-locally, then say that. Don't imply
that there's such a thing, defined anywhere, as
a buffer-local function. Or else define it
somewhere.
next prev parent reply other threads:[~2022-09-20 15:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 21:51 bug#51930: 27.2; Buffer-local functions? Buffers specified buffer-locally? Drew Adams
2021-11-18 8:27 ` Eli Zaretskii
2021-11-18 9:42 ` Lars Ingebrigtsen
2021-11-18 11:12 ` Eli Zaretskii
2021-11-18 17:12 ` bug#51930: [External] : " Drew Adams
2022-09-20 15:23 ` Lars Ingebrigtsen
2022-09-20 15:58 ` Drew Adams [this message]
2022-09-20 16:18 ` Eli Zaretskii
2022-09-20 16:37 ` Drew Adams
2022-09-20 16:47 ` Eli Zaretskii
2022-09-20 18:11 ` Drew Adams
2022-09-21 0:13 ` Phil Sainty
2022-09-21 1:27 ` Drew Adams
2022-09-21 2:36 ` Eli Zaretskii
2022-09-21 4:05 ` Phil Sainty
2022-09-21 6:21 ` Stefan Kangas
2022-09-22 3:11 ` Richard Stallman
2022-09-22 6:54 ` 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=SJ0PR10MB548895C6693206D88C719E60F34C9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=51930@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).