From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kevin Rodgers Newsgroups: gmane.emacs.devel Subject: Re: next-error Date: Tue, 31 Aug 2004 16:49:38 -0600 Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Message-ID: <41350082.1000905@yahoo.com> References: <16683.28246.52467.757743@ihs.com> <87vff1wgln.fsf@mail.jurta.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1093992602 20714 80.91.224.253 (31 Aug 2004 22:50:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Aug 2004 22:50:02 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 01 00:49:54 2004 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1C2HRp-0005i3-00 for ; Wed, 01 Sep 2004 00:49:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C2HWi-0005fZ-Dr for ged-emacs-devel@m.gmane.org; Tue, 31 Aug 2004 18:54:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1C2HWX-0005dd-1W for emacs-devel@gnu.org; Tue, 31 Aug 2004 18:54:45 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1C2HWV-0005cB-Au for emacs-devel@gnu.org; Tue, 31 Aug 2004 18:54:44 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1C2HWV-0005c4-7W for emacs-devel@gnu.org; Tue, 31 Aug 2004 18:54:43 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1C2HRa-0007Kd-OW for emacs-devel@gnu.org; Tue, 31 Aug 2004 18:49:38 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1C2HRX-00019t-00 for ; Wed, 01 Sep 2004 00:49:38 +0200 Original-Received: from 170.207.1.200 ([170.207.1.200]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Sep 2004 00:49:35 +0200 Original-Received: from ihs_4664 by 170.207.1.200 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Sep 2004 00:49:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 38 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 170.207.1.200 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: 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: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:26664 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:26664 Juri Linkov wrote: > I have some changes not yet installed in CVS (I will install them in > the next few days) and one of them is changing the rules for finding > the appropriate source buffer for `next-error'. Perhaps, this change > will fix your problem. Could you provide more details about this case? Sure. Here's what the user reports while debugging my igrep-next-error function (which contains a call to next-error): This just doesn't make sense to me. When I call next-error and then do a M-: (current-buffer) the correct source buffer is displayed as the current-buffer. However, when I capture the "current buffer" value after calling next-error from within igrep-next-error, it shows to be the *igrep* buffer. > From what buffer do you call `next-error'? The problem occurs when the user calls next-error from any buffer except the *igrep* compilation buffer. > What was the command that produced the last next-error capable > buffer? Only one such command was executed, which calls compile-start in exactly the same way as M-x grep does. > Maybe, you need to change the rules in the `next-error-find-buffer' > function? Why? IIUC that function is used to get the compilation buffer, not the source buffer. There doesn't seem to be a problem finding that buffer, as it is highlighted by M-x next-error according to compilation-start's HIGHLIGHT-REGEXP arg. Thanks, -- Kevin Rodgers