all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: duncan@bayne.id.au
Cc: rpluim@gmail.com, 74337-done@debbugs.gnu.org
Subject: bug#74337: 29.4; Visiting a file with Unicode emojis is very slow
Date: Sat, 30 Nov 2024 11:53:04 +0200	[thread overview]
Message-ID: <864j3p9hfj.fsf@gnu.org> (raw)
In-Reply-To: <86frnrgvo4.fsf@gnu.org> (message from Eli Zaretskii on Sat, 16 Nov 2024 15:22:51 +0200)

> Cc: 74337@debbugs.gnu.org, rpluim@gmail.com
> Date: Sat, 16 Nov 2024 15:22:51 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Duncan Bayne <duncan@bayne.id.au>
> > Cc: Eli Zaretskii <eliz@gnu.org>, 74337@debbugs.gnu.org
> > Date: Sat, 16 Nov 2024 22:29:46 +1100
> > 
> > Installing Symbola "fixed" the issue - visiting the file is now almost
> > instantaneous.
> > 
> > So it looks like the *actual* issue might be: visiting a file with a
> > codepoint that doesn't match any installed fonts takes minutes?
> 
> Yes, but only if you have a very large number of fonts installed, none
> of which supports that codepoint.  Because Emacs will try all of the
> fonts that could potentially have a glyph for the codepoint.

No further comments in 2 weeks, so I'm closing this bug.





      reply	other threads:[~2024-11-30  9:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-13 12:13 bug#74337: 29.4; Visiting a file with Unicode emojis is very slow Duncan Bayne
2024-11-13 15:10 ` Eli Zaretskii
     [not found]   ` <861pzeevpy.fsf@bayne.id.au>
2024-11-13 20:33     ` Eli Zaretskii
2024-11-13 20:47       ` Duncan Bayne
2024-11-14  6:41         ` Eli Zaretskii
2024-11-14 11:42           ` Duncan Bayne
2024-11-14 14:31             ` Eli Zaretskii
2024-11-14 14:49               ` Robert Pluim
2024-11-16 11:29                 ` Duncan Bayne
2024-11-16 13:22                   ` Eli Zaretskii
2024-11-30  9:53                     ` Eli Zaretskii [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864j3p9hfj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=74337-done@debbugs.gnu.org \
    --cc=duncan@bayne.id.au \
    --cc=rpluim@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.