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

Previous Next

Full log

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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 23926 <at> debbugs.gnu.org, npostavs <at> users.sourceforge.net
Subject: Re: bug#23926: defcustom with STANDARD=<non-pure-expression> gives
 confusing results
Date: Sat, 09 Jul 2016 19:52:36 +0300

> Date: Sat, 9 Jul 2016 14:59:06 +0000 (UTC)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: npostavs <at> users.sourceforge.net, 23926 <at> debbugs.gnu.org
> 
> > > 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.

Yes, it was changed, because the value returned by the function
changes each time it's called.

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

Of course, I do.  Maybe you don't realize how many times Emacs
evaluates the value of a defcustom, but I do.

Previous Next

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