From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.bugs Subject: bug#18637: 24.4.50; doc of frame parameter DISPLAY vs actual value on MS Windows Date: Tue, 7 Oct 2014 13:25:40 -0700 (PDT) Message-ID: References: <83tx3flxn2.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1412713593 20455 80.91.229.3 (7 Oct 2014 20:26:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 7 Oct 2014 20:26:33 +0000 (UTC) To: Andy Moreton , 18637@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Oct 07 22:26:26 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1XbbKz-0001Ga-4v for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Oct 2014 22:26:25 +0200 Original-Received: from localhost ([::1]:60788 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbbKy-0006df-OJ for geb-bug-gnu-emacs@m.gmane.org; Tue, 07 Oct 2014 16:26:24 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43848) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbbKm-0006dF-1m for bug-gnu-emacs@gnu.org; Tue, 07 Oct 2014 16:26:20 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XbbKc-0002Yr-Pw for bug-gnu-emacs@gnu.org; Tue, 07 Oct 2014 16:26:11 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:45379) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XbbKc-0002Yc-Mu for bug-gnu-emacs@gnu.org; Tue, 07 Oct 2014 16:26:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1XbbKc-0003VZ-C3 for bug-gnu-emacs@gnu.org; Tue, 07 Oct 2014 16:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Drew Adams Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 07 Oct 2014 20:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 18637 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 18637-submit@debbugs.gnu.org id=B18637.141271354613463 (code B ref 18637); Tue, 07 Oct 2014 20:26:02 +0000 Original-Received: (at 18637) by debbugs.gnu.org; 7 Oct 2014 20:25:46 +0000 Original-Received: from localhost ([127.0.0.1]:36943 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1XbbKK-0003V3-W3 for submit@debbugs.gnu.org; Tue, 07 Oct 2014 16:25:45 -0400 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:37435) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1XbbKJ-0003Uv-1G for 18637@debbugs.gnu.org; Tue, 07 Oct 2014 16:25:43 -0400 Original-Received: from acsinet21.oracle.com (acsinet21.oracle.com [141.146.126.237]) by aserp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id s97KPfs4027659 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 7 Oct 2014 20:25:42 GMT Original-Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by acsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s97KPeRT009294 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 7 Oct 2014 20:25:41 GMT Original-Received: from abhmp0013.oracle.com (abhmp0013.oracle.com [141.146.116.19]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id s97KPepA020706; Tue, 7 Oct 2014 20:25:40 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.8.2 (807160) [OL 12.0.6691.5000 (x86)] X-Source-IP: acsinet21.oracle.com [141.146.126.237] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:94263 Archived-At: > I have a multi-monitor system, but I'm not going to perform > experiments without a clearer recipe. I did try rearranging the physical > monitor layout as follows (which makes it quite easy to lose the position > of the cursor). Things may get more confusing with three or more monitors= ... >=20 > ;; Two monitors arranged physically as: > ;; +---------+ > ;; | | > ;; | 2 |+---------+ > ;; | || | > ;; +---------+| 1 | > ;; | | > ;; +---------+ > (display-monitor-attributes-list) > ;; =3D=3D> > (((geometry 0 0 1920 1080) > (workarea 0 0 1920 1050) > (mm-size 677 381) > (name . "\\\\.\\DISPLAY1") > (frames)) > ((geometry -1680 -646 1680 1050) > (workarea -1680 -646 1680 1050) > (mm-size 593 370) > (name . "\\\\.\\DISPLAY2") > (frames))) >=20 > (display-pixel-height) ;; =3D=3D> 1726 > (display-pixel-width) ;; =3D=3D> 3600 >=20 > (display-mm-height) ;; =3D=3D> 609 > (display-mm-width) ;; =3D=3D> 1269 Thanks for the offer, Andy. I don't have a better recipe to give, unfortunately. I've mentioned in this thread all of the info I have. I think it might be enough if you tried the `maximize-frame' and `restore-frame' commands in frame-cmds.el, especially if (I'm guessing, based on the conversation with Eli) you have one monitor that is smaller than the other. It sounds like perhaps you will see a frame that you maximize or restore this way jump from one frame to another. Perhaps that will happen more if most of the frame before the operation is in fact shown on the other frame. But the OP did not mention that. His report seemed to suggest that the frame was shown completely in one frame and then jumped to another frame when it was maximized (or restored?). The frame-cmds.el code just changes frame parameters `left', `top', `width', and `height'. In principle, restoring just resets the original values for these, and maximizing sets them to values that fill the screen (which is not necessarily the same thing as the monitor).