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

[Drew Adams]

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

    Isn't the backup file for the custom file sufficient in case of this?

Strictly speaking, yes. But insufficient if we're aiming to reduce
inadvertent error and loss. You could accidentally hit it twice, with
interim changes, for instance.

Relying on users to 1) recognize that they accidentally saved options, 2)
know about the backup file, and 3) recuperate the backup file, is
blindfolding ourselves. Without any feedback (let alone confirmation) for
#1, I expect that lots of people will save options without even realizing
it.

But, as I said, this one (Save Options) is much more minor than the
Customize button pb.