unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Greg A. Woods" <woods@robohack.ca>
Cc: 53924@debbugs.gnu.org
Subject: bug#53924: 26.1; fontification sometimes fails for some characters despite available glyphs
Date: Wed, 16 Feb 2022 05:36:24 +0200	[thread overview]
Message-ID: <83k0dv32kn.fsf@gnu.org> (raw)
In-Reply-To: <m1nKA7D-0036s20@more.local> (woods@robohack.ca)

> Date: Tue, 15 Feb 2022 18:32:23 -0800
> From: "Greg A. Woods" <woods@robohack.ca>
> CC: GNU Emacs Bug Reports <53924@debbugs.gnu.org>
> 
> Hopefully this message encodes properly, it should be text/plain, in
> the ISO10646-1 charset, with BASE64 encoding.
> 
> Run "emacs -q" in the debugger, switch to the *scratch* buffer and
> insert the forms below, then:
> 
> M-x eval-buffer <return>
> 
> Switch to the new *Font Families* buffer and scroll slowly through it.
> Depending on how many fonts you have installed, and how, and what kind
> of resources your system(s) have, this could take quite a long time.
> 
> If that doesn't trigger a crash try going back to the beginning,
> increase the text scale with C-u C-x C-+ and scroll through again.
> 
> This seems to reliably cause the crash for me, at least with the Git
> master version I have built using the lucid toolkit..

Like I said before: please try to figure out which font causes the
crashes, and post a recipe with that font alone.  Otherwise, trying to
reproduce this is a huge waste of time, because the results depend
critically on the fonts actually installed on the system.

Thanks.





  reply	other threads:[~2022-02-16  3:36 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-10 19:02 bug#53924: 26.1; fontification sometimes fails for some characters despite available glyphs Greg A. Woods
2022-02-10 20:21 ` Eli Zaretskii
2022-02-10 23:34   ` Greg A. Woods
2022-02-11  7:15     ` Eli Zaretskii
2022-02-11 21:56       ` Greg A. Woods
2022-02-13  6:06       ` Greg A. Woods
2022-02-13 11:53         ` Eli Zaretskii
2022-02-15  2:01           ` Greg A. Woods
2022-02-15 14:21             ` Eli Zaretskii
2022-02-15 22:04               ` Greg A. Woods
2022-02-16  2:32               ` Greg A. Woods
2022-02-16  3:36                 ` Eli Zaretskii [this message]
2022-02-16 21:55                   ` Greg A. Woods
2022-02-16 22:14                 ` Lars Ingebrigtsen
     [not found] ` <handler.53924.B.164452023325832.ack@debbugs.gnu.org>
2022-02-10 22:42   ` Greg A. Woods

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=83k0dv32kn.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53924@debbugs.gnu.org \
    --cc=woods@robohack.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).