From: Eli Zaretskii <eliz@gnu.org>
To: Yuan MEI <yuan.mei.list@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Redisplay issue
Date: Sat, 28 Nov 2015 22:49:07 +0200 [thread overview]
Message-ID: <83y4dhonng.fsf@gnu.org> (raw)
In-Reply-To: <CANGGyWaa14d1p5r5E-Q61xGoAKc5GByceTVjq0cy1K1-tv_qWg@mail.gmail.com>
> Date: Sat, 28 Nov 2015 12:19:31 -0800
> From: Yuan MEI <yuan.mei.list@gmail.com>
> Cc: emacs-devel <emacs-devel@gnu.org>
>
> > Then please see if the scenario in which this happens causes the
> > expose events to be delivered to Emacs by X. If they are, the
> > function expose_frame should be called, and it should perform the
> > necessary redisplay. If these events are not reported, Emacs has no
> > way of knowing that its frame(s) need to be redrawn.
> >
> > Thanks.
>
> It seems the expose event is sent to Emacs and Emacs does respond to
> it. However the response is not redrawing the entire frame but
> redrawing part of it. And it looks that some parts that should be
> redrawn is not. Any suggestions?
Can you see if the coordinates of the exposed region, as reported to
Emacs, correspond to what is in fact exposed?
next prev parent reply other threads:[~2015-11-28 20:49 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 22:31 Redisplay issue Yuan MEI
2015-11-28 8:06 ` Eli Zaretskii
2015-11-28 8:27 ` Yuan MEI
2015-11-28 9:44 ` Eli Zaretskii
2015-11-28 20:19 ` Yuan MEI
2015-11-28 20:49 ` Eli Zaretskii [this message]
2015-11-29 2:54 ` Yuan MEI
2015-11-29 15:42 ` Eli Zaretskii
2015-11-29 23:35 ` Yuan MEI
2015-11-30 16:16 ` Eli Zaretskii
2015-12-01 4:51 ` Yuan MEI
2015-12-01 16:01 ` Eli Zaretskii
2015-12-02 4:35 ` Yuan MEI
2015-12-02 13:57 ` Eli Zaretskii
2015-12-03 4:55 ` Yuan MEI
2015-12-03 7:47 ` Eli Zaretskii
2015-12-03 8:09 ` Yuan MEI
2015-12-03 10:23 ` Eli Zaretskii
2015-12-03 18:16 ` martin rudalics
2015-12-03 21:23 ` Yuan MEI
2015-12-04 8:08 ` martin rudalics
2015-12-04 8:30 ` Yuan MEI
2015-12-04 8:48 ` martin rudalics
2015-12-04 8:54 ` Yuan MEI
2015-12-04 8:56 ` martin rudalics
2015-12-04 9:00 ` Yuan MEI
2015-12-04 9:05 ` martin rudalics
2015-12-04 9:47 ` Eli Zaretskii
2015-12-04 10:21 ` martin rudalics
2015-12-04 11:01 ` Eli Zaretskii
2015-12-04 11:12 ` Eli Zaretskii
2015-12-05 0:25 ` YAMAMOTO Mitsuharu
2015-12-05 9:17 ` Eli Zaretskii
2015-12-06 0:49 ` Yuan MEI
2015-12-07 3:33 ` YAMAMOTO Mitsuharu
2015-12-07 17:19 ` Eli Zaretskii
2015-12-08 4:03 ` YAMAMOTO Mitsuharu
2015-12-11 8:48 ` Eli Zaretskii
2015-11-28 21:44 ` joakim
2015-11-29 0:14 ` Yuan MEI
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=83y4dhonng.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yuan.mei.list@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 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).