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: Sun, 29 Sep 2024 18:20:14 +0100 [thread overview]
Message-ID: <CALDnm53+v=CbNOOcL=E=CWzKF1hFdeREKqJ-N58rGQ33t_SEgg@mail.gmail.com> (raw)
In-Reply-To: <452a24b1-14e8-40a6-b921-a26522278a82@fbengineering.ch>
[-- Attachment #1: Type: text/plain, Size: 1006 bytes --]
On Sun, Sep 29, 2024, 18:00 Federico Beffa <federico.beffa@fbengineering.ch>
wrote:
> On 28/09/2024 23:18, João Távora wrote:
>
> On Sat, Sep 28, 2024 at 4:23 PM Federico Beffa
> ... Anyway, I couldn't reproduce your problem simply because the Main.hs
> program you provided does not seem to produce any diagnostics, according
> the haskell-language-server I installed in my system, which identifies
> itself as
>
> haskell-language-server version: 1.9.1.0 (GHC: 9.2.8) (PATH: /usr/bin/haskell-language-server)
>
>
> This is not the version I indicated in the `README.md` file: GHC 9.6.5
> with the supported haskell-language-server 2.8.0.0 (indicated in the
> initial bug report).
>
Well that's the server archlinux has on its repos.
Please use the indicated tool versions.
>
No I won't do that, sorry. Maybe you'll find someone who has time to
install your specific toolkit. But you can try out my recipe and see if you
get the one-char underlines I got.
João
>
[-- Attachment #2: Type: text/html, Size: 2070 bytes --]
next prev parent reply other threads:[~2024-09-29 17:20 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 [this message]
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
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='CALDnm53+v=CbNOOcL=E=CWzKF1hFdeREKqJ-N58rGQ33t_SEgg@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).