This repository was archived by the owner on Mar 21, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 63
WSL: opam local switch environment #287
Copy link
Copy link
Open
Description
If I run code . from a WSL shell, the current environment variables are not inherited in vscode (see here).
If merlin is only installed in the local switch and not in the global switch, it won't be found since PATH won't include the local _opam/bin/. Same for other local binaries.
I could set paths in the workspace settings (.vscode/settings.json) like this:
{
"reason.path.ocamlmerlin": "_opam/bin/ocamlmerlin",
"reason.path.ocamlfind": "_opam/bin/ocamlfind",
"reason.path.ocpindent": "_opam/bin/ocp-indent",
"reason.path.opam": "_opam/bin/opam"
}However if I have code in a workspace foo/bar/ and open vscode in the parent workspace foo/ it would fail unless I adjust the settings there as well (set paths to "bar/_opam/bin/ocamlmerlin" etc.).
If ocamlmerlin is not found, it could run opam env for the current directory to get the fixed PATH that includes the local switch.
Alternatively:
- check the current workspace for a folder
_opam/bin(this would fix the usual local switch per workspace case) - walk up the path of an opened .ml file until the project root and look for
_opam/bin(this would also work for the nested workspace example).
Metadata
Metadata
Assignees
Labels
No labels