unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Eli Zaretskii <eliz@gnu.org>
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 17:48:59 +0100	[thread overview]
Message-ID: <52C98CFB.4020809@gmx.at> (raw)
In-Reply-To: <83wqietmef.fsf@gnu.org>

 >> 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.
 >
 > I believe what you want is to reset the enabled_p flag of each glyph
 > row in the current glyph matrix.  But since each window in a GUI
 > session has its own glyph matrix, you will need to do that for every
 > window on the current frame.
 >
 > (Maybe there's a variable that has the same effect, I didn't check.)

I'm not sure whether that would suffice.  Currently emacs does all sorts
of erasing and redrawing backgrounds of scrollbars, fringes, borders and
the like.  In many cases, it doesn't get that right.  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.

martin





  reply	other threads:[~2014-01-05 16:48 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 [this message]
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.
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=52C98CFB.4020809@gmx.at \
    --to=rudalics@gmx.at \
    --cc=16348@debbugs.gnu.org \
    --cc=eliz@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).