From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: find-file-noselect needs save-match-data Date: Sat, 09 Jun 2007 05:46:27 -0400 Message-ID: References: <46643852.6070709@gmx.at> <46665AD7.7040706@gmx.at> <87k5ueq23m.fsf@kfs-lx.testafd.dk> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1181382458 22223 80.91.229.12 (9 Jun 2007 09:47:38 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 9 Jun 2007 09:47:38 +0000 (UTC) Cc: rudalics@gmx.at, herberteuler@hotmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: storm@cua.dk (Kim F. Storm) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 09 11:47:36 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HwxXk-00041c-CY for ged-emacs-devel@m.gmane.org; Sat, 09 Jun 2007 11:47:36 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HwxXk-0000pW-1I for ged-emacs-devel@m.gmane.org; Sat, 09 Jun 2007 05:47:36 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HwxWe-0007uq-PP for emacs-devel@gnu.org; Sat, 09 Jun 2007 05:46:28 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HwxWe-0007uU-8U for emacs-devel@gnu.org; Sat, 09 Jun 2007 05:46:28 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HwxWd-0007uP-R9 for emacs-devel@gnu.org; Sat, 09 Jun 2007 05:46:27 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HwxWd-0004rf-Dm for emacs-devel@gnu.org; Sat, 09 Jun 2007 05:46:27 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1HwxWd-0005q7-42; Sat, 09 Jun 2007 05:46:27 -0400 In-reply-to: <87k5ueq23m.fsf@kfs-lx.testafd.dk> (storm@cua.dk) X-detected-kernel: Linux 2.6, seldom 2.4 (older, 4) 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:72534 Archived-At: It's quite the opposite IMO. "safe" can mean many things, whereas "nodata" clearly indicates that it doesn't set (or modify) match-data. Just "data" doesn't clearly refer to the match data. What this function would do is avoid side effects. What other names do people use to mean "without side effects"? Again, I like the inhibit- name, as other similar variables use the same The name `inhibit-match-data' doesn't fit with a feature that inhibit _setting_ the match data. Other variables called `inhibit-...' followed by a the name of some data inhibit the data from being obeyed or acted on. It doesn't seem right to use a similar name to prevent setting the data.