Re: custom-file should be allowed to be an alist

Re: custom-file should be allowed to be an alist

[Richard Stallman]

    Some people like sorting their various customization variables into
    different files so as to keep them under version control, and to see
    what they have there, or so that they can exchange some files for
    functionality they want to have configured sometimes so, sometimes
    so.  How to support this?  Well, if custom-file was an alist, one
    could just look up the group of the variable to be customized in it,
    and associate a filename with it.  If the group is not in there, take
    the parent group and repeat.  Top groups of course have a parent of
    nil.  That way, a cons cell with nil in its car would serve as a
    fallback for variables which have no group in their ancestry
    specified.

It seems like a reasonable feature if someone wants to do it.