Issue with rust-analyzer LSP: helix tries to use the "wrong" channel #9226
Replies: 2 comments
-
Ok, I think that I understand: the project I was peeking into has a
So I guess this means that helix (or my terminal?) finds this file, and then forces rust tooling to use the 1.65.0? Is there a way / would it make sense to overwrite this behavior in helix somehow, so that I do not need to end up installing loads of versions of rust-analyzer that match every possible project I want to peek into? |
Beta Was this translation helpful? Give feedback.
-
This is not a helix issue, this is just how rustup works. You can either install |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have helix installed:
and the rust-analyzer installed too:
However, it seems that helix does not like the channel for which the rust-analyzer is installed: when I open a project in the current project, the rust-analyzer lsp does not seem to work, and the
log-open
command gives me the reason in the logs:Checking my rustup, there is indeed such a version of the toolchain, but it is not my default:
How should I make this work? :) Any way to force helix to use the "correctly installed and working" rust-analyzer version? Or should I install / maintain a number of different versions of the rust-analyzer?
Beta Was this translation helpful? Give feedback.
All reactions