Re: Bug, probably related to Custom Themes.

["Richard M. Stallman" <rms@gnu.org>]

    But the user has some bad experiences with the new value and wants to
    get rid of it.  He chooses "Erase Customization" in a Custom buffer.

    _Now_ what is supposed to happen?  Do we restore the value set by foo
    or the "standard" value that would be in effect if there were no themes?

It should restore the value set by foo, because that's the only
consistent meaning.  It should get rid of "user" customizations,
but it cannot get rid of theme values.

    Loading a theme means installing a new set of defaults.  "Erase
    Customization" should restore the theme value.  If the user wants the
    no-themes default, he should set and save bar in a Custom buffer to
    the no-themes default, thereby making the no-theme default the user
    theme value which explicitly overrides any theme, present or future.
    That is the only way one can be consistent.

I agree.

In what way does the current behavior differ from that?

    I have the impression that the purpose of the:

    (custom-reset-variables
     '(bar nil))

    is to override foo's value and restore the no-themes default.

I'm not sure what that ought to do.  Looking at the doc string, it is
not clear that this case was intended to be used at all.

Thus, if it doesn't do anything useful, and it's not easy to make it
do anything useful, we could simply make it an error.