From: Eli Zaretskii <eliz@gnu.org>
To: Fabrice Popineau <fabrice.popineau@gmail.com>
Cc: 30672@debbugs.gnu.org
Subject: bug#30672: 26.0.91, Font face lost ?
Date: Fri, 02 Mar 2018 12:59:53 +0200 [thread overview]
Message-ID: <83k1uuwxna.fsf@gnu.org> (raw)
In-Reply-To: <CAFgFV9M89wCk+LCv2gGb+D7ufq7yPFVcfTZQncKsw0D7Z0KZag@mail.gmail.com> (message from Fabrice Popineau on Fri, 2 Mar 2018 11:29:11 +0100)
> From: Fabrice Popineau <fabrice.popineau@gmail.com>
> Date: Fri, 2 Mar 2018 11:29:11 +0100
> Cc: 30672@debbugs.gnu.org
>
> then please explain what you mean by
> "the font face is lost".
>
> (I cannot afford repeating your recipe, because it requires installing
> weird fonts on my system. Sorry.)
>
> I attach 2 screen captures to show the problem.
>
> First image is the glyph selection and second image shows that the font has been lost
> somehow ("no font available").
Thanks, but the images don't provide the important information
required to understand what is going on. The characters used by those
fonts to display the icons are from Private Use Areas (PUA) of the
Unicode codepoints, so it is quite OK for Emacs not to support them
without tricks or customizations. It is those tricks that I expected
you to describe -- what does the package do to display these PUA
characters in the buffer(s) where you do see them. Probably some
specialized text properties or some such (which is why I asked about
yank-excluded-properties). E.g., what does describe-text-properties
say about those icons in the buffer where they display as icons?
> I hope it is not related to my own build with mingw64 but it has definitely worked with
> some previous version of the same emacs-26 branch. Without any other clue,
> I'll try to rewind the branch and see if I can track some related change.
You could try bisecting, but I think a better way forward would be to
understand how the package arranges for these PUA characters to
display as icons, then we might get an idea which changes to look for.
One way of making these codepoints display everywhere as glyphs from
those special fonts is to customize your fontset, btw.
next prev parent reply other threads:[~2018-03-02 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 20:40 bug#30672: 26.0.91, Font face lost ? Fabrice Popineau
2018-03-02 8:53 ` Eli Zaretskii
2018-03-02 10:29 ` Fabrice Popineau
2018-03-02 10:59 ` Eli Zaretskii [this message]
2018-03-02 11:17 ` Eli Zaretskii
2018-03-07 14:22 ` Fabrice Popineau
2018-03-07 18:08 ` Eli Zaretskii
2018-03-07 21:11 ` Fabrice Popineau
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=83k1uuwxna.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30672@debbugs.gnu.org \
--cc=fabrice.popineau@gmail.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).