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: Documentation for custom-file - is not (load custom-file) needed? Date: Tue, 7 Dec 2004 22:35:57 -0600 (CST) Message-ID: <200412080435.iB84ZvQ06453@raven.dms.auburn.edu> References: <075b01c4d9a4$52799460$0200a8c0@sedrcw11488> <00bb01c4daee$5eb81350$0200a8c0@sedrcw11488> <200412051733.iB5HXIX13206@raven.dms.auburn.edu> <000001c4db1a$8d3770f0$0200a8c0@sedrcw11488> <200412060046.iB60kZj15003@raven.dms.auburn.edu> <003e01c4db31$e45a2550$0200a8c0@sedrcw11488> <200412060402.iB6421q15173@raven.dms.auburn.edu> <200412070539.iB75dV924747@raven.dms.auburn.edu> <03be01c4dcbf$139bfa30$0200a8c0@sedrcw11488> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1102480709 3007 80.91.229.6 (8 Dec 2004 04:38:29 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 8 Dec 2004 04:38:29 +0000 (UTC) Cc: rms@gnu.org, jpw@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 08 05:38:25 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Cbtap-0005yN-00 for ; Wed, 08 Dec 2004 05:38:24 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cbtkf-00085A-7t for ged-emacs-devel@m.gmane.org; Tue, 07 Dec 2004 23:48:33 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CbtkX-00083H-Di for emacs-devel@gnu.org; Tue, 07 Dec 2004 23:48:25 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CbtkW-00081w-EN for emacs-devel@gnu.org; Tue, 07 Dec 2004 23:48:24 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CbtkW-00081p-B6 for emacs-devel@gnu.org; Tue, 07 Dec 2004 23:48:24 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CbtaA-00024S-JZ; Tue, 07 Dec 2004 23:37:42 -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 iB84bfFu007135; Tue, 7 Dec 2004 22:37:41 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id iB84ZvQ06453; Tue, 7 Dec 2004 22:35:57 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: lennart.borgman.073@student.lu.se In-reply-to: <03be01c4dcbf$139bfa30$0200a8c0@sedrcw11488> (lennart.borgman.073@student.lu.se) 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: main.gmane.org gmane.emacs.devel:30834 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:30834 It does not appear to me that your reply addresses the following argument I made previously: On second thought, I start doubting the utility of the feature you are proposing. One of the main reasons to have a custom file is to have different custom files for different versions of Emacs. Those versions share .emacs. So Custom should not write anything into .emacs of the type you are proposing, since the custom file usually is version dependent and .emacs is version independent. If Custom is to write anything in .emacs, it should allow the user to specify different custom files for different ranges of Emacs versions and write a `cond' form into .emacs of the type below. That might be useful, but I believe we should wait with that until after the release. (cond ((< emacs-major-version 21) (load "~/.custom-20.el")) ((< emacs-minor-version 4) (load "~/.custom-21.el")) (t (load "~/.custom-21.4.el"))) Note that when the user would choose the special option to set `custom-file' according to the Emacs version (maybe using an alist), then he would imply with that choice that he wanted Custom to edit his .emacs, so we would not have to ask any questions, which simplifies things. If the user wanted only one Custom file , he could still use the feature by using an alist with only one element (".custom" . t), or whatever. Concretely, I was thinking of adding a third element to the current choice: :type '(choice (const :tag "Your Emacs init file" nil) file) That third element might be of type alist and mean the above. The details need to be thought out carefully. It might be better to wait till after the release, unless it would turn out to be easy, which maybe it could be. Sincerely, Luc.