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

From: Eli Zaretskii <[email-masked]>
Date: Sat, 09 Jul 2016 17:12:11 +0300

> Date: Sat, 9 Jul 2016 14:09:17 +0000 (UTC)
> From: Drew Adams <[email-masked]>
> Cc: [email-masked]
> 
> 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, because each time the sexp is evaluated it yields a
different value.  "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.

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

See above.