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: Tue, 11 May 2004 11:36:57 -0400 Organization: =?koi8-r?q?=F4=C5=CF=C4=CF=D2=20=FA=CC=C1=D4=C1=CE=CF=D7?= @ Cienfuegos Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: <4nn04fgeli.fsf@lifelogs.com> References: <871xluig40.fsf@mail.jurta.org> <873c6983t9.fsf@mail.jurta.org> <8765b3vm0r.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 1084291142 2074 80.91.224.253 (11 May 2004 15:59:02 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 11 May 2004 15:59:02 +0000 (UTC) Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue May 11 17:58:57 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 1BNZei-0001YM-00 for ; Tue, 11 May 2004 17:58:56 +0200 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1BNZei-0007lw-00 for ; Tue, 11 May 2004 17:58:56 +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 1BNZdg-0000o4-VL for emacs-devel@quimby.gnus.org; Tue, 11 May 2004 11:57:53 -0400 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BNZaq-00007m-Dq for emacs-devel@gnu.org; Tue, 11 May 2004 11:54:56 -0400 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BNZYy-0007r2-JL for emacs-devel@gnu.org; Tue, 11 May 2004 11:53:32 -0400 Original-Received: from [80.91.224.249] (helo=main.gmane.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BNZYv-0007qW-RI for emacs-devel@gnu.org; Tue, 11 May 2004 11:52:58 -0400 Original-Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BNZYv-0006Kw-00 for ; Tue, 11 May 2004 17:52:57 +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 ; Tue, 11 May 2004 17:52:57 +0200 Original-Received: from tzz by asimov.bwh.harvard.edu with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 11 May 2004 17:52:57 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-To: emacs-devel@gnu.org Original-Lines: 26 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:WK2FvnxxyodnE/xgogNLHe1qhEM= 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:23152 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:23152 On Tue, 11 May 2004, juri@jurta.org wrote: > It seems nobody really tried yet to use two or more different > compile/grep/occur processes at the same time. Otherwise, > it would be apparent that this behavior is the most useful. Juri, while I have no particular attachment to the current next-error logic or to your replacement suggestions, I'd like to mention that my goal when I wrote the next-error patch was NOT to facilitate multiple grep/compile/occur processes simultaneously, but to provide a SINGLE interface to all of them through next-error. In other words, I wanted C-x ` to work no matter what single task I was doing. It's very possible that different approaches to multiple next-error client buffers will emerge from this discussion; my only suggestion is that the eventual API should have a few presets, but otherwise be function-based so users can install any logic they like. The basic question we want to ask the user is, "what next?" and DWIM can be very hard with such intuitive tasks. I'll be glad to help with suggestions and code to implement the changes you want in the next-error API. Thanks Ted