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

From: Eli Zaretskii <[email-masked]>
Date: Sat, 09 Jul 2016 15:31:42 +0300

> From: [email-masked]
> Cc: [email-masked]
> Date: Sat, 09 Jul 2016 07:54:58 -0400
> 
> Yeah, it seems expected because you're familiar with the code.  But it
> causes Emacs to claim the "original" value is different from what it
> originally was, which seems nonsensical.

It's not nonsensical, it's what actually happens, AFAIK.

> I wonder why Emacs saves only the original expression and not the
> actual original value?

It does, but then it reevaluates at startup.