From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?ISO-8859-1?Q?Jan_Dj=E4rv?= Newsgroups: gmane.emacs.devel Subject: Re: [Stephen.Berman@gmx.net: Re: redisplay] Date: Mon, 23 Apr 2007 21:14:35 +0200 Message-ID: <462D059B.7020001@swipnet.se> References: <87mz0z5dux.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1177355711 28178 80.91.229.12 (23 Apr 2007 19:15:11 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 23 Apr 2007 19:15:11 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 23 21:15:05 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Hg407-0003N7-Rq for ged-emacs-devel@m.gmane.org; Mon, 23 Apr 2007 21:15:04 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hg45Y-0002YM-5a for ged-emacs-devel@m.gmane.org; Mon, 23 Apr 2007 15:20:40 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Hg45M-0002Rg-OU for emacs-devel@gnu.org; Mon, 23 Apr 2007 15:20:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Hg45L-0002Qx-78 for emacs-devel@gnu.org; Mon, 23 Apr 2007 15:20:27 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hg45L-0002Qk-3h for emacs-devel@gnu.org; Mon, 23 Apr 2007 15:20:27 -0400 Original-Received: from av9-2-sn2.hy.skanova.net ([81.228.8.180]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Hg3zt-0004WQ-66; Mon, 23 Apr 2007 15:14:49 -0400 Original-Received: by av9-2-sn2.hy.skanova.net (Postfix, from userid 502) id 7CEE03858D; Mon, 23 Apr 2007 21:14:47 +0200 (CEST) Original-Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net [81.228.8.92]) by av9-2-sn2.hy.skanova.net (Postfix) with ESMTP id 50EF93800D; Mon, 23 Apr 2007 21:14:47 +0200 (CEST) Original-Received: from husetbladh.homeip.net (81-235-205-78-no59.tbcn.telia.com [81.235.205.78]) by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 0A5DF37E48; Mon, 23 Apr 2007 21:14:46 +0200 (CEST) User-Agent: Thunderbird 1.5.0.10 (X11/20070302) In-Reply-To: <87mz0z5dux.fsf@stupidchicken.com> X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:69868 Archived-At: Chong Yidong skrev: > Richard Stallman writes: > >> Would someone please debug this, then ack? >> >> From: Stephen Berman >> Subject: Re: redisplay >> To: emacs-pretest-bug@gnu.org >> >> On Sat, 21 Apr 2007 20:47:19 -0400 Richard Stallman wrote: >> >>> (progn (new-frame) >>> (redisplay t) >>> (x-popup-dialog t '("Foo" ("Bar" . 1)))) >>> >>> I tried this but it didn't fail -- the new frame was not empty. >> In my Emacs (GNU Emacs 22.0.98.2 (i686-pc-linux-gnu, GTK+ Version >> 2.10.6) of 2007-04-20 on escher) I see two behaviors: >> >> 1. Evalling the above sexp in *scratch* with C-j or in any buffer with >> M-: results in what the OP reported: "produces a blank frame while the >> popup dialog is active, i.e., (redisplay t) fails to wait for >> redisplay to finish." >> >> 2. Evalling the sexp with C-x C-e in any buffer results in what RMS >> reported. > > I believe this is because x-popup-dialog is handled with a GTK dialog > when you build under GTK, instead of using the Emacs redisplay engine. The redisplay engine don't handle any dialogs, Gtk+, Motif or otherwise. > So the behaviors are slightly different. I don't think this > "problem"---if it's really a problem---is serious, and it certainly > shouldn't block the Emacs 22 release. 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. My guess is that it just makes the needed X calls and then returns. For some reason or another, the dialog blocks the handling of other X events. Can the OP try to move the dialog around a bit and see if the frame below it is redrawn at all? Jan D.