Path: utzoo!attcan!uunet!husc6!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU
Newsgroups: comp.windows.x
Subject: Re: Simple programming quiz
Message-ID: <8906161206.AA00607@expire.lcs.mit.edu>
Date: 16 Jun 89 12:06:41 GMT
References: <3184@ncsuvx.ncsu.edu>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 23


   The Scheifler book -- which I take as official, whether it is not -- says on
   p44 ...

Yes, it says something bogus, thanks for pointing it out.  But note that in the
next paragraph it does go on to explain that a window manager may get in your
way.  Also, in the more "biblical" part of the book, MapWindow on page 368 has
a correct definition.  I'll agree the wording doesn't bludgeon you with a
warning.

    Therefore the bug must be that the window is mapped but not exposed.

Nope.

    If the server needs extra time to finish mapping the window, well fine.

Nope.  It's all on account of window manager redirection.

    But the Consortium needs to make sure that the protocol definition is
    unambiguous about such behavior,

I believe the protocol definition is unambiguous.  The Xlib manual has
wording that is clearly causing confusion for you.