From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Lennart Borgman" Newsgroups: gmane.emacs.devel Subject: Re: Documentation for custom-file - is not (load custom-file) needed? Date: Tue, 14 Dec 2004 01:34:30 +0100 Message-ID: <014a01c4e174$b83bcfc0$0200a8c0@sedrcw11488> References: NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1102984743 2548 80.91.229.6 (14 Dec 2004 00:39:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Dec 2004 00:39:03 +0000 (UTC) Cc: Juri Linkov , Luc Teirlinck , Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 14 01:38:55 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 1Ce0iM-0006qI-00 for ; Tue, 14 Dec 2004 01:38:54 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Ce0sU-0002TP-1y for ged-emacs-devel@m.gmane.org; Mon, 13 Dec 2004 19:49:22 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Ce0ru-0002SL-PV for emacs-devel@gnu.org; Mon, 13 Dec 2004 19:48:47 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Ce0rs-0002Pm-2f for emacs-devel@gnu.org; Mon, 13 Dec 2004 19:48:44 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Ce0rr-0002Pj-Vw for emacs-devel@gnu.org; Mon, 13 Dec 2004 19:48:44 -0500 Original-Received: from [81.228.11.115] (helo=av9-1-sn1.fre.skanova.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1Ce0eu-0005bd-Bv; Mon, 13 Dec 2004 19:35:20 -0500 Original-Received: by av9-1-sn1.fre.skanova.net (Postfix, from userid 502) id A0CD237E9D; Tue, 14 Dec 2004 01:35:18 +0100 (CET) Original-Received: from smtp3-1-sn1.fre.skanova.net (smtp3-1-sn1.fre.skanova.net [81.228.11.163]) by av9-1-sn1.fre.skanova.net (Postfix) with ESMTP id 932BF37E4F; Tue, 14 Dec 2004 01:35:18 +0100 (CET) Original-Received: from sedrcw11488 (t3o58p169.telia.com [195.252.56.169]) by smtp3-1-sn1.fre.skanova.net (Postfix) with SMTP id 9893737E45; Tue, 14 Dec 2004 01:35:15 +0100 (CET) Original-To: , X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1409 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 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:31091 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:31091 ----- Original Message ----- From: "Richard Stallman" To: Sent: Monday, December 13, 2004 8:51 PM Subject: Re: Documentation for custom-file - is not (load custom-file) needed? > I read the various messages about custom-file, and this > is what I think we should do. > > 1. We should eliminate custom-file as a defcustom. Yes. But I believe we also should try to eleminate it from the (custom-set-variables ...) where it currently could be. Could that be done by avoiding defvar too and using boundp later for the checks? > 2. We should eliminate loading custom-file on startup. > We should tell users that .emacs should load the appropriate file > where custom values are stored. Yes. But maybe we could reuse Stefans idea of loading "custom file" after .emacs in another way. I would like to get (custom-set-variables ...) out of .emacs by default, because I believe most users do not want it to be edited automatically. Why not use another file name as default for (custom-set-variables ...), say .emacs-custom? This file could be loaded by startup.el if not loaded before, the way Stefan has suggested for "custom file". > 3. Calling custom-set-variables in a file should add that file > to a list of files that have done so. > > 4. Evaluating a custom-set-variables call in a buffer should not do > any such thing. Why not? > 5. When saving custom variables, if custom-file is set, save in that file.... > 6. If the user wants to specify which file to save in,... > 7. Eventually, in the future, we might figure out some clean UI for ... I agree. - Lennart