From: Robert Pluim <rpluim@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: master 57d2f24: * lisp/frame.el (make-frame-on-monitor): New command. (Bug#34516)
Date: Thu, 28 Feb 2019 17:52:15 +0100 [thread overview]
Message-ID: <m2d0nb3lfk.fsf@gmail.com> (raw)
In-Reply-To: <m24l8o45hy.fsf@gmail.com> (Robert Pluim's message of "Thu, 28 Feb 2019 10:38:49 +0100")
Robert Pluim <rpluim@gmail.com> writes:
> I can do that. I have a small problem with 'make-frame-on-monitor':
> the resulting frame is too tall (itʼs correctly
> positioned though). Perhaps toolbars etc need to be
> accounted for?
>
> (Iʼll note that both outer-size and tool-bar-size are wider than the
> actual display, so perhaps this is an issue in the macOS code geometry
> code).
Thereʼs no issue on macOS: there was a scrollbar off to the right that
I hadn't realised was off-screen.
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).
Robert
next prev parent reply other threads:[~2019-02-28 16:52 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 [this message]
2019-02-28 20:40 ` Juri Linkov
2019-03-01 13:40 ` Robert Pluim
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=m2d0nb3lfk.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--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).