From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 51930@debbugs.gnu.org, larsi@gnus.org, drew.adams@oracle.com
Subject: bug#51930: 27.2; Buffer-local functions? Buffers specified buffer-locally?
Date: Wed, 21 Sep 2022 16:05:10 +1200 [thread overview]
Message-ID: <7110e0330e878c144a6364a8e6ad651c@webmail.orcon.net.nz> (raw)
In-Reply-To: <83pmfpv4fs.fsf@gnu.org>
On 2022-09-21 14:36, Eli Zaretskii wrote:
>> From: Phil Sainty <psainty@orcon.net.nz>
>> Functions specified by the buffer-local value are called ...
>> Functions specified by the default value are called ...
>
> Double passive tense? no, thanks.
Well one of those is what's already in the manual.
I personally disagree that the double passive tense is bad here,
but here's another alternative:
-- Variable: window-buffer-change-functions
A list of functions called during redisplay when window buffers
have changed. Each function takes a single argument.
For the buffer-local value, each function is called for any window
showing the corresponding buffer, if that window has been created
or assigned that buffer since the last time window change functions
were run. In this case the window is passed as argument.
For the default value, each function is called for a frame if at
least one window on that frame has been added, deleted or assigned
another buffer since the last time window change functions were
run. In this case the frame is passed as argument.
next prev parent reply other threads:[~2022-09-21 4:05 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
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 [this message]
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=7110e0330e878c144a6364a8e6ad651c@webmail.orcon.net.nz \
--to=psainty@orcon.net.nz \
--cc=51930@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).