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: Getting more info on a variable in Customize buffers Date: Thu, 06 Jan 2005 14:56:21 -0500 Message-ID: References: <200501040054.j040sAr12434@raven.dms.auburn.edu> <87wtusiizq.fsf-monnier+emacs@gnu.org> <200501060346.j063kht03686@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1105042673 3680 80.91.229.6 (6 Jan 2005 20:17:53 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 6 Jan 2005 20:17:53 +0000 (UTC) Cc: drew.adams@oracle.com, monnier@iro.umontreal.ca, Reiner.Steib@gmx.de, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jan 06 21:17:36 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Cmdst-00087E-00 for ; Thu, 06 Jan 2005 21:05:27 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cme4D-0007mT-9Z for ged-emacs-devel@m.gmane.org; Thu, 06 Jan 2005 15:17:09 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Cme2n-0006wq-Rv for emacs-devel@gnu.org; Thu, 06 Jan 2005 15:15:41 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1Cme2m-0006v1-2j for emacs-devel@gnu.org; Thu, 06 Jan 2005 15:15:40 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cme2l-0006uD-Ni for emacs-devel@gnu.org; Thu, 06 Jan 2005 15:15:39 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CmdrE-00031R-89 for emacs-devel@gnu.org; Thu, 06 Jan 2005 15:03:44 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1Cmdk5-0006is-A1; Thu, 06 Jan 2005 14:56:25 -0500 Original-To: Luc Teirlinck In-reply-to: <200501060346.j063kht03686@raven.dms.auburn.edu> (message from Luc Teirlinck on Wed, 5 Jan 2005 21:46:43 -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 Xref: main.gmane.org gmane.emacs.devel:31972 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:31972 The best way to make set-variable work buffer-locally depends on whether and how we want to make Custom work buffer-locally. We want to make Custom work buffer-locally. This is not super-urgent, but it is very desirable for the long term. For interactive use, `custom-local-buffer' seems to inconvenient (even if it worked reliably, which it does not). Of course this is not meant as an end-user interface. It is meant as a mechanism for the end-user interface to use. For that purpose, it is clean enough. If we do not care about making Custom set buffer-local values, the best thing would probably be :set-local and :get-local keywords, as Richard suggested. That _maybe_ could also be the case if we wanted to make Custom work buffer-locally. I had forgotten about custom-local-buffer. Now that I remember it, I see no advantage in :set-local and :get-local. The :set and :get functions can just as easily test custom-local-buffer. Making Custom work buffer locally is very tricky. It does not seem like something for before the next release. If specific :set and :get functions fail to handle custom-local-buffer, that is a bug. We can fix these bugs at any time. Would you like to find some cases that fail, and fix them? Adding a nice UI so that Custom uses custom-local-buffer is a different job. We might not want to install that now; however, people could start implementing it now, to be installed later.