From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 26402@debbugs.gnu.org, Gennady Uraltsev <gennady.uraltsev@gmail.com>
Subject: bug#26402: 25.2; Font rendering extremely slow on any non-default font
Date: Sun, 17 Nov 2019 08:47:36 +0100 [thread overview]
Message-ID: <871ru7c5bb.fsf@gnus.org> (raw)
In-Reply-To: <83tw5xlrl7.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Apr 2017 14:59:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> The function we are interested in is font-info, or Ffont_info on the C
> level. Its code is in the file font.c around line 5100. It calls
> various other functions, like fs_query_fontset and font_open_by_name.
> I'd like to know which one of them takes most of the time, then drill
> down into that function and find out which of its subroutines takes
> most of the time, etc. One way of doing that is step through the code
> and find the line whose execution takes a perceptible time.
This was two years ago, and there was no followup. I'm not able to
reproduce the problem here, and the font machinery in Emacs has changed
substantially in Emacs 27, so I'm closing this bug report.
If this is still a problem, please reopen.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2019-11-17 7:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-08 13:48 bug#26402: 25.2; Font rendering extremely slow on any non-default font Gennady Uraltsev
2017-04-08 14:44 ` Eli Zaretskii
2017-04-08 14:54 ` Gennady Uraltsev
2017-04-08 16:10 ` Eli Zaretskii
[not found] ` <541302bf-540b-aedb-4ca4-2ba3acfe495e@gmail.com>
2017-04-08 17:18 ` Eli Zaretskii
2017-04-08 22:33 ` Gennady Uraltsev
2017-04-09 5:44 ` Eli Zaretskii
2017-04-09 9:45 ` Eli Zaretskii
2017-04-09 11:07 ` Gennady Uraltsev
2017-04-09 11:59 ` Eli Zaretskii
2019-11-17 7:47 ` Lars Ingebrigtsen [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
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=871ru7c5bb.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=26402@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gennady.uraltsev@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).