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: Mon, 07 Jun 2004 12:11:47 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <4nhdtnqrek.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> <4nd64j6u3p.fsf@lifelogs.com> <4n3c5c64mx.fsf@lifelogs.com> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1086625813 8484 80.91.224.253 (7 Jun 2004 16:30:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 7 Jun 2004 16:30:13 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Mon Jun 07 18:30:05 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 1BXN0f-0004y4-00 for ; Mon, 07 Jun 2004 18:30:05 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BXN0f-000726-00 for ; Mon, 07 Jun 2004 18:30:05 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BXN1C-0005kc-QG for emacs-devel@quimby.gnus.org; Mon, 07 Jun 2004 12:30:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BXN13-0005kR-JE for emacs-devel@gnu.org; Mon, 07 Jun 2004 12:30:29 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BXN11-0005k0-M4 for emacs-devel@gnu.org; Mon, 07 Jun 2004 12:30:29 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BXN11-0005jx-Ij for emacs-devel@gnu.org; Mon, 07 Jun 2004 12:30:27 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BXN0D-0002Ca-7y for emacs-devel@gnu.org; Mon, 07 Jun 2004 12:29:38 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BXN0B-00075N-00 for ; Mon, 07 Jun 2004 18:29:35 +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, 07 Jun 2004 18:29:35 +0200 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 07 Jun 2004 18:29:35 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 27 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:za1o1KhH1gZH5wRJD2c1vcdPlLA= 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:24674 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24674 On Thu, 03 Jun 2004, rms@gnu.org wrote: > I'm trying to make next-error a universal "next DWIM" interface, > > I think it is better if we don't do that now; I am not sure it is > a good idea. > > However, if you make a proposal and argue for it, I will think about > it. I've made the case several times on this mailing list. There are two reasons: 1) There are many modes that can benefit from a next-error (or whatever it's called by then) approach. In code, for instance, next-error could move between functions. In dired, it could move to the next file. In W3 it could go back/forward in the history or between links. 2) Approaching next-error as we do now, in a haphazard fashion, implemented specifically in every mode that needs to use it, is painful for the developer. It's much easier to provide hooks, a keymap, and all the other niceties of a standalone minor mode. Users will certainly appreciate that too. Also, if and when next-error changes, developers won't have to change their code. Ted