From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: 46853@debbugs.gnu.org
Subject: bug#46853: Confusing terminology "face height" instead of "font size"
Date: Wed, 3 Mar 2021 18:16:02 -0600 [thread overview]
Message-ID: <CADwFkmmoVW2xqLrWEPncHYb4jxbkd9NxYVHfOmb4PYP3i9ShWA@mail.gmail.com> (raw)
In-Reply-To: <83sg5e7ihe.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: stefan@marxist.se, 46853@debbugs.gnu.org
>> Date: Mon, 01 Mar 2021 20:45:28 +0100
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>
>> > No, it's because enlarging _all_ faces makes no sense.
>>
>> I really thought that's how this command worked, but
>>
>> emacs -Q -f list-faces-display
>>
>> and then `C-x C-+' in the buffer enlarges all the faces, even
>> variable-pitch...
>
> It only enlarges those faces which inherit their size from 'default'.
I find the semantics here confusing. I do this in emacs -Q:
(progn
(defface foo-bar '((t :weight bold)) "foo")
(pop-to-buffer (get-buffer-create "foo"))
(insert "aaa " (propertize "bbb" 'face 'foo-bar) " ccc")
(text-scale-adjust 3))
And I see that "bbb" has its font size increased together with "aaa" and
"ccc". But `M-x describe-face RET foo-bar' says that "Inherit:
unspecified".
Looking at the manual, the node `(elisp) Basic Faces' says:
‘default’
The default face, whose attributes are all specified. All other
faces implicitly inherit from it: any unspecified attribute
defaults to the attribute on this face (*note Face Attributes::).
So when you say that "it only enlarges those faces which inherit their
size from 'default'", doesn't that just mean that *any* face is resized,
unless that face itself or any its parents specify an absolute :height
(an integer)?
next prev parent reply other threads:[~2021-03-04 0:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 16:40 bug#46853: Confusing terminology "face height" instead of "font size" Stefan Kangas
2021-03-01 17:06 ` Eli Zaretskii
2021-03-01 19:31 ` Stefan Kangas
2021-03-01 19:46 ` Eli Zaretskii
2021-03-01 17:12 ` Lars Ingebrigtsen
2021-03-01 17:17 ` Eli Zaretskii
2021-03-01 19:15 ` Stefan Kangas
2021-03-01 19:25 ` Lars Ingebrigtsen
2021-03-01 19:33 ` Lars Ingebrigtsen
2021-03-01 19:37 ` Lars Ingebrigtsen
2021-03-01 19:50 ` Eli Zaretskii
2021-03-01 19:48 ` Eli Zaretskii
2021-03-01 20:05 ` Lars Ingebrigtsen
2021-03-01 20:17 ` Eli Zaretskii
2021-03-03 22:43 ` Stefan Kangas
2021-03-04 13:41 ` Eli Zaretskii
2021-03-04 18:05 ` Stefan Kangas
2022-06-19 23:27 ` Lars Ingebrigtsen
2021-03-01 19:35 ` Eli Zaretskii
2021-03-01 19:45 ` Lars Ingebrigtsen
2021-03-01 19:59 ` Eli Zaretskii
2021-03-04 0:16 ` Stefan Kangas [this message]
2021-03-04 13:46 ` Eli Zaretskii
2021-03-04 17:35 ` Stefan Kangas
2021-03-01 19:33 ` Eli Zaretskii
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=CADwFkmmoVW2xqLrWEPncHYb4jxbkd9NxYVHfOmb4PYP3i9ShWA@mail.gmail.com \
--to=stefan@marxist.se \
--cc=46853@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).