From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: customize-apropos
Date: Mon, 12 Dec 2005 19:55:24 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICOECHDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <200512130045.jBD0jnl08038@raven.dms.auburn.edu>
But current policy also shows non-customizable variables if you use
the numeric arg.
I have already told you: this is not a policy, but a way to _override_
a policy. The _default_ behavior (no numeric arg) is the policy. (If
not, Richard can correct me.)
Well, excuse me, but it is I who first used the term "current policy" in
this context - what _I_ meant was "current behavior". Whether or not you or
Richard considers the current numeric-argument behavior to be "the policy"
is irrelevant to my meaning. The context of my use of the term "current
policy" made it clear that I was referring to the numeric-argument behavior.
I kept the numeric arg just so if
anybody, for any reason whatsoever, had gotten used to it, they would
still be able to use it (although I seriously doubt that this applies
to a lot of people). That numeric argument is an *obscure unimportant
detail*. Let us just stop worrying about it.
Why you kept it is irrelevant at this point also - if the behavior exists,
people can use it, and some will. _You_ went to the trouble of changing the
doc strings to clarify this "*obscure unimportant detail*". Why did you
bother? I, for one, am glad you did.
I return to my original question:
"Wouldn't it be at least as useful to be able to show all user options
(i.e., including those that are not customizable) in a Custom buffer
as it is to show _all_ variables in a Custom buffer (i.e., including
those that a user should not change)?
If we keep the current [behavior] of showing stuff that cannot be
customized, then it would also be good to clearly indicate when a
user option [is not a defcustom option] and when a variable is
internal and should not be changed. That is, clearly distinguish
the three classes in a Custom buffer.
For "not customizable" and "cannot be customized", read "not defined with
defcustom".
next prev parent reply other threads:[~2005-12-13 3:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-10 3:47 customize-apropos Luc Teirlinck
2005-12-10 3:51 ` customize-apropos Luc Teirlinck
2005-12-10 23:04 ` customize-apropos Kim F. Storm
2005-12-10 23:07 ` customize-apropos Luc Teirlinck
2005-12-11 16:49 ` customize-apropos Richard M. Stallman
2005-12-11 5:03 ` customize-apropos Richard M. Stallman
2005-12-11 17:57 ` customize-apropos Drew Adams
2005-12-12 5:03 ` customize-apropos Luc Teirlinck
2005-12-12 5:40 ` customize-apropos Drew Adams
2005-12-12 23:56 ` customize-apropos Luc Teirlinck
2005-12-13 0:22 ` customize-apropos Drew Adams
2005-12-13 0:45 ` customize-apropos Luc Teirlinck
2005-12-13 3:55 ` Drew Adams [this message]
2005-12-13 1:01 ` customize-apropos Luc Teirlinck
2005-12-13 1:29 ` customize-apropos Luc Teirlinck
2005-12-13 23:33 ` customize-apropos Richard M. Stallman
2005-12-14 1:14 ` customize-apropos Luc Teirlinck
2005-12-14 1:25 ` customize-apropos Drew Adams
2005-12-14 2:13 ` customize-apropos Luc Teirlinck
2005-12-14 3:20 ` customize-apropos Drew Adams
2005-12-14 3:40 ` customize-apropos Luc Teirlinck
2005-12-14 3:52 ` customize-apropos Drew Adams
2005-12-14 5:58 ` customize-apropos Luc Teirlinck
2005-12-14 15:07 ` customize-apropos Drew Adams
2005-12-15 5:33 ` customize-apropos Luc Teirlinck
2005-12-15 16:33 ` customize-apropos Drew Adams
2005-12-16 5:09 ` customize-apropos Richard M. Stallman
2005-12-14 3:45 ` customize-apropos Luc Teirlinck
2005-12-14 3:54 ` customize-apropos Drew Adams
2005-12-14 20:02 ` customize-apropos Richard M. Stallman
2005-12-15 4:18 ` customize-apropos Luc Teirlinck
2005-12-16 1:51 ` customize-apropos Richard M. Stallman
2005-12-16 3:47 ` customize-apropos Luc Teirlinck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DNEMKBNJBGPAOPIJOOICOECHDAAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.