From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org, martin rudalics <rudalics@gmx.at>
Cc: psainty@orcon.net.nz, 51930@debbugs.gnu.org, larsi@gnus.org,
drew.adams@oracle.com
Subject: bug#51930: 27.2; Buffer-local functions? Buffers specified buffer-locally?
Date: Thu, 22 Sep 2022 09:54:44 +0300 [thread overview]
Message-ID: <837d1vucej.fsf@gnu.org> (raw)
In-Reply-To: <E1obCcy-0003K7-LR@fencepost.gnu.org> (message from Richard Stallman on Wed, 21 Sep 2022 23:11:52 -0400)
> From: Richard Stallman <rms@gnu.org>
> Cc: eliz@gnu.org, 51930@debbugs.gnu.org, larsi@gnus.org,
> drew.adams@oracle.com
> Date: Wed, 21 Sep 2022 23:11:52 -0400
>
> ======================================================================
> A list of functions for redisplay to call when the assignment of
> buffers to windows has changed. Each function takes a single
> argument.
>
> This variable is peculiar in that its default value has one meaning
> and its actual value (normally buffer-local) has a different meaning.
> Redisplay uses both of these values, each in a different way.
>
> For the actual (buffer-local) value, redisplay calls each function
> once for each window, with the window as argument, if that window has
> been created or assigned that buffer since the last time the window
> change functions were called.
>
> For the default value, redisplay calls each function once for each
> frame, with the frame as argument, if at least one window on that
> frame has been added, deleted or assigned another buffer since the
> last time window change functions were called.
> ======================================================================
>
> However, looking at the doc string of the variable seems to describe
> a different behavior, more like this:
>
> ======================================================================
> A list of functions for redisplay to call when the assignment of
> buffers to windows has changed. Each function takes a single
> argument.
>
> Redisplay examines the global value of this variable, and calls each
> function once for each frame, with the frame as argument, if at least
> one window on that frame has been added, deleted or made to display a
> different buffer since the last time window change functions were
> called.
>
> Redisplay also checks a buffer-local value of this variable in each
> buffer that's currenly displayed in a window. If there is one,
> redisplay calls each function listed there for each window that
> displays the buffer in question, with the window as argument,
> @emph{if} the window has been created, or made to display that buffer,
> since the last time the window change functions were called.
> ======================================================================
>
> Is this correct? I can't tell from the text available.
The manual is more correct: the code goes through windows and invokes
these functions for a window if its buffer has a non-nil buffer-local
value of the variable.
prev parent reply other threads:[~2022-09-22 6:54 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
2022-09-21 6:21 ` Stefan Kangas
2022-09-22 3:11 ` Richard Stallman
2022-09-22 6:54 ` Eli Zaretskii [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
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=837d1vucej.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51930@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.org \
--cc=psainty@orcon.net.nz \
--cc=rms@gnu.org \
--cc=rudalics@gmx.at \
/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).