From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: next-error use cases Date: Mon, 09 Apr 2018 05:24:50 +0300 Message-ID: <836051yv4d.fsf@gnu.org> References: <87zi2esn7l.fsf@mail.linkov.net> <83in91zu5o.fsf@gnu.org> <878t9xu1yc.fsf@mail.linkov.net> <24bb4cb2-a295-2f49-262f-4916ab9ac1c1@gmail.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1523240571 23781 195.159.176.226 (9 Apr 2018 02:22:51 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 9 Apr 2018 02:22:51 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 09 04:22:47 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1f5MSE-00066l-O7 for ged-emacs-devel@m.gmane.org; Mon, 09 Apr 2018 04:22:46 +0200 Original-Received: from localhost ([::1]:49554 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f5MUK-0000MV-IT for ged-emacs-devel@m.gmane.org; Sun, 08 Apr 2018 22:24:56 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57259) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f5MUD-0000Kl-PF for emacs-devel@gnu.org; Sun, 08 Apr 2018 22:24:50 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f5MUA-0002JN-LG for emacs-devel@gnu.org; Sun, 08 Apr 2018 22:24:49 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44598) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f5MUA-0002JH-HJ; Sun, 08 Apr 2018 22:24:46 -0400 Original-Received: from [176.228.60.248] (port=1968 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1f5MU9-0000Pb-UU; Sun, 08 Apr 2018 22:24:46 -0400 In-reply-to: <24bb4cb2-a295-2f49-262f-4916ab9ac1c1@gmail.com> (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Sun, 8 Apr 2018 16:26:59 -0400) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:224450 Archived-At: > From: Clément Pit-Claudel > Date: Sun, 8 Apr 2018 16:26:59 -0400 > > > We could try to define priorities by ‘add-function’. > > Or we could query all backends and go to the closest location. It would match with what the user sees on the screen: if I have a flyspell underline followed by a FlyCheck error, it would visit one then the other. I don't think "closest location" is a reliable indicator in this case. next-error exists to go to the next/previous locus, which could be far away.