Re: Custom themes and precedence

[Chong Yidong]

Dave Abrahams <address@hidden> writes:

> I customized default-frame-alist in the theme for machine X... which
> worked fine until I customized default-frame-alist "non-themedly"
> somewhere else.  That caused the new setting to go into the "user" theme
> *which takes precedence over all others*.  That last bit isn't working
> out so well for my use-case.  Should this usage be accomodated, is it
> outside the intended applications of themes, or...?

Non-theme customization settings are intended to take precedence over
theme settings.  The idea is that if you load a theme that's not written
by you, it is easy to use Customize to override some of its settings.
I think I understand the problem you have, but I don't have any easy
solution.