Re: Customize buttons that change user's custom fileshouldaskforconfirmation

[Richard Stallman <rms@gnu.org>]

    But the problem is exactly that he may _not_ be satisfied with all the
    current "settings" (widget values).  He may just have wanted to set
    them, or even more likely, just has been looking at them.

The arguments you are making are arguments for complexity.  That is
the wrong approach for designing a user interface to help beginners.
So please stop raising such arguments.

We need to design a simple interface that is easy for beginners to
understand, so that they are not afraid to use it.  This means
rejecting the goal that it should be able to do "whatever the user
might want to do".  We have to design it to do the most common things
in the most straightforward way.

So please stop making arguments about "but maybe the user only wants X".

      Other
    interfaces are not trying to handle an underlying customization system
    that is anywhere as complex and extensive as Emacs'.

This is no excuse for making it more complex than it has to be,
so please don't mention it.

							  The average
    Custom buffer is a lot longer and contains a lot more options than the
    average customization "page" (or whatever they call it).

If that is a real cause of difficulty, lets subdivide the groups more.

      The choices
    you have for an individual option can be a lot more complex.  Complex
    types like `choice' force a concept of a `widget' value.

What do you mean by a "widget" value?