all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Federico Beffa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 73500@debbugs.gnu.org
Subject: bug#73500: eglot: diagnostic location not always shown
Date: Thu, 26 Sep 2024 15:49:41 +0200	[thread overview]
Message-ID: <f6b90279-f593-48ec-9b33-e7862213272a@fbengineering.ch> (raw)

[-- Attachment #1: Type: text/plain, Size: 1916 bytes --]

I'm using `emacs` 29.4 with the `haskell-language-server` 2.8.0.0 on 
NixOS 24.05.

The following code
```haskell
isAscending [x] =True
```
produces the following diagnostic from the lsp
```elisp
(:jsonrpc "2.0" :method "textDocument/publishDiagnostics" :params
           (:diagnostics
            [(:code "-Wunused-matches" :message "Defined but not used: 
‘x’" :range
                    (:end
                     (:character 14 :line 17)
                     :start
                     (:character 13 :line 17))
                    :severity 2 :source "typecheck" :tags
                    [1])
             (:code "-Wmissing-signatures" :message "Top-level binding 
with no type signature:\n  fbeCircle :: 
svg-builder-0.1.1:Graphics.Svg.Core.Element" :range
                    (:end
                     (:character 9 :line 25)
                     :start
                     (:character 0 :line 25))
                    :severity 2 :source "typecheck")]
            :uri 
"file:///home/user/tmp/haskell/test-flake-utils/test/src/Main.hs" 
:version 0))
```
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.

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.

[-- Attachment #2: Type: text/html, Size: 2827 bytes --]

             reply	other threads:[~2024-09-26 13:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 13:49 Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-09-28 11:16 ` bug#73500: eglot: diagnostic location not always shown 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
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=f6b90279-f593-48ec-9b33-e7862213272a@fbengineering.ch \
    --to=bug-gnu-emacs@gnu.org \
    --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.