From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: =?UTF-8?B?SmFuIERqw6Rydg==?= Newsgroups: gmane.emacs.devel Subject: Re: GTK frame changes Date: Thu, 02 Jul 2009 21:44:14 +0200 Message-ID: <4A4D0E0E.70405@swipnet.se> References: <4A4CADCB.8000304@gmx.de> <4A4CC3D7.40109@swipnet.se> <4A4CD73D.2080802@gmx.de> <4A4CDDF2.4030608@swipnet.se> <4A4CF264.6040306@gmx.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1246563877 21985 80.91.229.12 (2 Jul 2009 19:44:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 2 Jul 2009 19:44:37 +0000 (UTC) Cc: emacs-devel@gnu.org To: grischka Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 02 21:44:30 2009 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 1MMSCq-00089Q-2P for ged-emacs-devel@m.gmane.org; Thu, 02 Jul 2009 21:44:28 +0200 Original-Received: from localhost ([127.0.0.1]:42275 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MMSCp-0000Am-HW for ged-emacs-devel@m.gmane.org; Thu, 02 Jul 2009 15:44:27 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MMSCk-00009n-Rt for emacs-devel@gnu.org; Thu, 02 Jul 2009 15:44:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MMSCg-0008Ul-2y for emacs-devel@gnu.org; Thu, 02 Jul 2009 15:44:22 -0400 Original-Received: from [199.232.76.173] (port=49106 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MMSCf-0008UL-SC for emacs-devel@gnu.org; Thu, 02 Jul 2009 15:44:17 -0400 Original-Received: from mtah11.telenor.se ([62.127.194.4]:52199) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MMSCf-0003LU-80 for emacs-devel@gnu.org; Thu, 02 Jul 2009 15:44:17 -0400 Original-Received: from iph1.telenor.se (iph1.telenor.se [195.54.127.132]) by mtah11.telenor.se (Postfix) with ESMTP id C49AF3362D for ; Thu, 2 Jul 2009 21:44:15 +0200 (CEST) X-SMTPAUTH-B2: X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: As2UAGeqTEpV4S1uPGdsb2JhbACBUYgXjxsBAQEBN7cVhBAF X-IronPort-AV: E=Sophos;i="4.42,337,1243807200"; d="scan'208";a="26057823" Original-Received: from c-6e2de155.25-1-64736c10.cust.bredbandsbolaget.se (HELO coolsville.localdomain) ([85.225.45.110]) by iph1.telenor.se with ESMTP; 02 Jul 2009 21:44:15 +0200 Original-Received: from [172.20.199.2] (gaffa [172.20.199.2]) by coolsville.localdomain (Postfix) with ESMTP id 00D1F7FA07B; Thu, 2 Jul 2009 21:44:14 +0200 (CEST) User-Agent: Thunderbird 2.0.0.22 (X11/20090608) In-Reply-To: <4A4CF264.6040306@gmx.de> X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:111923 Archived-At: grischka skrev: > Jan Dj=C3=A4rv wrote: >> XSync sends a request to the server and waits for a reply. The resize >> request is sent before that, so the resize should be handeled before=20 >> the XSync reply is sent. >=20 > Yes, but this reply is something in the sense of the X protocol, not > in the sense of ConfigureNotify. It just means that the X server got > the resize message when XSync returns. It doesn't mean at all that > a ConfigureNotify is already in the client queue let alone that emacs > now knows how big it is. >=20 The XProtocol specification (the oldest I have is R6.8, the newest is 7.4= ,=20 they say the same thing) says this: "Whether or not a server is implemented with internal concurrency, the overall effect must be as if individual requests are executed to=20 completion in some serial order, and requests from a given connection must be executed in delivery order (that is, the total execution order is a shuffle of the individual stream= s). The execution of a request includes validating all arguments, collecting all data for any reply, and generating and queueing all required events. However, it does not include the actual transmission of the reply and the= events. In addition, the effect of any other cause that can generate multiple eve= nts (for example, activation of a grab or pointer motion) must effectively=20 generate and queue all required events indivisibly with respect to all ot= her=20 causes and requests. For a request from a given client, any events destined for that client that are caused by executing the requ= est must be sent to the client before any reply or error is sent." I interpret this as for a given X connection, all requests are run to=20 completion and replies and events are queued in order. Since XSync waits= for=20 the reply, it also means that after XSync has returned, events and replie= s=20 generated by previous requests have indeed arrived. Jan D.