From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.devel Subject: Re: next-error-last-buffer Date: Sun, 30 May 2004 10:30:17 -0400 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <871xluig40.fsf@mail.jurta.org> <87u0y6jjq9.fsf@mail.jurta.org> <4nwu31j4ff.fsf@lifelogs.com> <87zn7wgtel.fsf@mail.jurta.org> <4nu0y0ef4z.fsf@lifelogs.com> <87n03sfd1x.fsf@mail.jurta.org> <4nd64ndhdt.fsf@lifelogs.com> Reply-To: rms@gnu.org NNTP-Posting-Host: deer.gmane.org X-Trace: sea.gmane.org 1085927598 21192 80.91.224.253 (30 May 2004 14:33:18 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 30 May 2004 14:33:18 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sun May 30 16:33:14 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 1BURNC-0004am-00 for ; Sun, 30 May 2004 16:33:14 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BURNC-0004ga-00 for ; Sun, 30 May 2004 16:33:14 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BURNK-0000xO-H4 for emacs-devel@quimby.gnus.org; Sun, 30 May 2004 10:33:22 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BURKy-0007n3-Gj for emacs-devel@gnu.org; Sun, 30 May 2004 10:30:56 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BURKv-0007lt-SA for emacs-devel@gnu.org; Sun, 30 May 2004 10:30:54 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BURKv-0007km-Lr for emacs-devel@gnu.org; Sun, 30 May 2004 10:30:53 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BURKM-00023a-Oy for emacs-devel@gnu.org; Sun, 30 May 2004 10:30:18 -0400 Original-Received: from rms by fencepost.gnu.org with local (Exim 4.34) id 1BURKL-0001v7-Do; Sun, 30 May 2004 10:30:17 -0400 Original-To: Ted Zlatanov In-reply-to: <4nd64ndhdt.fsf@lifelogs.com> (message from Ted Zlatanov on Fri, 28 May 2004 23:47:10 -0400) 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:24216 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24216 > So the only change needed is to modify the rule order like you proposed, > which could look as below: > > 1. If one window on the selected frame displays such buffer, return it. > 2. If next-error-last-buffer is set to a live buffer, use that. > 3. If the current buffer is a next-error capable buffer, return it. > ... That might solve the problem, but what you have written is very different: +;; 1. If next-error-last-buffer is set to a live buffer, use that. +;; 2. If the current buffer is a next-error capable buffer, return it. +;; 3. If one window on the selected frame displays such buffer, return it. ;; 4. Otherwise, look for a next-error capable buffer in a buffer list. ;; 5. Signal an error if there are none. This change has the unpleasant side effect of eliminating any convenient way to control which buffer you want to take errors from. next-error-last-buffer takes precedence over everything else, so there is no way to deliberately override it. Using the current buffer is wrong only in one special case: where that buffer was found as the source locus for an error. In all other cases, it is right to use the current buffer rather than next-error-last-buffer.