From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: dimensions when doing text-scale-increase, and including minibuffer in text-scale-increase
Date: Tue, 10 Dec 2019 21:37:47 +0200 [thread overview]
Message-ID: <83blsgas50.fsf@gnu.org> (raw)
In-Reply-To: <CAJcAo8sQx3SqbJq3rMP529pDPsosp390sJfG5CoZQpFYs0cxtQ@mail.gmail.com> (message from Samuel Wales on Tue, 10 Dec 2019 12:28:29 -0700)
> From: Samuel Wales <samologist@gmail.com>
> Date: Tue, 10 Dec 2019 12:28:29 -0700
>
> question 1:
>
> if i want to know the usable default dimensions in human lines and
> columns terms, i can do:
>
> (let ((r (list (frame-width)
> (frame-height))))
> (message "%s =frame width and height =(should be (110 32) at
> /native resolution 1440/ with /dpi of 216/)"
> r)
>
> but if i do text-scale-increase the result is the same.
Yes, because frame-width and frame-height return values in units of
the canonical character size.
> i want to know the same data about what is /there now/.
Then use frame-pixel-width and frame-pixel-height, and divide by
default-font-width and default-font-height to get the results in
columns and lines.
> i want to do text-scale increase on exactly the active buffer and
> "its" minibuffer, but not any other buffers. i'd prefer modeline not
> increase, however.
>
> whenever i switch back to the increased buffer, i want it and "its"
> echo area / minibuffer to still be increased.
For the echo area and the minibuffer you will have to use hooks,
because switching to another buffer doesn't switch the echo-area or
minibuffer. IOW, there's no separate echo-area/minibuffer for each
buffer.
next prev parent reply other threads:[~2019-12-10 19:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 19:28 dimensions when doing text-scale-increase, and including minibuffer in text-scale-increase Samuel Wales
2019-12-10 19:37 ` Eli Zaretskii [this message]
2019-12-22 21:05 ` Samuel Wales
2019-12-23 13:23 ` Eli Zaretskii
2019-12-23 15:21 ` 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
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=83blsgas50.fsf@gnu.org \
--to=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).