From: Dmitry Gutov <dmitry@gutov.dev>
To: Federico Beffa <federico.beffa@fbengineering.ch>, 73500@debbugs.gnu.org
Subject: bug#73500: eglot: diagnostic location not always shown
Date: Tue, 1 Oct 2024 19:08:08 +0300 [thread overview]
Message-ID: <1f4a7412-4bbf-4d08-ab41-e92d0398b541@gutov.dev> (raw)
In-Reply-To: <f6b90279-f593-48ec-9b33-e7862213272a@fbengineering.ch>
Hi!
I cannot comment on the whole previous discussion, but what I'm seeing
here's is both diagnostics are rendered, but one of them (the first one)
gets lost inside the second one visually.
Is that the problem?
On 26/09/2024 16:49, Federico Beffa via Bug reports for GNU Emacs, the
Swiss army knife of text editors wrote:
> The first diagnostics (corresponding to the above code) is shown in the
> Emacs buffer only with an exclamation mark in the fringe. However, the
> diagnostic message is not shown anywhere unless the cursor is placed on
> the exact location in question (the 'x' in the square brakes). Without
> any visual aid, it's very difficult to pinpoint the exact location of
> the problem to see the message.
That's a fair complaint, but we have a limited number of tools at our
disposal. For warnings, we use underlines, and the color of the
underline is set. When there are several diagnostics in the same place,
they can get difficult to distinguish, true.
> The other diagnostic in the same server message, on top of the
> exclamation mark, it's properly highlighted with a blue wiggled
> underline and easy to locate. I'd expect this to happen for all diagnostics.
When you say "this", what exactly would you expect to happen, and when?
Eglot prints diagnostics (through Flymake) at the positions that the
language server reports them for. The second diagnostic spans the whole
line; the first one is reported to be just 1 character long.
One existing way to see the warnings separate from each other is invoke
Flymake's diagnostics buffer: 'M-x flymake-show-buffer-diagnostics'. It
shows this:
1 1 warning e-f-b typecheck [-Wmissing-signatures]: Top-level
binding with no type signature:
1 1 warning e-f-b compile [-Wincomplete-patterns]: Pattern
match(es) are non-exhaustive
1 14 warning e-f-b typecheck [-Wunused-matches]: Defined but
not used: ‘x’
next prev parent reply other threads:[~2024-10-01 16:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-26 13:49 bug#73500: eglot: diagnostic location not always shown Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-28 11:16 ` Eli Zaretskii
2024-09-28 11:47 ` João Távora
2024-09-28 15:23 ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-28 21:18 ` João Távora
[not found] ` <452a24b1-14e8-40a6-b921-a26522278a82@fbengineering.ch>
2024-09-29 17:20 ` João Távora
2024-09-29 18:59 ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-29 21:18 ` João Távora
2024-09-30 9:19 ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-30 9:41 ` João Távora
[not found] ` <bee5efd8-c015-43d1-b37d-392d4ffc08d7@fbengineering.ch>
[not found] ` <CALDnm501CMXD8x_9s6Hm0fD5_+K4wmH58t7wXf5buKDuU+=vGg@mail.gmail.com>
2024-09-30 12:08 ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-30 15:32 ` João Távora
2024-09-30 15:45 ` Federico Beffa
2024-10-01 16:08 ` Dmitry Gutov [this message]
2024-10-01 16:32 ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-01 19:48 ` Dmitry Gutov
2024-10-01 20:18 ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-01 20:39 ` Dmitry Gutov
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1f4a7412-4bbf-4d08-ab41-e92d0398b541@gutov.dev \
--to=dmitry@gutov.dev \
--cc=73500@debbugs.gnu.org \
--cc=federico.beffa@fbengineering.ch \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.