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: [External] : Re: bug#51930: 27.2; Buffer-local functions? Buffers specified buffer-locally?
Date: Thu, 18 Nov 2021 17:12:53 +0000 [thread overview]
Message-ID: <SJ0PR10MB54883989AEC9A097E14183BFF39B9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <875yspls0a.fsf@gnus.org>
> I think "Functions specified buffer-locally" is an unusual way to say
> "the buffer-local value of window-buffer-change-functions"
To put it mildly. And it _doesn't_ say that,
at all. There's no way to legitimately read
it as saying that.
> -- if indeed that's what it's trying to say.
Yes. It's a question any reader will pose:
What is it trying to say?
> I think rewriting this in a less passive voice
> would be a good idea:
>
> ---
> Functions specified buffer-locally
That has the same problem. A reader asks,
What are they trying to say? What does it
mean for a _function_ to be specified
buffer-locally? Means nothing, so far.
next prev parent reply other threads:[~2021-11-18 17:12 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 ` Drew Adams [this message]
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=SJ0PR10MB54883989AEC9A097E14183BFF39B9@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).