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: Thu, 03 Jun 2004 11:30:14 -0400 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <4n3c5c64mx.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> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1086277726 26012 80.91.224.253 (3 Jun 2004 15:48:46 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 3 Jun 2004 15:48:46 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Thu Jun 03 17:48:20 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 1BVuS3-0006gM-00 for ; Thu, 03 Jun 2004 17:48:19 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BVuS2-0003mU-00 for ; Thu, 03 Jun 2004 17:48:19 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BVuSM-0002fv-6J for emacs-devel@quimby.gnus.org; Thu, 03 Jun 2004 11:48:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BVuSJ-0002fi-Pi for emacs-devel@gnu.org; Thu, 03 Jun 2004 11:48:35 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BVuSH-0002fW-KB for emacs-devel@gnu.org; Thu, 03 Jun 2004 11:48:35 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BVuSH-0002fM-GQ for emacs-devel@gnu.org; Thu, 03 Jun 2004 11:48:33 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BVuRV-0004ae-TA for emacs-devel@gnu.org; Thu, 03 Jun 2004 11:47:46 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BVuRV-0007Jk-00 for ; Thu, 03 Jun 2004 17:47: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 ; Thu, 03 Jun 2004 17:47:45 +0200 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 03 Jun 2004 17:47:45 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 42 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:BbA16xhvnWT74XcqETGlRVQl+mc= 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:24477 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:24477 On Wed, 02 Jun 2004, rms@gnu.org wrote: >> Is it time to make next-error a minor mode with its own next-error.el > > file? > > > > We already have a minor mode for this: compilation-minor-mode. > > Yes, but the name "compilation-minor-mode" hardly addresses the DWIM > nature of next-error as it stands now, and the compilation-minor-mode > has other side effects (fontification, for instance). > > Those go together because they are used together. > > Introducing unnecessary levels of abstraction for small things > creates clutter. I'm trying to make next-error a universal "next DWIM" interface, and being tied to compilation-minor-mode will hamper that effort. For instance, it would look very strange if compilation-minor-mode was on in a mail article summary, even though next-error (or some sensibly named alias) could make sense for moving to the next article. It would be easier to name hooks for next-error, as well, if it had its own mode. I would like to create hooks that developers can easily use to register their next-error capability, instead of the current situation where next-error mode has to be enabled by magically setting a variable, and discovering next-error buffers is an error-prone algorithm. I'm thinking of next-error-register and next-error-unregister functions a developer would call in a buffer; to register a next-error-function has to be provided (plus other things, probably) and in return the buffer is registered as a next-error capable buffer. Also, users will be less confused if next-error has its own minor mode. > We do not want a separate mode for next-error parsing alone, > distinct from the rest of error handling. Understood. I would like to make next-error more than that. Ted