From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: 23926@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#23926: defcustom with STANDARD=<non-pure-expression> gives confusing results
Date: Sat, 9 Jul 2016 14:59:06 +0000 (UTC) [thread overview]
Message-ID: <c0dd88c2-51ef-4f4f-964c-f0254db970f7@default> (raw)
In-Reply-To: <<8337nihpdw.fsf@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.
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?
next parent reply other threads:[~2016-07-09 14:59 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<CAM-tV-8cG3gLgf-A+wBYPZWNy2WPGFV3uEdNE7=ad3oq4rXmnw@mail.gmail.com>
[not found] ` <<<83vb0fgu83.fsf@gnu.org>
[not found] ` <<443f2e44-5167-48e7-abc6-cce1e243461e@default>
[not found] ` <<8337nihpdw.fsf@gnu.org>
2016-07-09 14:59 ` Drew Adams [this message]
2016-07-09 16:52 ` bug#23926: defcustom with STANDARD=<non-pure-expression> gives confusing results Eli Zaretskii
2016-07-09 20:48 ` npostavs
2016-07-10 14:19 ` Eli Zaretskii
[not found] ` <<871t32ilm0.fsf@users.sourceforge.net>
[not found] ` <<83k2gtfue4.fsf@gnu.org>
2016-07-10 17:18 ` Drew Adams
2016-07-11 18:40 ` Eli Zaretskii
[not found] <<<<<CAM-tV-8cG3gLgf-A+wBYPZWNy2WPGFV3uEdNE7=ad3oq4rXmnw@mail.gmail.com>
[not found] ` <<<<<83vb0fgu83.fsf@gnu.org>
[not found] ` <<<<443f2e44-5167-48e7-abc6-cce1e243461e@default>
[not found] ` <<<<8337nihpdw.fsf@gnu.org>
[not found] ` <<<c0dd88c2-51ef-4f4f-964c-f0254db970f7@default>
[not found] ` <<<83zipqg3e3.fsf@gnu.org>
[not found] ` <<ff33c2cc-337a-433b-a87a-0ea1814311d2@default>
[not found] ` <<83bn24c8io.fsf@gnu.org>
2016-07-12 0:53 ` Drew Adams
[not found] <<CAM-tV-8cG3gLgf-A+wBYPZWNy2WPGFV3uEdNE7=ad3oq4rXmnw@mail.gmail.com>
[not found] ` <<83vb0fgu83.fsf@gnu.org>
2016-07-09 14:09 ` Drew Adams
2016-07-09 14:12 ` Eli Zaretskii
[not found] ` <<c0dd88c2-51ef-4f4f-964c-f0254db970f7@default>
[not found] ` <<83zipqg3e3.fsf@gnu.org>
2016-07-10 17:18 ` Drew Adams
2016-07-11 18:52 ` Eli Zaretskii
2016-07-09 3:11 Noam Postavsky
2016-07-09 6:31 ` Drew Adams
2016-07-09 7:13 ` Eli Zaretskii
2016-07-09 11:54 ` npostavs
2016-07-09 12:31 ` Eli Zaretskii
2016-07-09 12:55 ` Noam Postavsky
2016-07-09 13:14 ` Eli Zaretskii
2016-07-09 13:48 ` Noam Postavsky
2016-07-09 14:03 ` Eli Zaretskii
2016-07-12 3:26 ` npostavs
2016-07-12 5:20 ` Eli Zaretskii
2016-07-09 14:34 ` Drew Adams
[not found] ` <<8360sehps4.fsf@gnu.org>
2016-07-09 14:54 ` Drew Adams
2016-07-09 15:09 ` Drew Adams
2016-07-10 17:23 ` Drew Adams
2023-10-17 14:19 ` bug#23926: defcustom with STANDARD=<non-constant-expression> " Mauro Aranda
2023-10-17 14:29 ` Mauro Aranda
[not found] <<<<CAM-tV-8cG3gLgf-A+wBYPZWNy2WPGFV3uEdNE7=ad3oq4rXmnw@mail.gmail.com>
[not found] ` <<<<83vb0fgu83.fsf@gnu.org>
[not found] ` <<<443f2e44-5167-48e7-abc6-cce1e243461e@default>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0dd88c2-51ef-4f4f-964c-f0254db970f7@default \
--to=drew.adams@oracle.com \
--cc=23926@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=npostavs@users.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).