GNU bug report logs - #50244
28.0.50; Support project-wide diagnostics reports in flymake.el

Previous Next

Full log

Message #79 received at 50244 <at> debbugs.gnu.org (full text, mbox):

From: João Távora <joaotavora <at> gmail.com>
To: Dmitry Gutov <dgutov <at> yandex.ru>
Cc: 50244 <at> debbugs.gnu.org, Philipp Stephani <p.stephani2 <at> gmail.com>,
 Theodor Thornhill <theo <at> thornhill.no>
Subject: Re: bug#50244: 28.0.50; Support project-wide diagnostics reports in
 flymake.el
Date: Fri, 17 Sep 2021 00:37:31 +0100

Dmitry Gutov <dgutov <at> yandex.ru> writes:

> When I said "belong to default-directory", I didn't mean "reside
> inside". I meant "all diagnostics that, in the opinion of the
> diagnostics source, relate to the specified default-directory".
>
> Basically all diagnostics belonging to the project which
> default-directory belongs to (with implicit assumption that
> default-directory can uniquely identify the project).

I think I answered this is my other email.

>> Indeed, I even thought that flymake-show-project-diagnostics could go
> into the 'C-x p' map.  But users can do that easily if they want to, so
> I won't argue for that now.
>
> Uh, maybe. I was thinking we'd rather add a new keymap (in the spirit
> of Flycheck's 'C-c !') with Flymake-related commands. Then the
> "aggregated diagnostics" could be on its own button, or they could
> even be displayed by 'M-x flymake-show-diagnostics-buffer'.

OK. Could be.  Won't argue that now.

João

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.