From: Chong Yidong <cyd@stupidchicken.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: "David Reitter" <david.reitter@gmail.com>,
"Jan Djärv" <jan.h.d@swipnet.se>,
emacs-devel@gnu.org
Subject: Re: [Stephen.Berman@gmx.net: Re: redisplay]
Date: Tue, 17 Mar 2009 11:13:02 -0400 [thread overview]
Message-ID: <87tz5sxjwh.fsf@cyd.mit.edu> (raw)
In-Reply-To: <wl8wn47c31.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Tue, 17 Mar 2009 18:06:26 +0900")
YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:
> I tried it myself with Ubuntu 8.10, GTK+ (as I could not reproduce the
> redraw-failure with X11 on Mac OS X, Xaw). It sometimes failed in
> redrawing with each of three Fredisplay call positions, including the
> original one. So I think this is a separate issue.
The failure seems to happen more often with the earlier Fredisplay call
position. This is not surprising: the Fredisplay call is an attempt to
update the display of the frames, which depends on X server timings that
Emacs cannot affect directly. Since the goal is to perform the update
just before opening the dialog, calling Fredisplay earlier makes this
hack less reliable.
Your analysis, however, makes it clear that this hack is problematic.
However, I don't see any good solution right now. So, please go ahead
and move the Fredisplay call to an earlier, safe position.
next prev parent reply other threads:[~2009-03-17 15:13 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
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 [this message]
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=87tz5sxjwh.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=mituharu@math.s.chiba-u.ac.jp \
/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).