Neovim: how to setup Sui-Move for neovim

[Menh1505]

• I want to try coding with Sui Move in Neovim, but I'm a beginner and I don't really understand how LSP works. I installed sui-cli and configured it with nvim-lspconfig, but it’s not working.

• Here’s my configuration in Neovim:
  

• The server is being initiated, but I get the following error:
  
  

• Is there a way to set up Sui Move development in Neovim??

[hapeeeeee]

First of all, the process shown in the screenshot is move-analyzer, not sui-move-analyzer, so it seems that you are not using our LSP program.

Additionally, in the logs, you can see that the LSP server is already running and has successfully compiled the program. You can try using features like Go to Definition or Hover to check its functionality.

Lastly, you might be wondering why the plugin does not provide syntax highlighting. In our analyzer, syntax highlighting relies on move-msl-syx, which is based on VSCode’s regular expressions to achieve highlighting.

Hope this helps!

[johnsaigle]

@Menh1505 I was able to get it to work using the Lua I posted here: mason-org/mason.nvim#2006 (comment)

[jawoznia]

I will add to it native config for anyone searching for such approach.

Minimal config for neovim v0.11.3 without Mason or nvim-lspconfig

local on_attach = function(_, bufnr)
-- your key bindings
end

vim.lsp.config("sui-move-analyzer", {
    on_attach = config.on_attach,
    cmd = { "sui-move-analyzer" },
    filetypes = { "move" },
    root_markers = { "Move.toml", ".git" },
})

vim.lsp.enable("sui-move-analyzer")

-- for highlighing
return { "yanganto/move.vim", branch = "sui-move" },

It's not updating lint checks on edit/save for me though and sometimes I'm stuck with the errors that are not relevant anymore. Not sure if it is an issue with setup or the analyzer.

[johnsaigle]

It's probably an issue with the set-up. Often with these sorts of plugins, there is logic needed to re-run on save as well as clear old errors.

[hapeeeeee]

It's not updating lint checks on edit/save for me though and sometimes I'm stuck with the errors that are not relevant anymore. Not sure if it is an issue with setup or the analyzer.

Yes, there are some issue in lint, we have found this. and we will pulish a new version tomorrow to fix it

[hapeeeeee]

we have update new version, the only thing you need do is update extension to 1.4.8 and restart your vscode/cursor

[jawoznia]

Working much better, thanks ;)