From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.devel Subject: Re: next-error use cases Date: Wed, 20 May 2020 01:12:38 +0300 Organization: LINKOV.NET Message-ID: <871rnfbmll.fsf@mail.linkov.net> References: <87zi2esn7l.fsf@mail.linkov.net> <87r2nknpaz.fsf@mail.linkov.net> <83y3hr5z35.fsf@gnu.org> <87d0z2anv8.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="119342"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (x86_64-pc-linux-gnu) Cc: emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed May 20 00:25:54 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jbAgM-000UxM-5I for ged-emacs-devel@m.gmane-mx.org; Wed, 20 May 2020 00:25:54 +0200 Original-Received: from localhost ([::1]:52154 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jbAgL-0004Bo-7S for ged-emacs-devel@m.gmane-mx.org; Tue, 19 May 2020 18:25:53 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44096) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbAfs-0003m7-Rr for emacs-devel@gnu.org; Tue, 19 May 2020 18:25:25 -0400 Original-Received: from relay9-d.mail.gandi.net ([217.70.183.199]:35123) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jbAfq-00015d-F6 for emacs-devel@gnu.org; Tue, 19 May 2020 18:25:24 -0400 X-Originating-IP: 91.129.97.200 Original-Received: from mail.gandi.net (m91-129-97-200.cust.tele2.ee [91.129.97.200]) (Authenticated sender: juri@linkov.net) by relay9-d.mail.gandi.net (Postfix) with ESMTPSA id 1B390FF803; Tue, 19 May 2020 22:25:18 +0000 (UTC) In-Reply-To: (Dmitry Gutov's message of "Tue, 19 May 2020 04:10:51 +0300") Received-SPF: pass client-ip=217.70.183.199; envelope-from=juri@linkov.net; helo=relay9-d.mail.gandi.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/05/19 18:25:20 X-ACL-Warn: Detected OS = Linux 3.11 and newer X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001 autolearn=_AUTOLEARN X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:250987 Archived-At: > I have to say it's a solid improvement over the previous related change. > > And one peculiarity: if I'm not mistaken, the value of next-error-buffer > itself is never used in the current code, there's only the check > (local-variable-p 'next-error-buffer) that references it, effectively > turning it into a buffer-local boolean. > > But it could probably still be used in custom values of > next-error-find-buffer-function. > > Too bad it didn't solve the flymake+next-error-function problem, but that > seems more difficult. > > Some rough idea: pick some similar keybinding in flymake-supported buffers > ('C-c C-c'? wouldn't it be too presumptuous to take over?)... and make it, And bind it to next-error-select-buffer. > I don't know, echo the error text? Or (!) show the diagnostics buffer, for > which there's no default key binding still. And in the end, call > next-error-found. Indeed, using the diagnostics buffer is a good idea (even without showing it).