From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Luc Teirlinck Newsgroups: gmane.emacs.devel Subject: Re: Customize buttons that change user's customfileshouldaskforconfirmation Date: Sat, 12 Feb 2005 14:09:22 -0600 (CST) Message-ID: <200502122009.j1CK9MF19427@raven.dms.auburn.edu> References: NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1108239779 32161 80.91.229.2 (12 Feb 2005 20:22:59 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 12 Feb 2005 20:22:59 +0000 (UTC) Cc: emacs-devel@gnu.org, storm@cua.dk Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 12 21:22:59 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D03mv-0000wk-Pt for ged-emacs-devel@m.gmane.org; Sat, 12 Feb 2005 21:22:46 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D0428-0002SG-1t for ged-emacs-devel@m.gmane.org; Sat, 12 Feb 2005 15:38:28 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D03s6-0005As-81 for emacs-devel@gnu.org; Sat, 12 Feb 2005 15:28:07 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D03rm-00052N-TS for emacs-devel@gnu.org; Sat, 12 Feb 2005 15:27:47 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D03rm-000523-Q0 for emacs-devel@gnu.org; Sat, 12 Feb 2005 15:27:46 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D03bh-0004Vk-B2 for emacs-devel@gnu.org; Sat, 12 Feb 2005 15:11:09 -0500 Original-Received: from raven.dms.auburn.edu (raven.dms.auburn.edu [131.204.53.29]) by manatee.dms.auburn.edu (8.12.10/8.12.10) with ESMTP id j1CKB29N021371; Sat, 12 Feb 2005 14:11:02 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id j1CK9MF19427; Sat, 12 Feb 2005 14:09:22 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: drew.adams@oracle.com In-reply-to: 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: main.gmane.org gmane.emacs.devel:33311 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33311 After all, I do not understand why Custom _needs_ to read custom-file in the first place. It _knows_ what it wrote into the custom-set-variables form. If you edit that form by hand and want Custom to know about it, use C-M-x. But I do not understand why we are having all these detailed long discussions about Custom buttons _now_. Following changes related to Custom are planned or being discussed: 1. Change Custom to be able to handle especially hooks, but also other listvars, to which elements can be added both by code and by the user. 2. Change set-variable to make it use :set functions. 3. Make Custom handle buffer-local values. 4. Maybe change the button structure. 5. Maybe make Custom handle mode-dependent variables. 6. _Maybe_ reimplement custom-file. I believe we agreed that we should not do _any_ of this until after the 22 release. We will be trying to fix some current bugs that can be fixed without non-trivial changes in Custom before the release. Custom is not straightforward to change. I do not understand why we are currently trying to discuss (4) completely up to minor implementation details. The relatively most urgent of the above is (1), because it is necessary to fix several fundamental bugs. Implementation details concerning (4) will depend on how 1, 2 and 3 are implemented. Clearly questions about how to handle custom-file depend on whether or not we will decide to do (6) and if so how. I believe that the proper time to discuss this in detail is when somebody finds the time to implement it. Sincerely, Luc.