bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#50244: 28.0.50; Support project-wide diagnostics reports in flymake.


From: Dmitry Gutov
Subject: bug#50244: 28.0.50; Support project-wide diagnostics reports in flymake.el
Date: Tue, 14 Sep 2021 02:35:51 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0

On 13.09.2021 23:53, João Távora wrote:

Anyway, I asked about this because because the use of global variable
(flymake-list-only-diagnostics) seems like it would make supporting
multiple projects at the same time more difficult.

I can't guess what you are hinting at, sorry.  You can call M-x
flymake-show-project-diagnostics in two or more projects, of course, and
you'll get separate listings.  I don't know if that counts as
"supporting multiple projects at the same time".

If a backend reports diagnostics through flymake-list-only-diagnostics, woudln't one of those values be overridden when two backends offer reports?

Again, I don't understand your suggestion, but if you can propose it in
the form of code it would be much better, since there would be no
ambiguity.  A word of caution though: making these things work correctly
in tandem with domestic diagnostics, new file visits and buffer killings
was relatively hard.  I tried many different approaches and settled on
these two ("foreign" and "list-only").  Of course if you can clearly
describe a use case where they are unsuitable, a third style may be
invented.  But I would first exhaust the possibilities in these two.

I was thinking of a way to get by with only two types: "domestic" and "foreign", without adding a third one. No code, sorry.

In the meantime, please say if version-bumping project.el is OK.  That
is the only thing holding up the merge.

Already replied to that on 13.09.2021, 23:11: yes, sure, go ahead.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]