From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.bugs Subject: Re: next-error modifies *compilation* buffer Date: Tue, 27 May 2003 09:21:13 -0600 Sender: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Message-ID: <3ED38269.1010106@yahoo.com> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1054051167 5264 80.91.224.249 (27 May 2003 15:59:27 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 27 May 2003 15:59:27 +0000 (UTC) Original-X-From: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Tue May 27 17:59:25 2003 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 19Kgoj-00017Z-00 for ; Tue, 27 May 2003 17:56:50 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.20) id 19Kgo0-0004ia-6E for gnu-bug-gnu-emacs@m.gmane.org; Tue, 27 May 2003 11:56:04 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20) id 19KggN-0002fJ-TP for bug-gnu-emacs@prep.ai.mit.edu; Tue, 27 May 2003 11:48:11 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20) id 19KgXZ-0000FZ-4q for bug-gnu-emacs@prep.ai.mit.edu; Tue, 27 May 2003 11:39:05 -0400 Original-Received: from chi6-2.relay.mail.uu.net ([199.171.54.99]) by monty-python.gnu.org with esmtp (Exim 4.20) id 19KgGK-0004ar-Cu for bug-gnu-emacs@prep.ai.mit.edu; Tue, 27 May 2003 11:21:16 -0400 Original-Received: from mail.fu-berlin.de by chi6sosrv11.alter.net with ESMTP (peer crosschecked as: mail.fu-berlin.de [160.45.11.165]) id QQoqmv00909 for ; Tue, 27 May 2003 15:21:14 GMT Original-Received: by mail.fu-berlin.de (Smail3.2.0.98) from Curry.ZEDAT.FU-Berlin.DE (160.45.10.36) with esmtp id ; Tue, 27 May 2003 17:21:11 +0200 (MEST) Original-Received: by Curry.ZEDAT.FU-Berlin.DE (Smail3.2.0.98) from news.fu-berlin.de with bsmtp id ; Tue, 27 May 2003 17:21:11 +0200 (MEST) Original-To: gnu-emacs-bug@moderators.isc.org Original-Path: 170.207.51.80!not-for-mail Original-Newsgroups: gnu.emacs.bug Original-Lines: 17 X-Orig-NNTP-Posting-Host: 170.207.51.80 X-Orig-X-Trace: fu-berlin.de 1054048871 4423638 170.207.51.80 (16 [82742]) User-Agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2 X-Accept-Language: en-us X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Bug reports for GNU Emacs, the Swiss army knife of text editors List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: bug-gnu-emacs-bounces+gnu-bug-gnu-emacs=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.bugs:5180 X-Report-Spam: http://spam.gmane.org/gmane.emacs.bugs:5180 Dan Jacobson wrote: > Gentlemen, apparently next-error changes the *compilation* buffer. > Let's say you save a *grep* or *compilation* buffer to a file, then > proceed to do some next-error. Well, looking at the modeline, one can > see that buffer has now been modified for some unnecessary reason. > Even if one does vc-toggle-read-only first too. I could not repeat this in Emacs 21.3. (I didn't actually save the *grep* buffer to a file, but just made it read-only with C-x C-q. If next-error tried to modify the buffer, C-x ` should have signalled an error, which didn't happen.) Did you start emacs with the -q and --no-site-file command line options? -- Kevin Rodgers