Paul Stodghill <stodghil(a)cs.cornell.edu> writes:
Suppose that you use .Xdefaults to setup the 'default face when
you are
But suppose that you use customize to set up 'default when you are running
under mswindows,
Then you lose. Partly by design unfortunately. You can not mix
resources and customize (for now).
(custom-set-faces
'(default ((((type mswindows) (class color))
(:foreground "white" :background "black"))) t)
...)
However: One could argue that in this case customize is being to
zealous as...
faces.el contains the following code around line 1210 or so...
(let ((frames (relevant-custom-frames)))
none of the 'frames' will later match any of the settings and thus no
settings will be applied.
Is it that x-init-global-faces is called in face-spec-set?
Yes, but that is intentional.
It wasn't in 20.4,
and everything seemed to work fine.
Note the "seemed". There were just other failure modes.
Is it that x-init-global-faces doesn't call
x-init-face-from-resources to try
to setup 'default?
No it shouldn't. Note that face-spec-set does call
init-face-from-resources later.
So what should have happened (under X) was:
- reset face is called
- x-init-global-faces is called. This basically resets the 'default
face to the compiled in values.
- customize calls 'face-display-set', but as none of the display specs
matches the (type mswindows) the default font the 'default face is
is not modified.
- init-face-from-resources is called. As the the default face has not
been modified the X resources should be used.
Could you find out why that does not work for you?
Jan