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 refactoring Date: Fri, 28 May 2004 23:54:09 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <4n8yfbdh26.fsf@lifelogs.com> References: <20040503.071327.124836670.Takaaki.Ota@am.sony.com> <20040504.075437.207586641.Takaaki.Ota@am.sony.com> <87llk552oz.fsf@mail.jurta.org> <87isf6e7ji.fsf@mail.jurta.org> <87iseg4x5d.fsf@mail.jurta.org> <4npt8oeet9.fsf_-_@lifelogs.com> <87d64os9kd.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 1085806449 29115 80.91.224.253 (29 May 2004 04:54:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 29 May 2004 04:54:09 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Sat May 29 06:54:04 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 1BTvrA-0007Zn-00 for ; Sat, 29 May 2004 06:54:04 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BTvr9-0003BY-00 for ; Sat, 29 May 2004 06:54:03 +0200 Original-Received: from [127.0.0.1] (helo=mailman.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BTvrC-00066m-T1 for emacs-devel@quimby.gnus.org; Sat, 29 May 2004 00:54:06 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BTvqz-0005u9-Gh for emacs-devel@gnu.org; Sat, 29 May 2004 00:53:53 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BTvqx-0005sT-Hr for emacs-devel@gnu.org; Sat, 29 May 2004 00:53:52 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BTvqx-0005sH-D9 for emacs-devel@gnu.org; Sat, 29 May 2004 00:53:51 -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 1BTvpz-0000bo-5a for emacs-devel@gnu.org; Sat, 29 May 2004 00:52:51 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by mx20.gnu.org with esmtp (Exim 4.34) id 1BTvCn-0004C1-G3 for emacs-devel@gnu.org; Sat, 29 May 2004 00:12:22 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BTvBp-00059C-00 for ; Sat, 29 May 2004 06:11:21 +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 ; Sat, 29 May 2004 06:11:20 +0200 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 29 May 2004 06:11:20 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 23 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:EDtjomwCct1wE62OF67/wDaxDNQ= 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:24126 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24126 On Fri, 28 May 2004, juri@jurta.org wrote: > Yes, making [next-error] a minor mode with its own file would be a > very useful thing! > > However, I think the name `next-error' is not right anymore when > applied to non-`compile' modes like `grep', `diff', `occur', and > possible future modes. This was already discussed, and the *-locus and *-match aliases were proposed. I have no preference regarding the function names, but the *minor mode* should be called next-dwim IMO. I can't think of any other names that would fit the mode, as opposed to the function. > Its name should clearly constitute its essence which is to visit the > locations described in one buffer sequentially or in a user-defined > order in other buffers. Feel free to make suggestions, everyone :) Ted