From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: How to restore the layout? Date: Wed, 10 Jul 2013 09:20:01 +0200 Message-ID: <51DD0B21.5070502@gmx.at> References: <51C5AA68.4000204@alice.it> <51D02AB0.5070103@gmx.at> <51D5DE14.4090507@alice.it> <51D600D8.90801@alice.it> <51D67985.7010806@gmx.at> <51D69AF8.2050606@alice.it> <51D6C2FA.7040708@gmx.at> <51D6CD1C.5050504@alice.it> <51D6DB49.7020005@gmx.at> <831u7czx1i.fsf@gnu.org> <51D72CC9.9040704@alice.it> <51D7D9B1.8080102@gmx.at> <51D7DF18.2010502@alice.it> <51D7F501.7020207@gmx.at> <51D7F9C1.4000801@alice.it> <51D81657.8020108@gmx.at> <972fd406-97dc-42fc-9727-03642e351c88@default> <51D949AD.6020800@gmx.at> <51D96326.9040500@gmx.at> <5f8e3fb9-8dba-4cd2-ab31-9ae03fa8ec07@default> <51DA608F.3040400@gmx.at> <51DBD2E5.4050408@gmx.at> <46783987-8f32-41b4-b8bb-c28965306cfc@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1373440824 27815 80.91.229.3 (10 Jul 2013 07:20:24 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 10 Jul 2013 07:20:24 +0000 (UTC) Cc: Juanma Barranquero , Eli Zaretskii , Emacs developers , Angelo Graziosi To: Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 10 09:20:25 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UwohM-0005Or-GF for ged-emacs-devel@m.gmane.org; Wed, 10 Jul 2013 09:20:24 +0200 Original-Received: from localhost ([::1]:50558 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwohL-0003t7-V4 for ged-emacs-devel@m.gmane.org; Wed, 10 Jul 2013 03:20:23 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45568) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwohI-0003t2-DA for emacs-devel@gnu.org; Wed, 10 Jul 2013 03:20:22 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UwohD-0007Nu-Gt for emacs-devel@gnu.org; Wed, 10 Jul 2013 03:20:20 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:50046) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UwohB-0007NQ-L3; Wed, 10 Jul 2013 03:20:13 -0400 Original-Received: from [62.47.61.1] ([62.47.61.1]) by mail.gmx.com (mrgmx001) with ESMTPA (Nemesis) id 0MLNpK-1UxMev2sc6-000e5x; Wed, 10 Jul 2013 09:20:12 +0200 In-Reply-To: <46783987-8f32-41b4-b8bb-c28965306cfc@default> X-Provags-ID: V03:K0:rGaunWcaUsMJ5rX6YvYX0BErfFGsGq1M35pQShNsLiVYFV8gNh7 I0WNiuJd0ya9Bxn/vwiJm0Rysi9wiQUFrRS46Z0zVKf/q+uS1rgGD1N5mECfXnafX+nIbOo OCRbf9rKI4lQFzI5QuwIlRVyY3cO8NRKt6HgpFcl2BYMBctuanZUvsxjM/CKwPluAUWvPEf ks4Qj5Q21h1f0j14SbS2A== X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:161795 Archived-At: >> If you maximize another application on your system, do you see any >> borders? I don't here. > > On MS Windows, clicking the maximize button in the title bar (or maximizing > in some other way) makes the window take up the full screen space, but still > with its borders, including the title bar. Maximize and "fullscreen" are not > the same thing, AFAIK. When I start an application like the Windows Explorer I see, above the title bar, the upper border of its window. When I maximize the Explorer's window, I still see the title bar, but the upper border has disappeared. When I make the Explorer window fullscreen (via F11) title bar and upper border both disappear. >> Yes. But sending the window manager an explicit resizing request >> lifts that restriction, IIUC. > > How would I/you check that outside of Emacs, with MS Windows? No idea. But with Emacs I can maximize a frame and do (set-frame-position (selected-frame) 12 12) to move it, keeping its previous size, while (set-frame-position (selected-frame) 0 0) will move it just for a short moment and back to the previous state afterwards. In any case, I can clearly see that the frame keeps its outer borders, confirming an earlier claim of Juanma. >> > Is this the behavior to be expected, that you can move a fullscreen frame >> > around and resize it (so it is, in effect, no longer "full screen"? To >> > be clear, I don't care, a priori, either way; I'm just reporting what I see, >> > in case it helps. >> >> It depends on how you move and resize it. > > How so? Please elaborate. What is the design - the "behavior to be expected" > in the different cases of how you move/resize? I can't elaborate because I don't know what you tried to do when you reported what you saw. Here I cannot move a maximized Emacse frame by dragging the mouse or via the System Menu. I can move it by evaluating (set-frame-position (selected-frame) 12 12) or resize it by doing (set-frame-height (selected-frame) (1- (frame-height))) though and there's still a button enabled telling me that I can "restore its size" so Windows still thinks that the Emacs window is maximized. There's one funny discrepancy: I can't mouse-drag the moved window but can drag the resized one. > As I said, you cannot get to the Move or resizing > items of the system menu for a maximized window. The fact that you can move > or resize a "maximized" Emacs frame suggests that the Emacs "maximize" is > not quite the same thing as Windows maximize. Not necessarily. I unfortunately lost my Emacs trunk version and am not sure whether and when I'm able to recuperate it, but IIRC I had lots of incoherent states after doing M-F10. But, maximizing Emacs via the button in the upper right corner (I never use that but call WinMaximize via a key combination instead) always works as expected. martin