From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
To: jan.h.d@swipnet.se
Cc: rgm@gnu.org, cyd@stupidchicken.com, monnier@iro.umontreal.ca,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [Stephen.Berman@gmx.net: Re: redisplay]
Date: Thu, 26 Apr 2007 04:44:22 +0900 (JST) [thread overview]
Message-ID: <20070426.044422.158290364.mituharu@math.s.chiba-u.ac.jp> (raw)
In-Reply-To: <462F9E30.4000702@swipnet.se>
>>>>> On Wed, 25 Apr 2007 20:30:08 +0200, Jan Djärv <jan.h.d@swipnet.se> said:
>> Yes, you are right. It would also require to run redisplay
>> directly on the Expose event.
But Lisp evaluations might occur during redisplay (unless
inhibit-eval-during-redisplay is non-nil), and thus it's not safe to
do so in general.
> After some experimenting it seems that this patch fixes it. Note
> that a call to redisplay() does not fix the bug. I don't know why.
I think that's because redisplay is paused by a pending Expose event
if redisplay-dont-pause is nil (`Fredisplay (Qt)' temporarily binds it
to t). I observed similar undrawn area with "compositing window mode"
mentioned in *1 when redisplay-dont-pause is nil and without the patch
in *2.
*1: http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg01003.html
*2: http://lists.gnu.org/archive/html/emacs-devel/2007-04/msg01013.html
YAMAMOTO Mitsuharu
mituharu@math.s.chiba-u.ac.jp
next prev parent reply other threads:[~2007-04-25 19:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 3:48 [Stephen.Berman@gmx.net: Re: redisplay] Richard Stallman
2007-04-23 15:07 ` Chong Yidong
2007-04-23 19:14 ` Jan Djärv
2007-04-23 22:12 ` Stephen Berman
2007-04-23 22:50 ` YAMAMOTO Mitsuharu
2007-04-24 1:10 ` YAMAMOTO Mitsuharu
2007-04-26 20:58 ` Stephen Berman
2007-04-27 8:57 ` YAMAMOTO Mitsuharu
2007-04-28 4:06 ` Richard Stallman
2007-04-29 7:35 ` YAMAMOTO Mitsuharu
2007-04-29 21:41 ` Richard Stallman
2007-05-01 8:30 ` YAMAMOTO Mitsuharu
2007-05-02 0:12 ` Richard Stallman
2007-04-29 7:51 ` David Kastrup
2007-04-29 9:25 ` Nick Roberts
2007-04-29 21:41 ` Richard Stallman
2007-04-29 22:14 ` David Kastrup
2007-05-01 0:23 ` YAMAMOTO Mitsuharu
2007-04-24 14:08 ` Stefan Monnier
2007-04-24 14:49 ` Jan Djärv
2007-04-24 18:27 ` Glenn Morris
2007-04-25 8:47 ` Jan Djärv
2007-04-25 14:36 ` Stefan Monnier
2007-04-25 14:50 ` Jan Djärv
2007-04-25 18:30 ` Jan Djärv
2007-04-25 19:34 ` Stefan Monnier
2007-04-25 19:44 ` YAMAMOTO Mitsuharu [this message]
2007-04-26 5:58 ` Jan Djärv
2007-04-26 8:35 ` YAMAMOTO Mitsuharu
2007-04-26 3:08 ` Glenn Morris
2007-04-26 20:59 ` Stephen Berman
2007-04-27 5:58 ` Jan Djärv
2009-03-16 1:37 ` YAMAMOTO Mitsuharu
2009-03-16 12:16 ` David Reitter
2009-03-16 15:18 ` Chong Yidong
2009-03-17 2:43 ` YAMAMOTO Mitsuharu
2009-03-17 3:59 ` Chong Yidong
2009-03-17 4:13 ` YAMAMOTO Mitsuharu
2009-03-17 9:06 ` YAMAMOTO Mitsuharu
2009-03-17 15:13 ` Chong Yidong
2009-03-18 8:56 ` 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=20070426.044422.158290364.mituharu@math.s.chiba-u.ac.jp \
--to=mituharu@math.s.chiba-u.ac.jp \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@gnu.org \
--cc=rms@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).