Re: Bug, probably related to Custom Themes.

[Richard M. Stallman]

    If you save a "setting" (to use the brand new terminology) and then
    choose "Erase Customization" for the same setting, the no-themes
    default gets restored for the current session and for future sessions
    _until_ you choose "Erase Customization" for some _other_ setting.
    After that, the no-themes default stays into effect for the remainder
    of that session but for sessions started after that, the theme value is
    restored.

Yidong, could you fix this?  Erase Customization should remove the
`user' customization, and doing that consistently would put the theme
value back into effect.

               This, of course, makes no sense whatsoever.  This is no
    surprise.  Very few things in the current Themes code make any sense
    whatsoever.

Please don't exaggerate the negative.  Despite the existence of a few
bugs such as this one, the custom themes code basically works.
Now we'll fix this bug, and it will work even better.