From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 51930@debbugs.gnu.org
Subject: bug#51930: 27.2; Buffer-local functions? Buffers specified buffer-locally?
Date: Thu, 18 Nov 2021 10:27:10 +0200 [thread overview]
Message-ID: <83o86hyild.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54886AFA7B33CF1E43E2E013F39A9@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Wed, 17 Nov 2021 21:51:29 +0000)
> From: Drew Adams <drew.adams@oracle.com>
> Date: Wed, 17 Nov 2021 21:51:29 +0000
>
> I'm trying to read (elisp) `Window Hooks', and I can't make heads or
> tails of it. Throughout this node there's mention of buffer-local
> functions: "functions specified buffer-locally".
>
> I have no idea what is meant by this. I search the Elisp manual for
> buffer-local, and I find zillions of matches that are about
> buffer-local variables, of course. And I find a couple of mentions
> of buffer-local faces. No mention, that I can find, of buffer-local
> functions or "functions specified buffer-locally". How to specify a
> function buffer-locally?
>
> A wild guess is that what you're trying to say has something to do
> with using the LOCAL argument to `add-hook' or `remove-hook`. But
> if so, it's not clear what.
>
> Please clean up this text so it's comprehensible by an average reader.
> If buffer-local functions are indeed a thing now, please document what
> they are, somewhere.
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.
next prev parent reply other threads:[~2021-11-18 8:27 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 [this message]
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
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=83o86hyild.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51930@debbugs.gnu.org \
--cc=drew.adams@oracle.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 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).