Re: Customize buttons that change user's custom fileshouldaskforconfirmation

["Lennart Borgman" <lennart.borgman.073@student.lu.se>]

----- Original Message ----- 
From: "Richard Stallman" <rms@gnu.org>

> One possible solution for that is to discourage, or even get rid of,
> of the per-variable command button.  If there is only the whole-buffer
> Set and the whole-buffer Save, this confusion won't happen.

I do not think that is a good solution because the customization buffer
might be a result of a search.

> ISTR that I have seen apps where there is no difference between the
> field value and the active value within the customization tool, but
> all the changes require confirmation when you exit the customization
> tool.

It is an unusual behaviour I think. Maybe it is because it is tedious?

> The concept of "exiting" does not make sense for a Custom buffer, but
> there could be a buffer-wide Activate command, "Put this in effect",
> which combines Set and Save.  If that were the only way to make values
> take effect, it would be a lot simpler than the current Custom
> facility.

It is rather common on w32 that there is an Apply command which does this.

> In addition to Activate, there would be Cancel and Standard Values.
> And perhaps What's Changed, which says what would change if you use
> Activate right now.

I miss the Set button. IMO opinion the names you propose makes it a bit more
difficult to have a Set button.