all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Kevin Yu <yujie052@gmail.com>, 1952@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug <emacs-pretest-bug@gnu.org>
Subject: bug#1952: 23.0.60[W32-Mingw]; opening etc/HELLO is slower than before
Date: Mon, 19 Jan 2009 22:14:06 +0800	[thread overview]
Message-ID: <49748AAE.6070509@gnu.org> (raw)
In-Reply-To: <42b562540901181840v1cfc73bbxec292b40aa4a60aa@mail.gmail.com>

"slower than before" means what exactly? Can you pinpoint the change 
that caused the slowdown? Or are you comparing with Emacs 22.3?

If the latter, then at least part of the slowdown can be attributed to 
the fact that Emacs 23 is finding all the fonts it can to display the 
characters in etc/HELLO correctly, while Emacs 22.3 displays about half 
the languages as empty boxes, and another couple of languages as the 
font's "undefined" glyph.








  reply	other threads:[~2009-01-19 14:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <874ozowchu.fsf@cyd.mit.edu>
2009-01-19  2:40 ` bug#1952: 23.0.60[W32-Mingw]; opening etc/HELLO is slower than before Kevin Yu
2009-01-19 14:14   ` Jason Rumney [this message]
2009-01-19 14:52     ` Juanma Barranquero
2009-01-20 12:52       ` Jason Rumney
2009-01-20 15:49         ` Juanma Barranquero
2009-01-20 16:05           ` Jason Rumney
2009-01-20 16:21             ` Juanma Barranquero
2009-01-20  2:05     ` Kevin Yu
2009-01-20 12:23       ` Jason Rumney
2009-01-24 22:50   ` bug#1952: marked as done (23.0.60[W32-Mingw];opening etc/HELLO is slower than before) Emacs bug Tracking System
2009-01-22 13:22 ` bug#1990: 23.0.60; Emacs trying too hard to find fonts that don't exist Jason Rumney
2009-01-24 13:28   ` Juanma Barranquero
2009-01-24 14:02     ` Jason Rumney
2009-01-24 22:50   ` bug#1990: marked as done (23.0.60; Emacs trying too hard to find fonts that don't exist) Emacs bug Tracking System

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=49748AAE.6070509@gnu.org \
    --to=jasonr@gnu.org \
    --cc=1952@emacsbugs.donarmstrong.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=yujie052@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.