Re: Bug, probably related to Custom Themes.

[Luc Teirlinck]

Richard Stallman wrote:

       and makes you wonder what the shown values are
       (defaults, saved values?).

   That is good!  The values shown in the buffer are NOT
   in general the current values.

They are the current value _unless_ you edited the value.  They can
sometimes be the saved or standard value in addition to being the current
value, but they are shown _because_ they are the current value.  If
you change the current value, the shown value changes to the new
current value.

Anyway, the main thing the button does is to get rid of your edits.
It does not just temporarily show the current value, before you go
back to your edits.

The reason to press the "Reset to Current" button is to discard (or
revert or undo) your edits, so you do not accidentally set or save them.
The fact that it also again shows the current set value is a side effect.
That is why I proposed to rename "Reset to Current" to "Revert Edits"
or similar.  But the current "Reset to Current" is acceptable and
better than something which only emphasizes a side effect.

          What about "Cancel Customization", "Cancel Saved Settings",
          "Erase Saved Settings", etc?

       The last two would be misleading: it is not just going to cancel and
       erase saved values, but edited, set and rogue values as well.

   That is not a problem.  It is fine if the name of an operation
   describes only the most important thing it does.  The name need not
   describe all the lesser things the operation also does.

The most important thing it is going to do depends on whether the
value you apply it to is saved, set or edited.  Why use a misleading
two word term (Saved Settings) while you have a clear one word term
(Customization)?

Sincerely,

Luc.