From: Chong Yidong <cyd@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: Geoff Gole <geoffgole@gmail.com>,
Emacs development discussions <emacs-devel@gnu.org>
Subject: Re: xterm.c (x_clear_frame) - commented out call to XClearWindow
Date: Wed, 23 Nov 2011 14:09:27 +0800 [thread overview]
Message-ID: <8739dfid48.fsf@gnu.org> (raw)
In-Reply-To: <FB1031B5-E1ED-49E2-913A-93EAA540AB0A@swipnet.se> ("Jan \=\?utf-8\?Q\?Dj\=C3\=A4rv\=22's\?\= message of "Tue, 22 Nov 2011 07:41:51 +0100")
Jan Djärv <jan.h.d@swipnet.se> writes:
> It would be nice if we could just fix ther leftover spaces. But I
> think it is too long in to pretest to fix this. You have to first
> find all leftover spaces (i.e. under/between scroll bars, minibuffer,
> fringe) in all cases (font size not a multiple of frame size,
> fullscreen, and so on) and in all configurations (lucid, Gtk, just X,
> motif, with or without native scrollbars, with or without Xaw3d
> scrollbars).
AFAICT, we know where the extra spaces are: they're to the right of the
scroll bar, below the echo area, and to the right of the echo area. It
shouldn't be difficult to clear precisely these three areas.
> And then for different environments, some redraw errors only appears
> with XFCE, some with Gnome-shell.
Any idea why? I don't understand why the redisplay engine should behave
differently on different desktop environments. If so, surely we'll have
bigger problems than merely unpainted frame areas.
next prev parent reply other threads:[~2011-11-23 6:09 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
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 [this message]
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
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=8739dfid48.fsf@gnu.org \
--to=cyd@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=geoffgole@gmail.com \
--cc=jan.h.d@swipnet.se \
/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).