unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: emacs-devel@gnu.org
Subject: Re: master 57d2f24: * lisp/frame.el (make-frame-on-monitor): New command. (Bug#34516)
Date: Fri, 01 Mar 2019 14:40:37 +0100	[thread overview]
Message-ID: <m2pnrazp9m.fsf@gmail.com> (raw)
In-Reply-To: 87k1hjk5ow.fsf@mail.linkov.net

Juri Linkov <juri@linkov.net> writes:

>> If Iʼve understood correctly, you want to create a frame that covers
>> the entire workarea of the chosen monitor. Would it not work to
>> specify the x,y of the top corner plus (fullscreen . maximized) rather
>> than specifying the width and height explicitly? That will do the
>> toolbar/titlebar/scrollbar subtractions for you (I haven't tested this).

Now that Iʼve tested this, it works for my primary display, but not
the secondary, which is because the secondary is to my left,
and ns-parse-geometry has an issue with negative offsets.

In any case, I think using x-parse-geometry is not necessary. The
workarea already contains the relevant coördinates, and you can just
pass (fullscreen . maximized) to get the right size. Sample patch
below (which Iʼve tested only on macOS, not under X).

> I already have this for personal customization in ~/.emacs:
>
>   (add-hook 'after-make-frame-functions 'toggle-frame-maximized)
>   (advice-add 'make-frame-on-monitor :around
>               (lambda (orig-fun monitor &optional display parameters)
>                 (funcall orig-fun monitor display '((undecorated . t))))
>               '((name . make-frame-on-monitor-undecorated)))
>
> But my intention was to implement a general command that would make
> a new frame according to the physical monitor attributes returned by
> display-monitor-attributes-list.
>
> I have no idea why display-monitor-attributes-list returns
> workarea that doesn't fit into the created frame on macOS.

It does that because thatʼs what itʼs supposed to do, itʼs describing
the characteristics of the monitor. The issue is with make-frame. From
(elisp) Frame Size:

   The text size of any frame can be set and retrieved with the help of
the ‘height’ and ‘width’ frame parameters (*note Size Parameters::).

Note it says 'text size', which means you have to account for
scrollbars, toolbars, etc.

> While testing it without customization in GDK on GNU/Linux,
> I see that the created frames cover the whole physical monitor,
> including toolbar/titlebar/scrollbar.

That I suspect is window-manager dependent: there are window managers
that won't let you create a frame bigger than the monitor, or maybe
x-parse-geometry is performing clipping.

> Maybe there is still an issue in ns-display-monitor-attributes-list?

Not that I can see.

Sample implementation using (fullscreen . maximized):

diff --git a/lisp/frame.el b/lisp/frame.el
index 8a4a0b6639..f8e9a1ff1a 100644
--- a/lisp/frame.el
+++ b/lisp/frame.el
@@ -666,19 +666,19 @@ make-frame-on-monitor
                                    (when (equal (cdr (assq 'name a)) monitor)
                                      (cdr (assq 'workarea a))))
                                  (display-monitor-attributes-list display)))))
-         (frame-geometry
-          (when monitor-geometry
-            (x-parse-geometry (format "%dx%d+%d+%d"
-                                      (nth 2 monitor-geometry)
-                                      (nth 3 monitor-geometry)
-                                      (nth 0 monitor-geometry)
-                                      (nth 1 monitor-geometry)))))
          (frame-geometry-in-pixels
-          (when frame-geometry
-            `((top . ,(cdr (assq 'top frame-geometry)))
-              (left . ,(cdr (assq 'left frame-geometry)))
-              (height . (text-pixels . ,(cdr (assq 'height frame-geometry))))
-              (width . (text-pixels . ,(cdr (assq 'width frame-geometry))))))))
+          (when monitor-geometry
+            (let* ((top (nth 1 monitor-geometry))
+                   (left (nth 0 monitor-geometry))
+                   (top (if (< top 0)
+                                 `(- ,(abs top))
+                               top))
+                   (left (if (< left 0)
+                             `(- ,(abs left))
+                           left)))
+              `((top . ,top)
+                (left . ,left)
+                (fullscreen . maximized))))))
     (make-frame (append frame-geometry-in-pixels parameters))))



  reply	other threads:[~2019-03-01 13:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190225211142.21954.14993@vcs0.savannah.gnu.org>
     [not found] ` <20190225211144.0DD23206A2@vcs0.savannah.gnu.org>
2019-02-26  9:12   ` master 57d2f24: * lisp/frame.el (make-frame-on-monitor): New command. (Bug#34516) Robert Pluim
2019-02-26 15:23     ` Eli Zaretskii
2019-02-27 20:59       ` Juri Linkov
2019-02-28  9:38         ` Robert Pluim
2019-02-28 16:52           ` Robert Pluim
2019-02-28 20:40             ` Juri Linkov
2019-03-01 13:40               ` Robert Pluim [this message]
2019-03-02 21:09                 ` Juri Linkov
2019-03-03  1:05                   ` Drew Adams
2019-03-03 21:30                     ` Juri Linkov
2019-03-04  0:01                       ` Drew Adams
2019-03-04  8:53                   ` Robert Pluim
2019-02-28 18:11         ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2pnrazp9m.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).