Skip to content

Using with neovim's built in LSP  #53

Open
@physicophilic

Description

Hi.

I am trying to configure neovim's built in LSP for this server. I have been able to get neovim to detect the language server, but it is crashing on launch.

I am getting the same error as in #36, but this is happening even when I am running the language server inside of neovim.

The neovim log shows same thing as commnad line:

Expand
[ ERROR ] 2021-05-28T14:12:39+0530 ] /usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:457 ]	"rpc"	"wolfram"	"stderr"	"[INFO  2021-05-28T14:12:39] Initializing Wolfram Language Server\n"
[ ERROR ] 2021-05-28T14:12:40+0530 ] /usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:457 ]	"rpc"	"wolfram"	"stderr"	"[INFO  2021-05-28T14:12:40] Language server is connecting the client through\nsocket.\n"
[ ERROR ] 2021-05-28T14:12:40+0530 ] /usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:457 ]	"rpc"	"wolfram"	"stderr"	"\n"
[ ERROR ] 2021-05-28T14:12:40+0530 ] /usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:457 ]	"rpc"	"wolfram"	"stderr"	"SocketConnect::zmqexception: \n   A ZeroMQLink exception was thrown - Connection refused (code 111)\n"
[ ERROR ] 2021-05-28T14:12:40+0530 ] /usr/share/nvim/runtime/lua/vim/lsp/rpc.lua:457 ]	"rpc"	"wolfram"	"stderr"	"[ERROR 2021-05-28T14:12:40] Cannot connect to client via socket.\n"

I am able to run the server from Mathematica itself using

initfile = "/path/to/lsp-wl/init.wls";
args = {};
Block[{$ScriptCommandLine = Prepend[args, initfile], Quit = Function[{}, Throw[Null]]},
    Catch[<< (initfile)]
];

Although I don't know if it will help, here's my neovim config for lsp-wl.

Expand
local lspconfig = require "lspconfig"
local configs = require "lspconfig/configs"
local util = require "lspconfig/util"

if not lspconfig.lsp_wl then
  configs.lsp_wl = {
    default_config = {
      cmd = {"wolfram", "-script", "/home/manish/lsp-wl/init.wls"},
      filetypes = {"mma", "wl"},
      root_dir = util.path.dirname,
      settings = {}
    }
  }
end

lspconfig.lsp_wl.setup {}

In #36 it was recommended to look at the vs-code client with claim that it would not run into this issue.
Should I try that out to figure out what I can do?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions