From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: customize-apropos
Date: Sun, 11 Dec 2005 09:57:53 -0800 [thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICKEAMDAAA.drew.adams@oracle.com> (raw)
In-Reply-To: <200512100347.jBA3lr917144@raven.dms.auburn.edu>
Variables should not be included in the customize-apropos output
just because their docstring starts with a `*'. If a variable
should appear in a customization buffer, one should define it
with defcustom.
The patch below fixes these two problems. If people absolutely want
to list non-defcustomed variables in the Custom buffer, they still can
after my patch, by giving customize-apropos a numeric argument.
Your doc-string changes correctly reflect the current prefix-arg behavior -
the arg distinguishes customizable variables from other variables. However,
wouldn't it also be useful to be able to distinguish all user variables
(options) - whether customizable or not - from internal variables?
We have 3 sets of vars:
1. customizable user options - defined with defcustom.
2. non-customizable user options - defined with defvar, with * as first
doc-string char.
3. internal variables - defined with defvar, with no * starting doc string
The prefix arg currently distinguishes #1 from (#2 union #3). That can be
useful, but it can also be useful to distinguish variables designed to be
changed by users from those intended to be used internally: (#1 union #2) vs
#3.
I agree that customize-* commands should show customize stuff by default and
extra stuff, if at all, via prefix arg. But I think that a user will often
be more interested in seeing all user options than all variables, so some
means of showing #1 union #2 would be good to have.
next prev parent reply other threads:[~2005-12-11 17:57 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 ` Drew Adams [this message]
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 ` customize-apropos Drew Adams
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
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=DNEMKBNJBGPAOPIJOOICKEAMDAAA.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 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).