[Bug: 21.5-b29] Xemacs ignores custom.el
Mike Kupfer
mike.kupfer at xemacs.org
Sat Mar 5 18:45:07 EST 2011
Jerry James wrote:
> On Tue, Mar 1, 2011 at 11:53 AM, Rodney Sparapani <rsparapa at mcw.edu> wrote:
> > Right. Issue 411 is NOT that custom.el is NOT loaded; it is loaded.
> > The bug is that no action is taken with respect to fonts :o(
>
> Argh. I wish I had some clue what we should check next, Rodney. Or
> some clue how the font system works so we could make GDB do the dirty
> work for us. Is the problem that XEmacs fails to find the X font you
> want or, having found it, that it fails to apply it to the GUI? If
> anybody has a clue how to check either of those, please let us know.
I recall running into something similar to what Rodney is reporting, on
21.5 as well. I would set the font from the Options menu, and it would
look okay in that process. But when I restarted XEmacs (after invoking
Options>Save Options To Custom File), I got a different font. At the
time I chalked it up to the Xft work being incomplete and interacting
badly with the bitmap font support, so I didn't pursue it.
Here are the things I would look at:
* what does "M-! xrdb -query | grep -i font" report? (I know Rodney has
said there is nothing in .Xresources, but maybe something else is
creating font specifications behind his back.)
* run M-x edit-faces and see if it shows anything interesting. (In
particular, what font does it show for the default face. And do the
other faces seem derived from default, or do they seem to be derived
from something else.)
* set debug-x-fonts and debug-x-faces to a non-zero value and
see if XEmacs reports anything useful
mike
More information about the XEmacs-Beta
mailing list