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: Wed, 5 Jan 2005 21:46:43 -0600 (CST) Message-ID: <200501060346.j063kht03686@raven.dms.auburn.edu> References: <200501040054.j040sAr12434@raven.dms.auburn.edu> <87wtusiizq.fsf-monnier+emacs@gnu.org> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1104983311 10813 80.91.229.6 (6 Jan 2005 03:48:31 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 6 Jan 2005 03:48:31 +0000 (UTC) Cc: drew.adams@oracle.com, rms@gnu.org, 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 04:48:18 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 1CmOdG-0004eg-00 for ; Thu, 06 Jan 2005 04:48:18 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CmOoX-0001PG-Nl for ged-emacs-devel@m.gmane.org; Wed, 05 Jan 2005 22:59:57 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CmOoJ-0001Ng-8H for emacs-devel@gnu.org; Wed, 05 Jan 2005 22:59:43 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CmOoG-0001M6-Ru for emacs-devel@gnu.org; Wed, 05 Jan 2005 22:59:41 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CmOoG-0001Lw-M9 for emacs-devel@gnu.org; Wed, 05 Jan 2005 22:59:40 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CmObv-0005xH-9t; Wed, 05 Jan 2005 22:46:55 -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 j063kj9N002664; Wed, 5 Jan 2005 21:46:45 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.7p1+Sun/8.11.7) id j063kht03686; Wed, 5 Jan 2005 21:46:43 -0600 (CST) X-Authentication-Warning: raven.dms.auburn.edu: teirllm set sender to teirllm@dms.auburn.edu using -f Original-To: monnier@iro.umontreal.ca In-reply-to: <87wtusiizq.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Tue, 04 Jan 2005 23:43:52 -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:31933 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:31933 Stefan Monnier wrote: Currently :set and :get are supposed to work buffer-locally if custom-local-buffer is non-nil. Actually it is quite confusing. The default :set function is `custom-set-default' for `custom-theme-set-variables' (and for the defcustom docstring) and `set-default' for all the rest of the Custom machinery. Is there some rationale behind that? What is the intended use? For interactive use, `custom-local-buffer' seems to inconvenient (even if it worked reliably, which it does not). Anyway, any case where `custom-set-default' would be used seems irrelevant to the discussion. In the cases where it works, it does not do anything different from what `set-variable' currently does. What we discussed was calling the :set function if there was a _non-default_ :set function. Most of these were not designed to work buffer-locally. The best way to make set-variable work buffer-locally depends on whether and how we want to make Custom work buffer-locally. 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. Making Custom work buffer locally is very tricky. It does not seem like something for before the next release. The question is whether we still want to change something to `set-variable' before the next release. Sincerely, Luc.