RE: can't set both mode-line color and default frame font?

[Davis Herring]

> OK, but that argues that .emacs or `custom-file' is generally a better
> place to customize than X resources, because it is more flexible/powerful.
> I'm not sure that argument speaks to the question of precedence when
> multiple customization sources are employed. It is not uncommon to have a
> less flexible decision mechanism assume higher precedence/priority.

Emacs Lisp can also choose not to customize something at all.  So if it
does choose to do so, that has greater weight than the opinion of
something which only ever has one.

We could of course use that power/flexibility to define ways of specifying
customizations that did and others that did not override X resources (or
whatever other source), or simply provide a way to (perhaps in the middle
of some Lisp customizations) reapply the X resources as desired.  These
would be more complicated than a fixed precedence, but they might be
simpler than trying to make one mechanism dodge out of the way of the
other.

Davis

-- 
This product is sold by volume, not by mass.  If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.