From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: find-file-hook as illustration of Custom problems Date: Wed, 09 Feb 2005 03:10:46 -0500 Message-ID: References: <200502040036.j140atb03430@raven.dms.auburn.edu> <200502060150.j161oqh15336@raven.dms.auburn.edu> <200502080150.j181oMf07339@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org X-Trace: sea.gmane.org 1107939562 4418 80.91.229.2 (9 Feb 2005 08:59:22 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 9 Feb 2005 08:59:22 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 09 09:59:22 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Cyngq-0003DH-I2 for ged-emacs-devel@m.gmane.org; Wed, 09 Feb 2005 09:59:16 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CynvK-0006qh-Qh for ged-emacs-devel@m.gmane.org; Wed, 09 Feb 2005 04:14:15 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1CyneJ-0003SV-7u for emacs-devel@gnu.org; Wed, 09 Feb 2005 03:56:39 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1CyneH-0003Rz-Jw for emacs-devel@gnu.org; Wed, 09 Feb 2005 03:56:38 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1CynbO-0002rA-UI for emacs-devel@gnu.org; Wed, 09 Feb 2005 03:53:39 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CymzR-0007nX-2l for emacs-devel@gnu.org; Wed, 09 Feb 2005 03:14:25 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1Cymvu-0005SV-C7; Wed, 09 Feb 2005 03:10:47 -0500 Original-To: Luc Teirlinck In-reply-to: <200502080150.j181oMf07339@raven.dms.auburn.edu> (message from Luc Teirlinck on Mon, 7 Feb 2005 19:50:22 -0600 (CST)) 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:33119 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33119 If you mean removing the "Changed outside Custom" warning from those rogue-at-startup (with emacs -q) variables that are really harmless, then I could definitely do that way in time for Emacs 22 (old 21.4). The way in which I would do that could be a temporary solution until a more fundamental solution is implemented. I could mention that in a comment. This is the wrong solution. The right solution for variables such as minibuffer-prompt-properties is to set up a valid expression for its standard value. It may be necessary to store the current default value in a new variable so that the standard value can use that variable. This is easy and simple, it's just that each variable needs to be looked at separately. Would you like to do this for some of the variables?