I just started using neovim. I could get the lua language server to work but not the rust language server (rust-analyzer). When I open a rust file likehello.rs I get the error

LSP [rust_analyzer] Failed to load workspaces

and the language server is not displaying anything. When I do:checkhealth vim.lsp I get

loadOutDirsFromCheck

Concerning the neovim and rust-analyzer version:

nvim --version gives

NVIM v0.12.0-dev-1664+ge0308dc147Build type: RelWithDebInfoLuaJIT 2.1.1763318511Run "nvim -V1 -v" for more info

and

rust-analyzer-aarch64-apple-darwin --version gives

rust-analyzer-aarch64-apple-darwin --versionrust-analyzer 0.3.2683-standalone (2efc800780 2025-11-11)

What concerns the neovim settings I have: In thelsp.lua (which I call withrequire('config.lsp') from theinit.lua), I have

vim.lsp.config['lua_ls'] = {    -- Command and arguments to start the server.    cmd = { 'lua-language-server' },    -- Filetypes to automatically attach to.    filetypes = { 'lua' },    -- Sets the "workspace" to the directory where any of these files is found.    -- Files that share a root directory will reuse the LSP server connection.    -- Nested lists indicate equal priority, see |vim.lsp.Config|.    root_markers = { { '.luarc.json', '.luarc.jsonc' }, '.git' },    -- Specific settings to send to the server. The schema is server-defined.    -- Example: https://raw.githubusercontent.com/LuaLS/vscode-lua/master/setting/schema.json    settings = {        Lua = {            runtime = {                version = 'LuaJIT',            },            -- diagnostics = {            --  globals = { 'vim' },            -- }        }    }}vim.lsp.config['rust_analyzer'] = {    -- Command and arguments to start the server.    cmd = { '/Users/johnsmith/Downloads/rust-analyzer-aarch64-apple-darwin' },    -- Filetypes to automatically attach to.    filetypes = { 'rust' },    -- Root markers to identify the root directory of the workspace.    root_markers = { 'Cargo.toml', '.git' },    -- Specific settings to send to the server (optional).    settings = {        ["rust_analyzer"] = {            -- Example settings: enable/disable features in rust-analyzer            assist = {                importGranularity = "module", -- Defines import granularity (e.g., 'crate', 'module', etc.)                importPrefix = "by_self", -- Prefix to use for importing (can be 'by_self' or 'none')            },            cargo = {                loadOutDirsFromCheck = true, -- Ensures that the output directory is correctly loaded for builds            },            procMacro = {                enable = true, -- Enables procedural macros support in Rust            },            diagnostics = {                disabled = { "unresolved-proc-macro" }, -- Optionally disable specific diagnostics                enable = true, -- Enable diagnostics            },            -- You can also set other settings for rust-analyzer like:            --   - enableClippyLints            --   - checkOnSave            --   - rustfmt        }    }}vim.lsp.enable('lua_ls')vim.lsp.enable('rust_analyzer')vim.api.nvim_create_autocmd('LspAttach', {    group = vim.api.nvim_create_augroup('my.lsp', {}),    callback = function(args)        local client = assert(vim.lsp.get_client_by_id(args.data.client_id))        if client:supports_method('textDocument/implementation')        then            -- Create a keymap for vim.lsp.buf.implementation ...        end        if client:supports_method('textDocument/references') then            vim.keymap.set('n', 'grr', function()                require('fzf-lua').lsp_references()            end, { noremap = true, silent = true, buffer = args.buf })        end        -- Enable auto-completion. Note: Use CTRL-Y to select an item. |complete_CTRL-Y|        if client:supports_method('textDocument/completion') then            -- Optional: trigger autocompletion on EVERY keypress. May be slow!            -- local chars = {}; for i = 32, 126 do table.insert(chars, string.char(i)) end            -- client.server_capabilities.completionProvider.triggerCharacters = chars            vim.opt.completeopt = { 'menu', 'menuone', 'noinsert', 'fuzzy', 'popup' }            vim.lsp.completion.enable(true, client.id, args.buf, { autotrigger = true })        end        -- Auto-format ("lint") on save.        -- Usually not needed if server supports "textDocument/willSaveWaitUntil".        if not client:supports_method('textDocument/willSaveWaitUntil')            and client:supports_method('textDocument/formatting') then            vim.api.nvim_create_autocmd('BufWritePre', {                group = vim.api.nvim_create_augroup('my.lsp', { clear = false }),                buffer = args.buf,                callback = function()                    vim.lsp.buf.format({ bufnr = args.buf, id = client.id, timeout_ms = 1000 })                end,            })        end    end,})vim.diagnostic.config({    virtual_lines = ({        current_line = true,    }),})

• 1
  I think the vim-filetype of a Rust file isrust, notrs, not sure what exactly you should specify there since I just usenvim-lspconfigs defaults.

  cafce25

  – cafce25

  2025-11-24 13:58:24 +00:00

  CommentedNov 24 at 13:58
• Thank you. You were right. I thought the filetype was just the extension. At least now when checking the health it seems it detects the LSP but it is still not working and printing the error: LSP [rust_analyzer] Failed to load workspaces. I edited the post

  edamondo

  – edamondo

  2025-11-24 19:11:54 +00:00

  CommentedNov 24 at 19:11
• What's in rust-analyzer logs?

  Chayim Friedman

  – Chayim Friedman

  2025-11-24 19:42:57 +00:00

  CommentedNov 24 at 19:42
• @ChayimFriedman, by default I see no logs but I am not sure how I would access the logs

  edamondo

  – edamondo

  2025-11-25 08:08:15 +00:00

  CommentedNov 25 at 8:08

0

Start asking to get answers

Find the answer to your question by asking.

Explore related questions

See similar questions with these tags.