Re: custom-themes BAD?

[W . Greenhouse]

Rainer M Krug <Rainer@krugs.de> writes:

> Dan Espen <despen@verizon.net> writes:

[...]

>> It should be a simple matter for all themes to run a hook that removes
>> the previous theme.  Then have each theme define it's own hook function.
>> But removing a face won't revert to the prior face, so each theme would
>> have to query the current setting, then save it in the hook function
>> for removal.
>
> Exactly - should not be to difficult to implement.

The by-default-cumulative behavior of themes is confusing to newbies,
but there is already `disable-theme'.  `load-theme' does not normally
call `disable-theme' on the rest of `custom-enable-themes' prior to
loading a new one, but you could advice it to do so.  See also M-x
customize-themes, which already is hooked up to enable one theme at a
time, removing others.