From: "João Távora" <joaotavora@gmail.com>
To: David Ventimiglia <davidaventimiglia@neptunestation.com>
Cc: 59824@debbugs.gnu.org
Subject: bug#59824: flymake-show-project-diagnotics not updating (eglot for Java with jdtls)
Date: Sun, 4 Dec 2022 20:46:56 +0000 [thread overview]
Message-ID: <CALDnm50Dd2XsZWj7apVscEGiVvrLEH9yrMudzgP_arZ8Xshp7A@mail.gmail.com> (raw)
In-Reply-To: <CAPTUb8YsSQmGWOcJueK2F8pGfe0F2B3cJY88MEdYMjtSn9Zx3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]
Thanks David. Please also repost here the transcripts of the events buffer
that you collected and shared in the original discussion, for convenience.
On Sun, Dec 4, 2022, 20:39 David Ventimiglia <
davidaventimiglia@neptunestation.com> wrote:
> Hello,
>
> When I run flymake-show-project-diagnostics some warnings are listed for
> my Java project. As I jump to those locations and fix the warnings, the
> diagnostics buffer doesn't update. One problem I have is that I don't even
> know where to begin to look in order to troubleshoot this. It could be a
> problem with eglot, jdtls, flymake, or some combination thereof. I started
> a GitHub discussion for the eglot project here:
>
> https://github.com/joaotavora/eglot/discussions/1131#discussion-4626934
>
> In summary, for Java if I add say an unused import to a file, jdtls
> publishes a diagnostic event for this and the flymake buffer shows a
> warning for the unused import. If I correct the issue by deleting the
> unused import, jdtls again publishes a correct diagnostic report for the
> file, but the flymake diagnostics buffer doesn't update.
>
> After some correspondence with its maintainer, I believe we ruled out the
> jdtls server, since the events buffer seems to show an accurate diagnostics
> report being delivered from the server to Emacs/eglot/flymake. We're
> wondering if perhaps the problem lies therefore in eglot and/or flymake. I
> should also say that I'm using the "stock" eglot and flymake built into
> Emacs, as I'm using emacs-snapshot. Here's my Emacs version info:
>
> GNU Emacs 30.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.33,
> cairo version 1.16.0) of 2022-12-03
>
> I grant that this may not be a bug and could be a mis-configuration, but I
> am trying to track that down. Thanks!
>
> Best,
> David Ventimiglia
>
>
[-- Attachment #2: Type: text/html, Size: 2408 bytes --]
next prev parent reply other threads:[~2022-12-04 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 20:38 bug#59826: flymake-show-project-diagnotics not updating (eglot for Java with jdtls) David Ventimiglia
2022-12-04 20:46 ` João Távora [this message]
2022-12-04 21:03 ` bug#59824: " João Távora
2022-12-04 23:22 ` David Ventimiglia
2022-12-05 11:30 ` João Távora
2022-12-05 22:28 ` David Ventimiglia
2022-12-07 11:34 ` João Távora
2022-12-05 22:27 ` bug#59826: additional info David Ventimiglia
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=CALDnm50Dd2XsZWj7apVscEGiVvrLEH9yrMudzgP_arZ8Xshp7A@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=59824@debbugs.gnu.org \
--cc=davidaventimiglia@neptunestation.com \
/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).