From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Chong Yidong <cyd@stupidchicken.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: [Stephen.Berman@gmx.net: Re: redisplay]
Date: Tue, 24 Apr 2007 16:49:34 +0200 [thread overview]
Message-ID: <462E18FE.10301@swipnet.se> (raw)
In-Reply-To: <jwvhcr5rhoi.fsf-monnier+emacs@gnu.org>
Stefan Monnier skrev:
>> I can't reproduce it with or without Gtk+, *scratch* or not. I suspect it
>> is a timing issue in X. I don't think redisplay guarantees that all
>> redisplay related events has been received and handeled by Emacs before it
>> returns.
>
> Even if it does an XSync?
XSync only guarantees that events have been sent to the server and replies
have been received into Xlib. There might be stuff Emacs have left to do
still. But I don't know redisplay that well to be sure. XSync is our bet bet
though.
>
> In any case, I have regularly seen similar problems when leaving Emacs: if
> I have processes running, Emacs displays a *processes* list, and because of my
> pop-up-frames (and/or special-display-regexps) settings, it does it by first
> popping up a new frame displaying this *processes* buffer, and then pops up
> a dialog asking me whether I really want to quit.
> The problem is that the *processes* frame is generally blank at that point.
Hmm, I'll try to reproduce this some more.
Jan D.
next prev parent reply other threads:[~2007-04-24 14:49 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 [this message]
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
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=462E18FE.10301@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--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).