From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: grischka <grishka@gmx.de>
Cc: "Jan Djärv" <jan.h.d@swipnet.se>, emacs-devel@gnu.org
Subject: Re: GTK frame changes
Date: Fri, 03 Jul 2009 21:14:59 +0900 [thread overview]
Message-ID: <87ws6qufng.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <4A4DE33F.4060006@gmx.de>
grischka writes:
> Jan Djärv wrote:
> > The XProtocol specification (the oldest I have is R6.8, the newest is
> > 7.4, 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 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
> > streams).
Jan is missing a number of issues, I think. First, there are (at
least) two clients and *two* connections involved here. One is
Emacs's, the other is the WM's. This leaves a lot of room for
nondeterminism ("shuffling") in the order in which configuration
events arrive on Emacs's connection.
Second, the process that generates the ConfigureNotify event is *not*,
and cannot be, atomic. When the WM has set the SubstructureRedirect
flag on the root window, a request by Emacs to configure one of its
(X) windows will propagate up the toolkit hierarchy to a shell window,
which will then execute X protocol. However the reaction of the
server to that protocol request is *not* to configure the window and
send a ConfigureNotify event. It is to *do nothing* except send a
ConfigureRequest event to the window, which will be processed by the
WM (because of the substructure redirection), not Emacs. The WM *then
issues the configuration request again*, which will succeed this time
because the WM "owns" the substructure redirection.
> I'm somehow confused what they mean by reply here. If events are sent
> before replies then replies must be something else.
Yes. An event is sent as a reaction to something that happens to or
in a window. A reply is something that the server says as an
informational matter in response to a request, which doesn't need to
specifically refer to any window.
> Just with WM redirection (metacity here) the ConfigureNotify
> clearly arrives about 2 ms later and the behavior is completely
> unimpressed by XSync.
"metacity"? As a developer of an X client, that's not my favorite
WM.... metacity's idea of "well-behaved" is a bit more restrictive
than fdo's standards specify.
next prev parent reply other threads:[~2009-07-03 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-02 12:53 GTK frame changes grischka
2009-07-02 14:27 ` Jan Djärv
2009-07-02 15:50 ` grischka
2009-07-02 16:18 ` Jan Djärv
2009-07-02 17:46 ` grischka
2009-07-02 19:44 ` Jan Djärv
2009-07-03 10:53 ` grischka
2009-07-03 11:37 ` Jan Djärv
2009-07-03 12:14 ` Stephen J. Turnbull [this message]
2009-07-03 12:43 ` Jan Djärv
2009-07-03 12:47 ` Stephen J. Turnbull
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ws6qufng.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--cc=grishka@gmx.de \
--cc=jan.h.d@swipnet.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.