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: Getting more info on a variable in Customize buffers Date: Thu, 6 Jan 2005 22:17:12 -0600 (CST) Message-ID: <200501070417.j074HCi08213@raven.dms.auburn.edu> References: <200501040054.j040sAr12434@raven.dms.auburn.edu> <87wtusiizq.fsf-monnier+emacs@gnu.org> <200501060346.j063kht03686@raven.dms.auburn.edu> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1105071536 11700 80.91.229.6 (7 Jan 2005 04:18:56 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 7 Jan 2005 04:18:56 +0000 (UTC) Cc: Reiner.Steib@gmx.de, monnier@iro.umontreal.ca, drew.adams@oracle.com, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jan 07 05:18:48 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 1CmlaJ-0002CL-00 for ; Fri, 07 Jan 2005 05:18:48 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Cmlle-0006Wa-0Q for ged-emacs-devel@m.gmane.org; Thu, 06 Jan 2005 23:30:30 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CmllO-0006Ux-H4 for emacs-devel@gnu.org; Thu, 06 Jan 2005 23:30:14 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CmllM-0006Tz-Rv for emacs-devel@gnu.org; Thu, 06 Jan 2005 23:30:13 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CmllM-0006Tl-JW for emacs-devel@gnu.org; Thu, 06 Jan 2005 23:30:12 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CmlZD-0004PE-JW; Thu, 06 Jan 2005 23:17:39 -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 j074HF9N007735; Thu, 6 Jan 2005 22:17:15 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id j074HCi08213; Thu, 6 Jan 2005 22:17:12 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: rms@gnu.org In-reply-to: (message from Richard Stallman on Thu, 06 Jan 2005 14:56:21 -0500) 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:31990 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:31990 Richard Stallman wrote: If specific :set and :get functions fail to handle custom-local-buffer, that is a bug. They are _currently_ not really bugs (at least not user visible bugs), since there currently are no situations where custom-local-buffer can be meaningfully used. From the moment we start using custom-local-buffer they would become (user visible) bugs. We can fix these bugs at any time. Yes, except that time spent doing that means less time spent working toward a release. We only have a motivation to spend time on that _before_ rather than _after_ the release if we plan on using `custom-local-buffer' meaningfully before the next release. Would you like to find some cases that fail, and fix them? I could look at those defcustoms that I am very familiar with, but that is a very small fraction of all defcustoms with :set functions that are out there. (Fortunately, :get functions appear to be very rare.) For many :set functions it may not be immediately obvious what the best way to make them work buffer-locally is, and there are tons of defcustoms with :set functions. The only reason to worry about making :set and :get functions work buffer locally now would be to allow `set-variable' to call the :set functions buffer locally. But if we try to do that _now_, the next release will be full of newly introduced bugs, because we will not be able to come even remotely close to adapt all :set functions. The next release seems already remote enough that I do not believe that we should delay it further by trying to change the behavior of `set-variable' right now. All of this is not a question about what should be done, but whether it should be done for 21.4 or for 22. Sincerely, Luc.