From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 16348@debbugs.gnu.org
Subject: bug#16348: 24.3.50; Increasing internal-border-width cuts menubar and toolbar on non-toolkit builds
Date: Sun, 05 Jan 2014 19:07:30 +0200 [thread overview]
Message-ID: <83r48mtl0t.fsf@gnu.org> (raw)
In-Reply-To: <52C98CFB.4020809@gmx.at>
> Date: Sun, 05 Jan 2014 17:48:59 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: mituharu@math.s.chiba-u.ac.jp, 16348@debbugs.gnu.org
>
> The only practical solution I usually see is to resize the frame to
> some other size and size it back. I doubt that this is the same as
> resetting the enabled_p flags.
What do you think it does, in addition? It reallocates the glyph
matrices to fit the new dimensions, which clears that flag.
Anyway, I'm not aware of any mechanism in the display engine to avoid
redrawing portions of the screen, except the one that compares glyph
rows. All the other redisplay optimizations are suppressed by setting
windows_or_buffers_changed, and I imagine you already do that.
If I'm wrong, can you point to the code that avoids redrawing those
parts?
next prev parent reply other threads:[~2014-01-05 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 5:34 bug#16348: 24.3.50; Increasing internal-border-width cuts menubar and toolbar on non-toolkit builds YAMAMOTO Mitsuharu
2014-01-05 10:38 ` martin rudalics
2014-01-05 16:37 ` Eli Zaretskii
2014-01-05 16:48 ` martin rudalics
2014-01-05 17:07 ` Eli Zaretskii [this message]
2014-01-05 17:59 ` martin rudalics
2014-01-05 18:08 ` Eli Zaretskii
2014-01-05 18:38 ` martin rudalics
2014-01-05 19:22 ` Eli Zaretskii
2014-01-05 20:04 ` Eli Zaretskii
2014-01-05 19:00 ` Jan D.
2014-01-11 10:24 ` martin rudalics
2014-01-11 11:11 ` Jan Djärv
2014-01-11 14:00 ` martin rudalics
2014-01-13 1:20 ` YAMAMOTO Mitsuharu
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=83r48mtl0t.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=16348@debbugs.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 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.