From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>,
"'Stephen Berman'" <stephen.berman@gmx.net>
Cc: 10907@debbugs.gnu.org
Subject: bug#10907: 24.0.94; Updating display of Customize buffer
Date: Tue, 28 Feb 2012 14:11:22 -0800 [thread overview]
Message-ID: <5D50FB57830546E49BA986F7932928F5@us.oracle.com> (raw)
In-Reply-To: <m2hayabzyo.fsf@igel.home>
> *Note (elisp) Customization Types::
> You specify the customization type in `defcustom' with
> the `:type' keyword. The argument of `:type' is evaluated,
> but only once when the `defcustom' is executed, so it isn't
> useful for the value to vary.
Having this in the Elisp manual helps developers, but it is not all that helpful
for a Customize user trying to understand the behavior.
Stephen described a purely end-user interaction. And yes, the behavior is not
obvious. We obviously felt it sufficiently non-obvious to add that paragraph to
the Elisp manual. End users deserve some info that helps them too understand a
bit.
At the least there seems to be an Emacs-manual doc bug here. Let's please add
something to help users navigate the labyrinth.
next prev parent reply other threads:[~2012-02-28 22:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 13:07 bug#10907: 24.0.94; Updating display of Customize buffer Stephen Berman
2012-02-28 13:46 ` Andreas Schwab
2012-02-28 15:19 ` Stephen Berman
2012-02-28 17:23 ` Andreas Schwab
2012-02-28 17:50 ` Stephen Berman
2012-02-28 18:00 ` Andreas Schwab
2012-02-28 18:33 ` Stephen Berman
2012-02-29 2:06 ` Stefan Monnier
2012-02-29 9:05 ` Andreas Schwab
2012-02-29 12:26 ` Stephen Berman
2012-02-29 19:45 ` Glenn Morris
2012-03-01 2:42 ` Stefan Monnier
2012-03-03 17:03 ` Stephen Berman
2022-04-21 13:49 ` Lars Ingebrigtsen
2012-02-29 4:00 ` Eli Zaretskii
2012-02-29 12:20 ` Stephen Berman
2012-02-28 22:11 ` Drew Adams [this message]
2012-02-28 23:11 ` Andreas Schwab
2012-02-29 1:01 ` Drew Adams
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=5D50FB57830546E49BA986F7932928F5@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=10907@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=stephen.berman@gmx.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).