Skip to content
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

[Question] Couldn't start client Rust Language Server #48

Closed
SangwooJung98 opened this issue Sep 2, 2020 · 6 comments
Closed

[Question] Couldn't start client Rust Language Server #48

SangwooJung98 opened this issue Sep 2, 2020 · 6 comments
Assignees
Labels
question Further information is requested

Comments

@SangwooJung98
Copy link

캡처

Although I installed Rust, codell at vscode while connected to ssh server and rustup to my laptop, I'm still getting same error message everytime I try to build the atomic.rs file.
I tried reconnecting the ssh server, deleting the .vscode-server folder but there's no difference.

My development environment is windows10.
Is there anyone who figured out a solution for this problem??

@SangwooJung98 SangwooJung98 added the question Further information is requested label Sep 2, 2020
@jeehoonkang
Copy link
Member

jeehoonkang commented Sep 2, 2020

@blue-int
Copy link

blue-int commented Sep 2, 2020

I tried the solution, but it does not work.
I installed codelldb and rust vscode extensions on the server, and ran rustup component add rls to install rls.

@blue-int
Copy link

blue-int commented Sep 2, 2020

I found the reason why. Check this issue on rust vscode extension github.
rust-lang/vscode-rust#814

@Lee-Janggun
Copy link
Member

Lee-Janggun commented Sep 2, 2020

Hello. Can I ask if you managed to get it to work? I read the issue but I do not think we can edit setting.json on the server. I instead tried what was mentioned here rust-lang/vscode-rust#620, but this did not resolve the issue.

@tomtomjhj
Copy link
Member

tomtomjhj commented Sep 2, 2020

  1. Ensure that you have ~/.cargo/bin/rustup.
  2. Ensure that your ~/.profile contains following line:
    . "$HOME/.cargo/env"
    This also works:
    export PATH="$HOME/.cargo/bin:$PATH"
  3. Create a file ~/.bash_profile with following line:
    source ~/.profile
  4. Kill the vscode remote session and restart.

This way, vscode will read the PATH set in ~/.profile without changing bash's behavior.

Reference

@Lee-Janggun
Copy link
Member

This solved the issue. Thank you very much!

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

No branches or pull requests

5 participants