From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: "Stefan Monnier " Newsgroups: gmane.emacs.help Subject: Re: save-excursion doesn't always work Date: 16 Dec 2002 12:00:17 -0500 Organization: Yale University Sender: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Message-ID: <5lu1hdew66.fsf@rum.cs.yale.edu> References: <1a52e3d.0212142138.2f5aed8@posting.google.com> <5l7keaeyuy.fsf@rum.cs.yale.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1040059076 15760 80.91.224.249 (16 Dec 2002 17:17:56 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 16 Dec 2002 17:17:56 +0000 (UTC) Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18NysN-000464-00 for ; Mon, 16 Dec 2002 18:17:55 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18NylJ-0006ie-05 for gnu-help-gnu-emacs@m.gmane.org; Mon, 16 Dec 2002 12:10:37 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!news-hog.berkeley.edu!ucberkeley!news.ycc.yale.edu!rum.cs.yale.edu!rum.cs.yale.edu Original-Newsgroups: gnu.emacs.help Original-Lines: 14 Original-NNTP-Posting-Host: rum.cs.yale.edu User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-Original-NNTP-Posting-Host: rum.cs.yale.edu X-Original-Trace: 16 Dec 2002 12:00:17 -0500, rum.cs.yale.edu Original-Xref: shelby.stanford.edu gnu.emacs.help:108175 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: help-gnu-emacs-bounces+gnu-help-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.help:4704 X-Report-Spam: http://spam.gmane.org/gmane.emacs.help:4704 >> It might do a few things slightly differently, but it will modify the >> buffer anyway, even if the end result is exactly the same as the >> starting point (e.g. it will first turn all \n into spaces and then >> turn them back into \n). > We are not talking about modification of the buffer, but about marks > being moved around in seemingly random manner. Unless they're explicitly moved, marks only move in response to buffer modifications. Maybe the default filling function works better than AUCTeX in this regard (I don't know) but even if it does, it doesn't work 100% as the user wants it to. Stefan