From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: next-error-last-buffer Date: Mon, 24 May 2004 10:16:52 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <4nwu31j4ff.fsf@lifelogs.com> References: <871xluig40.fsf@mail.jurta.org> <87u0y6jjq9.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 1085444292 17056 80.91.224.253 (25 May 2004 00:18:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 25 May 2004 00:18:12 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 25 02:18:06 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 1BSPdu-00021f-00 for ; Tue, 25 May 2004 02:18:06 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BSPdt-0000Ik-00 for ; Tue, 25 May 2004 02:18:06 +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 1BSNIs-0003Cg-EC for emacs-devel@quimby.gnus.org; Mon, 24 May 2004 17:48:14 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BSMkP-0002t4-Be for emacs-devel@gnu.org; Mon, 24 May 2004 17:12:37 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BSJ1x-0003fY-HI for emacs-devel@gnu.org; Mon, 24 May 2004 13:15:04 -0400 Original-Received: from [199.232.41.8] (helo=mx20.gnu.org) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1BSImj-00014W-Bu for emacs-devel@gnu.org; Mon, 24 May 2004 12:58:50 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by mx20.gnu.org with esmtp (Exim 4.34) id 1BSGa7-00059m-Vd for emacs-devel@gnu.org; Mon, 24 May 2004 10:37:40 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BSGWP-00024Z-00 for ; Mon, 24 May 2004 16:33:45 +0200 Original-Received: from asimov.bwh.harvard.edu ([134.174.9.63]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 May 2004 16:33:45 +0200 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 24 May 2004 16:33:45 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 29 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: asimov.bwh.harvard.edu X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:eGEn1Z0Pn4/pyQrFN+tf6JhAy0o= 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:23908 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23908 On Mon, 24 May 2004, juri@jurta.org wrote: > There is another problem related to `next-error-last-buffer'. > > When `next-error' visits a next-error capable buffer, it continues > to visit places from that buffer instead of the original buffer > from which it was found. > > This problem occurs when going through results in a grep buffer > visits a patch file in diff mode. The next call of `next-error' > continues to visit places from a patch file, not from a grep buffer. Excellent catch, I had not seen that problem. I don't know if it's a bug, though! > To avoid this problem, the variable `next-error-function' could be set > to nil in a buffer visited by the latest call of > `next-error-function'. But what if the user wants the next place in the patch file? It would be very useful to have next-error support that as well. Maybe next-error should know when a user visits a buffer interactively (with a keyboard command or a mouse click) versus through a next-error invocation. That way, the user can select the diff buffer manually when they want the next diff hunk, but otherwise next-error will keep using the original invocant buffer. Ted