GNU bug report logs - #23926
defcustom with STANDARD=<non-constant-expression> gives confusing results

Previous Next

Full log

Message #22 received at 23926 <at> debbugs.gnu.org (full text, mbox):

From: Noam Postavsky <npostavs <at> users.sourceforge.net>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 23926 <at> debbugs.gnu.org
Subject: Re: bug#23926: defcustom with STANDARD=<non-pure-expression> gives
 confusing results
Date: Sat, 9 Jul 2016 08:55:48 -0400

On Sat, Jul 9, 2016 at 8:31 AM, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> From: npostavs <at> users.sourceforge.net
>> Cc: 23926 <at> debbugs.gnu.org
>> 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.

What actually happens is that Emacs goes back in time to change what
the original value was? Perhaps the dates in etc/future-bug are wrong
then ;)

>
>> I wonder why Emacs saves only the original expression and not the
>> actual original value?
>
> It does, but then it reevaluates at startup.

It seems it's also reevaluated every time the variable is looked at
with customize, or describe-variable.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.