From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Richard M. Stallman" Newsgroups: gmane.emacs.devel Subject: Re: Risky local variable mechanism Date: Tue, 07 Feb 2006 01:07:14 -0500 Message-ID: References: <87mzhbly89.fsf-monnier+emacs@gnu.org> <200602040434.k144Y2D21725@raven.dms.auburn.edu> <200602060600.k1660ep20338@raven.dms.auburn.edu> Reply-To: rms@gnu.org NNTP-Posting-Host: main.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1139292867 23029 80.91.229.2 (7 Feb 2006 06:14:27 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 7 Feb 2006 06:14:27 +0000 (UTC) Cc: storm@cua.dk, monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 07 07:14:21 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F6M7H-0001AJ-Vq for ged-emacs-devel@m.gmane.org; Tue, 07 Feb 2006 07:14:20 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F6MAd-0000dH-Bz for ged-emacs-devel@m.gmane.org; Tue, 07 Feb 2006 01:17:47 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1F6M5L-0007gO-8p for emacs-devel@gnu.org; Tue, 07 Feb 2006 01:12:19 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1F6M5K-0007g3-Mi for emacs-devel@gnu.org; Tue, 07 Feb 2006 01:12:18 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1F6M5K-0007fq-AB for emacs-devel@gnu.org; Tue, 07 Feb 2006 01:12:18 -0500 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.52) id 1F6M50-00055F-0d for emacs-devel@gnu.org; Tue, 07 Feb 2006 01:11:58 -0500 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1F6M0Q-0005ki-VH; Tue, 07 Feb 2006 01:07:15 -0500 Original-To: Luc Teirlinck In-reply-to: <200602060600.k1660ep20338@raven.dms.auburn.edu> (message from Luc Teirlinck on Mon, 6 Feb 2006 00:00:40 -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: news.gmane.org gmane.emacs.devel:50133 Archived-At: If I understand the proposed interface correctly, it would try to update the currently customizable (through Custom) variable safe-local-eval-forms automatically when the user visits a file. Not "automatically". It would ask the user questions. It would create another option, customizable through Custom, for variables and try to update that one in the same way too. The idea is not that specific. That could be one way of doing it. The details can be worked out in various ways. There are way worse problems, if the user would try to customize these variables _through Custom_ instead of .emacs. I don't think so. It makes no difference whether the change is made using the Custom buffer or using the ask-questions-when-visiting interface; either way it will update .emacs just the same. But even if you are right, it is just a side issue, not very important. We have a grave problem that we need to solve. If the solution introduces minor problems, that's ok. I do not see how the automatic updating could be done in a way that works well both for people who customize these two options in their .emacs _and_ for people who customize them through Custom, especially not given Custom's current problems with this type of listvars. I think it will work right without any special effort. If not, we can easily work around it by making two variables, one to set with Custom and one that ask-questions-when-visiting will set. Please learn to put minor imperfections in perspective. They are not show-stoppers.