From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: customize-apropos Date: Sun, 11 Dec 2005 09:57:53 -0800 Message-ID: References: <200512100347.jBA3lr917144@raven.dms.auburn.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1134327110 475 80.91.229.2 (11 Dec 2005 18:51:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 11 Dec 2005 18:51:50 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 11 19:51:43 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1ElWFu-0000gF-1x for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2005 19:49:06 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElWGL-0001Qz-25 for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2005 13:49:33 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ElVT2-0000S5-W1 for emacs-devel@gnu.org; Sun, 11 Dec 2005 12:58:37 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ElVSy-0000Q8-Po for emacs-devel@gnu.org; Sun, 11 Dec 2005 12:58:36 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ElVSx-0000Pi-P9 for emacs-devel@gnu.org; Sun, 11 Dec 2005 12:58:32 -0500 Original-Received: from [148.87.122.30] (helo=rgminet01.oracle.com) by monty-python.gnu.org with esmtp (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.34) id 1ElVUX-0000nC-Qj for emacs-devel@gnu.org; Sun, 11 Dec 2005 13:00:10 -0500 Original-Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.186.49]) by rgminet01.oracle.com (Switch-3.1.6/Switch-3.1.6) with ESMTP id jBBHvxMS000847 for ; Sun, 11 Dec 2005 10:57:59 -0700 Original-Received: from rgmsgw300.us.oracle.com (localhost [127.0.0.1]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id jBBHvxiW006360 for ; Sun, 11 Dec 2005 10:57:59 -0700 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-81-104.vpn.oracle.com [141.144.81.104]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id jBBHvw70006350 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Sun, 11 Dec 2005 10:57:59 -0700 Original-To: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 In-Reply-To: <200512100347.jBA3lr917144@raven.dms.auburn.edu> Importance: Normal X-Brightmail-Tracker: AAAAAQAAAAI= X-Whitelist: TRUE X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:47470 Archived-At: 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.