From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Kenichi Handa <handa@gnu.org>
Cc: 11484@debbugs.gnu.org
Subject: bug#11484: 23.4; Scrolling leaves traces of old text behind
Date: Tue, 23 Oct 2012 08:59:35 -0400 [thread overview]
Message-ID: <jwvhapl8i3y.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87txtlvlkf.fsf@gnu.org> (Kenichi Handa's message of "Tue, 23 Oct 2012 13:50:24 +0900")
> I think the better way is to do something like this:
> if (NILP (spec))
> signal_error ("Invalid font name", ascii_font);
OK, that makes sense, it gives me:
Debugger entered--Lisp error: (error "Invalid font name" "-Misc-Fixed-normal-normal-semi-condensed-*-13-*-*-*-c-60-iso10646-1")
but I have no idea where this "semi-condensed" comes from. The full
backtrace shows that it was generated "internally". My guess is that
xft returns a font info where the width says "semi-condensed", so "turn
it into an XFD and parse it back" ends up failing.
Stefan
Debugger entered--Lisp error: (error "Invalid font name" "-Misc-Fixed-normal-normal-semi-condensed-*-13-*-*-*-c-60-iso10646-1")
internal-set-lisp-face-attribute(default :width normal #<frame emacs@pastel 0x8a52c10>)
set-face-attribute(default #<frame emacs@pastel 0x8a52c10> :width normal :weight normal :slant normal :font "-misc-fixed-*-r-semicondensed-*-13-*-*-*-*-*-*-*")
font-setting-change-default-font(":0.0" nil)
dynamic-setting-handle-config-changed-event((config-changed-event font-render ":0.0"))
call-interactively(dynamic-setting-handle-config-changed-event nil [(config-changed-event font-render ":0.0")])
next prev parent reply other threads:[~2012-10-23 12:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 22:02 bug#11484: 23.4; Scrolling leaves traces of old text behind Frank Marcoline
2012-10-21 19:07 ` Jan Djärv
2012-10-21 19:56 ` Eli Zaretskii
2012-10-22 5:07 ` Jan Djärv
2012-10-22 5:11 ` Daniel Colascione
2012-10-22 13:19 ` Stefan Monnier
2012-10-22 15:06 ` Kenichi Handa
2012-10-23 1:22 ` Stefan Monnier
2012-10-23 4:50 ` Kenichi Handa
2012-10-23 12:59 ` Stefan Monnier [this message]
2012-10-22 17:27 ` Achim Gratz
2012-10-22 17:33 ` Eli Zaretskii
2012-10-22 17:29 ` Eli Zaretskii
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=jwvhapl8i3y.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=11484@debbugs.gnu.org \
--cc=handa@gnu.org \
/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).