From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: next-error-last-buffer Date: 10 May 2004 22:19:59 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <8765b3pv3x.fsf-monnier+emacs@gnu.org> References: <871xluig40.fsf@mail.jurta.org> <873c6983t9.fsf@mail.jurta.org> <8765b3vm0r.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1084242187 20777 80.91.224.253 (11 May 2004 02:23:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 May 2004 02:23:07 +0000 (UTC) Cc: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 11 04:22:57 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNMv3-0005IL-00 for ; Tue, 11 May 2004 04:22:57 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNMv1-0000Kd-00 for ; Tue, 11 May 2004 04:22:55 +0200 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNMuZ-0005d3-IK for emacs-devel@quimby.gnus.org; Mon, 10 May 2004 22:22:27 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNMt8-0004wq-I9 for emacs-devel@gnu.org; Mon, 10 May 2004 22:20:58 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNMsM-0004Zr-Vo for emacs-devel@gnu.org; Mon, 10 May 2004 22:20:43 -0400 Original-Received: from [209.226.175.188] (helo=tomts25-srv.bellnexxia.net) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNMsM-0004ZC-0K; Mon, 10 May 2004 22:20:10 -0400 Original-Received: from alfajor ([67.68.218.161]) by tomts25-srv.bellnexxia.net (InterMail vM.5.01.06.05 201-253-122-130-105-20030824) with ESMTP id <20040511022003.GOUB17358.tomts25-srv.bellnexxia.net@alfajor>; Mon, 10 May 2004 22:20:03 -0400 Original-Received: by alfajor (Postfix, from userid 1000) id CB9FED73CE; Mon, 10 May 2004 22:19:59 -0400 (EDT) Original-To: Juri Linkov In-Reply-To: <8765b3vm0r.fsf@mail.jurta.org> Original-Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.4 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:23102 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23102 >> If you switch to another source buffer that was last reached >> through C-x ` from a compilation error, then C-x ` will get the >> next compilation error, rather than the next occurrence. >> At least, it sounds like your change would have that result. > Exactly. This is the most expected behavior, because the user > associates the buffer visited through C-x ` with the compilation > buffer from which it was visited, and will expect that next-error > will show next compilation errors in the same source buffer. No: I do M-x compile, visit a few error in xdisp.c. Then an hour later, I do M-x grep, follow a hit, do a M-. which brings me to xdisp.c, then try C-x ` to get to the next hit and !bang! I'm brought to the next error in the compilation I completely forgot about. The main problem with your approach is that its memory lasts too long. Stefan