How to use hover range?

[afonsolage]

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

Sorry if this is a dumb question, but I couldn't find the answer anywhere. How to use the hover range cmd?

                        vim.keymap.set("v", "K",
                        function()
                                vim.cmd.RustLsp { 'hover', 'range' }
                        end, opts)

hover actions works fine, but with this command, when I select multiple lines, nothing is shown.

Example Code

vim.keymap.set("v", "K",
                        function()
                                vim.cmd.RustLsp { 'hover', 'range' }
                        end, opts)

Neovim version (nvim -v)

0.11

Operating system/version

NixOS 25.05

Output of :checkhealth rustaceanvim

==============================================================================
rustaceanvim:                                                               ✅

Checking for Lua dependencies ~
- ✅ OK [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap) installed.

Checking external dependencies ~
- ✅ OK rust-analyzer: found rust-analyzer 1.90.0-nightly (adcb3d3 2025-07-31)
- ✅ OK Cargo: found cargo 1.90.0-nightly (9b296973b 2025-07-25)
- ✅ OK rustc: found rustc 1.90.0-nightly (adcb3d3b4 2025-07-31)
- ✅ OK debug adapter: found codelldb 

Checking config ~
- ✅ OK No errors found in config.

Checking for conflicting plugins ~
- ✅ OK No conflicting plugins detected.

Checking for tree-sitter parser ~
- ✅ OK tree-sitter parser for Rust detected.

[mrcjkb]

Are you sure it's not working? I just tried it (by sourcing your example) and it works fine on my end.
One thing to keep in mind is that the hover range feature has different behaviour than the hover feature.

• Generally, it will only show you the type of what you have selected.
• If it can't determine the type, it'll just show () (unit type), which opens a very small hover window.

[afonsolage]

Thanks, you right, I misunderstood what it does.