Re: reducing defface redundancy

[Richard Stallman]

    Remember, by default (unless you select `Show All Display Specs'), the
    face customization widget basically tosses out all the clauses of the
    current defface spec except the active one.  So, 99% of the time, the
    user only deals with the _current_ definition of a face, and is happy.

Simple face customization is clean now because it affects just one
alternative, and it is easy and well-defined to select just the
alternative that applies.

With your propose defface change, the attributes actually specified
would not come from a single alternative in a simple way.  So the
customization of the active parts of the defface spec would raise
difficult issues.  If the user adds a new attribute, where in the
structure does it go?