Subject: bug#23926: defcustom with STANDARD=<non-pure-expression> gives confusing results

From: Drew Adams <[email-masked]>
Date: Sat, 9 Jul 2016 14:59:06 +0000 (UTC)

> > 2. Is it not a bug that Customize tells you that the value
> >    was changed outside Customize?  In what way was it
> >    changed outside Customize?  In fact, it was not even
> >    changed.
> 
> It was changed, 

The option value was changed?  I don't think so.

The standard value (labeled "original" in `C-h v') is changed
each time the sexp is evaluated.  But the option value is not.

The option value was not changed at all in the recipe Noam gave.
It was and remained exactly what it was from the defcustom.
The mere fact of entering Customize did not change its value,
and nothing else changed its value.  It still has the original
value from when the defcustom was evaluated.

> because each time the sexp is evaluated it yields a
> different value.

See above.

> "Outside Customize" means not by the user who is typing values
> into the Custom buffer and saves those values by using the
> "set state" menu.

Correct.  And nothing changed the option value at all.  Not
that way or any other way.  It remains as it was from defcustom.

> > How about the reverse: Why do you think this is not a bug?
> 
> See above.

See above.  Do you still think this is not a bug?