From: Drew Adams <drew.adams@oracle.com>
To: "Charles A. Roelli" <charles@aurox.ch>,
Drew Adams <drew.adams@oracle.com>
Cc: 30539@debbugs.gnu.org
Subject: bug#30539: 26.0; `char-displayable-p' is much slower in Emacs 25 and 26
Date: Wed, 28 Feb 2018 11:53:49 -0800 (PST) [thread overview]
Message-ID: <9c58c5b3-dccc-4b8e-a5b3-d4d23ba696e3@default> (raw)
In-Reply-To: <<m2d10oj4xj.fsf@aurox.ch>>
> But I have noticed that displaying files containing certain Unicode
> characters can lock Emacs for a little while. I wonder if that is
> also some manifestation of this bug. Do you also see a slow down when
> you visit a file containing the characters in the `char-names'
> variable you defined? Or is the slowness limited to running them
> through `char-displayable-p'?
If `inhibit-compacting-font-caches is `t' then there is no
slowdown in `char-displayable-p'. The slowdown is for chars
that are not displayable, it seems.
If such chars are inserted in a buffer where they are not
displayable (which happens in my case) then they appear
as rectangles enclosing the char code. There is no slowdown
displaying that - the chars themselves are not displayed.
(I was using `char-displayable-p' to optionally exclude
such chars from a list of chars and their descriptions.)
next parent reply other threads:[~2018-02-28 19:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<8c79c39f-7abb-4591-a676-17fb46af5a8f@default>
[not found] ` <<ec3497d7-9a7d-4be8-8712-19bb6bdd96e8@default>
[not found] ` <<m2d10oj4xj.fsf@aurox.ch>
2018-02-28 19:53 ` Drew Adams [this message]
2018-02-19 22:07 bug#30539: 26.0; `char-displayable-p' is much slower in Emacs 25 and 26 Drew Adams
2018-02-20 18:08 ` Drew Adams
2018-02-22 14:50 ` Drew Adams
2018-02-23 1:49 ` Noam Postavsky
2018-02-23 2:43 ` Drew Adams
2018-02-23 3:32 ` Noam Postavsky
2018-02-23 4:07 ` Drew Adams
2018-02-23 7:14 ` Eli Zaretskii
2020-06-27 21:34 ` Drew Adams
2020-11-18 15:35 ` Stefan Kangas
2020-11-18 17:21 ` Eli Zaretskii
2020-11-18 18:30 ` Stefan Kangas
2018-02-28 19:21 ` Charles A. Roelli
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=9c58c5b3-dccc-4b8e-a5b3-d4d23ba696e3@default \
--to=drew.adams@oracle.com \
--cc=30539@debbugs.gnu.org \
--cc=charles@aurox.ch \
/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).