From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jorgen Schaefer Newsgroups: gmane.emacs.devel Subject: Multiple next-error sources Date: Thu, 6 Nov 2014 18:08:15 +0100 Message-ID: <20141106180815.207bf7ad@forcix> References: <20141102151524.0d9c665c@forcix> <20141102172944.0f7944e3@forcix> <20141103084433.12117c03@forcix> <86fvdwgxqs.fsf@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1415293772 6993 80.91.229.3 (6 Nov 2014 17:09:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 6 Nov 2014 17:09:32 +0000 (UTC) Cc: emacs-devel@gnu.org To: Helmut Eller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 06 18:09:25 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1XmQYl-0006NK-Sr for ged-emacs-devel@m.gmane.org; Thu, 06 Nov 2014 18:09:24 +0100 Original-Received: from localhost ([::1]:55152 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmQYk-0007AP-OI for ged-emacs-devel@m.gmane.org; Thu, 06 Nov 2014 12:09:22 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:33361) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmQYQ-0007AE-Uz for emacs-devel@gnu.org; Thu, 06 Nov 2014 12:09:10 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XmQYE-0007g8-Lw for emacs-devel@gnu.org; Thu, 06 Nov 2014 12:09:02 -0500 Original-Received: from loki.jorgenschaefer.de ([87.230.15.51]:56002) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XmQYE-0007fh-FL for emacs-devel@gnu.org; Thu, 06 Nov 2014 12:08:50 -0500 Original-Received: by loki.jorgenschaefer.de (Postfix, from userid 998) id 8CAAA2045B3; Thu, 6 Nov 2014 18:08:17 +0100 (CET) Original-Received: from forcix (port-6100.pppoe.wtnet.de [84.46.23.235]) by loki.jorgenschaefer.de (Postfix) with ESMTPSA id 9F46F2045B2; Thu, 6 Nov 2014 18:08:16 +0100 (CET) In-Reply-To: X-Mailer: Claws Mail 3.10.1 (GTK+ 2.24.25; i586-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 87.230.15.51 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:176462 Archived-At: On Thu, 06 Nov 2014 18:00:24 +0100 Helmut Eller wrote: > On Thu, Nov 06 2014, Stefan Monnier wrote: > > >> And if find-tag will provide the "multiple occurences" interface on > >> its own, there won't be a need for the "next tag" command. > > > > Good point. If we don't have a such a global-map "next-tag" command > > anymore, then I guess it's OK to change M-, to do the job of M-*. > > An idea would be to merge the next-error and next-tag commands. After > all, they are quite similar. I'm not sure if they are sufficiently similar, but there are other use cases for something like this. For example, I recently wanted to extend `next-error' to find flymake highlights. An idea I had was to replace/extend `next-error-function' with a hook where the first non-nil return value is used as the location of the next error. Regards, Jorgen