all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@gnu.org>
To: Geoff Gole <geoffgole@gmail.com>
Cc: Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: xterm.c (x_clear_frame) - commented out call to XClearWindow
Date: Mon, 21 Nov 2011 16:54:00 +0800	[thread overview]
Message-ID: <87d3cldffb.fsf@gnu.org> (raw)
In-Reply-To: <CALhHxSWrZNnMrs7HwnnLYdRBuF14_iLkqOEvaEXhoVM3VhC-qQ@mail.gmail.com> (Geoff Gole's message of "Mon, 21 Nov 2011 15:19:57 +0800")

Geoff Gole <geoffgole@gmail.com> writes:

> Let me amend my reproduction recipe a bit. I usually run emacs under a
> tiling window manager which fullscreens everything by default, making
> it easy to see the stale pixels. Under a more normal window manager I
> have to do something like
>
>   emacs -Q
>   maximize the emacs
>   M-: (set-background-color "red")

OK, I see the problem now; thanks.  I guess your proposed fix is an OK
band-aid.  A more correct fix would be to make sure that the echo area
is painted properly when drawing glyph strings, i.e. all the way to the
bottom of the frame.  But that may not be a straightforward change.

The problem doesn't stop there, though: depending on the screen width,
there's a similar unpainted space to the right of the GTK scroll bar,
and another in the echo area where the scroll bar normally appears.



  reply	other threads:[~2011-11-21  8:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19  2:09 xterm.c (x_clear_frame) - commented out call to XClearWindow Geoff Gole
2011-11-21  5:15 ` Chong Yidong
2011-11-21  7:19   ` Geoff Gole
2011-11-21  8:54     ` Chong Yidong [this message]
2011-11-21 11:36       ` Geoff Gole
2011-11-21 18:02         ` Jan Djärv
2011-11-22  2:38           ` Geoff Gole
2011-11-22  5:31           ` Chong Yidong
2011-11-22  6:41             ` Jan Djärv
2011-11-22 15:37               ` Stefan Monnier
2011-11-23  6:09               ` Chong Yidong
2011-11-29 18:13                 ` Jan Djärv

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=87d3cldffb.fsf@gnu.org \
    --to=cyd@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=geoffgole@gmail.com \
    /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.