From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca, npostavs@gmail.com
Subject: Re: "after" variable watchers
Date: Thu, 20 May 2021 16:49:42 +0300 [thread overview]
Message-ID: <83r1i1o6q1.fsf@gnu.org> (raw)
In-Reply-To: <b8fe3388-87bf-e487-300e-316c1418e1f7@gmx.at> (message from martin rudalics on Tue, 18 May 2021 19:01:34 +0200)
> Cc: Eli Zaretskii <eliz@gnu.org>, npostavs@gmail.com, emacs-devel@gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Tue, 18 May 2021 19:01:34 +0200
>
> > What was the problem you encountered when you tried to add:
> >
> > if (<dirty>) window_updeco_window (...);
> >
> > to the getters of the realized values?
>
> There are too many implicit "realized" values to make this work nicely.
> Think of macros like WINDOW_BODY_PIXEL_WIDTH, WINDOW_BOX_LEFT_EDGE_X,
> WINDOW_BOX_RIGHT_EDGE_X, WINDOW_SCROLL_BAR_X or functions like
> window_box_height in addition to the things window_updeco_window sets
> directly.
I don't think I understand this reasoning. Changes in these values
are only visible as result of the next redisplay cycle, no? So in
effect these values "wait" for the next redisplay anyway, right?
> Right. But note that I implicitly call window_updeco_window also
> whenever I change a window's size, for example, from adjust_frame_size
> after a frame got resized.
I think Stefan asks why do we need to do that. Why not wait for when
these values are needed by redisplay, and calculate them only then?
next prev parent reply other threads:[~2021-05-20 13:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 8:27 "after" variable watchers martin rudalics
2021-05-17 10:23 ` Eli Zaretskii
2021-05-17 16:40 ` martin rudalics
2021-05-17 16:57 ` Eli Zaretskii
2021-05-18 15:10 ` martin rudalics
2021-05-20 13:46 ` Eli Zaretskii
2021-05-24 8:47 ` martin rudalics
2021-05-27 16:51 ` Eli Zaretskii
2021-06-06 7:42 ` martin rudalics
2021-05-17 18:36 ` Stefan Monnier
2021-05-17 18:45 ` Eli Zaretskii
2021-05-17 18:54 ` Stefan Monnier
2021-05-17 18:55 ` Stefan Monnier
2021-05-18 15:10 ` martin rudalics
2021-05-18 15:57 ` Stefan Monnier
2021-05-18 17:01 ` martin rudalics
2021-05-20 13:49 ` Eli Zaretskii [this message]
2021-05-24 8:48 ` martin rudalics
2021-05-27 16:53 ` Eli Zaretskii
2021-05-17 14:57 ` Matt Armstrong
2021-05-17 16:41 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83r1i1o6q1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.