vim.lsp.config['rust-analyzer'] or vim.lsp.config['rust_analyzer']?

[Spxg]

Checked other resources

• This is not a bug report or feature request (Please use issues for those).
• This is a question about rustaceanvim, not rust-analyzer or Neovim.
• This is not a question about autocompletion.
• I have read the README.
• I have read the FAQ.
• I have searched for a solution using :h rustaceanvim.
• I have searched existing discussions.
• I have searched the existing issues/discussions of other plugins related to this question (if applicable).
• I have searched the existing rust-analyzer discussions (if applicable).
• I have added a very descriptive title to this question.

Description

The vim.lsp example uses rust_analyzer
https://github.com/neovim/nvim-lspconfig/blob/f0c6ccf43997a1c7e9ec4aea36ffbf2ddd9f15ef/lsp/rust_analyzer.lua#L10

rustaceanvim use rust-analyzer, will this have any impact?

rustaceanvim/lua/rustaceanvim/lsp/init.lua

Line 11 in eb606eb

local ra_client_name = 'rust-analyzer'

rustaceanvim/lua/rustaceanvim/lsp/init.lua

Line 165 in eb606eb

local ra_config = vim.lsp.config[ra_client_name] or {}

Example Code

no example code

Neovim version (nvim -v)

v0.11.2

Operating system/version

macOS 15.6

Output of :checkhealth rustaceanvim

1 ==============================================================================
  2 rustaceanvim:                                                               ✅
  3
  4 Checking for Lua dependencies
  5 - ✅ OK optional dependency nvim-dap not installed. Needed for debugging features [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap)
  6
  7 Checking external dependencies
  8 - ✅ OK rust-analyzer: found rust-analyzer 0.3.2519-standalone (6df12139bc 2025-06-29)
  9 - ✅ OK Cargo: found cargo 1.81.0-nightly (4dcbca118 2024-06-11)
 10 - ✅ OK rustc: found rustc 1.81.0-nightly (f1586001a 2024-06-13)
 11 - ✅ OK cargo-nextest: found cargo-nextest 0.9.99 (c8d5aac09 2025-06-16)
 12 - ✅ OK lldb: found lldb version 20.1.7
 13
 14 Checking config
 15 - ✅ OK No errors found in config.
 16
 17 Checking for conflicting plugins
 18 - ✅ OK No conflicting plugins detected.
 19
 20 Checking for tree-sitter parser
 21 - ✅ OK tree-sitter parser for Rust detected.
 22 - ✅ OK .vscode/settings.json loaded without errors.

[mrcjkb]

If you're using rustaceanvim, you shouldn't enable nvim-lspconfig's rust_analyzer configuration.
rustaceanvim is its own plugin, independent of nvim-lspconfig.

See also this discussion.