From: "Jan D." <jan.h.d@swipnet.se>
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 20:00:09 +0100 [thread overview]
Message-ID: <52C9ABB9.3000804@swipnet.se> (raw)
In-Reply-To: <52C9363A.9050008@gmx.at>
Hello.
martin rudalics skrev 2014-01-05 11:38:
> > Steps to reproduce:
> >
> > 1. Build emacs with --without-x-toolkit
> > 2. $ emacs -Q &
> > 3. (set-frame-parameter nil 'internal-border-width 10) C-j
> >
> > Then menubar and toolbar look as if they were cut by the internal
> > border (see the attached screenshot).
> >
> > (We can also see several other garbages in the internal border area,
> > but they had been there even on Emacs 24.3.)
> >
> > This does not happen with Lucid or GTK+ builds.
>
> I can see this here as well. There are many cases when redisplaying a
> frame fails in this way, especially after setting a frame parameter.
> Bug#14222 is another example. When you maximize the frame and
> subsequently restore its previous size the problems usually go away
> (that's what I do in such cases).
>
> What we needed here is some simple switch we can set and which causes
> the redisplay engine to do a through redisplay instead of trying to be
> clever and selectively clear/erase some space formerly occupied by a
> scrollbar, fringe or border
Does not SET_FRAME_GARBAGED do that?
Jan D.
next prev parent reply other threads:[~2014-01-05 19:00 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
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. [this message]
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
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=52C9ABB9.3000804@swipnet.se \
--to=jan.h.d@swipnet.se \
--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 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).