The XEmacs frame seems to disappear, but either it is (in "normal mode") locaded off screen, or it has a size that makes it "invisible". When using Windows GUI command "Maximize", it does appear and nicely occupies all of the screen, as it should. Choosing Windows GUI "Restore" makes it "go away" again.

This behavior has occurred a few times, and I do not know just what triggers it. When in this "none-or-maximal" state, I maximized it, switched to a "buffer in other frame", hoping to get a normal XEmacs frame.

Yes it did appear, but then the process crashed. This is not easy to reproduce. I have no steps that will guarantee that it happens. Anyway ...

Hi, Olle - On Sat, Sep 18, 2010 at 4:21 AM, Olle Olsson <redsky1066(a)gmail.com&gt; wrote: > The XEmacs frame seems to disappear, but either it is (in "normal > mode") locaded off screen, or it has a size that makes it > "invisible". When using Windows GUI command "Maximize", it does appear > and nicely occupies all of the screen, as it should. Choosing Windows > GUI "Restore" makes it "go away" again. > > This behavior has occurred a few times, and I do not know just what > triggers it. I have seen this behavior with other Windows applications. I believe you are correct that the window has been displayed off-screen. When the window is maximized, you should be able to evaluate these forms: (set-frame-properties (window-frame) 'left 5) (set-frame-properties (window-frame) 'top 5) in the *scratch* buffer to move the window back into a visible position. Does that help? Regards, Vin Shelton