From: Robert Pluim <rpluim@gmail.com>
To: uzibalqa <uzibalqa@proton.me>
Cc: Gregory Heytings <gregory@heytings.org>,
Eli Zaretskii <eliz@gnu.org>,
help-gnu-emacs@gnu.org
Subject: Re: Frame shifted upwards upon changing font size
Date: Thu, 15 Sep 2022 09:17:32 +0200 [thread overview]
Message-ID: <87bkrhksxf.fsf@gmail.com> (raw)
In-Reply-To: <KwjEa8c-6H65AhhpJC1HlkVY-eWs1QDq_Of_y6J03HZddfxaFIICUurLYWEge2Gn2ermgsANS99WRsfQ_SMG4kTr-pC2pJnemOov8Dt83rY=@proton.me> (uzibalqa@proton.me's message of "Wed, 14 Sep 2022 15:09:55 +0000")
>>>>> On Wed, 14 Sep 2022 15:09:55 +0000, uzibalqa <uzibalqa@proton.me> said:
uzibalqa> Could emacs get to understand the monitor within which the initial frame
>>
uzibalqa> gets displayed and be able to center the frame in that monitor?
>>
>>
>> `frame-monitor-attributes' will give you the same information as`
>> display-monitor-attributes-list', but for the monitor where the
>> currently selected frame is displayed.
>>
>>
>> Robert
>> --
uzibalqa> frame-monitor-attributes gives me
uzibalqa> ((geometry 1080 1152 1366 768) (workarea 1080 1152 1311 768) (mm-size 344 194)
uzibalqa> (frames #<frame *scratch* 0x1c111f0> #<frame Speedbar 0x30cefc0>) (source . "Gdk"))
uzibalqa> How do I interpret this, and how can I use this information?
Well, you do
(alist-get 'geometry (frame-monitor-attributes))
which gives you a list, of which the 3rd element is the width of
the monitor, which you can use in Gregoryʼs example function.
Robert
--
next prev parent reply other threads:[~2022-09-15 7:17 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
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 [this message]
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=87bkrhksxf.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=help-gnu-emacs@gnu.org \
--cc=uzibalqa@proton.me \
/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).