From: "Perry E. Metzger" <perry@piermont.com>
To: martin rudalics <rudalics@gmx.at>
Cc: emacs-devel@gnu.org
Subject: Re: Is there a way to control where frames get created?
Date: Sun, 30 Sep 2018 14:35:34 -0400 [thread overview]
Message-ID: <20180930143534.24d54ac5@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <5BB10C49.1030106@gmx.at>
On Sun, 30 Sep 2018 19:47:53 +0200 martin rudalics <rudalics@gmx.at>
wrote:
> > Actually, it is _almost_ perfect. For some odd reason, the new
> > window ends up a few pixels lower than the old. I can fix this
> > with some subtraction but I'm puzzled why setting top to (cdr
> > (frame-position)) isn't quite doing the right thing.
>
> What are the values returned by 'frame-geometry' for the old and the
> new frame? Which window manager do you use? Which toolkit?
This is under MacOS/aqua:
First frame:
((outer-position 0 . 23) (outer-size 675 . 874) (external-border-size
0 . 0) (title-bar-size 0 . 22) (menu-bar-external) (menu-bar-size 0 .
0) (tool-bar-external) (tool-bar-position . top) (tool-bar-size 0 .
0) (internal-border-width . 2))
"New" frame:
((outer-position 690 . 25) (outer-size 675 . 874)
(external-border-size 0 . 0) (title-bar-size 0 . 22)
(menu-bar-external) (menu-bar-size 0 . 0) (tool-bar-external)
(tool-bar-position . top) (tool-bar-size 0 . 0)
(internal-border-width . 2))
So it's two pixels different. Peculiar, eh?
Perry
--
Perry E. Metzger perry@piermont.com
next prev parent reply other threads:[~2018-09-30 18:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-29 22:37 Is there a way to control where frames get created? Perry E. Metzger
2018-09-30 1:37 ` Drew Adams
2018-09-30 7:57 ` martin rudalics
2018-09-30 12:05 ` Perry E. Metzger
2018-09-30 12:22 ` martin rudalics
2018-09-30 14:14 ` Perry E. Metzger
2018-09-30 14:41 ` Perry E. Metzger
2018-09-30 16:20 ` Stefan Monnier
2018-09-30 17:48 ` martin rudalics
2018-09-30 18:07 ` Perry E. Metzger
2018-09-30 17:47 ` martin rudalics
2018-09-30 18:35 ` Perry E. Metzger [this message]
2018-10-01 8:35 ` martin rudalics
2018-10-01 11:06 ` Perry E. Metzger
2018-10-01 15:06 ` martin rudalics
2018-09-30 11:58 ` Michael Heerdegen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180930143534.24d54ac5@jabberwock.cb.piermont.com \
--to=perry@piermont.com \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.