From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, handa@gnu.org, 37473@debbugs.gnu.org,
monnier@iro.umontreal.ca, da_vid@orange.fr
Subject: bug#37473: 27.0.50; antialias setting is not preserved by, inheriting
Date: Mon, 20 Jun 2022 18:57:13 +0300 [thread overview]
Message-ID: <83sfnzl44m.fsf@gnu.org> (raw)
In-Reply-To: <87o7yn1gtx.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 20 Jun 2022 17:43:06 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: luangruo@yahoo.com, handa@gnu.org, 37473@debbugs.gnu.org,
> da_vid@orange.fr, Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Mon, 20 Jun 2022 17:43:06 +0200
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > And likely in other use cases: if the :font attribute of a face
> > specifies some font properties, we want to keep them all, not
> > arbitrarily to ignore some of them.
>
> Yup.
>
> > Specifically, I propose the change for the master branch. Any
> > objections?
>
> Not from me, but perhaps Handa-san has some comments.
Sure, there's no rush.
My main problem with that change is that I don't understand why would
it make sense to "forget" all the attributes of a font when realizing
a face whose :font attribute is non-nil. It's like ignoring the
foreground color when a face specifies it.
If there are special situations where some font attributes should be
"forgotten", we should perhaps have separate functions for them, which
we should call only in those special situations.
next prev parent reply other threads:[~2022-06-20 15:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-21 4:19 bug#37473: 27.0.50; antialias setting is not preserved by inheriting YAMAMOTO Mitsuharu
2022-05-20 10:42 ` Lars Ingebrigtsen
2022-06-19 13:02 ` Lars Ingebrigtsen
2022-06-19 16:43 ` bug#37473: 27.0.50; antialias setting is not preserved by, inheriting David Ponce
2022-06-19 18:28 ` Colin Baxter
2022-06-19 19:14 ` Eli Zaretskii
2022-06-19 22:47 ` Lars Ingebrigtsen
2022-06-20 0:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 11:57 ` Eli Zaretskii
2022-06-20 12:04 ` Lars Ingebrigtsen
2022-06-20 12:11 ` Eli Zaretskii
2022-06-20 12:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:16 ` Eli Zaretskii
2022-06-20 13:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-20 13:37 ` Eli Zaretskii
2022-06-20 14:11 ` Eli Zaretskii
2022-06-20 15:43 ` Lars Ingebrigtsen
2022-06-20 15:57 ` Eli Zaretskii [this message]
2022-06-30 6:17 ` 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=83sfnzl44m.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=37473@debbugs.gnu.org \
--cc=da_vid@orange.fr \
--cc=handa@gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).