Plugin doesn't starts rust-analyzer on Windows

[TheRustifyer]

Have you read the docs and searched existing issues?

• I have read the README's troubleshooting guide.
• I have searched existing issues.
• I have searched existing discussions.
• I have searched the existing issues of other plugins related to this issue (if applicable).
• I have searched the existing rust-analyzer issues (if applicable).
• I can reproduce the issue with stable Neovim (not a distribution or nightly) and the minimal config.

Neovim version (nvim -v)

v0.10.0-dev-3060+gd26943a6e

Operating system/version

Windows 11

Output of :checkhealth rustaceanvim

.: require("..health").check()

- ERROR Failed to run healthcheck for "." plugin. Exception:
  [string "require("..health").check()"]:1: module '..health' not found:
  	no field package.preload['..health']
  cache_loader: module ..health not found
  cache_loader_lib: module ..health not found
  	no file '.\\\health.lua'
  	no file 'C:\Program Files (x86)\nvim\bin\lua\\\health.lua'
  	no file 'C:\Program Files (x86)\nvim\bin\lua\\\health\init.lua'
  	no file '.\\\health.dll'
  	no file 'C:\Program Files (x86)\nvim\bin\\\health.dll'
  	no file 'C:\Program Files (x86)\nvim\bin\loadall.dll'
  	no file '.\.dll'
  	no file 'C:\Program Files (x86)\nvim\bin\.dll'
  	no file 'C:\Program Files (x86)\nvim\bin\loadall.dll'

How to reproduce the issue

Install neovim on Windows 11
Install the required plugins

Expected behaviour

It should be found, it is in the path and available. VSCode finds it.

Actual behaviour

Plugin doesn't starts rust-analyzer

The minimal config used to reproduce this issue.

{
  'mrcjkb/rustaceanvim',
  version = '^4', -- Recommended
  ft = { 'rust' },
}

[mrcjkb]

Hey 👋

Your checkhealth output tells be there's probably something wrong with your neovim installation.

What happens when you call it without the rustaceanvim arg?

[mrcjkb]

I am only being able to get it work with lsp-config and the one from rust-analyzer.

Interesting, so all those scenarios work with lspconfig, but not rustaceanvim?

If so, is this reproducible in both rustaceanvim and lspconfig with a minimal setup?

[TheRustifyer]

Sure. Exactly them same. It's kinda strange.

I cleaned my nvim installations from both Windows machines and tried again with the minimal configs. Anything changed.

What's more strange is that the plugin is loaded without problem, and commands even works too (for ex: :RustEmitAsm) but none of the related with :RustLsp. In concrete, the error is: RustLsp, command not found.

Is this telling you something different?

PD: Could you add on the checkhealth the PATH on where rustaceanvim found ra? Regarding my issue, it could be helpful for others that sometimes can face kind of similar issues.

[mrcjkb]

Sure. Exactly them same. It's kinda strange.

What do you mean by this?

What's more strange is that the plugin is loaded without problem, and commands even works too (for ex: :RustEmitAsm) but none of the related with :RustLsp. In concrete, the error is: RustLsp, command not found.

RustEmitAsm is a command created by Neovim's built-in rust filetype plugin, not rustaceanvim.
RustLsp commands are only created when the LSP client has attached. So it's to be expected that they don't work if your client isn't attaching.
The RustAnalzyer start command should be available regardless of lsp client status.

Could you add on the checkhealth the PATH on where rustaceanvim found ra?

The health check uses vim.fn.executable, which doesn't return the path.
On unix, you can run :!which rust-analyzer in command mode. I don't know what the equivalent command would be on Windows.

[TheRustifyer]

What do you mean by this?

Q: Interesting, so all those scenarios work with lspconfig, but not rustaceanvim?
If so, is this reproducible in both rustaceanvim and lspconfig with a minimal setup?

That with a minimal configuration only for rustaceanvim and other for lspconfig the issue is exactly the same

On unix, you can run :!which rust-analyzer in command mode. I don't know what the equivalent command would be on Windows.

Since I am using a bash shell the execution of ra returns me the one bundled by default with the installation of Rust via rustup.

Windows equivalent is where. Same result.

I erased the gcc based toolchain (pc-windows-gnu) via rustup, in case it was causing conflicts (after installing the pc-windows-msvc one) in any way. Anything changed

[mrcjkb]

Maybe it's best if you set the command directly, via vim.g.rustaceanvim.server.cmd (see :h rustaceanvim.config).