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: Wed, 11 Apr 2018 23:46:24 +0300 Organization: LINKOV.NET Message-ID: <87bmepo4in.fsf@mail.linkov.net> References: <87zi2esn7l.fsf@mail.linkov.net> <83in91zu5o.fsf@gnu.org> <834lkkzb9n.fsf@gnu.org> <878t9wp0oa.fsf@mail.linkov.net> <86604z3czx.fsf@stephe-leake.org> <87y3huq3ta.fsf@mail.linkov.net> <86woxe1l0l.fsf@stephe-leake.org> <8a341680-0c63-bf28-a163-11f1d9adac20@yandex.ru> 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 1523479891 28464 195.159.176.226 (11 Apr 2018 20:51:31 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 11 Apr 2018 20:51:31 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (x86_64-pc-linux-gnu) Cc: Stephen Leake , emacs-devel To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Apr 11 22:51:27 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 1f6MiF-0007GC-9F for ged-emacs-devel@m.gmane.org; Wed, 11 Apr 2018 22:51:27 +0200 Original-Received: from localhost ([::1]:57208 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f6MkL-0004F0-PG for ged-emacs-devel@m.gmane.org; Wed, 11 Apr 2018 16:53:37 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51986) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f6Mjj-0004Dq-Al for emacs-devel@gnu.org; Wed, 11 Apr 2018 16:53:02 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f6Mjf-0004Y3-Eo for emacs-devel@gnu.org; Wed, 11 Apr 2018 16:52:59 -0400 Original-Received: from sub3.mail.dreamhost.com ([69.163.253.7]:40037 helo=homiemail-a17.g.dreamhost.com) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1f6Mjf-0004Wq-7w for emacs-devel@gnu.org; Wed, 11 Apr 2018 16:52:55 -0400 Original-Received: from homiemail-a17.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a17.g.dreamhost.com (Postfix) with ESMTP id 0C7972B207E; Wed, 11 Apr 2018 13:52:52 -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-a17.g.dreamhost.com (Postfix) with ESMTPSA id E79DA2B206E; Wed, 11 Apr 2018 13:52:50 -0700 (PDT) In-Reply-To: <8a341680-0c63-bf28-a163-11f1d9adac20@yandex.ru> (Dmitry Gutov's message of "Wed, 11 Apr 2018 10:29:30 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x (no timestamps) [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:224519 Archived-At: >>> But how can you reset it when the location list is in the same buffer >>> like in case of flyspell where locations of misspelled words are >>> in the same buffer where next-error navigates, or flymake where >>> locations of errors/warnings are in the same buffer? >> >> Position point on an error message, hit enter. > > The error message is usually visible only in the minibuffer, and only w= hen > point is over the error. If it's impossible to reset it by hitting enter, then I think we have only these remaining options: 1. If next-error can't work without the requirement to have a list of Flyspell mistakes or Flycheck/Flymake errors/warnings printed in a separa= te buffer (like "*Occur*"), then such buffer can be possibly implemented as a hidden buffer with a leading space in its name like for example " *Flycheck locations*". =E2=80=98next-error-select-buffer=E2=80=99 stil= l should propose it as a candidate for selection. 2. Flycheck provides its own keybinding =E2=80=98C-c ! n=E2=80=99 for =E2= =80=98flycheck-next-error=E2=80=99 that can be used to reset the navigation. There are also analogous funct= ions =E2=80=98flymake-goto-next-error=E2=80=99 and =E2=80=98flyspell-goto-next= -error=E2=80=99. 3. Maybe providing only the command next-error-select-buffer to switch the current navigation is enough even in case when next-error-function is defined in the same buffer that will be proposed as a candidate. 4. Otherwise, if all else fails, try harder to use visibility as DWIM, i.e. hide all other navigation windows to start using Flycheck navigation from the current buffer.