From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: Documentation not clear for the Lisp function set-variable Date: Wed, 29 Jun 2005 02:45:23 +0300 Organization: JURTA Message-ID: <87br5pri6l.fsf@jurta.org> References: <87slz6nr3h.fsf@jurta.org> <200506271609.j5RG9i020638@raven.dms.auburn.edu> <87vf3ztg62.fsf@jurta.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1120017471 11789 80.91.229.2 (29 Jun 2005 03:57:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 29 Jun 2005 03:57:51 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 29 05:57:50 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DnThN-0002zz-A7 for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2005 05:57:17 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DnTpL-0001AV-JR for ged-emacs-devel@m.gmane.org; Wed, 29 Jun 2005 00:05:31 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DnTlM-0007SU-MV for emacs-devel@gnu.org; Wed, 29 Jun 2005 00:01:24 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DnTlL-0007S3-S9 for emacs-devel@gnu.org; Wed, 29 Jun 2005 00:01:24 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DnTiX-00060K-NX for emacs-devel@gnu.org; Tue, 28 Jun 2005 23:58:29 -0400 Original-Received: from [194.126.101.98] (helo=mail.neti.ee) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DnTST-0006kT-Qz for emacs-devel@gnu.org; Tue, 28 Jun 2005 23:41:54 -0400 Original-Received: from mail.neti.ee (80-235-32-121-dsl.mus.estpak.ee [80.235.32.121]) by Relayhost2.neti.ee (Postfix) with ESMTP id CA5042703; Wed, 29 Jun 2005 06:37:07 +0300 (EEST) Original-To: Juanma Barranquero In-Reply-To: (Juanma Barranquero's message of "Tue, 28 Jun 2005 10:32:43 +0200") User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/22.0.50 (gnu/linux) X-Virus-Scanned: by amavisd-new-2.2.1 (20041222) (Debian) at neti.ee 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: news.gmane.org gmane.emacs.devel:39855 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:39855 > IMO, the user does M-x set-variable because he already knows the > variable he wants to set (and it's even likely he read the doc and > knows whether it is obsolete or not, though I'm willing to accept > there are users who simply set a variable because they read about it > in an old doc somewhere) and completion is just a help to do less > typing. So in my view, `set-variable' should not filter out any user > variable, whether it is an obsolete variable or an obsolete > alias. I certainly would be very pissed if I wanted to set > `messages-buffer-max-lines' and had to type it fully because > `set-variable' had decided that `message-log-max' was the way to go. `messages-buffer-max-lines' is not an obsolete alias for `message-log-max'. Rather it's the other way round: `message-log-max' is an obsolete variable (thought it is not marked as such yet), but its alias `messages-buffer-max-lines' is not obsolete (it was added recently as a better name instead of `message-log-max'). But anyway I see your point. I agree that filtering is not very necessary, and think that it would be sufficient to display a warning for obsolete variables and obsolete aliases after selecting the variable but before setting its value. -- Juri Linkov http://www.jurta.org/emacs/