-
Notifications
You must be signed in to change notification settings - Fork 31
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
if the server is started as a systemd service then it can't find rust-analyzer
#69
Comments
"Sometimes?" Does this really not happen every time? I'd expect this to be a difference between your systemd-user PATH and the path of your editor, probably your rust-analyzer is installed in ~/.rustup/... or ~/.cargo/bin and you only add that to your PATH in the shell initialization script, which doesn't get included in systemd-user environment. |
rust-analyzer
rust-analyzer
It worked fine for months and then last week I started having the problem of it not finding |
Hmm, and the only thing that change was a new version of |
I've added more context to the error message from the description here 247736b, that should help you figure out what's wrong with the PATH in the systemd service. |
I had the same problem and the The whole setup process I used is described here: https://gist.github.com/sasa-tomic/a53302b9935c2c13717f60cd86369579 |
You would get an error message like the above in
systemctl status ra-multiplex
This is solved by
pass_environment = ["PATH"]
in the ra-multiplex configThe text was updated successfully, but these errors were encountered: