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: Fri, 28 May 2004 11:38:04 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <4nu0y0ef4z.fsf@lifelogs.com> References: <871xluig40.fsf@mail.jurta.org> <87u0y6jjq9.fsf@mail.jurta.org> <4nwu31j4ff.fsf@lifelogs.com> <87zn7wgtel.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 1085773644 28343 80.91.224.253 (28 May 2004 19:47:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 28 May 2004 19:47:24 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Fri May 28 21:47:17 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 1BTnK1-0005sS-00 for ; Fri, 28 May 2004 21:47:17 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BTnK1-00081z-00 for ; Fri, 28 May 2004 21:47:17 +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 1BTl7x-0005xP-Rr for emacs-devel@quimby.gnus.org; Fri, 28 May 2004 13:26:41 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BTji2-0001R1-Qz for emacs-devel@gnu.org; Fri, 28 May 2004 11:55:50 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BTjhQ-0001GM-U0 for emacs-devel@gnu.org; Fri, 28 May 2004 11:55:45 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BTjhQ-0001G2-6q for emacs-devel@gnu.org; Fri, 28 May 2004 11:55:12 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BTjhP-0004Vg-00 for ; Fri, 28 May 2004 17:55:11 +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 ; Fri, 28 May 2004 17:55:11 +0200 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 28 May 2004 17:55:11 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 28 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:AtFr4xoQGJWgs/TMnleY2FxuISo= 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:24093 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24093 On Thu, 27 May 2004, rms@gnu.org wrote: > If there is a real need to enable next-error-function in the existing > buffer visited by next-error (i.e. if it's not too rare case when the > user needs to kill a buffer and create a new, that may be inconvenient > if performed too often), then next-error-function could be enabled again > by setting it to the initial value by typing C-m or one of other error > visiting keys available in the next-error capable buffer. > > That might be an ok solution. It is worth trying, at least. Let me make sure I understand the problem and solution. When next-error is called in buffer X, it may pop the user into buffer Y. We want to unset next-error-function in Y, so that next-error does not act in Y from that point on. Couldn't this be achieved by making the next-error-last-buffer check in next-error-find-buffer precede the current-buffer check? We need to define a function next-error-follow-this-buffer that would set next-error-last-buffer to (current-buffer). That way, users can force the behavior that now is the default, that next-error should act on (current-buffer) first and foremost. I would bind next-error-follow-this-buffer to C-x ~ (which on US keyboards is Shift-` so remembering it is not too bad). Ted