From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: next-error use cases Date: Mon, 09 Apr 2018 23:47:17 +0300 Organization: LINKOV.NET Message-ID: <878t9wp0oa.fsf@mail.linkov.net> References: <87zi2esn7l.fsf@mail.linkov.net> <83in91zu5o.fsf@gnu.org> <834lkkzb9n.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1523307117 14879 195.159.176.226 (9 Apr 2018 20:51:57 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 9 Apr 2018 20:51:57 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: Eli Zaretskii , emacs-devel@gnu.org, dgutov@yandex.ru To: charles@aurox.ch (Charles A. Roelli) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 09 22:51:53 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 1f5dlX-0003fn-Kb for ged-emacs-devel@m.gmane.org; Mon, 09 Apr 2018 22:51:51 +0200 Original-Received: from localhost ([::1]:38040 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f5dnd-0000IZ-Ff for ged-emacs-devel@m.gmane.org; Mon, 09 Apr 2018 16:54:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49161) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f5dlt-0007PY-1R for emacs-devel@gnu.org; Mon, 09 Apr 2018 16:52:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f5dls-0008PB-6F for emacs-devel@gnu.org; Mon, 09 Apr 2018 16:52:13 -0400 Original-Received: from sub3.mail.dreamhost.com ([69.163.253.7]:55538 helo=homiemail-a75.g.dreamhost.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f5dlq-0008Ni-QE; Mon, 09 Apr 2018 16:52:10 -0400 Original-Received: from homiemail-a75.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a75.g.dreamhost.com (Postfix) with ESMTP id CEAF15EC07C; Mon, 9 Apr 2018 13:52:09 -0700 (PDT) Original-Received: from localhost.linkov.net (m91-129-105-236.cust.tele2.ee [91.129.105.236]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: jurta@jurta.org) by homiemail-a75.g.dreamhost.com (Postfix) with ESMTPSA id 362495EC07F; Mon, 9 Apr 2018 13:52:07 -0700 (PDT) In-Reply-To: (Charles A. Roelli's message of "Mon, 09 Apr 2018 20:44:42 +0200") X-detected-operating-system: by eggs.gnu.org: Windows NT kernel [generic] [fuzzy] X-Received-From: 69.163.253.7 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:224476 Archived-At: >> > > Define some kind of priority between them? >> > I really doubt we can define priorities such that the user will alwa= ys >> > want to see the errors of some "kind" before the others. >> >> Then maybe this problem has no workable solution at all, and we >> shouldn't try running all those features from the same command. > > We could try, but in cases of doubt, ask the user what "next-error" > function he wants to use (and provide some command for actively > switching between them). For example, after calling "next-error" in > some dubious case, the user could be offered a list of functions to > choose between: > > - next Compile error from *compile* > - next Occur result from *scratch* > - next Grep result from *grep* > ... Answering this after every next-error command would be too tedious for us= ers, and it's not clear how to reduce the frequency of such questions, i.e. how to detect only dubious cases. > There could also be other interfaces to pick a next-error function (a > menu, or something like M-x list-buffers). Recently we created such command with the name =E2=80=98next-error-select= -buffer=E2=80=99. Still too inconvenient for users to run this command explicitly. We need next-error to be more DWIM.