RE: Customize buttons that change user's custom file should ask forconfirmation

[Drew Adams]

        For example, if you accidentally or mistakenly click
        mouse-1 (or mouse
        2) on the text (button) Reset to Standard (Erase Customization), all
        of your customizations in your custom file are wiped out!
        (all of the
        preferences that were visible in the Customize buffer, that
        is - which
        might be all of them).

    That is a good point.  Maybe these buttons should ask for confirmation
    with yes-or-no-p.

See my previous message (Subject: Custom-reset-standard has different menu
names). How about separating the two things this button does into two
buttons:

1) "Default Values" - resets to default (= installed) settings

2) "Save" - the existing button. It would update the custom file to use the
installed settings. It would have to smart enough to do what Erase
Customization does now: remove stuff, rather than adding stuff, to get back
to the default settings.

 - Drew