"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes:
(unless (equal face 'default) (reset-face face ...))
Jan> I think that is wrong.
Your example is correct. Too bad. Custom is inadequate here, because
you can't win. Your suggested default-saving breaks any later changes
the user makes to 'default. I gave an example of how it could break.
Of course Custom basically says "faces are mine, don't touch," and we
could document that and ignore it for 21.0, except that Mule users
have no choice but to use non-Custom interfaces like
`set-face-font'.
Custom already says "faces are mine, don't touch," for all the other
faces so I do not really why that should not be the case for the
default face.
are likely to have reservations about. Custom already has
mechanisms
for saving existing settings; it already uses them and you will have
to make sure that this default-saving behavior does not conflict with
them. Not worth it, IMO.
OK so we save the origional default face into the 'standard-value slot
used by custom. i.e. the default face behaves as if it was 'deffaced'
Jan