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

Extensions possibly don't inherit PATH/environment correctly? #545

Open
colemickens opened this issue Jan 13, 2024 · 2 comments
Open

Extensions possibly don't inherit PATH/environment correctly? #545

colemickens opened this issue Jan 13, 2024 · 2 comments

Comments

@colemickens
Copy link

Does this issue occur when all extensions are disabled?: n/a

  • VS Code Version: Version: 1.84.0
  • OS Version: nixos linux 6.6.8

Steps to Reproduce:

  1. use openvscode-server with systemd
  2. use nix-environment-selector and select a shell.nix that includes rust-analyzer
  3. note that rust-analyzer can't find the binary, even if you tell it to look for rust-analyzer (aka in PATH)

this works in desktop vscodium.

@colemickens
Copy link
Author

Oh, I left out the most interesting part, terminals launched after restarting seem to have inherited PATH though. I don't have rust-analyzer installed system wide, yet I can use it in a OVSCS Terminal after using nix-env-selector.

@colemickens
Copy link
Author

I suspect this may have to do with how systemd is running/managing the process, since I'm running it as a service. When I run it by hand from the command line, things seem to work as expected.

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

1 participant