unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: 50244@debbugs.gnu.org, Philipp Stephani <p.stephani2@gmail.com>,
	Theodor Thornhill <theo@thornhill.no>
Subject: bug#50244: 28.0.50; Support project-wide diagnostics reports in flymake.el
Date: Mon, 13 Sep 2021 19:03:19 +0100	[thread overview]
Message-ID: <87o88w4al4.fsf@gmail.com> (raw)
In-Reply-To: <CALDnm52w9JyV8R4dKm0bYtmOKZcY6NYgA9LjzH8=70JT9ozfEQ@mail.gmail.com> ("João Távora"'s message of "Mon, 13 Sep 2021 07:48:31 +0100")

João Távora <joaotavora@gmail.com> writes:

> On Mon, Sep 13, 2021 at 1:08 AM Dmitry Gutov <dgutov@yandex.ru> wrote:
>
>> Or maybe you will have unique "show diagnostics" buffers for every
>> project, to be invoked manually?
>
> This.  But it doesn't seem impossible to make a global diagnostics
> buffer for every project one has open.

The main changes to flymake.el and its documentation are now ready to
push.  There are some bugs regarding sorting in the diagnostics listing,
and the maybe order and length of columns needs rearranging, but these
can be sorted out later.

The only outstanding issue preventing me from landing this in main is
that I need to bump project.el's version so that the new
`project-buffers` API generic function becomes officially available to
the new bumped flymake.el version.  Dmitry is it OK for me to do so?

Here's the trivial patch to project.el.  I'm bumping the minor version
becasue a new backward-compatible feature was added.  I can bump
whatever you prefer if you think it's more in-line with the versioning
scheme you normally use.

diff --git a/lisp/progmodes/project.el b/lisp/progmodes/project.el
index ba95ed094e..a6e231b9d6 100644
--- a/lisp/progmodes/project.el
+++ b/lisp/progmodes/project.el
@@ -1,7 +1,7 @@
 ;;; project.el --- Operations on the current project  -*- lexical-binding: t; -*-
 
 ;; Copyright (C) 2015-2021 Free Software Foundation, Inc.
-;; Version: 0.6.1
+;; Version: 0.7.1
 ;; Package-Requires: ((emacs "26.1") (xref "1.0.2"))
 
 ;; This is a GNU ELPA :core package.  Avoid using functionality that

Another important aspect is that I haven't had a change to test this
with Eglot, which was one of the main motivators behind this change.
The reason is that I don't have easy access to a server which reports
diagnostics project wide (I thought clangd did, but I was mistaken).  So
the only client of the new functionality is the flymake-cc non-LSP
backend, for now.

Theodor, now would be a good time for you to step in with changes to
Eglot that use the new `flymake-list-only-diagnostics` experimental API
in flymake.el.  Likely, some adjustments will have to be made to both
packages.

Thanks,
João









  reply	other threads:[~2021-09-13 18:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-29  0:53 bug#50244: 28.0.50; Support project-wide diagnostics reports in flymake.el João Távora
2021-08-29 23:27 ` Dmitry Gutov
2021-08-30  7:00   ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-30  8:46   ` João Távora
2021-09-11  1:08 ` João Távora
2021-09-13  0:08   ` Dmitry Gutov
2021-09-13  6:48     ` João Távora
2021-09-13 18:03       ` João Távora [this message]
2021-09-13 19:47         ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-13 20:04           ` João Távora
2021-09-13 20:21             ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-14  8:50               ` João Távora
2021-09-14  9:21                 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-14 11:34                   ` João Távora
2021-09-14 12:22                     ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-23 19:22                     ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-10-23 20:22                       ` João Távora
2021-10-23 20:50                         ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-13 20:11         ` Dmitry Gutov
2021-09-14  8:20           ` João Távora
2021-09-16 22:27             ` Dmitry Gutov
2021-09-16 23:37               ` João Távora
2021-09-13 20:26       ` Dmitry Gutov
2021-09-13 20:53         ` João Távora
2021-09-13 23:35           ` Dmitry Gutov
2021-09-14  8:43             ` João Távora
2021-09-16 22:19               ` Dmitry Gutov
2021-09-16 23:36                 ` João Távora
2021-09-18  1:19                   ` Dmitry Gutov
2021-09-18  9:59                     ` João Távora

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o88w4al4.fsf@gmail.com \
    --to=joaotavora@gmail.com \
    --cc=50244@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=p.stephani2@gmail.com \
    --cc=theo@thornhill.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).