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: Tue, 19 Jun 2007 18:26:09 -0400 Message-ID: References: <18030.3441.204697.244518@rgrjr.dyndns.org> <87zm3515r4.fsf@jurta.org> <85k5u8x2gm.fsf@lola.goethe.zz> <87r6og6czf.fsf@catnip.gol.com> <85bqfkx0i5.fsf@lola.goethe.zz> <87odjjzaoz.fsf@catnip.gol.com> <85ps3xoui7.fsf@lola.goethe.zz> <857iq3n2b3.fsf@lola.goethe.zz> <85myyxkfl4.fsf@lola.goethe.zz> <85zm2xhrd7.fsf@lola.goethe.zz> Reply-To: rms@gnu.org NNTP-Posting-Host: lo.gmane.org Content-Type: text/plain; charset=ISO-8859-15 X-Trace: sea.gmane.org 1182292156 3775 80.91.229.12 (19 Jun 2007 22:29:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 19 Jun 2007 22:29:16 +0000 (UTC) Cc: miles.bader@necel.com, schwab@suse.de, emacs-devel@gnu.org, juri@jurta.org, monnier@iro.umontreal.ca, miles@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jun 20 00:29:14 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 1I0mCD-00045g-BB for ged-emacs-devel@m.gmane.org; Wed, 20 Jun 2007 00:29:09 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I0mCC-0005ed-NU for ged-emacs-devel@m.gmane.org; Tue, 19 Jun 2007 18:29:08 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1I0m9N-0003KD-0H for emacs-devel@gnu.org; Tue, 19 Jun 2007 18:26:13 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1I0m9L-0003JZ-Hw for emacs-devel@gnu.org; Tue, 19 Jun 2007 18:26:12 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1I0m9L-0003JU-B9 for emacs-devel@gnu.org; Tue, 19 Jun 2007 18:26:11 -0400 Original-Received: from fencepost.gnu.org ([140.186.70.10]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1I0m9L-00056H-2A for emacs-devel@gnu.org; Tue, 19 Jun 2007 18:26:11 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.60) (envelope-from ) id 1I0m9J-0000lV-O7; Tue, 19 Jun 2007 18:26:09 -0400 In-reply-to: <85zm2xhrd7.fsf@lola.goethe.zz> (message from David Kastrup on Mon, 18 Jun 2007 23:42:12 +0200) 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:73349 Archived-At: > If `save-match-data' was never changed, then there was no point at > which a change could have broken anything, thus no issue. I already gave an explicit Elisp example where save-match-data around a passage not accessing the match data leads to different results from not using save-match-data. Using markers helps avoid strange results when the code inside the construct edits the buffer. I think that is a good reason for this feature.