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

[Drew Adams]

    Instead of "Erase Customizations":

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

        2) "Save" - the existing button. It would update the custom
           file to use the installed settings.

    This seems like a good idea.  Does anyone see a problem with it?

A similar problem, though not as serious, is that Save Options in the
menu-bar Options menu does not ask for confirmation. If you accidentally
choose this item instead of another, then you might need to fix things up
afterward.

I think that anything like this that affects a user's custom file should ask
for confirmation - or at least make an option (and the default).