Stephen J. Turnbull
stephen at xemacs.org
Thu Feb 24 22:43:13 EST 2005
>>>>> "Hrvoje" == Hrvoje Niksic <hniksic at xemacs.org> writes:
Hrvoje> Could we try a list of default fonts? Anyway, I'm pretty
Hrvoje> sure I do have a "Courier" font on my installation.
Aidan is right, we should use "monospace" and let fontconfig do the
I think we should warn (although not in the inimitable jwz style! you
know, the xmodmap kvetching) if we detect something in the fontconfig
we don't grok, of course, but I don't think we should try to work
Hrvoje> I get the same crash with both 75 and 100 dpi, and I'm
Hrvoje> pretty sure I have the Vera font family, as I'm using it
Hrvoje> in other applications.
Very strange. I fixed a bogosity in my code that prevented the
fontconfig substitutions from getting properly applied, which may not
be in your xemacs yet (the src/ChangeLog is
2005-02-24 Stephen J. Turnbull <stephen at xemacs.org>
* objects-x.c (x_find_charset_font): ConfigSubstitute in the
_pattern_ before matching.
), but if you request a specific font that you do have by name, I
don't yet see why you would crash, even without that patch.
Can you give me a C backtrace? All the Lisp backtrace tells me is
that some fontconfig code is being called, but I don't see anything
wrong with the code just looking at it.
You should reenable the Xft debugging output, set debug_xft=1 in gdb.
If you do that, make sure you add the patch above which adds printout
of the truename of the font we're initializing. (The variable is
defined in xft-fonts.c if you want to do it permanently, but once
you've got XEmacs to stop crashing in font operations, that output
becomes completely uninteresting, until you start fiddling with Mule
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
More information about the XEmacs-Beta