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: defcustom :version Date: Tue, 14 Mar 2006 11:08:04 -0800 Message-ID: References: <1062.1142358578@olgas.newt.com> 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 1142363336 24394 80.91.229.2 (14 Mar 2006 19:08:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Mar 2006 19:08:56 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 14 20:08:55 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FJEsm-0003I4-5E for ged-emacs-devel@m.gmane.org; Tue, 14 Mar 2006 20:08:36 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FJEsl-0007hY-HY for ged-emacs-devel@m.gmane.org; Tue, 14 Mar 2006 14:08:35 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FJEsR-0007f3-1y for emacs-devel@gnu.org; Tue, 14 Mar 2006 14:08:15 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FJEsP-0007dg-V9 for emacs-devel@gnu.org; Tue, 14 Mar 2006 14:08:14 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FJEsP-0007dU-QX for emacs-devel@gnu.org; Tue, 14 Mar 2006 14:08:13 -0500 Original-Received: from [148.87.113.118] (helo=rgminet01.oracle.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA:24) (Exim 4.52) id 1FJEwf-0005Yc-IM for emacs-devel@gnu.org; Tue, 14 Mar 2006 14:12:37 -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 k2EJ8BtI030340 for ; Tue, 14 Mar 2006 12:08:11 -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 k2EJ8AX0020007 for ; Tue, 14 Mar 2006 12:08:10 -0700 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-80-47.vpn.oracle.com [141.144.80.47]) by rgmsgw300.us.oracle.com (Switch-3.1.7/Switch-3.1.7) with SMTP id k2EJ89WL019993 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO) for ; Tue, 14 Mar 2006 12:08:10 -0700 Original-To: X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-reply-to: <1062.1142358578@olgas.newt.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 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:51625 Archived-At: > Here's an idea. customize-changed could work like customize-browse, > except that it would show only the groups that cover settings which > have changed meanings. What do you think? I like it, with one caveat. As I browsed the output of customized-changed, a couple of variables caught my eye that I would have missed if they were hidden in a tree structure. However, that concern would be mitigated with an Expand All button (with a corresponding Collapse All button). I have not been following this thread closely. However, if the question is about changing the behavior of `customize-changed' now (before the release), then I am against it. I don't want to hear (or to miss) "Here's an idea" proposals about the Customize design now, unless it's to discuss changes that might occur _after_ the release. In particular, if the idea is to have `customize-changed' not show every single change, or to enclose the changes within a tree structure of groups, then I am against it at the present time. If some such abbreviation is (also) useful sometimes, then we can create a new command to do that. But why do even that before the release? We need a real discussion or two or three about Customize after the release. Please, let's not make changes to the Customize design now. Apologies if I misunderstood the question. I have not followed this thread. If this is about fixing a bug, then please try to find a way to do that without changing the design.