From: "Juanma Barranquero" <lekktu@gmail.com>
To: " Óscar Fuentes" <oscarfv@telefonica.net>
Cc: ofv@wanadoo.es, 597@emacsbugs.donarmstrong.com
Subject: bug#597: 23.0.60; Corrupted display.
Date: Wed, 23 Jul 2008 09:53:09 +0200 [thread overview]
Message-ID: <f7ccd24b0807230053i3615b6bci24b887724086c10c@mail.gmail.com> (raw)
In-Reply-To: <abg91lak.fsf@telefonica.net>
On Wed, Jul 23, 2008 at 02:44, Óscar Fuentes <oscarfv@telefonica.net> wrote:
> No. Just some blank boxes due to missing character sets.
Oh.
> It takes 2
> minutes to load and display the file on my Athlon 550 MHz, though.
Yes. Jason said that the time is spent looking up the fonts, which is
now much more thourough, but also much slower.
Juanma
next prev parent reply other threads:[~2008-07-23 7:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49297533.3040505@f2s.com>
2008-07-22 23:34 ` bug#597: 23.0.60; Corrupted display ofv
2008-07-23 0:01 ` Juanma Barranquero
2008-07-23 0:44 ` Óscar Fuentes
2008-07-23 7:53 ` Juanma Barranquero [this message]
2008-07-23 8:01 ` Jason Rumney
2008-07-23 13:06 ` ofv
2008-11-23 15:30 ` bug#597: marked as done (23.0.60; Corrupted display.) Emacs bug Tracking System
2008-08-01 14:42 ` bug#639: 23.0.60; tab bars use bizarre characters now Drew Adams
2008-11-23 15:30 ` bug#639: marked as done (23.0.60; tab bars use bizarre characters now) Emacs bug Tracking System
2008-08-02 20:23 ` bug#642: 23.0.60; garbled text (wrong font?) in About GNU Emacs screen Drew Adams
2008-08-02 21:05 ` Jason Rumney
2008-08-02 21:27 ` Drew Adams
2008-08-05 13:58 ` Drew Adams
2008-10-29 21:14 ` Drew Adams
2008-11-17 8:15 ` Drew Adams
2008-11-23 15:30 ` bug#642: marked as done (23.0.60; garbled text (wrong font?) in About GNU Emacs screen) Emacs bug Tracking System
2008-11-29 22:50 ` bug#642: 23.0.60; garbled text (wrong font?) in About GNU Emacs screen Drew Adams
2008-11-30 3:07 ` Jason Rumney
2008-12-22 21:30 ` Drew Adams
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=f7ccd24b0807230053i3615b6bci24b887724086c10c@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=597@emacsbugs.donarmstrong.com \
--cc=ofv@wanadoo.es \
--cc=oscarfv@telefonica.net \
/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).