From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] master 5c9304e: Disable some display optimizations when frames need redisplay
Date: Mon, 05 Oct 2015 18:46:20 -0400 [thread overview]
Message-ID: <jwv612lueb0.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <83bncdz20p.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 05 Oct 2015 19:57:42 +0300")
>> Fundamentally, the only redisplay flags needed are the window ones.
>> The frame and buffer's redisplay flags could be dispensed with, at the
>> cost of making [bf]set_redisplay more expensive since they'd have to
>> loop through all the windows of that frame/buffer.
> Yes, I agree. But is that justified?
I did not make any measurements, I only went with my intuition.
> At least for the frame's flag, a test for each window of the frame's
> window tree has the same cost as setting the window-specific flag in
> fset_redisplay.
Right. Tho we loop through all the frame's windows in the redisplay
anyway (IOW, I reused pre-existing loops).
> However, the test is made only once per redisplay cycle, whereas the
> setting could be done several times, depending on what Lisp is being
> run. Right?
I think for fset_frame either way would work about as well: it should be
relatively rarely used anyway. OTOH for bset_redisplay, I expect that the
cost of finding all the buffer's windows would be clearly too costly.
Stefan
next prev parent reply other threads:[~2015-10-05 22:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150930193450.11644.62040@vcs.savannah.gnu.org>
[not found] ` <E1ZhN9O-00032Q-5G@vcs.savannah.gnu.org>
2015-10-02 12:44 ` [Emacs-diffs] master 5c9304e: Disable some display optimizations when frames need redisplay Stefan Monnier
2015-10-02 13:40 ` Eli Zaretskii
2015-10-02 15:46 ` Stefan Monnier
2015-10-02 17:49 ` Eli Zaretskii
2015-10-02 20:55 ` Stefan Monnier
2015-10-02 21:24 ` Eli Zaretskii
2015-10-03 1:05 ` Stefan Monnier
2015-10-03 7:21 ` Eli Zaretskii
2015-10-04 2:33 ` Stefan Monnier
2015-10-04 9:53 ` Eli Zaretskii
2015-10-05 15:50 ` Stefan Monnier
2015-10-05 16:57 ` Eli Zaretskii
2015-10-05 22:46 ` Stefan Monnier [this message]
2015-10-06 1:19 ` Stefan Monnier
2015-10-06 7:57 ` martin rudalics
2015-10-06 16:15 ` Stefan Monnier
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=jwv612lueb0.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.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).