From: uzibalqa <uzibalqa@proton.me>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Frame shifted upwards upon changing font size
Date: Tue, 13 Sep 2022 13:15:19 +0000 [thread overview]
Message-ID: <oQuXOL8chIcHmEuiWP1wYDofvHZNrF-vFq8TBiUgomjfnpM8V6KB1BvKDVrtd5lfsvxgIcghm-ZcZqxIaimnJC06XWQ0hoLKuSAYKSthouU=@proton.me> (raw)
In-Reply-To: <83mtb34eb6.fsf@gnu.org>
------- Original Message -------
On Tuesday, September 13th, 2022 at 1:03 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Tue, 13 Sep 2022 12:40:38 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: help-gnu-emacs@gnu.org
> >
> > > > default-frame-alist is a confusing as it already has (width . 75) and
> > > > (height . 21) for the frame. What is the corresponding entry for
> > > > the font height?
> > >
> > > It's 'font' (and use the fully-qualified XLFD name as the value).
> >
> > It is even more difficult for user to identify a font name.
>
>
> No, it isn't. Evaluate this in a running Emacs session:
>
> (face-font 'default)
>
> > set-face-attribute is great because one just specifies its properties
> > without worrying about the actual font
> >
> > (set-face-attribute 'default nil :height 160 :weight 'bold)
>
>
> But you said that it doesn't do the job in this case, and asked for
> alternatives, right?
Neither does default-frame-alist
Seems that a solution would be a function that looks at the monitor size
and centers the frame.
prev parent reply other threads:[~2022-09-13 13:15 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
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 [this message]
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='oQuXOL8chIcHmEuiWP1wYDofvHZNrF-vFq8TBiUgomjfnpM8V6KB1BvKDVrtd5lfsvxgIcghm-ZcZqxIaimnJC06XWQ0hoLKuSAYKSthouU=@proton.me' \
--to=uzibalqa@proton.me \
--cc=eliz@gnu.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).