From: uzibalqa <uzibalqa@proton.me>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>, help-gnu-emacs@gnu.org
Subject: Re: Frame shifted upwards upon changing font size
Date: Tue, 13 Sep 2022 13:57:13 +0000 [thread overview]
Message-ID: <d08KNb7d0kkgnuKWRXQxsVajSf4cVfK-8gC90wttRniaE8ItlyNs3EElYdmHT5j6klK3hwhx91tIuXSFG8KJW6g6dvflxxQFZJrKY4Suv28=@proton.me> (raw)
In-Reply-To: <a993deec5877b724e048@heytings.org>
Sent with Proton Mail secure email.
------- Original Message -------
On Tuesday, September 13th, 2022 at 1:53 PM, Gregory Heytings <gregory@heytings.org> wrote:
> > > (defun frame-center (&optional frame display)
> > > (interactive)
> > > (set-frame-position
> > > frame
> > > (/ (- (display-pixel-width display) (frame-pixel-width frame)) 2)
> > > (/ (- (display-pixel-height display) (frame-pixel-height frame)) 2)))
> >
> > I have different monitors with different sizes, and the function is
> > transferring the frame to a different monitor.
>
>
> In that case you need to use display-monitor-attributes-list to get the
> size of the appropriate monitor.
I get
(((geometry 1080 1152 1366 768) (workarea 1080 1152 1311 768) (mm-size 344 194) (frames #<frame Speedbar 0x415c0c0>) (source . "Gdk"))
((geometry 0 0 1080 1920) (workarea 0 0 1080 1920) (mm-size 477 268) (frames #<frame *scratch* 0x2ca1040>) (source . "Gdk")))
What would be the way forward?
next prev parent reply other threads:[~2022-09-13 13:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 4:27 Frame shifted upwards upon changing font size uzibalqa
2022-09-13 11:29 ` Eli Zaretskii
2022-09-13 12:10 ` uzibalqa
2022-09-13 12:25 ` uzibalqa
2022-09-13 13:22 ` Gregory Heytings
2022-09-13 13:45 ` uzibalqa
2022-09-13 13:53 ` Gregory Heytings
2022-09-13 13:57 ` uzibalqa [this message]
2022-09-13 15:28 ` Gregory Heytings
2022-09-13 21:07 ` uzibalqa
2022-09-14 10:10 ` Robert Pluim
2022-09-14 15:09 ` uzibalqa
2022-09-15 7:17 ` Robert Pluim
2022-09-15 11:43 ` uzibalqa
2022-09-15 12:25 ` Robert Pluim
2022-09-15 13:38 ` Po Lu
2022-09-15 15:09 ` Pascal Quesseveur
2022-09-15 16:07 ` Yuri Khan
2022-09-15 16:27 ` Pascal Quesseveur
2022-09-14 10:30 ` Po Lu
2022-09-14 15:07 ` uzibalqa
2022-09-14 15:21 ` Christopher Dimech
2022-09-13 12:29 ` Eli Zaretskii
2022-09-13 12:40 ` uzibalqa
2022-09-13 13:03 ` Eli Zaretskii
2022-09-13 13:15 ` uzibalqa
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='d08KNb7d0kkgnuKWRXQxsVajSf4cVfK-8gC90wttRniaE8ItlyNs3EElYdmHT5j6klK3hwhx91tIuXSFG8KJW6g6dvflxxQFZJrKY4Suv28=@proton.me' \
--to=uzibalqa@proton.me \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).