GNU bug report logs - #2334
23.0.90; emacs-snapshot has ugly fonts when using set-default-font elisp function

Previous Next

Package: emacs;

Reported by: "Theodore Ts'o" <tytso <at> mit.edu>

Date: Sun, 15 Feb 2009 05:40:04 UTC

Severity: normal

Done: Chong Yidong <cyd <at> stupidchicken.com>

Bug is archived. No further changes may be made.

Full log


Message #35 received at 2334-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Kenichi Handa <handa <at> m17n.org>
Cc: tytso <at> mit.edu, 2334-done <at> debbugs.gnu.org
Subject: Re: 23.0.90; emacs-snapshot has ugly fonts when using set-default-font elisp function
Date: Wed, 18 Feb 2009 22:18:11 -0500
Kenichi Handa <handa <at> m17n.org> writes:

> I at first want to figure out why the above two methods for
> seting a font are different.  At least, I can't reproduce
> the difference.  Can you?  When I have "dejavu sans mono"
> fonts both for fontconfig and X as below, both methods set
> the default font to X font.

If the frame is already using an XFT font, doing

 (set-face-attribute 'default (selected-frame)
                     :font "DejaVu Sans Mono 10")

will give an XFT (anti-aliased) version of DejaVu Sans Mono.  If the
frame is using an X font, the same code gives the X version of DejaVu
Sans Mono.

Doing

  (modify-frame-parameters (selected-frame)
     (list (cons 'font "DejaVu Sans Mono 10")))

always returns the X version.  This discrepancy is due to the use of
font_open_by_name instead of font_load_for_lface.

I don't think there is anything that need to be corrected, apart from
giving the XFT driver a higher priority; I've just done that.




This bug report was last modified 16 years and 99 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.