From: Kenichi Handa <handa@m17n.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: cyd@stupidchicken.com, 1990@emacsbugs.donarmstrong.com
Subject: bug#1990: 23.0.60; Emacs trying too hard to find fonts that don't exist
Date: Mon, 26 Jan 2009 20:46:35 +0900 [thread overview]
Message-ID: <E1LRPvH-000554-S8@etlken> (raw)
In-Reply-To: <f7ccd24b0901250357p6ac606beh67a4f2d4562e6230@mail.gmail.com> (message from Juanma Barranquero on Sun, 25 Jan 2009 12:57:41 +0100)
In article <f7ccd24b0901250357p6ac606beh67a4f2d4562e6230@mail.gmail.com>, Juanma Barranquero <lekktu@gmail.com> writes:
> On Sun, Jan 25, 2009 at 06:22, Jason Rumney <jasonr@gnu.org> wrote:
> > That looks much better though. Before, each "font for:" log entry was
> > followed by a dozen or so "list:" entries, which is what takes excessive
> > time on Windows.
> They still are. That was the output of M-occur on the *Help* buffer.
> For example, that's the result of
> emacs -Q
> C-h H
> M-: (setq font-log nil)
> M-x font-show-log
> font for: (1513 . hebrew-iso8859-8)
> list: -outline-DejaVu Sans Mono-*-mono-*-iso10646-1:script=hebrew
> list: -outline-DejaVu Sans Mono-*-iso10646-1:script=hebrew
> list: -*-DejaVu Sans Mono-*-mono-*-iso10646-1:script=hebrew
> list: -*-DejaVu Sans Mono-*-iso10646-1:script=hebrew
> list: -outline-*-mono-*-iso10646-1:script=hebrew
> list: -outline-*-iso10646-1:script=hebrew
> list: -*-mono-*-iso10646-1:script=hebrew
> list: -*-iso10646-1:script=hebrew
[...]
As there's no logs from the font-backend's `list' method,
the above listings actually did cache looking up only, and
thus they should not be that slow. If you do:
M-: (setq font-log nil)
before C-h H, you'll see logs from the font-backend (labeled
"uniscribe-list:" or "w32font-list:" on Windows).
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-01-26 11:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 5:04 bug#1990: 23.0.60; Emacs trying too hard to find fonts that don't exist Chong Yidong
2009-01-23 14:00 ` Jason Rumney
2009-01-24 19:47 ` Chong Yidong
2009-01-24 21:50 ` Juanma Barranquero
2009-01-24 21:55 ` Chong Yidong
2009-01-24 22:06 ` Juanma Barranquero
2009-01-25 5:22 ` Jason Rumney
2009-01-25 11:57 ` Juanma Barranquero
2009-01-26 11:46 ` Kenichi Handa [this message]
2009-01-26 12:02 ` Juanma Barranquero
2009-01-26 8:00 ` Kenichi Handa
2009-01-26 15:51 ` Chong Yidong
-- strict thread matches above, loose matches on Subject: below --
2009-01-22 13:22 Jason Rumney
2009-01-24 13:28 ` Juanma Barranquero
2009-01-24 14:02 ` Jason Rumney
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=E1LRPvH-000554-S8@etlken \
--to=handa@m17n.org \
--cc=1990@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=lekktu@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).