On Sat, Feb 12, 2000 at 07:22:23PM +0000, Gunnar Evermann wrote: I'm to blame at this, I think. I moved the WM_COMMAND to the 'main window' of XEmacs (should be an invisible, unmapped window -- cause XEmacs really does not have a main window). This is the way any other 'new' application (i.e. GNOME and KDE) do it. Only the leader window may carry the command property, so the windowmanager can determine which window knows about the whole app (even apps with a main window -- The GIMP for example -- use an invisible window, cause the widget set -- gtk+ -- does the work. a bug in my eyes). The rename from session to wmcommand is because it has nothing to do with XSM, as far as I know. It's a windowmanager thing. What was changed in the code: - there is an invisible leader window - every XEmacs frame says that the leader is this leader - only the leader carries WM_COMMAND (prior to this the first frame got WM_COMMAND, and after you killed the first frame, WM_COMMAND was must to another frame -- this confused many window managers). I hope this brings some light into it (but I also don't know why the interaction with CDE is as it is). Regards, Oliver.