🚀 go-pugleaf

> This would have been nice if it had been defined earlier, but window_group
> is now being used for something else by the ICCCM.  This is the window
> on which the WM_CLIENT_MACHINE and WM_COMMAND properties are placed if
> the client opens multiple top-level windows (section 5.1.1).  Consider
> an editor, for example, which opens multiple top-level windows.  All of
> those windows are now perforce in the same window group, but it would
> probably not be proper behaviour to iconify and deiconify them in a group.
> Too bad.
> 
It is necessary to be very careful when you quote the ICCCM.  Here are
the actual words from Section 5.1.1:

	The client communicates with the session manager by placing
	two properties (WM_COMMAND and WM_CLIENT_MACHINE) on its
	top-level window.  If the client has a group of top-level
	windows,  these properties should be placed on the group
	leader window.

This does not say:

	This is the window on which the WM_CLIENT_MACHINE and WM_COMMAND
	properties are placed if the client opens multiple top-level windows

But rather:

	This is the window on which the WM_CLIENT_MACHINE and WM_COMMAND
	properties are placed if the client opens a group of top-level windows

There is no implication that multiple top-level windows have to be in the
same group,  or that a client can open only one group of top-level windows,
or any implication about the semantics a particular window manager chooses
to apply to window groups.

	David.