From: "João Távora" <joaotavora@gmail.com>
To: Federico Beffa <federico.beffa@fbengineering.ch>
Cc: 73500@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#73500: eglot: diagnostic location not always shown
Date: Mon, 30 Sep 2024 10:41:09 +0100 [thread overview]
Message-ID: <CALDnm51yu8vB8LUqcDaLn9cMQQOFtw0kP4L1X5M2HoUeFnMZJg@mail.gmail.com> (raw)
In-Reply-To: <c2210a41-e9d8-4f3c-b941-8e16fd781bf1@fbengineering.ch>
On Mon, Sep 30, 2024 at 10:19 AM Federico Beffa
<federico.beffa@fbengineering.ch> wrote:
>
> A few questions:
> * have you checked the provided lsp*.log files which show that the diagnostics is sent?
Yes. But I don't get that log, as I already showed.
> * have you checked the provided screenshots showing an exclamation mark in the fringe but no underlining?
These are not from emacs -Q so I ignored them. For all I know you may have a
(imaginary-bugs) in your init file. Or have a different setting of the
underlining face
to something that can't be rendered.
A screenshot of a clean Emacs -Q would have been slightly more useful (well
not really useful, but more interesting at least).
> * How do you explain the exclamation mark in the fringe which doess not appear if eglot is not enabled?
That's an odd question. I don't, of course. Much as I can't "explain"
that grainy
footage that someone says they took of bigfoot. Maybe bigfoot exists, maybe
it's just a far away hunchback person. I'll have a better change of
"explaining" something once I can investigate it myself, and so far
I haven't been able to reproduce your sighting.
> * Do you also see the exclamation mark in the fringe on the line in question?
No, when I tried your Emacs -Q recipe I didn't see any diagnostics. I
thought I
explained that.
> * Does "cabal run" works? Do you see the output? If not please provide the complete error message.
Eglot doesn't interact with cabal, it interacts via LSP with
haskell-language-server.
I can tell you I managed a successful interaction where the server in question
connected perfectly and analized the Main.hs program you provided. When
Tweaking the program, I got some diagnostics. As far as I'm concerned
witnessed first hand in an Emacs -Q session, Eglot correctly underlines all
diagnostics coming from that server, which is not suprising to me, since
they look a lot like any other diagnostic coming from any other server and
Eglot doesn't care about the provenance of diagnostics.
Also, I uninstalled everything haskell, it bloated up my system and I don't plan
on installing it again..
João
next prev parent reply other threads:[~2024-09-30 9:41 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 [this message]
[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
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=CALDnm51yu8vB8LUqcDaLn9cMQQOFtw0kP4L1X5M2HoUeFnMZJg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=73500@debbugs.gnu.org \
--cc=eliz@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 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).