Skip to content
This repository has been archived by the owner on Nov 12, 2022. It is now read-only.

:LspInfo after installing hls throws error #844

Closed
2 tasks done
cheeze2000 opened this issue Jul 1, 2022 · 1 comment · Fixed by #847
Closed
2 tasks done

:LspInfo after installing hls throws error #844

cheeze2000 opened this issue Jul 1, 2022 · 1 comment · Fixed by #847

Comments

@cheeze2000
Copy link

Problem description

After installing hls from the ui in :LspInstallInfo and restarting neovim, hls works perfectly (autocompletion and hover work fine). The only problem is when :LspInfo is run and it throws this error:
image
image

Why do you think this is an issue with nvim-lsp-installer?

I tried installing hls from ghcup myself and removed nvim-lsp-installer from my config and :LspInfo does not throw any error

Neovim version (>= 0.7)

NVIM v0.7.2
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3

Operating system/version

Linux Mozzarella 5.10.60.1-microsoft-standard-WSL2 #1 SMP Wed Aug 25 23:20:18 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

I've manually reviewed the Nvim LPS client log (:LspLog) to find potential errors

  • Yes

I've recently downloaded the latest plugin version of both nvim-lsp-installer and nvim-lspconfig

  • Yes

Affected language servers

hls

Steps to reproduce

  1. Download the minimal debug config
  2. Include this line lspconfig.hls.setup { on_attach = on_attach }
  3. Run neovim with that config and install hls
  4. Enter any haskell project
  5. LSP works but only :LspInfo throws

Actual behavior

:LspInfo throws an error, screenshot above

Expected behavior

:LspInfo does not throw an error and it shows that 1 server is running, which is hls

LspInfo

Doing this throws an error and upon dismissing the error, it is just a blank floating window

LspLog

No, the LSP works

Healthcheck

It is included in one of the screenshots above

Screenshots or recordings

No response

williamboman added a commit that referenced this issue Jul 3, 2022
Since these executables are not installed on PATH, lspconfig's
implementation in their `lspinfo` function will throw an error.
This overrides that function with an exact copy, with the only
difference being that we supply the absolute path to the command.

Closes #844.
williamboman added a commit that referenced this issue Jul 3, 2022
Since these executables are not installed on PATH (yet..), lspconfig's
implementation in their `lspinfo` function will throw an error. This
overrides that function with an exact copy, with the only difference
being that we supply the absolute path to the command.

Closes #844.
@williamboman
Copy link
Owner

Hello! Should be fixed in #847

williamboman added a commit that referenced this issue Jul 3, 2022
…le (#847)

Since these executables are not installed on PATH (yet..), lspconfig's
implementation in their `lspinfo` function will throw an error. This
overrides that function with an exact copy, with the only difference
being that we supply the absolute path to the command.

Closes #844.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
2 participants