unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>, David Ponce <da_vid@orange.fr>,
	37473@debbugs.gnu.org
Subject: bug#37473: 27.0.50; antialias setting is not preserved by, inheriting
Date: Mon, 20 Jun 2022 00:47:39 +0200	[thread overview]
Message-ID: <874k0gtgms.fsf@gnus.org> (raw)
In-Reply-To: <83k09cmpn6.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 19 Jun 2022 22:14:53 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> First, why is :antialiasing being singled out? won't the same happen
> for any attribute in FONT_EXTRA_INDEX, like :hinting, :hintstyle, and
> whatnot?

Yes, that's a bug -- there's all kinds of extra stuff, and :antialiasing
isn't special.

> And in addition, why does it make sense to reset foundry, family,
> registry, and adstyle of the font in attrs[]? don't we want the same
> font, for example, when resizing the text?
>
> IOW, do we really understand the reason for bug#37473?  Not the commit
> which introduced it, but the reason why :antialiasing is being reset
> and doesn't appear in attrs[] and in the realized face?  If so, could
> someone please spell that out?

bug#17973 was fixed by disregarding the font spec completely so that
font_load_for_lface would be free to recompute those bits:

> The patch below expresses the first part, but it looks like the second
> part doesn't exit: Emacs just doesn't find any font to use for the "thin
> space" of C-x SPC and indicates it to me with one of those big squares
> that say "0020", which is a lot more intrusive than the problem I'm
> trying to fix.

But that gets rid of all the data, which is what I attempted to fix.  I
think a better fix would just be to start with a blank spec and copy
:extra -- but I wasn't able to make that work.  That is, I needed to
copy more, but I wasn't able to determine what.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2022-06-19 22:47 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 [this message]
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
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=874k0gtgms.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=37473@debbugs.gnu.org \
    --cc=da_vid@orange.fr \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).