Skip to content

How to make it basically work? #2496

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
gh67uyyghj opened this issue Dec 8, 2019 · 3 comments
Closed

How to make it basically work? #2496

gh67uyyghj opened this issue Dec 8, 2019 · 3 comments

Comments

@gh67uyyghj
Copy link

gh67uyyghj commented Dec 8, 2019

Hi all, it seems that this is a very active project compared to buggy RLS and I really need to make it work for me since I've had enough of RLS due to the memory leak in Linux. I just can't run it, I used the instructions in the root README. On VScode startup I see the error message Couldn't start client Rust Analyzer Language Server. Please help me identify why it's not running. I am using archlinux if that helps.

@gh67uyyghj
Copy link
Author

I deeply apologize, I needed to explicitly set the custom path for ra_lsp_server in order for the server to run. Probably this is more related to archlinux than rust-analyzer itself.

@lnicola
Copy link
Member

lnicola commented Dec 8, 2019

It's not an Arch issue, but a Linux one. rustup adds ~/.cargo/bin to PATH in your shell's configuration file, but if you're using a DE it won't run the shell first. So your PATH is only set for terminals.

My workaround was to add PATH DEFAULT=/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:@{HOME}/.cargo/bin:@{HOME}/.local/bin to ~/.pam_environment. Another solution would be to move ra_lsp_server to /usr/local/bin.

@matklad
Copy link
Member

matklad commented Dec 8, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants