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: doc elisp intro cross reference fixes Date: Wed, 26 Nov 2003 17:49:02 -0600 (CST) Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <200311262349.hAQNn2l02786@raven.dms.auburn.edu> References: <87wua28zux.fsf@zip.com.au> <87ad6vdsxi.fsf@mail.jurta.org> <200311190418.hAJ4ITC02466@raven.dms.auburn.edu> <200311190528.hAJ5SrK02553@raven.dms.auburn.edu> <3FBBD155.2050703@yahoo.com> <200311192238.hAJMcTM06424@raven.dms.auburn.edu> <3FBD2533.6090503@yahoo.com> NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1069891801 6110 80.91.224.253 (27 Nov 2003 00:10:01 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 27 Nov 2003 00:10:01 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Nov 27 01:09:57 2003 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AP9jJ-0001OE-00 for ; Thu, 27 Nov 2003 01:09:57 +0100 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1AP9jI-0007A9-00 for ; Thu, 27 Nov 2003 01:09:57 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.24) id 1APAZ3-000659-O0 for emacs-devel@quimby.gnus.org; Wed, 26 Nov 2003 20:03:25 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.24) id 1APAYe-00061p-Op for emacs-devel@gnu.org; Wed, 26 Nov 2003 20:03:00 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.24) id 1APAST-0005Ek-0m for emacs-devel@gnu.org; Wed, 26 Nov 2003 19:57:08 -0500 Original-Received: from [131.204.53.104] (helo=manatee.dms.auburn.edu) by monty-python.gnu.org with esmtp (Exim 4.24) id 1APASQ-0005ER-MO for emacs-devel@gnu.org; Wed, 26 Nov 2003 19:56:34 -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 hAQNtDKk015711; Wed, 26 Nov 2003 17:55:14 -0600 (CST) Original-Received: (from teirllm@localhost) by raven.dms.auburn.edu (8.11.6+Sun/8.11.6) id hAQNn2l02786; Wed, 26 Nov 2003 17:49:02 -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: (message from Stefan Monnier on 26 Nov 2003 13:14:52 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.2 Precedence: list List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:18151 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:18151 Stefan Monnier wrote (in response to a quote from Per Abrahamsen): > It is an entirely different interface. > (defalias 'set-variable 'customize-set-variable) > or > (defalias 'set-variable 'customize-set-value) > would make sense though. The difference is that the first uses the > :set function, the later doesn't. Indeed. Indeed which one? These are two very different alternatives Per is proposing. From previous posts I would guess that you mean: Indeed: (defalias 'set-variable 'customize-set-variable) Note that if you mean this literally, this is a non-trivial change in as far as prefix arguments are concerned. Right now, C-u set-variable will set the buffer-local value. After the defalias, it will set the global value and prompt for a comment. On the other hand, customize-set-variable already accepts *-variables without defcustom. Indeed. We'd just need to make (defvar a b "*c") equivalent to (defcustom a b "c"). You make this sound a lot simpler than it would be. This will have to be handled individually and very carefully for each *-defvar, a huge amount of work. If an author decided to use a *-defvar instead of a defcustom, there probably is a good reason why he decided not to use a defcustom. For instance, default-enable-multibyte-characters has a *-defvar. You do not want to turn this into a defcustom, because it would duplicate the defcustom for enable-multibyte-characters, which also sets the default value. That would be extremely confusing to the Custom user. Not only would blindly turning a *-defvar into a defcustom be dangerous, it is impossible. You will have to decide on a :group, a :type and so on. Sincerely, Luc.